Signals Metadata

The Signals Metadata API provides detailed information about intersection metadata, including spatial dimensions, movement details, and geometric data. This API supports search functionality with location-based filtering.

Overview

The Signals Metadata API provides comprehensive intersection and movement information for spatial analysis and data discovery. Key capabilities include:

Intersection Discovery: Search and locate intersections within specific geographic areas using polygon, point, or line geometry
Movement Details: Access detailed information about traffic movements including inbound/outbound directions, turn types, and geometric data
Flexible Filtering: Filter by movement rank, turn maneuvers, directions, and movement types with powerful query operators
Location-Based Search: Support for radius-based searches around points, polygon containment, and corridor analysis along linestrings
Geometric Data: Access to LineString coordinates for movement paths enabling advanced spatial analysis and visualization
Pagination Support: Efficient data retrieval with configurable page sizes up to 10,000 intersections per query

Endpoint Summary

Base URL https://signals-api.inrix.com

Method	Path	Description
POST	`/v1/metadata/intersections`	Search provisioned intersection metadata using field filters and spatial geometry

Required Headers

Authorization: Bearer <token>
Content-Type: application/json

Request Schema

Field	Type	Required	Notes
`fields`	array	✓	Names of top-level or nested metadata fields to include.
`fieldFilters`	array		Filter objects with `name`, `operator`, and `expressions`. Defaults to rank 1 movements with no u-turns if omitted.
`locations`	array		GeoJSON shapes (Point + radius, Polygon, LineString + buffer) to constrain results.
`metadata`	object		Request map version overrides via `location` metadata array.
`pageSize`	integer		Defaults to 50; maximum 10,000 (no results returned beyond the first 10k intersections).
`offset`	integer		Zero-based paging offset; use with `pageSize` and respect 10k ceiling.

Filterable Fields

Field	Description	Supported Operators
`intersectionId`	Intersection identifier (lat_lon).	`EQUALS`, `IN_LIST`
`movements.rank`	Movement priority.	`EQUALS`, `IN_LIST`, `GREATER_THAN`, `GREATER_THAN_OR_EQUAL`, `LESS_THAN`, `LESS_THAN_OR_EQUAL`
`movements.movementType`	0 = standard, 1 = slip lane.	`EQUALS`, `IN_LIST`
`movements.turnManeuvers`	Turn classification.	`EQUALS`, `IN_LIST`
`movements.inbound.direction`, `movements.outbound.direction`	Cardinal or inter-cardinal directions.	`EQUALS`, `IN_LIST`

Location Search Patterns

Point + radius: Provide { "type": "Point", "coordinates": [lon, lat] } and radiusInMeters to capture nearby intersections.
Polygon: Supply closed coordinate rings to return intersections within the boundary.
LineString + buffer: Trace corridors and include radiusInMeters for lateral capture.

Metadata Options

metadata.location: Override default map version (mapVersion, country, state) when querying historical networks.

Response Fields

Field	Description
`createdDate`	Response timestamp.
`responseId`	Traceable request identifier.
`locations`	Echo of requested map metadata (if supplied).
`data`	Array of intersections containing requested fields (coordinates, movement arrays, inbound/outbound geometry, etc.).

Example

POST /v1/metadata/intersections
Content-Type: application/json

{
  "fields": [
    { "name": "intersectionId" },
    { "name": "name" },
    { "name": "coordinates" },
    { "name": "movements.id" },
    { "name": "movements.rank" },
    { "name": "movements.turnManeuvers" },
    { "name": "movements.inbound.direction" },
    { "name": "movements.outbound.direction" }
  ],
  "fieldFilters": [
    {
      "name": "movements.rank",
      "operator": "EQUALS",
      "expressions": [1]
    },
    {
      "name": "movements.turnManeuvers",
      "operator": "IN_LIST",
      "expressions": ["through", "left"]
    }
  ],
  "locations": [
    {
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [-122.3492, 47.6152],
            [-122.3405, 47.6152],
            [-122.3405, 47.6205],
            [-122.3492, 47.6205],
            [-122.3492, 47.6152]
          ]
        ]
      }
    }
  ],
  "pageSize": 100
}

Response excerpt (JSON):

{
  "createdDate": "2025-02-04T12:00:00Z",
  "responseId": "abc1234-def567-gh890",
  "data": [
    {
      "intersectionId": "47.6158_-122.3448",
      "name": "Aurora Ave N & Denny Way",
      "coordinates": {
        "lat": 47.6158,
        "lon": -122.3448
      },
      "movements": [
        {
          "id": "47.6158_-122.3448_d1",
          "rank": 1,
          "turnManeuvers": "through",
          "inbound": { "direction": "S" },
          "outbound": { "direction": "N" }
        }
      ]
    }
  ]
}

Documentation

SIGNALS