<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi, Imran.<br>
<br>
Yes, I think so. It depends on including GNM into GDAL. The python
binding using swig, so adding the java will be simple.<br>
<pre class="moz-signature" cols="72">Best regards,
Dmitry</pre>
09.09.2014 19:41, Imran Rajjad пишет:<br>
</div>
<blockquote
cite="mid:CADz3VuXMjwH-b89RJ0Z4BQKoxX-DE669b_MVHZ4wiG_HaBYADA@mail.gmail.com"
type="cite">
<p>Will this be available for java bindings too?</p>
<div class="gmail_quote">On Sep 9, 2014 12:53 AM, "Even Rouault"
<<a moz-do-not-send="true"
href="mailto:even.rouault@spatialys.com">even.rouault@spatialys.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> - gnm/frmts/gnm_frmts.h : I'm a bit concerned about
exposing (installed<br>
><br>
> > header + CPL_DLL) an interface that has not yet been
implemented. My<br>
> > intuition<br>
> > is that it might change once the first one or two
implementations have<br>
> > been made. So maybe keep it internal/experimental
for now.<br>
><br>
> I agree that the inclusion of the interfaces/capabilities
that can be (not<br>
> will be) extended in future is not a 100% good idea. I
hoped that someone<br>
> will be interested or even I will have time to implement
and extend<br>
> something of what I wrote at the "Future ideas" section
in my RFC. But we<br>
> do not know exactly will it be implemented or not. So:
(1) We can remove<br>
> for now all these interfaces "for future", which means to
leave only<br>
> GNMGdalNetwork and one analysing class. (2) Try to
implement these<br>
> capabilities: pgRouting for gnm_frmts.h and for example<br>
> GNMGdalStdRoutingAnalyser with some algorithm extension
(K shortest path).<br>
<br>
It's your call. Depend on how much time you have to implement
that, but we<br>
might go with the current state, if we clearly mark
experimental/unstabilized<br>
interfaces as such. Either by "hiding" them, or by
documentation if not<br>
possible.<br>
<br>
> - GNMManager::CreateConnectivity () : I'm confused by the
'native' term. In<br>
><br>
> > this method, native=false seems to imply the GDAL
"proprietary" network<br>
> > format<br>
> > that can work with any vector driver that has
similar capabilities than<br>
> > shapefile. Whereas in the RFC text, it seems to
imply the contrary (<br>
> > "network<br>
> > of ”GDAL-native” format").<br>
><br>
> Maybe I used it not correctly everywhere, but the general
idea is the<br>
> following: The term "native" corresponds to the existed
network formats (so<br>
> when we work with pgRouting network we work with its
native tables and<br>
> fields, rather than with GNMGdal- system layers), while
the GDAL-networks<br>
> are not "native" and more likely "common".<br>
><br>
<br>
Yes, that would be good if the language could be consistent
among the code and<br>
the RFC text. From your explanation, it seems that the text in
the RFC should<br>
be corrected. Yes GDAL-network is more a "common" or "generic"
network<br>
implementation.<br>
<br>
--<br>
Spatialys - Geospatial professional services<br>
<a moz-do-not-send="true" href="http://www.spatialys.com"
target="_blank">http://www.spatialys.com</a><br>
_______________________________________________<br>
gdal-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/gdal-dev"
target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a></blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gdal-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/gdal-dev">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a></pre>
</blockquote>
<br>
</body>
</html>