Super progress Davide, almost sounds like you've completed the gsoc requirements :-)<div><br></div><div>I'm getting places with the open street map importer, and that is data that is ideal for routing analysis, because the graph structure includes all topology information and distances of every edge. But it would be ideal to not have to rely on OSM structures for routing, but apply it to the JTS geometries also. Let's chat more about that so we find a general solution.<br>
<br><div class="gmail_quote">On Tue, Jun 8, 2010 at 12:32 AM, Davide <span dir="ltr"><<a href="mailto:davide.savazzi@gmail.com">davide.savazzi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
1) What did I do last week<br>
<br>
- cleaned / optimized the Neo4j Catalog plugin<br>
- written a proxy DataStore to log how uDig uses the Query support<br>
- implemented Query support for uDig basic operations (pan, zoom,<br>
info, box selection) using neo4j-spatial rtree index.<br>
- implemented Attribute support (to display Features metadata)<br>
<br>
2) What do I plan to do this week<br>
<br>
Now that support for simple feature layers is usable, I think it's<br>
time to begin experimenting with a networking / routing plugin.<br>
I plan to implement the routing plugin described in the training<br>
material using neo4j-spatial (instead of geotools graph module).<br>
<br>
Regards,<br>
<font color="#888888">--<br>
Davide Savazzi<br>
_______________________________________________<br>
SoC mailing list<br>
<a href="mailto:SoC@lists.osgeo.org">SoC@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/soc" target="_blank">http://lists.osgeo.org/mailman/listinfo/soc</a><br>
</font></blockquote></div><br></div>