Skip to content

Unsufficiently specified format for crs values #59

Closed

Description

@rouault

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

Activity

  1. cportele commented on Mar 6, 2018

    @cportele
    Member

    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.

  2. aaime commented on Mar 7, 2018

    @aaime
    Contributor

    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)."

  3. cportele commented on Mar 7, 2018

    @cportele
    Member

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

  4. self-assigned this
    on Mar 7, 2018
  5. added a commit that references this issue on Mar 7, 2018
    d36a63c
  6. added a commit that references this issue on Mar 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions