We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be great to be able to have ExtraMember concept for a GeoJSON feature. This is also in line with the GeoJSON specification https://www.rfc-editor.org/rfc/rfc7946#section-5.
ExtraMember
The text was updated successfully, but these errors were encountered:
Is "Foreign/extra members in a feature collection" not what you need?
https://github.com/paulmach/orb/tree/master/geojson#foreignextra-members-in-a-feature-collection
Sorry, something went wrong.
Thanks for the quick response. I meant at the Feature level so I could end up with a GeoJSON like this (note the new key myNewFeature):
Feature
myNewFeature
{ "type": "FeatureCollection", "generator": "myapp", "timestamp": "2020-06-15T01:02:03Z", "features": [ { "type": "Feature", "myNewFeature": "blah", "geometry": {"type": "Point", "coordinates": [102.0, 0.5]}, "properties": {"prop0": "value0"} } ] }
No branches or pull requests
It would be great to be able to have
ExtraMember
concept for a GeoJSON feature. This is also in line with the GeoJSON specification https://www.rfc-editor.org/rfc/rfc7946#section-5.The text was updated successfully, but these errors were encountered: