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.

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

Unsufficiently specified format for crs values #59

Closed
rouault opened this issue Mar 5, 2018 · 3 comments
Closed

Unsufficiently specified format for crs values #59

rouault opened this issue Mar 5, 2018 · 3 comments
Assignees
Labels

Comments

@rouault
Copy link
Contributor

rouault commented Mar 5, 2018

From https://raw.githubusercontent.com/opengeospatial/WFS_FES/master/core/openapi/schemas/collectionInfo.yaml , one can guess that the format for crs values is OGC URLs, but would be good to mention it if that's the case. The reference is probably "OGC CRS Name Type Definition" [OGC 11-135] / https://portal.opengeospatial.org/files/?artifact_id=46361

@cportele
Copy link
Member

cportele commented Mar 6, 2018

So far, crs is mainly a placeholder for future use in extensions (there is also a note in the text) as the Core is restricted to WGS84 lon/lat. This is the reason why this is not discussed in more detail as there are currently no requirements related to CRSs. But I guess it can be confusing as it is. Either drop it from the Core and only add it in extensions or provide more guidance.

@aaime
Copy link
Contributor

aaime commented Mar 7, 2018

The specification could use a prominent statement (a dedicated section maybe?) that everything must be in CRS84 though. The only statement I could find is in Example 3, there it's easily overlooked imho: "Coordinate reference system information is not provided as the service provides geometries only in the default system (WGS84 longitude/latitude)."

@cportele
Copy link
Member

cportele commented Mar 7, 2018

@aaime You are right, I thought we had a normative statement about this somewhere, but obviously not. This needs to be fixed.

@cportele cportele self-assigned this Mar 7, 2018
@cportele cportele added bug Part 1: Core Issue related to Part 1 - Core labels Mar 7, 2018
@cportele cportele added this to the Part 1, First Draft Release milestone Mar 8, 2018
cportele added a commit that referenced this issue Mar 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

3 participants