Is your feature request related to a problem? Please describe.
the long syntax of crs is not widely known, when used, pygeoapi returns an error
https://demo.pygeoapi.io/master/collections/dutch_castles/items?crs=EPSG:28992
vs
https://demo.pygeoapi.io/master/collections/dutch_castles/items?crs=http://www.opengis.net/def/crs/EPSG/0/28992
Describe the solution you'd like
Suggestion would be to allow abbreviated epsg:28992 codes to indicate a crs, when requesting items in a crs
Additional context
Or maybe not:
- people may expect short crs codes to work on any ogcapi:features
- usage of epsg:4326 sometimes expects altered axisorder
Is your feature request related to a problem? Please describe.
the long syntax of crs is not widely known, when used, pygeoapi returns an error
https://demo.pygeoapi.io/master/collections/dutch_castles/items?crs=EPSG:28992
vs
https://demo.pygeoapi.io/master/collections/dutch_castles/items?crs=http://www.opengis.net/def/crs/EPSG/0/28992
Describe the solution you'd like
Suggestion would be to allow abbreviated epsg:28992 codes to indicate a crs, when requesting items in a crs
Additional context
Or maybe not: