Timeline for OpenLayers spatial filter polygon problem
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 31, 2012 at 9:21 | comment | added | Pete | That bit of code now uses a BBOX. The selection is being carried out using a beforefeatureadded on a polygon layer. The user draws a polygon into the polyLayer layer, and that should select any intersecting polgons from CountyLayerDay2. As this now looks to be something to do with SQL Server as opposed to a projection issue, I'm wondering if this should be opened as a new question? | |
| Oct 30, 2012 at 20:11 | comment | added | geographika | You are using a OpenLayers.Strategy.Fixed() strategy that requests all features once when the map is loaded. It is not clear to me how you are doing a selection. If MapServer is set to return a single result then it could be any arbitrary feature in the dataset. | |
| Oct 30, 2012 at 17:15 | comment | added | Pete | Abit more info, if I do a GetFeature request and specify a filter manually using BBOX, Envelope and uppercorner \ lowercorner tags in the URL, I get the correct response. To me it looks like using a SQL Server 2008 dataset is affecting the way the filter is being formed on the web page before being passed to OpenLayers. | |
| Oct 30, 2012 at 16:27 | comment | added | Pete | I've removed any multipart features and there is still no change. I've tweaked my layer definition in my aspx page so that I can now switch easily between shp and sql data by altering the mapfile specified in the URL. There are no differences in terms of projections etc specified in the map files, I've been through them line by line. Using a shapefile the intersect works perfectly but with the SQL connection it still produces a massively different polygon from what I've drawn before carrying out the intersect. I'm now officially out of ideas... | |
| Oct 30, 2012 at 14:57 | comment | added | geographika | MULTILINESTRING types have issues in MapServer, so this may be the same with MULTIPOLYGONS. I'd recommend splitting them into single part features and seeing if the issue remains. | |
| Oct 30, 2012 at 14:43 | comment | added | Pete | I've now got WFS version 1.1.0 working but am still having some issues. I have to have a reference to EPSG:4326 in my mapfile Web--MetaData--wfssrs otherwise I get a "Invalid GetFeature Request:Invalid SRS" error in my response. I've no other references to anything 4326 so not sure why this is needed. With 4326 added, I can see the XML response coming back, but no polygons appear on screen. I can even draw a polygon filter and see the response alter. However, as soon as I use SQL instead of shp, I get the same issue as my original posts, just a multisurface now due to using WFS 1.1.0 | |
| Oct 30, 2012 at 13:14 | comment | added | geographika | Your protocol constructor should be this: dev.openlayers.org/docs/files/OpenLayers/Protocol/WFS/… | |
| Oct 30, 2012 at 13:02 | comment | added | Pete | Thanks for the link and additional information. When I switch to WFS version 1.1.0 in my WFS protocol, I notice that the format of what is returned alters and I get no features returned. This is the case when i switch from 1.0.0 to 1.1.0 using my shapefile data. Do I need to change some other configuration settings somewhere? I've seen GML2 and GML3 formats mentioned but haven't had any luck utilising them. I'm seeing bounding boxes being replaced by envelopes that use lower / upper corner tags, rather than a string of coordinates, to define them. | |
| Oct 29, 2012 at 18:55 | history | answered | geographika | CC BY-SA 3.0 |