Skip to content
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.

Sign up for GitHub

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

Jump to bottom

GeoJSON second proposal (continuing work with ET-AT) #90

Closed
petersilva opened this issue May 10, 2022 · 3 comments
Closed

GeoJSON second proposal (continuing work with ET-AT) #90

petersilva opened this issue May 10, 2022 · 3 comments
Assignees
@josusky

Comments

@petersilva
Copy link
Contributor

@josusky can you produce an updated spec and examples based on latest discussions?

background:
#78
@petersilva petersilva changed the title GeoJSON second proposal (continuation of #78 ) GeoJSON second proposal (continuing work with ET-AT) May 10, 2022
@petersilva petersilva mentioned this issue May 10, 2022
Closed
@antje-s
Copy link
Contributor

antje-s commented May 13, 2022

Currently I wonder if we could put "links" under "properties". Then we are closer to the geoJSON standard (https://geojson.org/) . or are there reasons against it?

@petersilva
Copy link
Contributor Author

@antje-s have a look at #86 :

interop is the rationale.

@josusky josusky mentioned this issue May 26, 2022
Closed
@josusky josusky mentioned this issue Jul 11, 2022
Merged
josusky added a commit that referenced this issue Jul 11, 2022
@josusky
Make integrity optional #90
c36e7c7 
Plus some minor editorial changes.
@petersilva
Copy link
Contributor Author

closing, as ET-AT now has their own propoal. deferring:

https://github.com/wmo-im/wis2-notification-message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@josusky josusky

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@petersilva @josusky @antje-s