-
Notifications
You must be signed in to change notification settings - Fork 90
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
Investigate GeoJSON support for non-string property values #627
Comments
I'm open to suggestions. Most of our current views assume tabular data (feature list, feature info) and thus flatting the nested structure might help fit into those. |
jsalankey
added a commit
to jsalankey/opensphere
that referenced
this issue
Jul 10, 2019
…nsphere:fix-warning to master * commit 'd304aba86b4a2de9821bd0cf38c5620cbe7aff0f': chore(query): fixes compile warning
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Normally the properties are simple key:value pairs. However there are cases like:
where that doesn't hold.
https://tools.ietf.org/html/rfc7946 suggests nesting is valid.
The text was updated successfully, but these errors were encountered: