-
Notifications
You must be signed in to change notification settings - Fork 265
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
GeoJSON Feature support #4114
Comments
FeaturesCollection type should be also supported:
|
PR #4116 |
This was referenced May 18, 2022
Extra PR #4126, changing the retrieval logic, based in internal discussions. |
Extra PR #4129 to support ignoreType in the new geo:json types |
Extra PR #4139 fixing some ignoreType support gaps |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem / use case? Please describe.
Orion doesn't support valid GeoJSON as this one (can be checked here:
given that is a
Feature
and MongoDB doesn't support that type and a 500 Internal Error response results in that case.Describe the solution you'd like
The structure of the
Feature
GeoJSON is fixed, so it would be easy for Orion to move directly thegeometry
field to thelocation
fiedl in the DB where the geo index is builtDescribe alternatives you've considered
User can use
ignoreType
metadata to support that case, but the geo-location of the entity will be lost (i.e. a query query covering will not work).Describe why you need this feature
Do you have the intention to implement the solution
The text was updated successfully, but these errors were encountered: