Christopher, thanks for the pointers! Yes, I am mainly thinking that the only stuff required to include "simple" spatial work into the Lucene index implementation is to pull in the SpatialHepler equivalent, which adds the "lon", "lat" and the CartesianPlotterField to the document (node, relationship, etc) being indexed. This should not break anything, and add a very simple way to get spatial functionality. I am thinking of the popularity of the MongoDB spatial extension. Not much functionality, but very easy accessible as part of a "normal" index operation. Question is what the API should look like in order not to add too much.
I think this is so small that the help could be added to the existing index components (when someone has a bit of time :) WDYT? 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://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Sun, Nov 14, 2010 at 12:42 AM, Christopher Schmidt <fakod...@googlemail.com> wrote: > Hi, > > I think Lucene provides a simple way to do distance queries. > The limit is, that you can use only points (and a circle to define a > distance). No interception with lines, polylines or stuff like that is > possible. If you do not need it - fine... > > BTW: > There is currently a discussion about changing lucenes spatial > implementation. See > http://www.mail-archive.com/d...@lucene.apache.org/msg03593.html and > http://www.mail-archive.com/d...@lucene.apache.org/msg09654.html. Mainly due > to the sinusoidal projection. > > (and if you are interested, I did Mikes spatial example with Lucene 3.0.2 > and in Scala > http://blog.fakod.eu/2010/11/02/spatial-lucene-example-in-scala/) > > -- > Christopher > twitter: @fakod > blog: http://blog.fakod.eu > > On Sat, Nov 13, 2010 at 11:05 PM, Peter Neubauer < > peter.neuba...@neotechnology.com> wrote: > >> Hi there, >> I just tried the examples for searching spatial with Lucene at >> http://develop.nydi.ch/2010/10/lucene-spatial-example/ >> >> I am wondering if this still fits into the current Lucene framework >> integration, so we could add spatial indexing for simple Nodes with >> lat/lon properties into the existing index component, or simply have >> another (spatial) index backed by neo4j-lucene-index and exposed >> through the index framework? This is not on the level of Neo4j >> Spatial, but it would give a simple geo-lookup boundary for nodes or >> relationships. Is the support for adding the required Lucene spatial >> document fields already exposed so this could be added without bigger >> modifications to existing code? >> >> WDYT? >> >> 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://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. >> _______________________________________________ >> 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 > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
