Coordinate reference systems for WCS 1.0.0

[dvhildeb]

I am running MapServer 5.3-dev (ms4w) and testing WCS 1.0.0. I discovered that the coordinate system in which the window is requested (CRS) must be the same as the coordinate system of the source image. If they are different an error is generated with respect to the bounding box of the request being outside the bounding box of the coverage. This is a major defect because it means that DescribeCoverage? must be used to query the coordinate system of source and then the client must convert the coordinate system (either input of output).

This defect is fairly simple to replicate. I have listed the MAP file and accompanying projection defination files.

MAP file

MAP
  NAME "mapserv"
  OUTPUTFORMAT     #default...
    NAME 'AGG_JPEG'
    DRIVER AGG/JPEG
    IMAGEMODE RGB
  END
  WEB
    METADATA
      "ows_title" "OGC mapserv"
      "ows_contactorganization" "Agriculture Financial Services Corporation"
      "ows_srs" "EPSG:3400 EPSG:2955 EPSG:2956 EPSG:3401 EPSG:3402 EPSG:3403 EPSG:4267 EPSG:4269 EPSG:4326 EPSG:26711 EPSG:26712 EPSG:26911 EPSG:26912 EPSG:32611 EPSG:32612 EPSG:42101 EPSG:42304 EPSG:43001 EPSG:900913"
      "ows_http_max_age" "3"
      "wcs_label" "WCS mapserv"
      "wcs_onlineresource" "http://172.16.12.76/cgi-bin/mapserv.wcs.100.exe?"
    END
    IMAGEPATH "/ms4w/tmp/ms_tmp/"
    IMAGEURL "/ms_tmp/"
  END
  SIZE 1200 1000   #arbitrary...
  INCLUDE "a10tm.prj"
  LAYER
    NAME "spot2009i"
    METADATA
      "wcs_label" "spot2009i"
      "wcs_rangeset_name" "Spot5pan"
      "wcs_rangeset_label" "Spot5 panchromatic"
      "ows_resolution" "2.5 2.5"
      INCLUDE "a10tm.ogc"
    END
    STATUS off
    MAXSCALEDENOM 100000
    TYPE raster
    TILEINDEX "//Plcoressatsb01/G$/SPOT/Alberta_2009_SPOT_Mosaic.shp"
    TILEITEM "MOSAIC"
    INCLUDE "a10tm.prj"
    TEMPLATE "empty.html"   #no useful information...
    DUMP TRUE
  END
END

a10tm.prj

PROJECTION
  "init=epsg:3400"
END
EXTENT 133000 5365600 905200 6721100
UNITS meters

a10tm.ogc

"wms_srs" "EPSG:3400"
"wms_extent" "133000 5365600 905200 6721100"
"wfs_srs" "EPSG:3400"
"wfs_extent" "133000 5365600 905200 6721100"
"wcs_srs" "EPSG:3400"
"wcs_extent" "133000 5365600 905200 6721100"

[dmorissette]

I believe WCS support has been improved quite a bit since MS 5.3. Is this also an issue with MS 5.6 or even better, with 6.0 beta?