Open tbonfort opened 12 years ago
Author: assefa Date: 2006/02/14 - 18:31
Julien,
If you do these changes, here are the other metadata that you might want to
change for consistency :
- wms_timeextent
- wms_timeitem
- wms_timedefault
Also notes :
- If the value of wms_dimension_time_units is diffrent from the ISO8601, It
can not really be used in the capabilities since mapserver won't be able to
support it
- wms_dimension_time_nearestvalue is also not supported so It should always
be set to 0 in the capabilities. Some issues might arise with the other
parametsrs. Just make sure to consider it.
Beside that I don't see any problem.
Author: jlacroix Date: 2006/02/14 - 21:43
I also noticed that the WCS code use time related metadata like:
wms_timeposition and wms_timeperiod. Do you think they should be changed too?
Normally the MapContext is only on the client side, however we are beginning to
configure the server related metadatas with mapcontext variables...
So this would add to the list:
wms_dimension_time_item
wms_dimension_time_extent
wms_dimension_time_position
wms_dimension_time_period
With of course the support of the old metadata names.
Are you ok with that?
Also the server configuration would be up to the user, if they specify manually
in the mapfile different nearest values or units, it's up to them. If one day we
support different ones, the parameters will be there.
Author: dmorissette Date: 2006/02/16 - 23:11
Steve, your advice on this with respect to WCS would be welcome.
Basically the question is: should we, or does it make sense at all to try to
unify the naming of time metadata accross all protocols (WMC, WMS and WCS) using
a wms_dimension_time_... scheme or should we keep that local to WMC? Does WCS
allow using dimensions other than time?
Author: sdlime Date: 2006/02/23 - 16:18
Sorry guys, I missed this one. Too much email these days. I believe WCS does
support other dimensions besides time, z for example. I need to go back to the
WCS code quickly (and the spec) to comment further. I'll try and do that today
and add to this bug.
Steve
Author: jlacroix Date: 2006/03/09 - 22:28
Since there's more than one dimension in WCS, I think I'll revise my position.
I'll hardcode the wms_time parameter in the context stuff and let alone the rest
of mapserver. When we will have time to review all the dimensions handling in
all MapServer, we will talk again.
I'ss keep that bug open for the dimension revision though.
Reporter: jlacroix Date: 2006/02/14 - 04:01