Skip to content

[ogcapi-records] bbox is put on map in original crs, no transformation to 4326 #1058

Open
@pvgenuchten

Description

@pvgenuchten

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

image

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions