Skip to content
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

Open
Apidcloud opened this issue Dec 13, 2023 · 6 comments
Open

Missing POINT type (feature request) #1583

Apidcloud opened this issue Dec 13, 2023 · 6 comments
Labels
community community Effort - Medium Effort - Medium Frequency - EveryTime Frequency - EveryTime geospatial Priority - Later Priority - Later Reach - Some Reach - Some Severity - S2 Severity - S2

Comments

@Apidcloud
Copy link

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.

@Apidcloud Apidcloud added the bug bug label Dec 13, 2023
@antejavor antejavor added Importance - I3 Importance - I3 community community Effort - Unknown Effort - Unknown Severity - S2 Severity - S2 and removed bug bug labels Dec 13, 2023
@antejavor
Copy link
Contributor

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.

@Apidcloud
Copy link
Author

Ah, awesome!

@gitbuda
Copy link
Member

gitbuda commented Dec 14, 2023

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

@DavIvek DavIvek added Effort - Medium Effort - Medium and removed Effort - Unknown Effort - Unknown labels Dec 18, 2023
@hal-eisen-MG hal-eisen-MG added Priority - Later Priority - Later and removed Priority - Later Priority - Later labels Feb 4, 2024
@hal-eisen-MG hal-eisen-MG added Priority - Later Priority - Later and removed Priority - Later Priority - Later labels Feb 11, 2024
@hal-eisen-MG hal-eisen-MG added Priority - Later Priority - Later and removed Priority - Later Priority - Later labels Feb 22, 2024
@katarinasupe katarinasupe added Frequency - Monthly Frequency - Monthly Reach - Some Reach - Some Frequency - EveryTime Frequency - EveryTime and removed Importance - I3 Importance - I3 Frequency - Monthly Frequency - Monthly labels Feb 26, 2024
@antejavor
Copy link
Contributor

Hi @Apidcloud, have you been able to avoid this blocker and push the project further to be compatible with Memgraph?

@Apidcloud
Copy link
Author

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.

@matea16
Copy link

matea16 commented Mar 14, 2024

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.
If it would be easier, we can always jump on a quick call

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community community Effort - Medium Effort - Medium Frequency - EveryTime Frequency - EveryTime geospatial Priority - Later Priority - Later Reach - Some Reach - Some Severity - S2 Severity - S2
Projects
Development

No branches or pull requests

7 participants