Hi,

Everything up till ? belongs to base URL.  The real WMS query string starts 
from that. See http://en.wikipedia.org/wiki/Query_string
If the base URL happens to contain /geoserver/wms does not make it as a WMS 
request.

However, there is an odd thing in the WMS standards.  Up till version 1.1.1 
SERVICE parameter was not mandatory for GetMap and GetFeatureInfo. Perhaps they 
have thought it does not need to be because GetMap and GetFeature info does not 
exist in other OGC services. Obviously they saw that saving one parameter was 
not worth the trouble and service is mandatory in WMS 1.3.0.  In 
GetCapabilities it has naturally been compulsory always because otherwise the 
server could not  know which OGC service is queried.
The WMS 1.1.1 standard does not say, or at least I can't see from it, which 
parameters are compulsory for GetStyles.  Reading version  1.3.0 does not help 
because GetStyles does not exist anymore in that version.

So I cannot say if it is right or wrong that GetStyles with WMS 1.1.1 does not 
work without SERVICE.  According to WMS standard it is OK that GetMap works and 
thus the query you copy-pasted is OK with WMS 1.1.1 GetMap but not with WMS 
1.3.0.  Not all WMS servers have even known that GetMap should work without 
&SERVICE and I would say it not wise at all to make a client to create such 
requests. If I would correct something I would edit the Geoserver demo requests 
to contain always the SERVICE parameter.  At least it would have saved a couple 
of hours of both your and my time in this case.

Geoserver documentation claims also that the SERVICE parameter is mandatory and 
it is good so even it actually is not.
http://docs.geoserver.org/stable/en/user/services/wms/reference.html


-Jukka Rahkonen-



Jonathan wrote:


I was basing it on the demo URL's. None of them have the "&service=wms". They 
all have "/geoserver/wms?" instead.

It does work with &service=wms. But doesn't with the "/geoserver/wms?".

Should they both act identically? I'd never even noticed they were different 
before.

Thanks,
Jonathan


On 1 February 2013 15:12, Rahkonen Jukka 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

Why not to include &service=wms in the request?

http://localhost:8080/geoserver/ows?service=wms&version=1.1.1&request=getstyles&layers=states
http://localhost:8080/geoserver/ows?service=wms&version=1.1.1&request=getstyles&layers=Img_Sample

-Jukka-



Lähettäjä: Jonathan Moules 
[mailto:[email protected]<mailto:[email protected]>]
Lähetetty: 1. helmikuuta 2013 17:03
Vastaanottaja: Rahkonen Jukka
Kopio: 
[email protected]<mailto:[email protected]>
Aihe: Re: [Geoserver-users] Scale Thresholds - how to get

Thanks Jukka. That looks like it should do something useful, but it doesn't 
seem to work.

Reading the SLD 1.0.0 specs I think the following should do it:

http://wppgeog3:8082/geoserver/wms?request=getStyles&version=1.3.0&layers=OS_Rasters:25000_Colour

But I get a xml failure (WMS 1.0.0, 1.1.0 or 1.3.0):
No such operation wms 1.1.0 getStyles


There doesn't seem to be a demo URL in the demo's list for me to work from.

Anyone know how to use this?
Thanks,
Jonathan

On 1 February 2013 14:31, Rahkonen Jukka 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

Just a guess, but see what you get with WMS GetStyles.

-Jukka Rahkonen

Jonathan Moules wrote:

Hi List,
  I have a number of layers that have scale denominators (aka, scale 
thresholds) in their styles and these work correctly.

My question is - is there a way for me to find out from the WMS what these 
scale denominators are? They don't appear to show up in a GetCapabilities 
request or a WMS 1.1.1 "describeLayer" request. I can't see anything obvious in 
the spec (ctrl-f for "scale" and "denominator").

Anyone have any ideas if this is possible?
Thanks,
Jonathan


This transmission is intended for the named addressee(s) only and may contain 
sensitive or protectively marked material up to RESTRICTED and should be 
handled accordingly. Unless you are the named addressee (or authorised to 
receive it for the addressee) you may not copy or use it, or disclose it to 
anyone else. If you have received this transmission in error please notify the 
sender immediately. All email traffic sent to or from us, including without 
limitation all GCSX traffic, may be subject to recording and/or monitoring in 
accordance with relevant legislation.



This transmission is intended for the named addressee(s) only and may contain 
sensitive or protectively marked material up to RESTRICTED and should be 
handled accordingly. Unless you are the named addressee (or authorised to 
receive it for the addressee) you may not copy or use it, or disclose it to 
anyone else. If you have received this transmission in error please notify the 
sender immediately. All email traffic sent to or from us, including without 
limitation all GCSX traffic, may be subject to recording and/or monitoring in 
accordance with relevant legislation.



This transmission is intended for the named addressee(s) only and may contain 
sensitive or protectively marked material up to RESTRICTED and should be 
handled accordingly. Unless you are the named addressee (or authorised to 
receive it for the addressee) you may not copy or use it, or disclose it to 
anyone else. If you have received this transmission in error please notify the 
sender immediately. All email traffic sent to or from us, including without 
limitation all GCSX traffic, may be subject to recording and/or monitoring in 
accordance with relevant legislation.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to