Opened 19 years ago
Closed 16 years ago
#1581 closed enhancement (fixed)
[Context] support for Web Map Context 1.1?
Reported by: | Owned by: | jmckenna | |
---|---|---|---|
Priority: | high | Milestone: | 5.0.3 release |
Component: | Documentation - MapServer | Version: | unspecified |
Severity: | minor | Keywords: | |
Cc: | mapserver@…, debbie.pagurek@… |
Description
Are there any plans to incorporate Web Map Context 1.1 support into Mapserver? http://schemas.opengis.net/context/1.1.0/
Attachments (1)
Change History (26)
comment:1 by , 19 years ago
Cc: | added |
---|
comment:2 by , 19 years ago
Cc: | added |
---|
comment:4 by , 19 years ago
Oh... and the spec doc is at https://portal.opengeospatial.org/files/?artifact_id=8618
comment:5 by , 19 years ago
Cc: | added |
---|
comment:6 by , 19 years ago
Another major change/advantage AFAIK should be the support of dimensions (like wms time).
comment:7 by , 18 years ago
Cc: | added |
---|
comment:9 by , 18 years ago
Component: | MapScript → WMS Server |
---|---|
Owner: | changed from | to
From a diff of the 1.0.0 vs 1.1.0 schemas, the changes are a bunch of changes/fixes to the various element's minOccurs and maxOccurs values, plus: Additions to LayerType: <xs:element ref="sld:MinScaleDenominator" minOccurs="0"/> <xs:element ref="sld:MaxScaleDenominator" minOccurs="0"/> <xs:element name="DimensionList" type="context:DimensionListType" minOccurs="0"/> The ServerType's service attribute value is restricted to the following (we used to use the value "WMS" with no "OGC:" prefix): <xs:simpleType name="serviceType"> <xs:restriction base="xs:string"> <xs:enumeration value="OGC:WMS"/> <xs:enumeration value="OGC:WFS"/> </xs:restriction> </xs:simpleType> Addition of LegendURL to SLDType: <xs:element name="LegendURL" type="context:URLType" minOccurs="0"/>
comment:10 by , 18 years ago
dependson: | → 1663 |
---|
Everything is in place, however the time dimension could not be used yet. The map context does not fill the wms_time parameter since it wants to be more general. See bug 1663 for more details. Beside that, the 1.1.0 version is now support in mapserver 4.9. The main difference is the support min/max scales and the support for dimensions. The context now have the following parameters for the dimension support: wms_dimension_%s_unitsymbol wms_dimension_%s_units wms_dimension_%s_uservalue wms_dimension_%s_default wms_dimension_%s_multiplevalues wms_dimension_%s_nearestvalue wms_dimensionlist wms_dimension It works like the styles, check those for more details. Note that with the time dimension, the context will check the wms_time, wms_timedefault metadata to replace wms_dimension_%s_uservalue and wms_dimension_%s_default when not available and the Units, unitSymbol and NearestValue parameters have the following default value: ISO8601, t and 0. Documentation will follow.
comment:11 by , 18 years ago
So are scales enabled from the client side? i.e. if chameleon reads a WMC with scale values, will it process as expected?
comment:12 by , 18 years ago
Hi Tom, Chameleon will read it through Mapscript and Mapscript will set the MINSCALE and MAXSCALE values on the LAYER, so everything should work as you expect. I haven't tested this yet though. Bart
comment:13 by , 18 years ago
Julien, can you please confirm that the MINSCALE and MAXSCALE are set in the layer from the value of MinScaleDenominator and MaxScaleDenominator from the context.
comment:14 by , 18 years ago
The minscale/maxscale of the layer is now set by the context Min/MaxScaleDenominator elements.
comment:15 by , 18 years ago
Owner: | changed from | to
---|
MapServer 4.9 now set the wms_time metadata when the dimension name in the context is "time". So the Support for Context 1.1.0 is now completed. Reassign to Jeff for documentation. There's the new parameter listed in comment 7 (Note that in wms_dimension_time_uservalue can be replaced by wms_time). The min/maxscale parameter are now used in the context 1.1.0. Should we also update the context example in there? let me know if you need any info or precision.
comment:16 by , 18 years ago
There is a problem though, sld:MinScaleDenominator and sld:MaxScaleDenominator are not written when saving a WMC 1.1 document.
comment:17 by , 18 years ago
Thanks for the catch Bart, I added the min/maxscale support in write mode for the WMC 1.1.0 in MapServer 4.9.
comment:18 by , 18 years ago
Hi Julien, I had a look at your change, don't you need to declare the sld namespace now in the root element of the Context XML? It is currently commented in the source (fprintf->msIO_fprintf): /* fprintf( stream, " xmlns:sld=\"http://www.opengis.net/sld"); */ Bart
comment:19 by , 18 years ago
Bart is right. As of WMC 1.1.0, one can define inline SLD objects, so we need the namespace decl in there.
comment:20 by , 18 years ago
There is yet another issue (the schema location is incorrect): http://schemas.opengeospatial.net/context/1.0.0/context.xsd this should be http://schemas.opengeospatial.net/context/1.1.0/context.xsd for WMC 1.1
comment:21 by , 18 years ago
I added the SLD and 1.1.0 xsd loading in the Context xml root element. Done in 4.9 version.
comment:22 by , 17 years ago
Milestone: | → 5.0 release |
---|---|
Owner: | changed from | to
comment:23 by , 16 years ago
Component: | WMS Server → MapServer Documentation |
---|
moving to documentation component
comment:24 by , 16 years ago
Status: | new → assigned |
---|
comment:25 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I added the wms_dimension* metadata to the mapcontext doc (checked into SVN in /trunk/docs.) I also tested each with 5.0.2, and updated the examples used in the doc.
Note:
See TracTickets
for help on using tickets.