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

[REQUEST] Introduce Coordinate Types #197

Open
zprobst opened this issue Jan 3, 2024 · 0 comments
Open

[REQUEST] Introduce Coordinate Types #197

zprobst opened this issue Jan 3, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@zprobst
Copy link
Contributor

zprobst commented Jan 3, 2024

Is your feature request related to a problem? Please describe.

Graph Databases are often paired with GeoSpacial data. It would be nice to support the creation of and storage of coordinate types in the native form for the graph database in question. This requires some design because right now we do not give an opportunity for the database connector to be part of the property creation phase. How does that work? Do they? Do we just create the coordinate and give the connector the space to map that to the database however they think is best?

We will also have to add a coordinate schema type(s).

Describe the solution you'd like
I think it would be ideal if nodestream exposed a !coordinate Value Provider that worked like this:

# x, y (z) coordinates 

- type: properties
   properties:
       coordinates: !coordinate 
          x: !jmespath location.coordinate.x
          y: !jmespath location.coordinate.y
          z: !jmespath location.coordinate.z
# lat, long, h coordinates (WGS84)

- type: properties
   properties:
       coordinates: !coordinate 
          latitude: !jmespath location.coordinate.lat
          longitude: !jmespath location.coordinate.long
          height: !jmespath location.coordinate.height
# geojson encoding https://geojson.org/

- type: properties
   properties:
       coordinates: !coordinate 
          geojson: !jmespath location.coordinate

Describe alternatives you've considered
The best you have the option to do now is map three properties for x,y,z which limits what can be done natively in the graph.

@zprobst zprobst added the enhancement New feature or request label Jan 3, 2024
@zprobst zprobst self-assigned this Jan 3, 2024
@zprobst zprobst added this to the Before 1.0.X milestone Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Ready
Development

No branches or pull requests

1 participant