Hi Jody,
Thanks for an excellent reply.
I’ll go have a look at the ENV parameter and try and get it to provide a default if none is supplied.
I take it that configuring…
<ogc:Function name=“env”> ogc:Literaldistance</ogc:Literal> ogc:Literal6</ogc:Literal> </ogc:Function>
into the layer style will mean that a WHERE clause such as…
SELECT … WHERE distance = 6 ;
is always going to be present in the query (unless) &env=distance:10 is supplied in the request then…
SELECT … WHERE distance = 10 ;
…will be executed. If so that is great.
But I don’t understand if/how it would work alongside the CQL_FILTER && WMTS… sorry, I think this is my lack of knowledge.
Huge thanks!
Andrew
On Wed, 23 Oct 2024 at 20:29, Jody Garnett via OSGeo Discourse <noreply@discourse.osgeo.org> wrote:
|
jive Leader October 23 |
Welcome @ahhughes thanks for joining us here.
I had to look up the CQL_FILTER in WMTS to learn what you are talking about, and I am still not sure what you mean by validate a CQL_FILTER.
WMS supports both:
- FILTER the official OGC parameter using CQL which does “property operation expression” filters
- CQL_FILTER - our extension ECQL which allows for “expression operation expression” filters
I expect you mean WMS vendor parameter ENV.
&env=distance:10
This allows defaults and is intend to be used to adjust the style easily.
<ogc:Function name="env">
<ogc:Literal>distance</ogc:Literal>
<ogc:Literal>6</ogc:Literal>
</ogc:Function>
All of these things change the style a lot, so configuration is needed in WMTS in order to allow it to create a separate tile cache for different values of distance
above.
That can be used to record a tileset for different values of the CQL_FILTER parameter; however there is nothing special going on, it is only if the value matches a tile will be recorded. Any CQL_FILTER can be provided to WMS.
To better restrict WMS use env
function above, or if you really like use env
to supply a value with a default, and then recode
to choose a longer expression based on the value provided.
Visit Topic or reply to this email to respond.
To unsubscribe from these emails, click here.