[Geomoose-users] WFS in GM3

TC Haddad tchaddad at gmail.com
Wed Sep 6 10:43:17 PDT 2017


 WEB
METADATA
'ows_title' 'taxlots'
'ows_srs' 'EPSG:3857'
'ows_enable_request' '*'
'ows_onlineresource' 'http://www.geomoose.org'
'wfs_srs' 'EPSG:2269 EPSG:4326 EPSG:3857 EPSG:900913'
'wms_feature_info_mime_type' 'application/json'
'wfs_getfeature_formatlist' 'gml,geojson'
END
END

On Wed, Sep 6, 2017 at 5:11 AM, Dan Little <theduckylittle at gmail.com> wrote:

> Okay, I'm back at it.
>
> I suspect it's due to how MapServer treats the *order* of the projections
> in the WEB definition.  Can you post that?
>
> On Mon, Aug 28, 2017 at 4:23 PM, TC Haddad <tchaddad at gmail.com> wrote:
>
>>
>> Yep, the WFS draws nicely from the GML response, so in that way,
>> projections are all happy...
>>
>>
>>
>> On Mon, Aug 28, 2017 at 2:03 PM, Dan Little <theduckylittle at gmail.com>
>> wrote:
>>
>>> Does the WFS layer *draw* on the map? (Define some styles,and then add a
>>> catalog item for it.)
>>>
>>> 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.
>>>
>>>
>>> On Mon, Aug 28, 2017 at 3:32 PM, TC Haddad <tchaddad at gmail.com> wrote:
>>>
>>>>
>>>> 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:
>>>>
>>>> - local data draws fine
>>>>
>>>> - Identify uses WMS GetFeatureInfo, and works fine
>>>>
>>>> - 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.
>>>>
>>>> troubleshooting:
>>>>
>>>> - 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...
>>>>
>>>> - 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...
>>>>
>>>>
>>>> Any ideas where else I can look for issues?
>>>>
>>>> _______________________________________________
>>>> Geomoose-users mailing list
>>>> Geomoose-users at lists.osgeo.org
>>>> https://lists.osgeo.org/mailman/listinfo/geomoose-users
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20170906/772227f2/attachment.html>


More information about the Geomoose-users mailing list