WCS 2.0 subsetting may return smaller images than expected by the standard

Description

This happens over sparse image mosaics that are not fully covering their bounding box.
By specification, the returned area must be the intersection between the requested area, and the bounds declared in DescribeCoverage.
However, if the mosaic is sparse the requested area might intersect only a subset of the images and leave a empty data area on a side, in this case the mosaic won't return pixels in that portion, and the WCS machinery won't pad it either, returning less data than expected.

In the picture:

  • In blue, requested area

  • In red, area currently returned

  • In salmon, area that GeoServer should be returning by specification

Environment

None

Attachments

1

Activity

Andrea Aime 
August 16, 2018 at 5:28 PM

We need some testing before that imho, the change was less than trivial

Simone Giannecchini 
August 16, 2018 at 5:13 PM

should we also backport?

Fixed

Details

Assignee

Reporter

Fix versions

Components

Priority

Created August 14, 2018 at 3:10 PM
Updated November 15, 2021 at 10:10 AM
Resolved September 19, 2018 at 5:17 PM