Bluetooth Travel Sensors - Individual Traffic Match Files (ITMF)
For information about the City of Austin's Bluetooth travel sensor data, visit our documentation page:
Each row in this dataset represents one Bluetooth enabled device that detected at two locations in the City of Austin's Bluetooth sensor network. Each record contains a detected device’s anonymized Media Access Control (MAC) address along with contain information about origin and destination points at which the device was detected, as well the time, date, and distance traveled.
How does the City of Austin use the Bluetooth travel sensor data?
The data enables transportation engineers to better understand short and long-term trends in Austin’s traffic patterns, supporting decisions about systems planning and traffic signal timing.
What information does the data contain?
The sensor data is available in three datasets:
Individual Address Records ( https://data.austintexas.gov/dataset/Bluetooth-Travel-Sensors-Individual-Addresses/qnpj-zrb9/data )
Each row in this dataset represents a Bluetooth device that was detected by one of our sensors. Each record contains a detected device’s anonymized Media Access Control (MAC) address along with the time and location the device was detected. These records alone are not traffic data but can be post-processed to measure the movement of detected devices through the roadway network
Individual Traffic Matches ( https://data.austintexas.gov/dataset/Bluetooth-Travel-Sensors-Individual-Traffic-Matche/x44q-icha/data )
Each row in this dataset represents one Bluetooth enabled device that detected at two locations in the roadway network. Each record contains a detected device’s anonymized Media Access Control (MAC) address along with contain information about origin and destination points at which the device was detected, as well the time, date, and distance traveled.
Traffic Summary Records ( https://data.austintexas.gov/dataset/Bluetooth-Travel-Sensors-Match-Summary-Records/v7zg-5jg9 )
The traffic summary records contain aggregate travel time and speed summaries based on the individual traffic match records. Each row in the dataset summarizes average travel time and speed along a sensor-equipped roadway segment in 15 minute intervals.
Does this data contain personally identifiable information?
No. The Media Access Control (MAC) addresses in these datasets are randomly generated.
|Name||Socrata field name||Column name in ||Data type||Description|
|Device Address||device_address||device_address||Text||The unique address of the device that was read by the field software. For security, the source MAC address is discarded and replaced with a unique address that is reset daily.|
|Record ID||record_id||record_id||Text||The unique record identifer generated as an MD5 hash of the row contents.|
|Start Time||start_time||start_time||Text||The time the device address was recorded at the origin sensor.|
|Match Validity||match_validity||match_validity||Text||Indicates whether the sensor server classified the traffic data sample as being valid or invalid based on the filtering algorithm and minimum/maximum allowable speeds applied to the roadway segment. Values are valid or invalid.|
|Travel Time Seconds||travel_time_seconds||travel_time_seconds||Number||The travel time in seconds from the origin to the destination sensor.|
|End Time||end_time||end_time||Text||The time the device address was recorded at the destination sensor.|
|Origin Reader Identifier||origin_reader_identifier||origin_reader_identifier||Text||The unique identifier assigned to origin sensor that recorded a device address match.|
|Destination Reader Identifier||destination_reader_identifier||destination_reader_identifier||Text||The unique identifier assigned to destination sensor that recorded a device address match.|
|Day of Week||day_of_week||day_of_week||Text||The name of the day of the week at the time the device address was recorded at the origin sensor.|
|Speed (Miles Per Hour)||speed_miles_per_hour||speed_miles_per_hour||Number||The speed in miles per hour between the origin and the destination sensors.|
|Filter Identifier||filter_identifier||filter_identifier||Text||The numeric code of the filtering algorithm used in the outlier filter for the roadway segment. See the host documentation section titled “Algorithm Configuration” for more information.|