GridCoverage Rendering's equality check on CRSs is not recognizing equal ProjectedCRS.
Description
There are some cases where GridCoverageRenderer machinery is actually not recognizing that requested mapEnvelope’s CRS and reader’s CRS are actually the same.
This may happen when the requested mapEnvelope is a ProjectedCRS and the reader’s CRS is the same ProjectedCRS but with the underlying BaseCRS having the axis defined in the switched order, although their Projection Axes are actually the same.
Handling them as different CRSs, will basically result on triggering the reprojection machinery between source and target CRS, which includes extra read, padding, additional scaling operations, and reprojection’s related additional steps.
There are some cases where GridCoverageRenderer machinery is actually not recognizing that requested mapEnvelope’s CRS and reader’s CRS are actually the same.
This may happen when the requested mapEnvelope is a ProjectedCRS and the reader’s CRS is the same ProjectedCRS but with the underlying BaseCRS having the axis defined in the switched order, although their Projection Axes are actually the same.
Handling them as different CRSs, will basically result on triggering the reprojection machinery between source and target CRS, which includes extra read, padding, additional scaling operations, and reprojection’s related additional steps.