Routing

Road attributes along a matched GPS trace

Trace attributes return road/network attributes for matched traces — match a GPS breadcrumb trail to the road network and get per-segment road names, classes, speed limits, surfaces, and truck-route flags, plus the matcher's confidence. Sparsely-reported traces (consecutive fixes farther apart than the default breakage distance) can split into multiple sections — see breakage_distance_m. Total matched distance is limited to 200 km per call; split longer sparse traces by distance, not only by the 100-point cap. Costs 1 quota unit per call.

post/v1/trace-attributes

Request

  • Base URL: https://geo.thinair.co
  • URL: https://geo.thinair.co/v1/trace-attributes
  • Auth: HTTP bearer

Request body

costing'auto' | 'truck' | 'bicycle' | 'pedestrian'

Transport mode the trace was driven with. Default: auto.

vehicle_profilestring

Truck preset (DRY_VAN_53, FLATBED_48, BOX_TRUCK_26, …) — same 10-profile table as /v1/directions. Implies costing=truck.

search_radiusnumber

Snap radius in meters around each point (1–100). Increase for noisy GPS.

breakage_distance_minteger

Maximum gap, in meters, between consecutive fixes before the trace is split into separate sections (100–20000). Increase for sparsely-reported GPS, such as fleet units reporting every several minutes on a highway. Optional — omitted uses the default.

Example request

{
  "shape": [
    {
      "lat": 47.6205,
      "lon": -122.3493
    }
  ],
  "costing": "auto"
}

Response

Per-segment attributes for the matched trace.

matchedboolean required
confidencenumber required

Matcher confidence 0–1.

distance_kmnumber required
duration_secondsnumber
edge_countnumber required
road_namesstring[] required
adminsobject[]
costingstring required
geojsonobject
geometryobject

Changes

No recorded changes to this operation across all 1 revision of this API.