Re: [mapserver-users] MapServer Layer Filter not applying to WFS

2012-11-07 Thread Hawk AA
] Sent: 5. november 2012 18:30 To: Hawk AA; mapserver-users@lists.osgeo.org Subject: RE: [mapserver-users] MapServer Layer Filter not applying to WFS One other idea. I believe you can avoid using OGR by adding your filter to class expressions and setting a template (which enables queries

[mapserver-users] MapServer Layer Filter not applying to WFS

2012-11-05 Thread Hawk AA
Hi there, mailing list, We have a customer sending us data with sensitive information. The most convenient way for us is to receive the complete data set and applying a filter in the mapfile. The layer definition looks like this: LAYER NAME Traseer

[mapserver-users] Connectiontype OGR with shapefile encoding

2012-11-05 Thread Hawk AA
Hi, You’ve probably had it with encoding issues, but I can’t seem to figure it out. I sure hope the Mailing List can help me with this one. I have a shapefile encoded in latin1 . Until recently I have been able to use CONNECTIONTYPE OGR to access that table like this: CONNECTIONTYPE

Re: [mapserver-users] Mapserver Layer Filter

2012-01-13 Thread Hawk AA
Hi all, Thank you for splendid support. I solved the problem by coincidence. By using the OGR driver to view the shape-file and using FILTER, the WFS would not be able to fetch the hidden data. CONNECTIONTYPE OGR CONNECTION TM_Nett/TM_Points.shp FILTER('[Type]' != SKAP)

[mapserver-users] Mapserver Layer Filter

2012-01-12 Thread Hawk AA
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

[mapserver-users] Post body is short

2011-12-04 Thread Hawk AA
Hi there, We are running a service where the access to mapfiles needs to be password protected. I’m using PHP Session for that, and until recently I’ve used a wrapper which looked like this: session_start(); $oParams = new HawkSoftware\URL\REQUESTParameters(); try {

Re: [mapserver-users] WFS Typename behavior

2011-09-29 Thread Hawk AA
for Traseer and Punkter. Otherwise it looks like a bug. -Jukka Rahkonen- Havard Tveite wrote: Ldhetetty: 22. syyskuuta 2011 9:26 I think that you have to use only one Typename per WFS request. Hevard On 9/20/2011 8:09 PM, Hawk AA wrote: Hi, It seems for me that by entering multiple layers

[mapserver-users] WFS Typename behavior

2011-09-20 Thread Hawk AA
Hi, It seems for me that by entering multiple layers in Typename, I am not getting the same results. For instance would using Typename=Traseer give me all of the geometries in the BBOX, but Typename=Traseer, Punkter will give me all in Punkter, but only some geometries from Traseer. Is it

[mapserver-users] Mapserver and MapScript performance issue

2011-09-09 Thread Hawk AA
Hi, First of all, thank you for Mapserver and all of the documentation. It’s really a great product. I’m having some performance issues when querying on a column in MapScript. I use the following code: $oResult = @$oLayerObject-queryByAttributes($strField, $strSearchString,