ehx-v1

All I know is that INTERSECTS and similar queries are there, see the manual linked in the readme. No idea about LINE_LOCATE_POINT, X or Y though...

I made a screenshot of the related part in the manual: 

You can also launch the JTS queries via Cypher, and access Cypher via REST, as shown in these screenshots:  

In Java API most probably yes, because from all I know the procedures do exactly what the Java API does.

This problem is documented in the Javadoc: The `numItemsToFind` parameter is used to calculate an Envelope based on the overall average layer density, so it's normal that this version returns...

So it's a known inconvenience, and none anyone is likely to do anything about (it's a downside of the implementation that made most sense), one just has to deal with...

I'm not quite into Neo4j Spatial yet but all around the other issues the first answer I see is "can you give a failing test?" so just a hint, you'd...

the manual linked is all about REST, I'd think that's enough? ah, getting it... this was issued before the manual was there, right?

At the time when this issue was started, the entire manual at http://neo4j-contrib.github.io/spatial was all about REST. By now, things changed though - I encountered the same situation as you...

Either way, someone with more in-depth access to neo4j-contrib.github.io should have a look at what is happening, because it's definitely an inconsistency. If the REST API really isn't supposed to...