If I paste the following into a browser, I get a full list of capabilities from geoserver, including LatLonBoundingBox and ScaleHint min/max.
aHostname:8090/geoserver/wms?service=wms&version=1.1.1&request=GetCapabilities
However, if I perform the same command from an ajax GET request, I get the LatLonBoundingBox but the ScaleHint info is missing from the XML returned.
Can anyone explain why?
Hi,
When you enter that URL with the browser, it’s a GET request too (just like the AJAX GET you mention). So they should both give the same response.
If they’re not getting the same response I’d suspect that your AJAX request is different; have you used the web-developer components (specifically the network tab) of your browser to see what the actual request is that AJAX is sending to confirm it’s identical?
If you want to go a level deeper and compare the browser request to the AJAX request, try something like Fiddler2.
That will narrow down how they differ. Then someone can hopefully explain why that difference in request results in a the scaleHint being there or not.
Cheers,
Jonathan
On 01/12/2015 11:43, Smart, Gary Export License Required - US UTAS wrote:
If I paste the following into a browser, I get a full list of capabilities from geoserver, including LatLonBoundingBox and ScaleHint min/max.
aHostname:8090/geoserver/wms?service=wms&version=1.1.1&request=GetCapabilities
However, if I perform the same command from an ajax GET request, I get the LatLonBoundingBox but the ScaleHint info is missing from the XML returned.
Can anyone explain why?
------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. [http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140](http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140)_______________________________________________ Geoserver-users mailing list [Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net) [https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)
OK – yes I see the difference – thanks for the prod!
I had two servers providing the same layer – one using geoserver to proxy a WMS, the other direct from the WMS.
When the GET occurs from the geoserver proxy – the hint is lost.
When the GET occurs direct from the WMS the hint is preserved.
I presume I would need to manually set the minScale maxScale parameters in the geoserver UI (for each STORE) in order for geoserver to pass them through
i.e. they are not simply inherited from the WMS source?
From: Jonathan [mailto:jonathan-lists@…7221…]
Sent: 03 December 2015 11:05
To: Smart, Gary Export License Required - US UTAS
Cc: geoserver-users@lists.sourceforge.net
Subject: [External] Re: [Geoserver-users] getCapabilities does not return scaleHint
Hi,
When you enter that URL with the browser, it’s a GET request too (just like the AJAX GET you mention). So they should both give the same response.
If they’re not getting the same response I’d suspect that your AJAX request is different; have you used the web-developer components (specifically the network tab) of your browser to see what the actual request is that AJAX is sending to confirm it’s identical?
If you want to go a level deeper and compare the browser request to the AJAX request, try something like Fiddler2.
That will narrow down how they differ. Then someone can hopefully explain why that difference in request results in a the scaleHint being there or not.
Cheers,
Jonathan
On 01/12/2015 11:43, Smart, Gary Export License Required - US UTAS wrote:
If I paste the following into a browser, I get a full list of capabilities from geoserver, including LatLonBoundingBox and ScaleHint min/max.
aHostname:8090/geoserver/wms?service=wms&version=1.1.1&request=GetCapabilities
However, if I perform the same command from an ajax GET request, I get the LatLonBoundingBox but the ScaleHint info is missing from the XML returned.
Can anyone explain why?
------------------------------------------------------------------------------Go from Idea to Many App Stores Faster with Intel(R) XDKGive your users amazing mobile app experiences with Intel(R) XDK.Use one codebase in this all-in-one HTML5 development environment.Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.[http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140](http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140)_______________________________________________Geoserver-users mailing list[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)
I don’t know, I’ve not done that myself, but off the top of my head I’d expect the proxy to send along that information. I can’t think of a good reason not to, but others will know better.
On 03/12/2015 17:05, Smart, Gary Export License Required - US UTAS wrote:
OK – yes I see the difference – thanks for the prod!
I had two servers providing the same layer – one using geoserver to proxy a WMS, the other direct from the WMS.
When the GET occurs from the geoserver proxy – the hint is lost.
When the GET occurs direct from the WMS the hint is preserved.
I presume I would need to manually set the minScale maxScale parameters in the geoserver UI (for each STORE) in order for geoserver to pass them through
i.e. they are not simply inherited from the WMS source?
From: Jonathan [mailto:jonathan-lists@anonymised.com]
Sent: 03 December 2015 11:05
To: Smart, Gary Export License Required - US UTAS
Cc: geoserver-users@lists.sourceforge.net
Subject: [External] Re: [Geoserver-users] getCapabilities does not return scaleHintHi,
When you enter that URL with the browser, it’s a GET request too (just like the AJAX GET you mention). So they should both give the same response.If they’re not getting the same response I’d suspect that your AJAX request is different; have you used the web-developer components (specifically the network tab) of your browser to see what the actual request is that AJAX is sending to confirm it’s identical?
If you want to go a level deeper and compare the browser request to the AJAX request, try something like Fiddler2.
That will narrow down how they differ. Then someone can hopefully explain why that difference in request results in a the scaleHint being there or not.Cheers,
JonathanOn 01/12/2015 11:43, Smart, Gary Export License Required - US UTAS wrote:
If I paste the following into a browser, I get a full list of capabilities from geoserver, including LatLonBoundingBox and ScaleHint min/max.
aHostname:8090/geoserver/wms?service=wms&version=1.1.1&request=GetCapabilities
However, if I perform the same command from an ajax GET request, I get the LatLonBoundingBox but the ScaleHint info is missing from the XML returned.
Can anyone explain why?
------------------------------------------------------------------------------Go from Idea to Many App Stores Faster with Intel(R) XDKGive your users amazing mobile app experiences with Intel(R) XDK.Use one codebase in this all-in-one HTML5 development environment.Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.[http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140](http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140)_______________________________________________Geoserver-users mailing list[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)
On Thu, Dec 3, 2015 at 6:05 PM, Smart, Gary Export License Required - US
UTAS <Gary.Smart@anonymised.com> wrote:
OK – yes I see the difference – thanks for the prod!
I had two servers providing the same layer – one using geoserver to proxy
a WMS, the other direct from the WMS.
Ah, so your "proxy" is in fact a WMS store that does WMS cascading
When the GET occurs from the geoserver proxy – the hint is lost.
When the GET occurs direct from the WMS the hint is preserved.
I presume I would need to manually set the minScale maxScale parameters in
the geoserver UI (for each STORE) in order for geoserver to pass them
throughi.e. they are not simply inherited from the WMS source?
Correct, they are not. GeoServer computes its own scale hints from the
default SLD style associated to the layer.
For cascaded WMS layers you don't even have a SLD style, so there is
nothing to go against... I believe some new code
needs to be written to allow scale hints to be set, or just directly
cascaded, for this type of layer.
See this guide if you would have to have this implemented:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Cheers
Andrea
*Geosolutions' Winter Holidays from 24/12 to 6/1*
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.
-------------------------------------------------------