-
Notifications
You must be signed in to change notification settings - Fork 6
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
CRS support in GeoJSON #6
Comments
It wasn't a specification at the time, only a proposal. RFC 7946 is the only specification, not a new specification. |
Both in the GeoJSON RFC 7946 and in the GeoSPARQL 1.1 spec on the geoJSON literal the fact that CRS specification is not supported in geoJSON is clearly stated. Also, in my opinion, this fact has become well-known in the community over the years. Since the I propose to resolve this issue either by
@andrea-perego what is your preference? |
Perhaps OGC Features and Geometries JSON could be suggested assuming it becomes an adopted standard |
@nmtoken Thank you for pointing out this initiative. Indeed, that could be also suggested, but in that case, we would also need to provide guidance on how to represent a FG-JSON literal in RDF, basically repeating what is described in #4 for GeoJSON before its adoption in GeoSPARQL - I would like to avoid that. Until that disucssion is resolved, and a resolution included in a furture GeoSPARQL release, all we can do in GeoDCAT-AP is to point to that discussion in the note. |
Resolution: No need to explicitly mention the lack of support for CRS in GeoJSON. |
At the time of the release of GeoDCAT-AP v1.0 (December 2015), GeoJSON provided support to arbitrary coordinate reference systems (see the original specification).
In the new specification (RFC 7946), standardised in the framework of IETF, this is no longer the case, and the only supported coordinate reference system is CRS84 (i.e., WGS84 lon/lat) - see RFC 7946, Section 4.
Because of this, the use of GeoJSON in GeoDCAT-AP might need to be reconsidered - at least by including a caveat, and some guidance on when and how to use it.
The text was updated successfully, but these errors were encountered: