On Thu, Jul 7, 2011 at 1:03 PM, Lauri Kajan <[email protected]> wrote:
> Hi all,
>
> The remote wms store from where I'm trying to publish layers supports
> many SRSs. In the getcapabilities of the remote wms service there is
> also defined multiple Bounding boxes, one for every srs.
>
> <Layer>
> <Title>Remote WMS Server</Title>
> <SRS>EPSG:3133</SRS>
> <SRS>EPSG:2391</SRS>
> <SRS>EPSG:4326</SRS>
> <SRS>EPSG:3386</SRS>
> <Layer>
> <Name>layer1/Name>
> <Title>Layer 1</Title>
> <LatLonBoundingBox minx="25" miny="61" maxx="26" maxy="62" />
> <BoundingBox SRS="EPSG:4326" minx="25" miny="61"maxx="26" maxy="62" />
> <BoundingBox SRS="EPSG:3133" minx="460000" miny="6858000"
> maxx="505000" maxy="6927000" />
> <BoundingBox SRS="EPSG:2391" minx="1723300" miny="6865200"
> maxx="1762900" maxy="6937500" />
> <BoundingBox SRS="EPSG:3386" minx="881000" miny="6879100"
> maxx="917200" maxy="6953300" />
> <ScaleHint min="0.177" max="362.039" />
> </Layer>
> </Layer>
>
> Now when I publish a layer from that store GS takse one of these SRSs
> as a native SRS. I haven't still figured out which srs of all the
> possibilities GS chooses but it seems to be always the same. It is not
> the first or the last one on the list nor the first or the last I have
> entered in the limited srs list of the wms settings. The
> GetCapabilites of my GS displays now only boundingbox of that "native"
> srs and not all of them that are available in the orginal wms.
>
> <Layer>
> <Title>My WMS Service</Title>
> <SRS>EPSG:3133</SRS>
> <SRS>EPSG:2391</SRS>
> <SRS>EPSG:4326</SRS>
> <SRS>EPSG:3386</SRS>
> <SRS>EPSG:3034</SRS>
> <SRS>EPSG:3035</SRS>
> <LatLonBoundingBox minx="21" miny="59" maxx="26" maxy="62" />
> <Layer queryable="0">
> <Name>mycascadedwms</Name>
> <Title>Turun opaskartta _Turku</Title>
> <SRS>EPSG:3136</SRS>
> <LatLonBoundingBox minx="21" miny="59" maxx="26" maxy="62" />
> <BoundingBox SRS="EPSG:3133" minx="460000" miny="6858000"
> maxx="505000" maxy="6927000" />
> </Layer>
> </Layer>
>
>
> Is there a way to specify the "native" srs that is used to pass the
> bounding box?
> Or even better if there is a way to pass all the bounding boxes from
> cascaded wms layer.
> Or just disable the BoundingBox attribute and just use LatLonBoundingBox
>
What you want is not available but has been recently ticketed here:
http://jira.codehaus.org/browse/GEOS-4659
Not sure when that ticket will be addressed though
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
