New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing POINT type (feature request) #1583
Comments
Hi @Apidcloud, thanks for opening the issue 🚀 , the milestone for Memgraph 2.14 contains the tasks to add geospatial datatype support. This is a subset of that issue. It may end up in 2.14. |
Ah, awesome! |
Quick update, the geospatial capabilities are not planned for v2.14 (the milestone was not up to date), sorry! It's not known where geospatil datatypes will be released at the moment... @Apidcloud I'm happy to jump on a call and figure out if there is a short term alternative 🤔 CC @antejavor |
Hi @Apidcloud, have you been able to avoid this blocker and push the project further to be compatible with Memgraph? |
Hey @antejavor Unfortunately no. There's a few (at least 1 big) other blockers that come to mind; the high availability from the cloud hosted solution is one example. |
Hi @Apidcloud, I'm sorry to hear that. Could you tell us about the other blockers you encountered? We'd appreciate any feedback you have to help improve our product. |
This is not a bug, but more of a feature request (and a blocker for me) to be further compatible with Neo4j. We rely on using the POINT type to save lists of locations inside a single node.
The use case is that the same place (think of a city or even the same street) can have multiple more fine/specific locations (latitude, longitude, height/altitude).
We can then use point.distance to check if said locations are within a certain radius (i.e., nearby). More info at https://neo4j.com/docs/cypher-manual/current/functions/spatial/ .
Let me know if you would need more details.
The text was updated successfully, but these errors were encountered: