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

Question about coordRefSys and compound-CRS #102

Closed
jratike80 opened this issue Oct 19, 2023 · 5 comments
Closed

Question about coordRefSys and compound-CRS #102

jratike80 opened this issue Oct 19, 2023 · 5 comments
Labels
question Further information is requested

Comments

@jratike80
Copy link

I am not sure if this is the right repository to ask, but is it possible to define in coordRefSys a compound CRS that does not have an EPSG code? I speak only about Spatial compound coordinate reference systems (vertical + height) without complexity of time.

For example ETRS89 / TM35FIN(N,E) + N2000 height has a code EPSG:3903
but a similar ETRS89 / TM35FIN(E,N) + N2000 height does not have a code.
The Proj library recognizes compound CRS from concatenated codes, as for the latter example
EPSG:3067+3900

The standard https://docs.ogc.org/as/18-005r4/18-005r4.html#36 supports compound crs.

The discussion about crs-compound in opengeospatial/architecture-dwg#29 may be related.

The question in this issue is related opengeospatial/ogcapi-features#357

@cportele
Copy link
Member

Compounds CRSs where each component CRS has a URI can be specified.

Example using CURIEs: "coordRefSys": ["[EPSG:3067]", "[EPSG:3900]"].

See https://docs.ogc.org/DRAFTS/21-045.html#_reference_system_values.

@cportele cportele added the question Further information is requested label Oct 19, 2023
@jratike80
Copy link
Author

How about OGCFeat? Is it possible to announce EPSG:3067+3900 as a storageCrs? What would be the syntax if plain EPSG:3067 is expressed as
"storageCrs" : "http://www.opengis.net/def/crs/EPSG/0/3067"?

@cportele
Copy link
Member

No, that is currently not possible and requires an update to Features Part 2. In hindsight, we should have supported such a capability already in v1.0.

@jratike80
Copy link
Author

jratike80 commented Oct 19, 2023

Would you mind creating an enhancement issue for Part 2? I am not lazy but I feel that you know better what to write into the description.

@cportele
Copy link
Member

Done, see opengeospatial/ogcapi-features#864. I am closing the issue here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants