Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#4006 closed defect (fixed)

WCS 2.0: Wrong offset vector and origin

Reported by: fschindler Owned by: fschindler
Priority: normal Milestone: 6.0.2 release
Component: WCS Server Version: 6.0
Severity: normal Keywords: WCS offset_vector origin
Cc: schpidi

Description

In WCS 2.0 DescribeCoverage and GetCoverage multipart responses the origin and offset vectors (wcs:CoverageDescription/gml:domainSet/gml:origin or gml:offsetVector) are not northed (using [minx, maxy] as origin and [resolutionx, -resolutiony] as offset vectors).

This results in different meta-data compared to the data retrieved with gdalinfo.

The resolving patch will be added as attachment.

Attachments (1)

r12507_wcs20_origin_ov_northing.patch​ (1.3 KB ) - added by fschindler 13 years ago.
Patch to resolve the described problem

Download all attachments as: .zip

Change History (3)

by fschindler, 13 years ago

Attachment: r12507_wcs20_origin_ov_northing.patch​ added

Patch to resolve the described problem

comment:1 by schpidi, 13 years ago

Resolution: → fixed
Status: new → closed

Committed adjustments with r12511.

comment:2 by schpidi, 12 years ago

Committed adjustments with r13155 in 6.0 branch.

Note: See TracTickets for help on using tickets.