Hi Tore,
yeah, by looking at the code it seems it ends up picking the last one that
it can understand, among the published ones.
I believe the original intention was to actually pick the first one, but we
forgot to add a "break;"
That said, the spec does not seem to provide a way to identify the "native"
one, it just says:
---
A Layer shall not provide a BoundingBox for a CRS it does not support.
Conversely, a Layer may support CRSs
for which it does not provide a BoundingBox: a server that has the ability
to transform data to different CRSs may
choose not to provide an explicit BoundingBox for every possible CRS
available for each Layer. The server
should provide BoundingBox information for at least the native CRS of the
Layer (that is, the CRS in which the
Layer is stored in the server’s database).
---
Cheers
Andrea
On Sat, Sep 27, 2014 at 11:49 AM, Tore Halset <[email protected]> wrote:
> Hello.
>
> I am trying to add my non-GeoServer WMS as a cascaded WMS to GeoServer.
> However, the detected SRS is not correct. GeoServer detect EPSG:3575, but
> EPSG:4326 would be a better fit.
>
> This is the WMS URL I am trying to add. Layer coverage.
> http://services.ecc.no/wms/wms_ip/anonymous
>
> How does GeoServer detect the native SRS of a cascaded WMS? It looks like
> CatalogBuilder#buildWMSLayer loops the bounding boxes of the layer, but
> this WMS has bounding boxes for several SRSs.
>
> My first guess was that GeoServer used the SRS-element of each Layer i
> capabilities, but that did not help (I have updated my development server
> with this attempt).
>
> Regards,
> Tore Halset.
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
-------------------------------------------------------
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
