<div dir="ltr">Can you try commenting out wfs_srs and copying all the projection codes into the ows_srs line? MapServer has some really obnoxious quirks WRT how the projections are defined for the OGC services.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 6, 2017 at 12:43 PM, TC Haddad <span dir="ltr"><<a href="mailto:tchaddad@gmail.com" target="_blank">tchaddad@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><span style="white-space:pre-wrap"> </span>WEB</div><div><span style="white-space:pre-wrap"> </span>METADATA</div><div><span style="white-space:pre-wrap"> </span>'ows_title' 'taxlots'</div><div><span style="white-space:pre-wrap"> </span>'ows_srs' 'EPSG:3857'</div><div><span style="white-space:pre-wrap"> </span>'ows_enable_request' '*'</div><div><span style="white-space:pre-wrap"> </span>'ows_onlineresource' '<a href="http://www.geomoose.org" target="_blank">http://www.geomoose.org</a>'</div><div><span style="white-space:pre-wrap"> </span>'wfs_srs' 'EPSG:2269 EPSG:4326 EPSG:3857 EPSG:900913'</div><div><span style="white-space:pre-wrap"> </span>'wms_feature_info_mime_type' 'application/json'</div><div><span style="white-space:pre-wrap"> </span>'wfs_getfeature_formatlist' 'gml,geojson'</div><div><span style="white-space:pre-wrap"> </span>END</div><div><span style="white-space:pre-wrap"> </span>END</div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 6, 2017 at 5:11 AM, Dan Little <span dir="ltr"><<a href="mailto:theduckylittle@gmail.com" target="_blank">theduckylittle@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Okay, I'm back at it.<div><br></div><div>I suspect it's due to how MapServer treats the *order* of the projections in the WEB definition. Can you post that?</div></div><div class="m_1016295554899498138HOEnZb"><div class="m_1016295554899498138h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 28, 2017 at 4:23 PM, TC Haddad <span dir="ltr"><<a href="mailto:tchaddad@gmail.com" target="_blank">tchaddad@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div>Yep, the WFS draws nicely from the GML response, so in that way, projections are all happy...<br><br><br></div><div class="m_1016295554899498138m_-661799767697438913HOEnZb"><div class="m_1016295554899498138m_-661799767697438913h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 28, 2017 at 2:03 PM, Dan Little <span dir="ltr"><<a href="mailto:theduckylittle@gmail.com" target="_blank">theduckylittle@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Does the WFS layer *draw* on the map? (Define some styles,and then add a catalog item for it.)<div><br></div><div>I suspect a projections issue as well. The reason the query happens in 4326 is due to some MapServer projection bugs that I had found while doing the dev work. The easiest way to handle it was to use 4326 for the query.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_1016295554899498138m_-661799767697438913m_6993483088836381028h5">On Mon, Aug 28, 2017 at 3:32 PM, TC Haddad <span dir="ltr"><<a href="mailto:tchaddad@gmail.com" target="_blank">tchaddad@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_1016295554899498138m_-661799767697438913m_6993483088836381028h5"><div dir="ltr"><div><div><br></div>I'm working my way through setting up GM3 with some local parcel data, and am having issues with the portions that use WFS. Here's what's happening:<br></div><div><br></div><div>- local data draws fine<br></div><div><br></div><div>- Identify uses WMS GetFeatureInfo, and works fine</div><div><br></div><div>- Search and Select both use WFS and seem to generate valid queries. They do not return an error when used, but do return an empty set of results.</div><div><br></div><div>troubleshooting:<br></div><div><br></div><div>- Search: figured out that there was a hard-coded field name in search.js that wasn't mentioned in the docs, but after fixing that, I'm still not getting any results from search...</div><div><br></div><div>- Select: seems to be passing valid coordinates in 4326 to the WFS. The data is in 3857. The data is drawing correctly so I'm assuming the map file is fine, but no results come back, so wondering about projection issues for this one...<br></div><div><br></div><div><br></div><div>Any ideas where else I can look for issues? <br></div></div>
<br></div></div>______________________________<wbr>_________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/geomoose-users</a><br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>