This is the documentation for the TrafficView API v3.13.5. The API allows users to query various types of data from the RITIS databases, e.g. traffic incidents, dynamic message signs, weather.
This document is a work in progress and subject to change at any time (see change log).
If you have additional questions, please email us at support@trafficview.org.
TrafficView is currently restricted to authorized users. You can request an API key.
If you need an additional API key for your system, please email us at support@trafficview.org.
The /event endpoint returns event data. For other data types, see Endpoints.
For a complete list of GET parameters, see Filters.
Multiple different filters are joined with AND, such as road is 'I-95' AND state is 'MD'.
Multiple filters of the same type are joined with OR, such as road is 'I-95' OR road is 'I-495', except for geospatial filters (box filter, radius filter).
Multiple geospatial filters of the same type are joined with AND: two box filters that do not overlap will return no results.
The API can return data in multiple formats. You can specify which using output parameters.
The ATIS/TMDD schema is an official standardized schema for traffic events, DMS & detector data. The CATT Lab includes a few extensions for information that is missing but deemed critical.
You can find the complete ATIS & TMDD schema here.
Thus the lanes are ordered from left to right in the order of travel per direction, regardless of the number of directions.
Lanes from the same direction are always grouped together, and directions are ordered, from left to right: south before north, west before east, and inner loop before outer loop.
The CATT Lab developed an unofficial schema for traffic events, DMS, & detector data base on our experiences working with the data. In general, this schema can provide more data. It can also express how an event changed over time for better analysis without complicated querying.
This schema is under development and not finalized.
You can find the complete CATT Lab schema here.
The structure of this schema matches the regular CATT Lab Schema (rf-schema-xml) almost exactly. Some elements have been restructured to follow JSON standards. For example, "event" tags in rf-schema-xml are enclosed in another tag called "events". In the JSON output, the "event" tags are removed and the "events" tag is turned into a JSON array.
These are all of the available agencies (system IDs) by data type.
Use the Agency API to learn more.
Uniquely identifies an event, detector, etc.
Filters are passed as GET parameters in the URL.