Opened 18 years ago

Closed 16 years ago

Last modified 16 years ago

#1604 closed defect (fixed)

[docs] convert WCS doc and add examples

Reported by: jmckenna@… Owned by: jmckenna
Priority: high Milestone: 5.0.3 release
Component: Documentation - MapServer Version: unspecified
Severity: normal Keywords:
Cc: tomkralidis, sdlime, warmerdam

Description (last modified by sdlime)

http://mapserver.gis.umn.edu/docs/howto/wcs_server should be converted to
restructured text, and formatted similar to wms/wfs server docs.

Also need to add note on SERVICE=wcs request:

"Note that when a request happens, it is passed through WMS, WFS, and WCS in
MapServer (in that order) until one of the services respond to it."

Change History (15)

comment:1 by jmckenna@…, 18 years ago

Owner: changed from kgeurts@… to jmckenna@…
Summary: [docs] convert WCS doc and add examples [docs] convert WCS doc and add examples
reassigning

comment:2 by jmckenna, 17 years ago

Milestone: 5.0 release
Owner: changed from jmckenna@… to jmckenna

comment:3 by jmckenna, 16 years ago

Status: newassigned

comment:4 by jmckenna, 16 years ago

Cc: tomkralidis added

comment:5 by jmckenna, 16 years ago

Cc: sdlime added
Resolution: fixed
Status: assignedclosed

I have updated the wcs_server doc (converted to reStructuredText, added examples, and tested with ms5.0.2 and 5.1-dev). It is committed in SVN /trunk/docs/.

While updating, I noticed 2 issues, which if you say are valid I can open separate tickets for:

1) the original wcs_server doc mentioned that the layer metadata "timeperiod" exists, however I could not get it to work (appear in a DescribeCoverage request that is), and in fact I see that mapwcs.c states "TODO: add TimePeriod" on line#996. Therefore I removed timeperiod from the latest doc.

2) I just could not get the layer metadata rangeset_axes (and the associated {rangeset_axis}_ metadata) to work (I got internal server errors on DescribeCoverage requests). However I was only testing with the gmap bathymetry.tif, and I was trying bogus values for that rangeset metadata...which could be the problem.

comment:6 by tomkralidis, 16 years ago

Cc: warmerdam added

timeperiod: See http://trac.osgeo.org/mapserver/browser/trunk/mapserver/mapwcs.c#L990 for use of timeperiod metadata. I think we need this clarified for this and #2487 (Steve explained this initially but I'm still fuzzy).

rangeset_axes: some clarification/explanation would be valued here as well

comment:7 by jmckenna, 16 years ago

timeperiod: yes but if you look below line990 to 996 it states that timeperiod is not done, which would explain why I could never get timeperiod to display in a DescribeCoverage request. 990 seems to check if timeperiod or timeposition layer metadata exist, if so then create a temporalDomain tag, then create a timeposition tag, but the section where a timeperiod tag would be created is missing. Am i wrong?

comment:8 by tomkralidis, 16 years ago

True. It's only checked and never output. Hence need for more clarification.

comment:9 by sdlime, 16 years ago

Description: modified (diff)

When the WCS support was written we didn't have any temporal operator support so we couldn't leverage a time period even if provided. That probably isn't the case any more but this isn't the bug to track it with. So, from a documentation standpoint, as you suggest, comment out any mention of timeperiod metadata until the support is added. A WCS timeperiod bug could turn into a documentation bug at that point.

As for rangesets I've got to go back to my original demos. Those are used to describe image "bands" correct? I've got a demo at the DNR that allowed users to choose different bands that might be helpful here. I just need to find it and dust it off.

Steve

comment:10 by jmckenna, 16 years ago

steve, i have my documentation hat on now for the next couple of weeks so if u can dig up some rangeset examples with data I can test and add the examples to the docs, thanks.

comment:11 by sdlime, 16 years ago

Jeff: I found my original demo. You can download at:

http://maps.dnr.state.mn.us/mapserver_demos/wcs_demo.tar.gz

I got it running again with MapServer SVN version at:

http://maps.dnr.state.mn.us/mapserver_demos/wcs/demo.html

Steve

comment:12 by jmckenna, 16 years ago

excellent Steve, thanks. I'll use your wcs demo server in the doc.

comment:13 by jmckenna, 16 years ago

Steve I have a specific question about that wcs server, I hope you don't mind.

I believe this is a valid GetCoverage request:

http://maps.dnr.state.mn.us/cgi-bin/mapserv50?MAP=/usr/local/www/docs_maps/mapserver_demos/wcs/demo.map&SERVICE=wcs&VERSION=1.0.0&REQUEST=GetCoverage&COVERAGE=modis&CRS=EPSG:26915&BBOX=159707,4597895,1400207,5501395&WIDTH=2480&HEIGHT=1806&FORMAT=GEOTIFF_16BIT

The error states:

msWCSGetCoverage(): WCS server error. Requested BBOX (-97.7420492932196,40.6391414622316,-80.5767480313426,50.0599285149526) is outside requested coverage BBOX (159707,4597895,1400207,5501395)

(clicking on the "Download" button in the demo also returns that same error: http://maps.dnr.state.mn.us/mapserver_demos/wcs/demo.html)

I grabbed the EPSG values from the DescribeCoverage (and I can also see that they are correct as stated in the demo.map file).

Do you have any ideas why a GetCoverage request will not work on this server? (I want to include this GetCoverage request in the wcs-server doc)

comment:14 by tomkralidis, 16 years ago

Jeff: I think this is a result of not having a PROJECTION block in the mapfile. See #2538 for more information. A more exhaustive ticket for this issue is at #2552.

comment:15 by jmckenna, 16 years ago

ah yes Tom, you look to be 100% correct, as the DNR mapfile does not contain a projection block. So for now the wcs-server doc will have to include one non-mapserver URL for the GetCoverage request. thanks Tom, that one really confused me.

Note: See TracTickets for help on using tickets.