Travel Sensors
City of Austin
@usgov.city_of_austin_travel_sensors
City of Austin
@usgov.city_of_austin_travel_sensors
This dataset is no longer actively maintained, because the devices referenced in this dataset have been removed from operation.
This dataset contains information about travel sensors in Austin, TX. Travel sensors are owned and operated by the City of Austin Transportation Department and are used to monitor traffic conditions across the city.
The output of these sensors is available for download in the following datasets:
Radar traffic counts related to this dataset with the 'KITS ID' value of a wavetronix travel sensor.
( https://data.austintexas.gov/Transportation-and-Mobility/Radar-Traffic-Counts/i626-g7ub )
Individual Address Records ( https://data.austintexas.gov/dataset/Bluetooth-Travel-Sensors-Individual-Addresses/qnpj-zrb9/data )
Individual Traffic Matches ( https://data.austintexas.gov/dataset/Bluetooth-Travel-Sensors-Individual-Traffic-Matche/x44q-icha/data )
Traffic Summary Records ( https://data.austintexas.gov/dataset/Bluetooth-Travel-Sensors-Match-Summary-Records/v7zg-5jg9 )
For information about Austin's Advanced Transportation Management System, visit the department website, here:
http://www.austintexas.gov/department/arterial-management
Organization: City of Austin
Last updated: 2020-11-12T13:22:43.502999
Tags: mobility, traffic, transportation, travel-sensors, travel-time
CREATE TABLE table_1 (
"reader_id" VARCHAR,
"atd_sensor_id" BIGINT,
"kits_id" DOUBLE,
"atd_location_id" VARCHAR,
"modified_date" VARCHAR,
"sensor_status" VARCHAR,
"turn_on_date" VARCHAR,
"sensor_type" VARCHAR,
"sensor_mfg" VARCHAR,
"coa_intersection_id" DOUBLE,
"primary_st_segment_id" VARCHAR,
"cross_st_segment_id" VARCHAR,
"landmark" VARCHAR,
"primary_st_aka" VARCHAR,
"cross_st_aka" VARCHAR,
"signal_eng_area" VARCHAR,
"council_district" VARCHAR,
"jurisdiction" VARCHAR,
"location_type" VARCHAR,
"location_name" VARCHAR,
"primary_st" VARCHAR,
"cross_st" VARCHAR,
"primary_st_block" DOUBLE,
"county" VARCHAR,
"cross_st_block" DOUBLE,
"ip_comm_status" VARCHAR,
"comm_status_datetime_utc" VARCHAR,
"location_latitude" VARCHAR,
"location_longitude" VARCHAR,
"source_db_id" VARCHAR,
"location" VARCHAR,
"primary_st_segment_display_name" VARCHAR,
"cross_st_segment_display_name" VARCHAR,
"jurisdiction_label" VARCHAR,
"corridor_name" VARCHAR
);Anyone who has the link will be able to view this.