You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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: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.
The text was updated successfully, but these errors were encountered: