Add WMS 'version' support (including 1.3.0)

[yvesm]

Add WMS 1.3.0 support in the Map widget. By default OpenLayers asks for WMS 1.1.1. We could probably add a DataStore option which is the Version of the protocol and pass that to OL Layer object though. that would fix the problem.

[adube]

done with r847, featuring :

• new options tag for services (support added in core for all services)

• version tag for services. When used with a WMS service, WMS layer objects created using the service will have the according version defined AND queries made by the QueryOnClick widget will also use the defined version

• A fix the the MapServer issue when using 1.3.0 in OpenLayers, see ticket ​2478

• A new ​sample showing the use of the service option 'version'

• More documentation about services added in ​Architecture and Concepts page.

• a bug fix in core file ConfigElement.php (org_geoprisma_option_Option objects now supported by getDomElements method)

Tested with all drivers, including PGSQLMapContextConfig ('version' service option added in .sql of sample)

All WMS versions are now supported.

[yvesm]

• A fix the the MapServer issue when using 1.3.0 in OpenLayers, see ticket ​2478

That ticket isn't closed AFAICT. Is the patch mentioned in the ticket in OL trunk ? In short, do we just need a fresh checkout of GP and all versions of WMS now work ?

Thanx !

[adube]

Replying to yvesm:

• A fix the the MapServer issue when using 1.3.0 in OpenLayers, see ticket ​2478

That ticket isn't closed AFAICT. Is the patch mentioned in the ticket in OL trunk ? In short, do we just need a fresh checkout of GP and all versions of WMS now work ?

Thanx !

Yes, you only need to have a fresh checkout of GP and all WMS versions should work.

[yvesm]

There's a small bug in the GeoPrisma sample : if one select an area where there's only a province, one gets 1 grid with tab title = "GMap Provinces". If one clicks on a city, one gets two tabs with the same name (GMap Cities). Same behaviour when clicks on a Park + Province.

[adube]

Please open a new ticket explaining the bug since it has nothing to do with this one. Thanks for reporting.

[yvesm]

Replying to adube:

Please open a new ticket explaining the bug since it has nothing to do with this one. Thanks for reporting.

Right. See : #170

A somewaht related issue though is tried the following urls from my local version of the sample :

GetMap 1.3.0

​http://localhost:8081/gp/samples/queryonclick/wms130/proxy.php?osmservice=S_WMS_DEV4G_GMAP&osmtoken=TODO%20Delete%20this&osmresource[]=R_GMAP_PARK&osmresource[]=R_GMAP_POPP&VERSION=1.3.0&EXCEPTIONS=INIMAGE&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=popplace&SERVICE=WMS&REQUEST=GetMap&STYLES=&CRS=EPSG%3A42304&BBOX=-5175875.27581,-185762.06373449,6148285.27581,2047320.0637345&WIDTH=1605&HEIGHT=316

GetMap 1.1.1

​http://localhost:8081/gp/samples/queryonclick/wms130/proxy.php?osmservice=S_WMS_DEV4G_GMAP&osmtoken=TODO%20Delete%20this&osmresource[]=R_GMAP_PARK&osmresource[]=R_GMAP_POPP&VERSION=1.1.1&EXCEPTIONS=INIMAGE&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=popplace&SERVICE=WMS&REQUEST=GetMap&STYLES=&CRS=EPSG%3A42304&BBOX=-5175875.27581,-185762.06373449,6148285.27581,2047320.0637345&WIDTH=1605&HEIGHT=316

I thought specifying VERSION=1.1.1 would mean I need to invert the coordinates of my BBOX but it is not so. I get the same image back irrespective of the VERSION number. Why ?

Also, if I specify VERSION-1.1.25 (not an existing standard #), I still get an image back. Is it because MapServer has a default VERSION ?

What I'm trying to do is find out how to set up a WMS 1.3.0 server using MapServer so I can test locally. Apparently, specifying the version query parameter does not force the service to behave as that version ??

TIA