Opened 4 years ago

Closed 4 years ago

#283 closed defect (fixed)

GetCapabilities response for non-2D coverages

Reported by: pcampalani Owned by: pcampalani
Priority: major Milestone: 8.4
Component: petascope Version: 8.3
Keywords: getcapabilities response dimensions Cc: abeccati
Complexity:

Description

The summary of coverages which are not 2D is wrong in the GetCapabilities response.

E.g., for 3D the reported dimensions are 2:

<CoverageSummary>
  <CoverageId>eobstest</CoverageId>
  <CoverageSubtype>RectifiedGridCoverage</CoverageSubtype>
  <BoundingBox xmlns="http://www.opengis.net/ows/2.0" crs="http://www.opengis.net/def/crs/EPSG/0/4326" dimensions="2">
    <LowerCorner>25.0 -40.0</LowerCorner>
    <UpperCorner>75.0 75.0</UpperCorner>
  </BoundingBox>
</CoverageSummary>

For 1D the bounding box is not reported:

<CoverageSummary>
  <CoverageId>OneD</CoverageId>
  <CoverageSubtype>GridCoverage</CoverageSubtype>
</CoverageSummary>

Change History (4)

comment:1 Changed 4 years ago by pcampalani

The ows:BoundingBox is not mandatory in a GetCapabilities::CoverageSummary, and the proposed solution would be to avoid listing unofficial compound crs URIs when possible.

Thus, we propose to remove this element from a GetCapabilities response while keeping the envelope information available in the DescribeCoverage::boundedBy element.

Future developments of CRS management will allow a more flexible management of mixed-CRSs coverages.

comment:2 Changed 4 years ago by abeccati

  • Status changed from new to assigned

Sounds good for 8.4 we might reintroduce that also in getCapabilities afterwards if needed to avoid a "special case" scenario. You then have probably to resubmit a patch for this and your previous one be reverted/rejected

comment:3 Changed 4 years ago by pcampalani

The solution I implemented in the patch "Optional bounding box element in GetCapabilities response to be set for 2D single-CRS coverages (ticket #283)." is to show up additional bbox information in case of coverages that fit in the ps_crsdetails table, hence 2D and with no CRS compounding.

If that solution is not accetpable, and a fixed behaviour is required for all the offered coverages, then the patch can be rejected and I'll proceed to the removal of the BoundingBox instead.

comment:4 Changed 4 years ago by pcampalani

  • Resolution set to fixed
  • Status changed from assigned to closed

Ticket addressed in 097dccc.

Note: See TracTickets for help on using tickets.