Opened 4 years ago

Closed 3 years ago

#432 closed task (fixed)

verify WCS extension list in capabilities document

Reported by: pbaumann Owned by: pcampalani
Priority: minor Milestone: 9.0
Component: petascope Version: 8.5
Keywords: Cc: j.yu,
Complexity: Medium

Description

as part of the final checks for 9.0 we should check that the <profile> list in the GetCapabilities? response correctly reflects implenetation.

Change History (5)

comment:1 Changed 4 years ago by j.yu

  • Cc pcampalani removed
  • Resolution set to fixed
  • Status changed from new to closed

OWS profiles are added dynamically by the ExtensionRegistry?

comment:2 Changed 3 years ago by pcampalani

  • Resolution fixed deleted
  • Status changed from closed to reopened

Re-opening since currently the scaling extension was wrongly removed from the service capabilities (changeset:3315a12), while all four variants are implemented:

$ grep scale <wcs_systemtest>/queries/*.kvp
./queries/09-get_coverage_scale1.kvp:scalefactor=2.0
./queries/10-get_coverage_scale2.kvp:scaleaxes=i(0.5)
./queries/11-get_coverage_scale3.kvp:scalesize=j(16)
./queries/12-get_coverage_scale4.kvp:scaleextent=j(16:34)

comment:3 Changed 3 years ago by pcampalani

Before publishing conformance to the scaling extension, ticket #607 needs to be fixed.

Additionally, changeset:3315a12 as well removed CRS extension from the registry but not completely throughout the code: crsMetadata element needs to be removed from capabilities.

comment:4 Changed 3 years ago by pcampalani

  • Milestone changed from 9.0-beta1 to 9.0
  • Owner changed from j.yu to pcampalani
  • Status changed from reopened to accepted

comment:5 Changed 3 years ago by pcampalani

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

changeset:7ceb4f2 : spurious CRS extension code cleaned up and scaling extension profile restored in the service capabilities.

Note: See TracTickets for help on using tickets.