WFS Error and Lacking Geometry

bharvey

I have a WFS Service I publish from ArcGIS Server.    I have used several clients to test and the service either does not display the geometry or it just throws an error.   The layer shows up in the TOC, I can access, and in some cases I can get to the attributes.    The ArcGIS MAP Service will load fine and I get geometry and attributes correctly.   Once I do that, I can find the geometry of the WFS, but it is off in a totally different area and rotated 90 degrees.   The MAP Service and WFS are the same publish with WFS capabilities set when I publish the .mxd.  MAP Service ok, WFS an issue....

When I load the service into ArcGIS Portal it seems to display fine.    Unfortunately,  that is just a test and clients need to get at the service through WFS without ArcGIS Portal.

When I view in Bentley/GAIA/GRASS/QGIS, and others, I get a different error.   Again, the layers show up in TOC in all of the products I have tested but throw various errors or totally skewed geometry.

Here is an error I get in QGIS when I test it for example.   

Layer xyz.GRID_SPACING_MAP: Download of features for layer Bentley_SpacingMap:xyz.GRID_SPACING_MAP failed or partially failed: Download of features failed: Error downloading https://xyz/arcgis/services/xyz/SpacingMap/MapServer/WFSServer?SERVICE=WFS&REQUEST=GetFeature&VERSION=2.0.0&TYPENAMES=xyz_SpacingMap:xyz.GRID_SPACING_MAP&SRSNAME=urn:ogc:def:crs:EPSG::4431&BBOX=1080020.71277404553256929,12232953.25763050653040409,1354911.23849608213640749,12477890.19503248669207096,urn:ogc:def:crs:EPSG::4431 - server replied: Bad Request. You may attempt reloading the layer with F5

The services pull data from ArcSDE, however I also tried from a File Geodatabase as a test and got the same results.

Thanks.

Bill Harvey

bharvey

It turns out this is a bug.

> Note in 10.3 the ObjectID is displayed, in 10.5 the ObjectID is
> omitted. **BUG-000110388**: ObjectID and GlobalID fields are not
> exposed in WFS services in ArcGIS server 10.5.x.
>
> There was an architecture change for WFS services at 10.5 release
> which included many improvements to become WFS 2.0.0 compliant. At
> 10.5 design decision was made to use the gmlid as the primary key for WFS services, as according to OGC specification. Since gmlid is used
> as the primary key, the old primary keys (objectid, globalid) are
> filtered out. It is better practice to use the gmlid as the primary
> key since it is required by all WFS services according to spec,
> whereas the objectid field is an Esri specific field and not all WFS
> services may have it.
>
> This defect brings awareness to the need of objectid/globalid fields
> as they may play a critical role in third party platforms consuming
> Esri WFS services. Fortunately, the defect is currently in our
> production plan to be addressed in a future release. For updates,
> please see the My Esri