Introduces a default geometry layer which can be indexed and queried & 0.4.0 release#3
Open
mukil wants to merge 11 commits intojri:masterfrom
Open
Introduces a default geometry layer which can be indexed and queried & 0.4.0 release#3mukil wants to merge 11 commits intojri:masterfrom
mukil wants to merge 11 commits intojri:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Extended the dm4-geospatial service about the functionality to query a specific property value of a given Feature within a Geometry by providing the property key and a single geo coordinate.
At the moment only one shapefile can be indexed at a time. Subsequent imports simply overwrite any existing default geometry layer. To be indexed, the shapefile must reside on sever side, e.g. the deepamehta filepreo.
Note: The shapefile you want to import as the default geometry layer must not contain "NULL" property values to be indexed sucessfully (see neo4j-spatial documentation on that)