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

Support for GeoJSON as output format for WFS (as part of OGC WFS 3.0) #849

Closed
tfr42 opened this issue Sep 29, 2017 · 5 comments
Closed

Support for GeoJSON as output format for WFS (as part of OGC WFS 3.0) #849

tfr42 opened this issue Sep 29, 2017 · 5 comments
Labels
feature feature ready WFS deegree Web Feature Service

Comments

@tfr42
Copy link
Member

tfr42 commented Sep 29, 2017

WFS shall support GeoJSON as output format.
outputFormat=application/geo+json as specified in RFC 7946, see http://geojson.org for more information.
@tfr42 tfr42 added contributions welcome asking for contribution (time and money sponsor) feature feature funding welcome financial sponsoring wanted (money) WFS deegree Web Feature Service labels Sep 29, 2017
@tfr42 tfr42 added this to the 3.5 milestone Sep 29, 2017
@tfr42
Copy link
Member Author

tfr42 commented Jan 19, 2018 •
edited
Loading

As part of OGC Testbed 14 the work will be continued on the WFS 3.0 spec. WFS3.0: Next Generation OGC RESTful Web service interfaces will accept GeoJSON as a geospatial data interchange format.

This feature will enable GeoJSON as output format. Further enhancements are needed to enable full WFS 3.0 support in deegree Web Feature Service.

References:

@tfr42 tfr42 added the hard label Jan 19, 2018
@tfr42 tfr42 modified the milestones: 3.5, Backlog Apr 7, 2018
@tfr42 tfr42 changed the title Support for GeoJSON as output format for WFS Support for GeoJSON as output format for WFS (as part of OGC WFS 3.0) Apr 8, 2018
@tfr42 tfr42 mentioned this issue Jul 11, 2018
Closed
4 tasks
@nmtoken
Copy link

nmtoken commented Jul 20, 2018

Down the line, for INSPIRE compliant services support, use of WFS 3 with GeoJSON only will be a problem. Because GeoJSON only supports one projection system, which is the equivalent of urn:ogc:def:crs:OGC::CRS84 and INSPIRE mandates ETRS89.

@tfr42 tfr42 mentioned this issue Nov 27, 2018
Closed
@tfr42
Copy link
Member Author

tfr42 commented Mar 12, 2020

In PR #941 is the extension for WFS 2.0 already available. Same implementation will be used in OGC API - Features #911.

@tfr42 tfr42 added in progress and removed contributions welcome asking for contribution (time and money sponsor) funding welcome financial sponsoring wanted (money) hard labels Mar 12, 2020
@tfr42 tfr42 added ready and removed in progress labels Mar 1, 2021
lgoltz added a commit to lat-lon/deegree3 that referenced this issue Jul 29, 2021
@lgoltz
deegree#849 - enhancements for OGC API Features implementation (PR221)
07b9700
lgoltz added a commit to lat-lon/deegree3 that referenced this issue Jul 29, 2021
@lgoltz
deegree#849 - writing of single features (PR285)
69e4982
lgoltz added a commit to lat-lon/deegree3 that referenced this issue Jul 29, 2021
@lgoltz
deegree#849 - Enhance GeoJson writer (deegree#257)
3e681a3
lgoltz added a commit to lat-lon/deegree3 that referenced this issue Jul 29, 2021
@lgoltz
deegree#849 - added method getStorageCrs (PR284)
12ef34e
@tfr42 tfr42 removed this from the Backlog milestone Jun 3, 2022
@tfr42
Copy link
Member Author

tfr42 commented Jun 3, 2022

Support for Json/GeoJson will be available with 3.5 line.

@tfr42
Copy link
Member Author

tfr42 commented Aug 10, 2022

PR #1164 was merged into main for 3.5 line.

@tfr42 tfr42 closed this as completed Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature feature ready WFS deegree Web Feature Service
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nmtoken @tfr42