Daniel, the OSM import is loaded into its own layer corresponding to the dataset file name as a default I think (there should be a layer node created fro it, much in the same way as for the 'geom' index. So, if you load that layer the same way as an index provider as you did with the 'geom' index, you should be able to do just that.
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 - NOSQL for the Enterprise. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. On Thu, Nov 24, 2011 at 1:52 PM, danielb <danielbercht...@gmail.com> wrote: > Hi Peter, > > I now have a graph with the 'geom' index + testnode from the above code and > imported some OSM data afterwards. I now want to find 2 nodes by bbox query > - 550349 and 205372 (see http://dl.dropbox.com/u/18693700/graph.png). How > can I achieve this? If I query for the bbox I should at least find the > corresponding GEOM nodes and then traverse over the incoming edge? > > I can for example do the following: > cypher> start n=node:node(way_osm_id = '119810554') > cypher> return n > cypher> > ==> > +--------------------------------------------------------------------------------------------------------------------------------------+ > ==> | n > | > ==> > +--------------------------------------------------------------------------------------------------------------------------------------+ > ==> | > Node[550349]{way_osm_id->119810554,oneway->"BOTH",timestamp->1309673329000,highway->"residential",name->"Frauenstraße",version->"2"} > | > ==> > +--------------------------------------------------------------------------------------------------------------------------------------+ > ==> 1 rows, 168 ms > > In the posts before I could query the geometry with index 'geom'. The index > manager only has the following entries: > > node lucene {"_blueprints:type":"MANUAL", "type":"exact"} > relation lucene {"_blueprints:type":"MANUAL", "type":"exact"} > geom spatial {"_blueprints:type":"MANUAL"} > way lucene {"_blueprints:type":"MANUAL", "type":"exact"} > changeset lucene {"_blueprints:type":"MANUAL", "type":"exact"} > user lucene {"_blueprints:type":"MANUAL", "type":"exact"} > > I also have uploaded the complete folder of Neo4j spatial + graph.db: > http://dl.dropbox.com/u/18693700/neo4j_spatial_osm_graphdb.rar > > Regards, Daniel > > > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-Spatial-build-run-problems-tp3515519p3533548.html > Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. > _______________________________________________ > 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
