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
RFC7946 states that Feature.id can be String or Number. Currently GeoJSON-Jackson forces the id to be a String.
Is there a specific reason for this?
The text was updated successfully, but these errors were encountered:
This library is based on the original 2008 GeoJson specification. At this point no specific type was defined for id properties. (https://geojson.org/geojson-spec.html#feature-objects)
Sorry, something went wrong.
That sounds like even more of a reason to not limit it to only String :)
No branches or pull requests
RFC7946 states that Feature.id can be String or Number. Currently GeoJSON-Jackson forces the id to be a String.
Is there a specific reason for this?
The text was updated successfully, but these errors were encountered: