[go: up one dir, main page]

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

Questions about Neo4j Spatial: Layer and Indexing Concerns #393

Open
GAISLBS opened this issue Aug 24, 2023 · 0 comments
Open

Questions about Neo4j Spatial: Layer and Indexing Concerns #393

GAISLBS opened this issue Aug 24, 2023 · 0 comments

Comments

@GAISLBS
Copy link
GAISLBS commented Aug 24, 2023

Hello,

I have been using Neo4j Spatial and I've come across a few questions:

  1. Limitations concerning layers and spatial operations: I understand that to process spatial data in Neo4j Spatial, we need to create a layer and store the data there. However, when executing operations, I'm wondering if it performs operations against all spatial objects in the layer, or if we can selectively operate on specific or a subset of objects. For instance, consider the following query:
WITH "POLYGON((15.3 60.2, 15.3 60.4, 15.7 60.4, 15.7 60.2, 15.3 60.2))" as polygon
CALL spatial.intersects('layer_roads',polygon) YIELD node RETURN node.name as name

In this case, does it perform operations against all objects in the 'layer_roads' layer, or can we operate only on certain objects that meet specific conditions?

  1. Layer and Indexing: When a layer is created and data is added, is spatial indexing automatically generated for each addition, or is there a separate process required?

  2. Practicality and efficiency issues: Practically using Neo4j Spatial, it seems time-consuming to perform operations with all spatial objects in a single layer. Therefore, I thought of storing spatial data as regular properties of Neo4j nodes or relationships and then, when needed, create a Spatial layer for the operations. However, if indexing needs to be recreated for each layer, this seems inefficient. How can this issue be addressed? Or is there a more efficient method?

I look forward to receiving feedback on these concerns and hope to use Neo4j Spatial more effectively. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant