and here is the exact geometry sent to QGIS (to compare to your own
GetFeature sent to QGIS):
https://demo.gatewaygeomatics.com/cgi-bin/wfs_gateway?SERVICE=WFS&REQUEST=GetFeature&VERSION=2.0.0&TYPENAMES=ms:park&TYPENAME=ms:park&STARTINDEX=0&COUNT=1000&SRSNAME=urn:ogc:def:crs:EPSG::4326&BBOX=-49.617463797383067,-177.44289621794916911,174.79117094839176616,-9.03851063211465089,urn:ogc:def:crs:EPSG::4326
If all else fails, it could be an issue with your dataset's geometry.
Next I would test on your same server with another simple dataset (to
cancel out possible issue of library on your server).
Then, if you narrow it down to that one exact dataset, I'd bring it into
GRASS GIS to rebuild geometry (others will have more elegant ways, but
that has worked for me for 20 years ha).
Be well,
-jeff
--
Jeff McKenna
MapServer Consulting and Training Services
https://gatewaygeomatics.com/
On 2020-03-19 8:30 a.m., Jeff McKenna wrote:
Hi Brent,
Odd, I have not seen that exact error before. But there could be a
problem with the geometry returned. Be sure to set the
"gml_include_items" and "gml_featureid" metadata in your layer in the
mapfile. (see examples at https://mapserver.org/ogc/wfs_server.html
)
Also, here is a proper DescribeFeatureType response, in case that helps
to see (save response as .xml and open in text editor)
https://demo.gatewaygeomatics.com/cgi-bin/wfs_gateway?SERVICE=WFS&REQUEST=DescribeFeatureType&VERSION=2.0.0&TYPENAMES=ms:park&TYPENAME=ms:park
Oh, and use Richard's great QGIS Network Logger plugin to get your exact
DescribeFeatureType url (to compare to my server's response above).
Cheers from the east coast of Canada,
-jeff
_______________________________________________
Qgis-user mailing list
[email protected]
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
