Query in PBF Format Returns Incorrect Geometry for POINT ZM Features

SaurabhDudhe

Hi Team,

We're seeing an issue when querying a feature layer using PBF (f=pbf) output format. The returned geometry is incorrect for a specific POINT ZM feature, while the same query using JSON (f=json) returns the correct geometry.

Feature Details

Feature ID: 1596769

The geometry stored in the database is:

POINT ZM (-117.586861 55.966933 -1851.2248 -1865.0)

Query

https://<server>/api/v1/map/arcgis/rest/services/<MAP_ROOT_FOLDER>/<PROJECT_NAME>/MapServer/1/query?f=pbf&geometry=...&outFields=*&spatialRel=esriSpatialRelIntersects&geometryType=esriGeometryPolygon&inSR=102100&outSR=102100

PBF Response

The feature is returned successfully, but the geometry is invalid:

{
  "features": [
    {
      "geometry": {
        "spatialReference": {
          "latestWkid": 3857,
          "wkid": 102100
        },
        "x": 961550052,
        "y": -1011691100
      },
      "attributes": {
        "ID": 1596769
      }
    }
  ]
}

The returned coordinates (x, y) are clearly incorrect and do not correspond to the actual location of the feature.

JSON Response

When the same query is executed with f=json, the geometry is returned correctly and the feature is displayed at the expected location.

Comparison

We also tested another feature with a standard 2D POINT geometry:

ID: 1594692
POINT (-117.581053 55.964658)

For this feature, both PBF and JSON responses return the correct geometry.

Question

Has anyone encountered an issue where PBF queries return incorrect geometry for POINT ZM features, while JSON works correctly?

• Is this a known limitation or bug in PBF encoding/decoding for POINT ZM geometries?

• Are there any ArcGIS Server settings, service configurations, or known fixes related to this behavior?

• Has anyone observed similar issues with Z/M-enabled feature classes?

Any guidance would be greatly appreciated.

Thank you!