Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wcs 1.0.0 getcoverage without BBOX but with time and CRS shows strange behaviour #4853

Closed
pfreimuth opened this issue Jan 24, 2014 · 1 comment

Comments

@pfreimuth
Copy link

Hi,
executing the following request
https://devcloud.blackbridge.com/wcs/PlenumsoftDemo?SERVICE=WCS&VERSION=1.0.0&REQUEST=GetCoverage&COVERAGE=testdata_raw&FORMAT=GEOTIFF_INT16&RESX=5&RESY=5&RESPONSE_CRS=EPSG:32616&CRS=EPSG:4326&TIME=2012-04-05

results in


msWCSGetCoverage(): WCS server error. Requested BBOX (-2.5,-2.5,2.5,2.5) is outside requested coverage BBOX (210500,2230500,261500,2281500)
msProjectRect(): Projection library error. All points failed to reproject.
msProjectPoint(): Projection library error. proj says: latitude or longitude exceeded limits

The corresponding layer d3efinition is:

MAP
...
LAYER
# this is the tileindex that aggregates the single image products together and makes them accessible by date and extend
NAME "data_raw_idx"
STATUS ON
DEBUG 5
TYPE POLYGON
DATA "/mnt/mapserver/mapserver_wms/Raster/Plenumosft_RE_Sample_forWCS/plenumsoft_demo_data"
PROJECTION
"init=epsg:32616"
END
VALIDATION
# 'productid' '^([0-9])$'
END
#FILTER ( '[productid]'='%productid%')
METADATA
#'productid_validation_pattern' '^([0-9])$'
#'default_productid' '1234567'
#disable explicitly everything that shall not be supported for this Layer
"wms_enable_request" "!GetCapabilities !GetMap !GetLegendgraphic"
"wcs_enable_request" "!GetCapabilities !GetCoverage !DescribeCoverage"
"wfs_enable_request" "!GetCapabilities !GetFeature !DescribeFeatureType"
END
END
LAYER
# this layer serves the 16bit raw data
NAME "testdata_raw"
STATUS ON
DUMP TRUE
DEBUG 5
TYPE RASTER ### required
PROJECTION
"init=epsg:32616"
END
OFFSITE 0 0 0
UNITS meters
TILEINDEX "data_raw_idx"
TILEITEM "location"
#MASK "mask2"
METADATA
"wcs_title" "5 band 16bit RE Testdata with time support"
"wcs_extent" "210500.0 2230500.0 261500.0 2281500.0" # shall be set dynamically by the wrapper script on mapObj base
"wcs_srs" "EPSG:4326 EPSG:900913 EPSG:3857 EPSG:32615 EPSG:32616 EPSG:32617"
"wcs_label" "5 band 16bit RE Testdata" ### required
"wcs_rangeset_axes" "bands"
"wcs_rangeset_name" "Bands" ### required to support DescribeCoverage request
"wcs_rangeset_label" "RE Radiometric Bands" ### required to support DescribeCoverage request
"wcs_rangeset_nullvalue" "0"
#"wcs_size" "15000 15000" #if we have a global ows_extent set in web-metadata and a wcs_resolution this gets calculated by mapserver
"wcs_resolution" "5.0 5.0"
"wcs_bandcount" "5"
"wcs_band_names" "Blue Green Red Rededge Nir"
"wcs_imagemode" "INT16"
"wcs_formats" "GEOTIFF_INT16 AAIGRID"
"wcs_native_format" "image/tiff"
"wcs_nativeformat" "GTiff"
"wcs_enable_request" "*"
"wcs_timeposition" "2011-01-04,2011-04-20,2012-04-05" #this might get set by the mapscript wrapper accodingly to the dates avaialable for the service and is mandatory to allow temporal subsettings
"wcs_timeextent" "2011-01-04/2012-04-05" # shall be set dynamically by the wrapper script on mapObj base
"wcs_timeitem" "acquidate"
#disable explicitly everything that shall not be supported for this Layer
"wms_enable_request" "!GetCapabilities !GetMap !GetLegendgraphic"
"wfs_enable_request" "!GetCapabilities !GetFeature !DescribeFeatureType"
END
CLASS
NAME "5 Band (16bit) RE Imagedata"
KEYIMAGE "drgs_keyimage.png"
END
END
...
END

If i use CRS=EPSG:32616 which is the epsg code of the layer itself, everything works fine. I would expect that mapserver would reproject the wcs_extent or layer_extent or map_extent to the given CRS and use that BBOX by default.

@mapserver-bot
Copy link

This is an automated comment

This issue has been closed due to lack of activity. This doesn't mean the issue is invalid, it simply got no attention within the last year. Please reopen with missing/relevant information if still valid.

Typically, issues fall in this state for one of the following reasons:

  • Hard, impossible or not enough information to reproduce
  • Missing test case
  • Lack of a champion with interest and/or funding to address the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants