Hi Jonathan,
there migth well be some issue in version negotiation, but the parameter to
be used normally
is acceptVersions, not version (version works for any other call but
GetCapabiltiies, GeoServer still uses it
in case there is an exact match). That might play a role too.
Cheers
Andrea
On Fri, Mar 30, 2018 at 5:52 PM, Jonathan Moules <
jonathan-li...@lightpear.com> wrote:
> Hi List,
> I have a version negotiation question for WCS.
>
> I'm making GetCapabilities requests to various public boxes for WCS
> version 1.1.2, and GeoServer doesn't seem to support this particular
> version. GeoServer seems to go from 1.1.1, then straight to 2.0.1; I guess
> that's what got funded.
>
> The odd thing is in this scenario, GeoServer is returning the 2.0.1
> GetCap. I would have expected the 1.1.1 GetCapabilities.
> The only WCS spec I can see that discusses version negotiation is the
> WCS 1.0.0 spec. Section 6.2.4 says:
>
> " If no version number is specified in the request, the server must
> respond with the highest version it understands and label the response
> accordingly."
>
> Ok, but I *did* specify a version number. My query is something like:
> http://example.com/geoserver/ows?request=GetCapabilities&se
> rvice=WCS&version=1.1.2
>
> So these are the negotiation rules in the spec:
> "a) If the server implements the requested version number, the server
> must send that version.
>
> b) If a version unknown to the server is requested, the server must
> send the highest version it knows that is less than the requested version.
>
> c) If the client request is for a version lower than any of those
> known to the server, then the server must send the lowest version it knows.
> [snip]"
>
> So my question is, which of these rules is triggering? To my mind it
> should be rule (b) - I'm requesting an unknown number, so the server should
> be returning the highest version that's *less* than it, so 1.1.1.
> Am I misreading the spec/situation or is this a bug in GeoServer's
> negotiating?
> Cheers,
> Jonathan
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-req
> uesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
--
Regards,
Andrea Aime
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
