Opened 16 years ago

Closed 16 years ago

#2538 closed defect (fixed)

bbox extents of a GetCoverage to a WCS 1.0.0 server are not reprojected correctly

Reported by: nsavard Owned by: sdlime
Priority: normal Milestone: 5.2 release
Component: WCS Server Version: svn-trunk (development)
Severity: blocker Keywords: OGC, Cite, TEAM, WCS 1.0.0
Cc: tomkralidis, warmerdam

Description

When a GetCoverage request is sent to a WCS 1.0.0 server with a requested bbox that is exactly the same as the coverage bbox, an exception is returned. If I check the extents of the requested bbox that are shown in the exception report (-178.694620505056, 2350.98746391444, 173.573166166742, 2845.59870358977), they seem to have incorrect values. The projection in the request is EPSG:4326.

The coverage bbox is: -97.7071758865421,41.0324719184183,-80.6778361148771,49.6650665681236

The request sent is: http://dev1.lan.mapgears.com/manwe/cgi-bin/mswcs100_ogc_cite?&VeRsIoN=1.0.0&SeRvIcE=WCS&ReQuEsT=GetCoverage&BbOx=-97.7071758865421,41.0324719184183,-80.6778361148771,49.6650665681236&CrS=EPSG:4326&WiDtH=200&BoGuS=ignored&FoRmAt=GeoTIFF&HeIgHt=100&CoVeRaGe=ndvi

The response is: <?xml version='1.0' encoding="ISO-8859-1" ?> <ServiceExceptionReport version="1.2.0" xmlns="http://www.opengis.net/ogc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/ogc http://schemas.opengis.net//wcs/1.0.0/OGC-exception.xsd">

<ServiceException code="NoApplicableCode" locator="bbox">msWCSGetCoverage(): WCS server error. Requested BBOX (-178.694620505056,2350.98746391444,173.573166166742,2845.59870358977) is outside requested coverage BBOX (159707,4597895,1400207,5501395) </ServiceException>

</ServiceExceptionReport>

Change History (11)

comment:1 by tomkralidis, 16 years ago

Cc: tomkralidis warmerdam added

comment:2 by tomkralidis, 16 years ago

I think this is a result of the changes made in #2503. There's some sort of "faked" extent going on. Frank might be able to comment on this issue.

comment:3 by nsavard, 16 years ago

Severity: normalblocker

I set the severity to blocker because I cannot test anymore without this fix.

comment:4 by tomkralidis, 16 years ago

Norm: I tried to replicate this against msautotest/wxs/wcs_simple.map (i.e. GetCoverage request where EPSG:4326 bbox in request is identical to the bbox output for the coverage in the GetCapabilities response, and where coverage has to be projected) and can't reproduce the error.

Can you package a minimal mapfile and test data for this ticket?

comment:5 by tomkralidis, 16 years ago

Norm: thanks for the testcase (emailed offline). I'm able to reproduce this issue, and have posted the testcase at http://devgeo.cciw.ca/ms_tmp/mstrac-2538.tgz. Frank is looking into this (irc convo)

comment:6 by warmerdam, 16 years ago

I have established that the request reprojection does not work because the layer lacks a PROJECTION block defining it's coordinate system.

If I add:

    PROJECTION 
      "+init=epsg:26915"
    END 

to the layer things work right.

So fundamentally I think the issue with this ticket is that WCS (and possibly other services) need to recognise the map lacks key information and refuse to operate with some sort of explanatory exception.

Alternatively we could try to derive some rules like defaulting layer and/or map projection objects based on stuff like ows_srs.

I don't have any strong opinions, so I don't plan on further work on this issue pending a clear resolution.

comment:7 by tomkralidis, 16 years ago

Norm: for CITE testing, I would suggest you add the projection block to your mapfile to continue testing and if that fixes this ticket than we can close.

I will open another ticket related to issues raised in comment:6

comment:8 by nsavard, 16 years ago

I added the projection block.

comment:9 by tomkralidis, 16 years ago

Does this fix the issue? If yes, we can close, as I have opened #2552 to address the PROJECTION issue for OWS in general.

comment:10 by nsavard, 16 years ago

Tom: Sorry for the delay, I needed to to deeper testing. That fixed the issue.

comment:11 by tomkralidis, 16 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.