ce.army.mil]
> Sent: June 12, 2013 8:57 AM
> To: Kralidis,Tom [Ontario]; steve.tout...@inspq.qc.ca
> Cc: mapserver-users@lists.osgeo.org; mapserver-users-
> boun...@lists.osgeo.org
> Subject: RE: [mapserver-users] RE WMS layer filtering (UNCLASSIFIED)
>
> Classification: UNCLASS
: steve.tout...@inspq.qc.ca
Cc: mapserver-users@lists.osgeo.org; mapserver-users-boun...@lists.osgeo.org
Subject: Re: [mapserver-users] RE WMS layer filtering
Steve: thanks for the info. Good point. It would help, however the client
would require apriori knowledge, which won't help in our
Does runtime substitution can help?
You could post latest_observation=1 when calling the wms and 0 and 1 when
using the wfs
the filter would be latest_observation in (%param%)
"Kralidis,Tom [Ontario]" @lists.osgeo.org
Envoyé par : mapserver-users-boun...@lists.osgeo.org
2013-06-12 08:23
A
Steve: thanks for the info. Good point. It would help, however the client
would require apriori knowledge, which won't help in our case because we want
things more generic.
Of course, there's always MapScript (i.e. set LAYER.FILTER only if it's a WMS
GetMap/GetFeatureInfo request), but I was
