WMS getCapabilities and SRS
Eijnden, Bart van den (AGI)
b.vdeijnden at AGI.RWS.MINVENW.NL
Wed Jul 12 00:21:14 PDT 2006
Hi Sture,
both are allowed. Remember that if you don't define it at the layer level, the layer will inherit from the parent layer. Check the WMS spec for the exact explanation.
You can have the same behaviour in Mapserver by only defining wms_srs at the WEB METADATA level and not at your LAYER METADATA level.
Best regards,
Bart
-----Oorspronkelijk bericht-----
Van: UMN MapServer Users List
[mailto:MAPSERVER-USERS at LISTS.UMN.EDU]Namens Sture Dingsøyr
Verzonden: woensdag 12 juli 2006 9:14
Aan: MAPSERVER-USERS at LISTS.UMN.EDU
Onderwerp: [UMN_MAPSERVER-USERS] WMS getCapabilities and SRS
Hi
I have a question regarding the SRS tag in getCapabilities.
In my mapfile I put all the EPSG codes that I want my layers to be available in with the METADATA tag ?wms_srs?, so that my layers look like this:
LAYER
PROJECTION
"init=epsg:32633"
END
METADATA
"wms_title" "Fylke flate"
"wms_srs" "EPSG:4326 EPSG:25831 EPSG:25832 EPSG:25833 EPSG:25834 EPSG:25835 EPSG:27391 EPSG:27392 EPSG:27393 EPSG:27394 EPSG:27395 EPSG:27396 EPSG:27397 EPSG:27398 EPSG:32631 EPSG:32632 EPSG:32633 EPSG:32634 EPSG:32635 EPSG:102132 EPSG:102133 EPSG:102134 EPSG:102135"
"wms_abstract" "For å hente dette tema via WMS må ein nytte layer_74 som verdi i LAYER parameter"
"gml_include_items" "all"
END
DATA "adaptive/74"
STATUS off
TRANSPARENCY 50
TYPE polygon
DUMP TRUE
TEMPLATE "TRUE"
NAME "layer_74"
CLASS
COLOR 0 0 0
NAME "Fylke flate"
OUTLINECOLOR 255 255 255
SYMBOL "horizontal"
END
END
In my getCapabilities file all the correct SRS tags are displayed like this:
- <Layer queryable="1" opaque="0" cascaded="0" noSubsets="0">
<Name>layer_74</Name>
<Title>Fylke flate</Title>
<Abstract>For å hente dette tema via WMS må ein nytte layer_74 som verdi i LAYER parameter</Abstract>
<SRS>EPSG:4326</SRS>
<SRS>EPSG:25831</SRS>
<SRS>EPSG:25832</SRS>
<SRS>EPSG:25833</SRS>
<SRS>EPSG:25834</SRS>
<SRS>EPSG:25835</SRS>
<SRS>EPSG:27391</SRS>
<SRS>EPSG:27392</SRS>
<SRS>EPSG:27393</SRS>
<SRS>EPSG:27394</SRS>
<SRS>EPSG:27395</SRS>
<SRS>EPSG:27396</SRS>
<SRS>EPSG:27397</SRS>
<SRS>EPSG:27398</SRS>
<SRS>EPSG:32631</SRS>
<SRS>EPSG:32632</SRS>
<SRS>EPSG:32633</SRS>
<SRS>EPSG:32634</SRS>
<SRS>EPSG:32635</SRS>
<SRS>EPSG:102132</SRS>
<SRS>EPSG:102133</SRS>
<SRS>EPSG:102134</SRS>
<SRS>EPSG:102135</SRS>
<LatLonBoundingBox minx="-0.952145" miny="57.7524" maxx="31.9287" maxy="71.5653" />
<BoundingBox SRS="EPSG:32633" minx="-77249.9" miny="6.4483e+06" maxx="1.11456e+06" maxy="7.94045e+06" />
- <Style>
<Name>default</Name>
<Title>default</Title>
- <LegendURL width="20" height="15">
<Format>image/png</Format>
<OnlineResource xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:href="http://adaptiveutv.avinet.no/wms.aspx?version=1.1.1&service=WMS&request=GetLegendGraphic&layer=layer_74&format=image/png" />
</LegendURL>
</Style>
</Layer>
Now I am connection to some other external WMS service that use ARCIMS, and I can see there that the SRS (EPSG code) is not put on each layer, but on the ?service level??
My question is: What is the correct way of dooing this according to the WMS standard? Should each SRS be on each layer or on the ?service level??
Best regards
Sture
Disclaimer
************************************************************************
Aan dit bericht kunnen geen rechten worden ontleend. Dit bericht is
uitsluitend bestemd voor de geadresseerde. Als u dit bericht per abuis
hebt ontvangen, wordt u verzocht het te vernietigen en de afzender te
informeren. Wij adviseren u om bij twijfel over de juistheid of de
volledigheid van de mail contact met afzender op te nemen.
This message shall not constitute any rights or obligations.
This message is intended solely for the addressee.
If you have received this message in error, please delete it and
notify the sender immediately. When in doubt whether this message
is correct or complete, please contact the sender.
************************************************************************
More information about the MapServer-users
mailing list