ReferencedEnvelope CRS compatibility check is not recognizing equivalent ProjectedCRS. (identity transformation between source and target CRS)

Description

As a consequence of https://osgeo-org.atlassian.net/browse/GEOT-7510 there are pieces of code in rendering that may attempt to intersect envelopes having same ProjectedCRS (i.e. 3857) where the only difference is on the underlying definition of the BaseCRS ‘s axes order although the Transformation between the 2 CRS is the identity.

Let’s update the CRS compatibilities check method in ReferencedEnvelope by falling back on the identity transformation check when the initial CRS.equalsIgnoreMetadata fails

Environment

None

Activity

Andrea Aime 
August 17, 2024 at 2:42 PM

I’ve marked it as resolved for 32-RC, was it backported too?

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created July 25, 2024 at 2:52 PM
Updated August 17, 2024 at 2:42 PM
Resolved August 17, 2024 at 2:41 PM