- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi BT_KBS,
Please go through the below steps, I hope it will help to solve your issue.
Current State of Geospatial Support in Neptune
Neptune provides strong support for graph models and queries using both SPARQL and Gremlin, but geospatial functionality is limited. While Gremlin in Neptune supports basic geospatial queries (such as finding points within a circle or bounding box), these capabilities are not mirrored in SPARQL.
Workarounds and Alternatives
Given this limitation, there are several approaches you might consider:
External Geospatial Processing:
- Preprocess Data: You can perform geospatial calculations externally using tools like PostGIS or a custom service, and then store the processed results (e.g., distances or spatial relationships) within Neptune as part of the graph data.
- Hybrid Architectures: Utilize AWS services like Lambda or Amazon Aurora (with PostGIS) to handle geospatial queries and integrate the results back into your Neptune database.
Using Gremlin for Geospatial Queries:
-
If your use case permits, you might consider using Gremlin instead of SPARQL for queries requiring geospatial functionality. Neptune supports Gremlin geospatial predicates such as within, contains, and intersects for basic geospatial operations.
-
Documentation: For more information on Gremlin's geospatial support in Neptune, you can refer to the Amazon Neptune Gremlin Reference.
Future Prospects:
- Feature Requests: AWS regularly updates its services based on customer feedback. While there are no official announcements about SPARQL geospatial support in Neptune, you can express your interest through AWS support channels, which could influence the development roadmap.
Documentation links:
https://docs.aws.amazon.com/neptune/latest/userguide/intro.html
Contenus pertinents
- demandé il y a 2 ans
- demandé il y a un an
- demandé il y a 2 ans
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a 4 ans
- AWS OFFICIELA mis à jour il y a 10 mois