You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It currently is like that since the only CRS supported by the Core is WGS84 lon/lat. But of course whatever we specify in the Core must be compatible with extensions that support other CRSs. If we want to make it work in general beyond WGS84 lon/lat we need to remove maxItems: 4 and the minimum/maximum - and clarify how to specify the CRS.
+1 for generalizing the BBOX to support other CRSes that CRS84, but defaulting to CRS84. I would also like to see placeholder to giving the crs ID as an optional parameter, even if the Core services are not required to support it
I removed the minimum/maximum values and changed maxItems to 6 to prepare for other CRSs. bbox-crs has been reserved for a parameter in the CRS extension to specify a different CRS for the BBOX values (I have made it a separate parameter so that bbox can still be an array of numbers).
https://raw.githubusercontent.com/opengeospatial/WFS_FES/master/core/openapi/parameters/bbox.yaml defines -180/180 as the min/max for bbox values. That won't work for default CRS that aren't geodetic ones.
The text was updated successfully, but these errors were encountered: