[Geoserver-users] cascading wms and native crs

GeoServer GeoServer User
1

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.

2

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:

···

On Sat, Sep 27, 2014 at 11:49 AM, Tore Halset <halset@…6696…> 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
Geoserver-users@anonymised.comsts.sourceforge.net
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.

3

Hi.

Thank you for the answer. The problem occurs when the different CRSs has different bounding boxes and GeoServer select one CRS that is valid for a smaller area than other CRSs and the actual data. As an example, this WMS has world coverage in EPSG:4326, but EPSG:3575 is only valid for the northern hemisphere.

Regards,
- Tore.

4

On Mon, Sep 29, 2014 at 8:41 AM, Tore Halset <halset@anonymised.com> wrote:

Hi.

Thank you for the answer. The problem occurs when the different CRSs has
different bounding boxes and GeoServer select one CRS that is valid for a
smaller area than other CRSs and the actual data. As an example, this WMS
has world coverage in EPSG:4326, but EPSG:3575 is only valid for the
northern hemisphere.

Ah, I see, the bbox is cut to each area domain of validity.

We could back transform each bbox to wgs84 and pick the largest one, yet,
the reprojection itself back and forth can make bboxes larger each way one
goes around (because of the rotation and the fact that the tilted
reprojected
bbox is turned into another axis parallel bbox), so reprojected bboxes
migth look larger than a "original" wgs84 one.

I'm leaning towards keeping things simple and just pick the first bbox in
the
list. Would that work in your case?

Cheers
Andrea

--

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.

-------------------------------------------------------

5

On 29 Sep 2014, at 09:10, Andrea Aime <andrea.aime@anonymised.com> wrote:

We could back transform each bbox to wgs84 and pick the largest one, yet,
the reprojection itself back and forth can make bboxes larger each way one
goes around (because of the rotation and the fact that the tilted reprojected
bbox is turned into another axis parallel bbox), so reprojected bboxes
migth look larger than a "original" wgs84 one.

I'm leaning towards keeping things simple and just pick the first bbox in the
list. Would that work in your case?

Picking the first is fine for me as I can tune the capabilities myself. However, choosing the box for EPSG:4326 would be a more logical (IMO) choice. And layer.getBoundingBoxes() return a HashMap, so we will have to dig a bit deeper to find the *first* than just adding a “break;”.

Regards,
Tore Halset.