WCS 2.0.1 can build BoundedBy with wrong axis order

Description

With some projected coordinate systems Geoserver creates BoundedBy elements of the DescribeCoverage by using a wrong axis order. For example the nurc__Pk50095 demo coverage:

http://localhost:8080/geoserver/ows?service=WCS&version=2.0.1&request=describecoverage&coverageid=nurc__Pk50095

I made a test also with EPSG:3067 which is a UTM projection with E-N axis order:

In both cases first coordinates are northings even they should be eastings.

Environment

None

Status

Assignee

Andrea Aime

Reporter

Jukka Rahkonen

Triage

None

Fix versions

Affects versions

2.7.2

Components

Priority

Medium
Configure