MapServer / WFS Request Issue

[theduckylittle]

The following is causing a boundedBy null error:

<GetFeature
 xmlns="http://www.opengis.net/wfs" service="WFS" version="1.1.0" outputFormat="text/xml; subtype=gml/2.1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd"><Query
 typeName="ms:Devices" srsName="EPSG:4326"><Filter xmlns="http://www.opengis.net/ogc"><Intersects><PropertyName>geom</PropertyName><Point xmlns="http://www.opengis.net/gml"><pos>-93.35131436860924 44.970039488140685</pos></Point></Intersects></Filter></Query></GetFeature>

This request is generated when doing an Identify on a WFS layer.

[brentfraser]

Can this be closed?

[jmckenna]

Good question. From testing the MS4W.dev demo, performing an identify on the parcels layer generates a valid WFS (MapServer) GetFeature response, and nicely shows the attributes in the left panel.

But that identify on the WFS (TinyOWS) layer "census cities" shows an error in the left panel (however the GetFeature response from TinyOWS looks valid: https://ms4w.dev/cgi-bin/tinyows.exe?typename=MS4W%3Acensus_cities

Maybe others can try this on https://ms4w.dev/gm3/desktop/index.html as I might be doing the steps wrong.

(it probably has to do with me not setting a template for this layer). I believe we can close this ticket.

[elil]

Identify on Census Cities of ID: 1001 (over in Newport Oregon) seems to work properly. For other features, I got errors. I noticed in some areas there are multiple "stacked" features. Maybe this is part of the error?

…

On Fri, Oct 15, 2021 at 12:04 PM Jeff McKenna ***@***.***> wrote: Good question. From testing the MS4W.dev demo, performing an identify on the parcels layer generates a valid WFS (MapServer) GetFeature response, and nicely shows the attributes in the left panel. But that identify on the WFS (TinyOWS) layer "census cities" shows an error in the left panel (however the GetFeature response from TinyOWS looks valid: https://ms4w.dev/cgi-bin/tinyows.exe?typename=MS4W%3Acensus_cities Maybe others can try this on https://ms4w.dev/gm3/desktop/index.html as I might be doing the steps wrong. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#236 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIE7GUWOQ2BXHVD5GKA2MDUHB3MDANCNFSM4D6XSRHA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[jmckenna]

ah true, yes could be.

[elil]

Hmm, looking at this more closely, identify on the "eye" of the elk gets an error too. I think the eye is an area of stacked geometries. I don't think that I made a hole in a polygon but don't actually remember since it was a long time ago.

…

On Fri, Oct 15, 2021 at 1:15 PM Jeff McKenna ***@***.***> wrote: ah true, yes could be. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#236 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIE7GWYOSBKHHDYK7CD2BDUHCDWHANCNFSM4D6XSRHA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[elil]

Maybe look at the backend data for attributes? Is the presence or absence of ID or other attributes impacting this?

…

On Fri, Oct 15, 2021 at 1:18 PM Eli Adam ***@***.***> wrote: Hmm, looking at this more closely, identify on the "eye" of the elk gets an error too. I think the eye is an area of stacked geometries. I don't think that I made a hole in a polygon but don't actually remember since it was a long time ago. On Fri, Oct 15, 2021 at 1:15 PM Jeff McKenna ***@***.***> wrote: > ah true, yes could be. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#236 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABIE7GWYOSBKHHDYK7CD2BDUHCDWHANCNFSM4D6XSRHA> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > >

[chughes-lincoln]

It looks like it's associated with identifying a polygon that has no attributes.

If you had zoomed out you would have seen a very large polygon covering much of the US (so also covering all the other polygons you were querying). After removing that feature, the identify starts working.

I then recreated the issue by adding a polygon over another polygon without adding any attributes (Identify returned same red error).

I then tried adding a polygon over another polygon with attributes and it worked.

[chughes-lincoln]

So back to the original point, this isn't related to the original issue.

[brentfraser]

I think the error on Identify is similar to #652