Hi,
Repeating myself: It never hurts to read the whole documentation.
You should not include layers etc. into CONNECTION as stated in the WMS client
documentation.
“CONNECTION - this is the remote server’s online resource URL, just the base
URL without any of the WMS parameters. The server
Hi,
It never hurts to read the whole documentation ☺
There is 'ows_name' 'rt_cat' in the mapfile and the manual page says also:
Note
Note that each of the above metadata can also be referred to as ‘ows_*’ instead
of ‘wms_*’. MapServer tries the ‘wms_*’ metadata first, and if not found it
Or you could create a calculated column in the data statement, call it e.g.
"AGE" being the result of the difference of your original date column and
the oracle sysdate.
Then you can easily use that "AGE" column to do your styling.
HTH
Martin
--
View this message in context:
hello,
I can correctly visualize a wms layer with mapserver and pmapper as:
CONNECTION
'http://web.regione.toscana.it/wmsraster/com.rt.wms.RTmap/wms?map=wmscatasto'.
If I add the parameter, it still works, but no selection of the
choosen layers is done (while in Qgis it is possible):
Peter,
It never hurts to read the documentation:
http://mapserver.org/ogc/wms_client.html#mapfile-configuration . Namely the
part where the "wms_name" metadata key is required and what you need.
--
Thomas
On 4 April 2016 at 10:56, pippi wrote:
> hello,
>
> I can
Thank you very much Rahkonen and Thomas, it works fine
Peter
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/selecting-a-wms-layer-tp5259459p5259493.html
Sent from the Mapserver - User mailing list archive at Nabble.com.
___
I went the view route for the time being, to get one of the class types (layer)
up and running. I was basing my questions on the fact that I’ve successfully
passed in all sorts of SQL into the Postgres connector with MapServer, but the
Oracle connector seems to be some limited in what it can
On 2016-04-04 12:33 AM, Inna Nogeste wrote:
Hi Thomas,
After many attempts using the same expression syntax it finally worked.
Is there any reason as to why the following expression syntax didn’t
work the first time?
You could be hitting a weird issue in your DBF file, where your
attributes
By the way, I have seen odd problems with column types happen after
exporting or importing from other formats. So be careful, and always
use ogr2ogr for converting :)
-jeff
--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/
On 2016-04-04 12:33 AM,