-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Marco,
it should be. There is a requirement within the WMS specification that
defines REQUEST=GetCapabilities to be supported by a WMS Server. But
it is not forbidden to have support for REQUEST=getcapabilities on
the server side, too. For WMS
The WMS client should use GetCapabilities, parameter values are case-sensitive.
Parameter names are not case-sensitive.
Best regards,
Bart
--
Bart van den Eijnden
OSGIS - http://osgis.nl
On Apr 22, 2013, at 11:04 AM, Marco Lechner - FOSSGIS e.V.
marco.lech...@fossgis.de wrote:
Hi,
is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
yes Andrea, but in my opinion it is not forbidden to have additional
support for the other alternative. You have to implement the case
sensitive KVP but it is not forbidden to implement the other additionally.
Regards
Sebastian
- --
l a t / l
On Mon, Apr 22, 2013 at 11:35 AM, Sebastian Goerke goe...@lat-lon.dewrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
yes Andrea, but in my opinion it is not forbidden to have additional
support for the other alternative. You have to implement the case
sensitive KVP but it is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
all those posts confirm my understanding. @sebastian, of course its not
a problem to make a server more tolerant (as many wms-servers are) to
make it working with non-compliant clients, but the client has to use
the correct request to stay in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
CITE WMS Client test suite is available through the current Beta
release of TEAM Engine:
http://cite.opengeospatial.org/te2/
I think, the WMS Client test suite covers this.
Regards
Sebastian
Am 22.04.2013 11:43, schrieb Andrea Aime:
On
