Re: [MapServer-users] converting an expression to an OGC filter

2022-12-02 Thread Eichner, Andreas - SID 
Your pattern seems to be wrong. You originally used a case insensitive regex 
0..$ meaning a value shall end with a '0' and to other arbitrary characters. 
Your PropertyIsLike filter is translated into an SQL "like": (for Postgres)
  postcode::text ilike '_%0__'
meaning a string as a whole shall consist of an arbitrary character followed by 
zero or more arbitrary characters followed by a '0' and two additional 
arbitrary characters. The corresponding regex would look like ^..*0..$
So I guess you would like want to use *0.. as pattern:
  
postcode
*0..
  

Regards, Andreas

-Ursprüngliche Nachricht-
Von: MapServer-users  Im Auftrag von 
Ian Turton
Gesendet: Freitag, 2. Dezember 2022 10:48
An: steve.l...@state.mn.us; mapserver-users@lists.osgeo.org
Betreff: Re: [MapServer-users] converting an expression to an OGC filter


On Thu, 1 Dec 2022 at 22:13, Lime, Steve D (MNIT) mailto:steve.l...@state.mn.us> > wrote:


Hi Ian: What’s the backend (e.g. shapefile, PostGIS, etc…)? MapServer 
expressions don’t support a wildcard operator (outside of a regex) so I’m not 
sure off the top of my head and things may vary by driver.


It's a postgis database on the backend, the original expression works fine but 
not when it's input as an OGC expression.

Ian 




 

--Steve

 

From: MapServer-users mailto:mapserver-users-boun...@lists.osgeo.org> > On Behalf Of Ian Turton
Sent: Thursday, December 1, 2022 9:50 AM
To: mapserver-users@lists.osgeo.org 
<mailto:mapserver-users@lists.osgeo.org> 
Subject: [MapServer-users] converting an expression to an OGC filter

 

I currently have an expression in my mapfile EXPRESSION ('[postcode]' 
~* '0..$') and I'm in the process of moving to using SLD for styling - I 
thought I could convert that expression to 

 

 
postcode
.*0..
  
Which I think should match from the start of the string (.*) to a 0 and 
then two characters (..) to the end of the string. But it doesn't work - 
neither does any variant on this work either.
Is there some issue with conversions between SLD Filters and internal 
expressions that I'm missing or is there something else I should know about 
LIKE filters?

Thanks

 

Ian

-- 

Ian Turton



-- 

Ian Turton



smime.p7s
Description: S/MIME cryptographic signature
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [MapServer-users] converting an expression to an OGC filter

2022-12-02 Thread Ian Turton 
On Thu, 1 Dec 2022 at 22:13, Lime, Steve D (MNIT) 
wrote:

> Hi Ian: What’s the backend (e.g. shapefile, PostGIS, etc…)? MapServer
> expressions don’t support a wildcard operator (outside of a regex) so I’m
> not sure off the top of my head and things may vary by driver.
>

It's a postgis database on the backend, the original expression works fine
but not when it's input as an OGC expression.

Ian

>
>
> --Steve
>
>
>
> *From:* MapServer-users  *On
> Behalf Of *Ian Turton
> *Sent:* Thursday, December 1, 2022 9:50 AM
> *To:* mapserver-users@lists.osgeo.org
> *Subject:* [MapServer-users] converting an expression to an OGC filter
>
>
>
> I currently have an expression in my mapfile EXPRESSION ('[postcode]' ~*
> '0..$') and I'm in the process of moving to using SLD for styling - I
> thought I could convert that expression to
>
>
>
>   matchCase="false">
>
> postcode
>
> .*0..
>
>   
>
> Which I think should match from the start of the string (.*) to a 0 and then 
> two characters (..) to the end of the string. But it doesn't work - neither 
> does any variant on this work either.
>
> Is there some issue with conversions between SLD Filters and internal 
> expressions that I'm missing or is there something else I should know about 
> LIKE filters?
>
> Thanks
>
>
>
> Ian
>
> --
>
> Ian Turton
>


-- 
Ian Turton
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users