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
Is this problematic in ogcapi-records only? would it be good to reproject the bounds to wgs84 at metadata import? Does for example spatial filters in CSW consider the projection of the bounds?
If reprojection is relevant, how do we manage the case where the projection info is unparseable?
The text was updated successfully, but these errors were encountered:
Description
An example record which has bounds in a non-wgs84 projection (also attached)
The record is imported without problems, including the crs definition, which is a bid awkward ('EPSG:32736 - WGS')
But when displaying this record on a map, the bbox is applied as if it is in wgs84, which results in a bbox from here to the sun and back
0083642f-36bd-465f-8e32-3859649ad9b4.zip
Is this problematic in ogcapi-records only? would it be good to reproject the bounds to wgs84 at metadata import? Does for example spatial filters in CSW consider the projection of the bounds?
If reprojection is relevant, how do we manage the case where the projection info is unparseable?
The text was updated successfully, but these errors were encountered: