#4191 closed defect (fixed)
WCS 2.0 bounded by wrong axis order
| Reported by: | fschindler | Owned by: | schpidi |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | WCS Server | Version: | unspecified |
| Severity: | major | Keywords: | wcs axis order bounded by |
| Cc: | schpidi |
Description
Currently, MapServer returns a wrong gml:boundedBy element in DescribeCoverage multipart GetCoverage for projection expressed in lat/long.
The axis labels are fixed to lat/long, even when the projection normally should have an long/lat axis order.
Additionally, the values in the lowerCorner/upperCorner element are fixed to minx/miny and maxx/maxy, also with no respect to the mandated axis order.
The axis should and the bounding box values should respect the axis order mandated by the projection definition.
The attached patch resolves this issue.
Attachments (1)
Change History (6)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
by , 12 years ago
| Attachment: | r13152_wcs20_boundedBy_axis_order.patch added |
|---|
comment:3 by , 12 years ago
The issue is now solved with the latest added patch. Also the gml:domainSet issue is addressed.
comment:4 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:5 by , 12 years ago
Note:
See TracTickets
for help on using tickets.
This also applies to the gml:domainSet with its gml:axisLabels, gml:origin and gml:offsetVector elements.