Feature Service

​

Service URL

https://app.arterial.us/api/arcgis/arterial/FeatureServer

​

Layers

​

Service manifest

GET /api/arcgis/arterial/FeatureServer?f=json&token=...

​

Layer descriptor

GET /api/arcgis/arterial/FeatureServer/{layerId}?f=json&token=...

​

Querying features

GET /api/arcgis/arterial/FeatureServer/{layerId}/query
    ?f=json
    &where=1%3D1
    &outFields=*
    &resultOffset=0
    &resultRecordCount=1000
    &returnGeometry=true
    &token=...

• f — json (default), pjson, or geojson. Use geojson to pull the layer straight into QGIS or a Mapbox style.
• where — must be 1=1. Custom predicates are not supported on this read-only mirror; subscribe to a sub-layer instead.
• outFields — * for all attributes, or a comma-separated list of field names.
• objectIds — comma-separated list of OBJECTID values to fetch.
• resultOffset / resultRecordCount — pagination. The maximum page size is 1000 records.
• returnGeometry — set false to omit geometry (handy for attribute-only joins).
• returnCountOnly — returns { count: N } and skips the feature payload.
• returnIdsOnly — returns the array of OBJECTID values only.

​

Attribute schemas

​

Hazards (/0, /5, /6)

​

Coverage cells (/1, /7, /8, /9)

​

Detections (/3, /10, /11)

​

Service area (/4)

​

Adding the service to ArcGIS Online

1. In ArcGIS Online, open Map Viewer and choose Add → Add layer from URL.
2. Paste the service URL with your token appended: https://app.arterial.us/api/arcgis/arterial/FeatureServer?token=artgis_…
3. ArcGIS reads the manifest and shows the layer list. Add as many as you want — top-level layers, sub-layers, or both.
4. Save the map. When the underlying data updates, refresh the layer from the layer settings menu.

​

Adding the service to QGIS

1. Open Layer → Add Layer → Add ArcGIS REST Server Layer.
2. Use New Connection, paste the service URL (without /0 — FeatureServer root only), and store the token in the query string.
3. Choose the layers you need from the connection’s layer list.

​

Multi-layer shapefile export

{
  "version": 1,
  "generatedAt": "2026-05-10T17:42:00.000Z",
  "layers": [
    {
      "id": 0,
      "key": "hazards.all",
      "name": "Hazards",
      "geometryType": "esriGeometryPoint",
      "featureCount": 1842
    },
    {
      "id": 4,
      "key": "service_area.all",
      "name": "Service Area",
      "geometryType": "esriGeometryPolygon",
      "featureCount": 1
    }
  ]
}

​

Multi-layer ESRI JSON export

{
  "version": 1,
  "exportedAt": "2026-05-10T17:42:00.000Z",
  "layers": [
    {
      "id": 0,
      "key": "hazards.all",
      "name": "Hazards",
      "geometryType": "esriGeometryPoint",
      "fields": [{ "name": "OBJECTID", "alias": "Object ID", "type": "esriFieldTypeOID" }, …],
      "result": {
        "exceededTransferLimit": false,
        "totalCount": 1842,
        "features": [{ "attributes": { … }, "geometry": { … } }, …]
      }
    },
    …
  ]
}

​

Limits and quirks

• Read-only — the service does not support applyEdits.
• where=1=1 is the only supported predicate. Filter by subscribing to the relevant sub-layer instead.
• Page size is capped at 1000 records. Iterate resultOffset to stream large layers.
• Coverage cells query against an H3 resolution-9 grid clipped to your service area. The lookback window for a single query is one year.
• Orphan detections are scoped to your org by checking each detection’s (latitude, longitude) against your service-area polygon — a detection that drifts outside the polygon will not appear in /11.