Craig, great work! Tobias helped me to refactor the BerkeleyDB index to work with the latest Indexing changes, so we should be able to upgrade even that part to Neo4j 1.3.M03 next week and test. Together, we might be able to get a better grip on insert performance, which is the main annoying thing before starting to test on bigger OSM datasets.
Great job, David and Craig! Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Thu, Feb 24, 2011 at 12:12 AM, Craig Taverner <cr...@amanzi.com> wrote: > Hi, > > I just merged in David Winslows CQL support into Neo4j Spatial. Basically it > is an alternative to the JSON based DynamicLayers we provided for OSM. The > main advantages of CQL are: > > - Works on the Geometries themselves, using the very extensive CQL > syntax, an SQL-like syntax for querying geometries and their attributes > - Works on more data than just OSM, so any layer that extends > DynamicLayer has easy and direct support > - It is a known standard, well supported in geotools, geoserver and udig > (see http://docs.codehaus.org/display/GEOTOOLS/ECQL+Parser+Design, and > http://www.loc.gov/standards/sru/specs/cql.html) > > The original JSON format is still supported, and it has its own advantages: > > - Is a graph-matching syntax, and so can query non-spatial data (any > sub-graph in your data model) > - Should be faster than CQL because the geometries do not need to be > created, only a traversal done > > I pushed this to github along with a few other changes I was working on, > notably initial support for changesets and users in the OSM model. This > change also reduces the disk space of the database, and should also > facilitate some of the performance enhancements Peter and I are working on > for OSM import and query. > > The full set of commits I, copied from the hudson server are: > > 1. Started supporting more efficient changeset and user structures for > OSM > (detail<http://buildbox.neo4j.org/hudson/job/spatial/246/changes#detail0> > ) > 2. Initial code for cool NEO4J text sample data in unit tests > (detail<http://buildbox.neo4j.org/hudson/job/spatial/246/changes#detail1> > ) > 3. Added new test class for testing performance of OSM imports as we > refactor the OSM structures > (detail<http://buildbox.neo4j.org/hudson/job/spatial/246/changes#detail2> > ) > 4. Update version to match Peters changes to the dependencies > (detail<http://buildbox.neo4j.org/hudson/job/spatial/246/changes#detail3> > ) > 5. Updated the very old README to be somewhat more relevant to the > current code. > (detail<http://buildbox.neo4j.org/hudson/job/spatial/246/changes#detail4> > ) > 6. Missing license header on new test class TestOSMImport > (detail<http://buildbox.neo4j.org/hudson/job/spatial/246/changes#detail5> > ) > 7. Reverse some of the memory settings that are too large, and support > optional large memory settings > (detail<http://buildbox.neo4j.org/hudson/job/spatial/246/changes#detail6> > ) > 8. Reduce memory settings for tests to more normal levels > (detail<http://buildbox.neo4j.org/hudson/job/spatial/246/changes#detail7> > ) > 9. Some refinements to the ongoing OSM changeset support > (detail<http://buildbox.neo4j.org/hudson/job/spatial/246/changes#detail8> > ) > 10. Manually merged in David Winslows CQL support so that we can support > both JSON and CQL based filtering for Dynamic Layers. The CQL support is now > also directly in the DynamicLayer class because it should work for non-OSM > layers as well as OSM layers. CQL allows much more complex filtering on the > Geometry objects themselves, while the previous JSON filter was really a > graph-matching query de-coupled from the Geometries. > (detail<http://buildbox.neo4j.org/hudson/job/spatial/246/changes#detail9> > ) > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
