Very cool. Maybe you could just doc the parameters more than pointing to the Oracle reference, so one can see it directly in the JavaDoc?
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, Jun 2, 2011 at 2:13 PM, Craig Taverner <[email protected]> wrote: > Hi, > > Recently someone asked a question on StackOverflow, if Neo4j Spatial was > capable of one of the Oracle geoprocessing funtions, SDO_LRS.LOCATE_PT > specifically. Since this is related to the ongoing GSoC projects for Neo4j > Spatial, I thought I would do a quick investigation. What I found was that > the requested capabilities are available in JTS (which we include in Neo4j > Spatial), but with very different names. The code to achieve this in JTS is > 'new LengthIndexedLine(geometry).extractPoint(measure,offset)'. I have > wrapped these in the > SpatialTopologyUtils.locatePoint(geometry,measure,offset), so that it is > accessible together with some other spatial topology functions, and also > looks more like the Oracle function. > > I pushed this to github, and think it can be included as a prototype for > the > discussions for the GSoC on Geoprocessing. > > Regards, Craig > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
