[mapserver-users] Mapserver Layer Filter

[Rahkonen Jukka]

Hi,

I made a test with a shapefile with ogrinfo as

>ogrinfo  -al roads.shp -sql "select * from roads where type!='motorway'"

It gives a correct result (everything that is not motorways). I would check first what happens with a type value which has just ASCII characters. Perhaps OGR just has troubles with  GRØFT.

-Jukka Rahkonen-
________________________________________
Eichner, Andreas wrote:


> You might try OGR Virtual Data Driver: http://www.gdal.org/ogr/drv_vrt.html.

>> -----Ursprüngliche Nachricht-----
>> Von: mapserver-users-bounces at lists.osgeo.org
>> [mailto:mapserver-users-bounces at lists.osgeo.org] Im Auftrag
>> von Hawk AA
> Gesendet: Donnerstag, 12. Januar 2012 17:24
> An: mapserver-users at lists.osgeo.org
> Betreff: [mapserver-users] Mapserver Layer Filter
>
> Hi there, Mailing List,
>
>
>
> We have a customer that wants their maps to be published
> online, but some of the features is confidential and should
> not be displayed.
>
>
>
> We have added following to the layer definition:
>
> FILTER ('[type]' != "GRØFT ")
>
> It works, the features with type GRØFT are not showed in the map.
>
>
>
> However, we have a window that let the user browse the data,
> and it will be possible to access the features of type GRØFT.
> When you press "show in map", the JavaScript clients triggers
> a WFS request with a filter asking for elements with the
> current ID. By doing this, WFS omits the LAYER FILTER
> definition, so the element can be showed in the map, even if
> it is of type GRØFT. I need a way to make sure the WFS can't
> deliver any data of type GRØFT.
>
>
>
> I've seen three possible solutions:
>
> 1.       We have a service that automatically converts
> uploaded MapInfo *.TAB-files to SHP. If I am correct, I could
> use the "-where"-argument on the ogr2ogr to filter data and
> only get features which does not have type GRØFT. I hope I do
> not have to do this, since debugging and developing a windows
> service is quite tricky.
>
> 2.       Add additional filter values to the WFS query. I
> could also define the types not to show in the JavaScript,
> and let the application automatically add
> <PropertyIsNotEqualTo>-tags to the AJAX query. This would be
> less secure, and I need to define types not to show at two places.
>
> 3.       The best solution in my eyes is to let the magic
> happen in the MAP-file, and that is mostly why I am posting
> here. Is there a way to add a query to the Layer Data
> definition, like you do if you are querying a MSSQL database?
> I can imagine a syntax like this:
> CONNECTIONTYPE OGR
> CONNECTION "TM_Nett/TM_Points"
> DATA "SELECT * FROM tm_points WHERE type!='GRØFT'"
> It does not seem to work.
>
>
>
> Any suggestions, especially regarding the third solution?
>
>
>
> Best regards,
>
> Håkon Åmdal
>
>
>
>
>
>
_______________________________________________
mapserver-users mailing list
mapserver-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users