Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

Data is from the small-scale demonstration of the Intelligent Network Flow Optimization (INFLO) Prototype System and applications in Seattle, Washington. Connected vehicle systems were deployed in 21 vehicles in a scripted driving scenario circuiting this I-5 corridor northbound and southbound during morning rush hour. This data set contains real-time volume, speed and loop occupancy data that were collected from WSDOT’s simulated roadway sensors every 20 seconds and aggregated according to user defined procedures and threshold by the Infrastructure Traffic Sensor System (TSS) Data Aggregator software.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program. This is the primary loop detector data table. It contains one-minute volume, occupancy, and data quality flags for the arterial loop detector data.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

This set of data files was acquired under USDOT FHWA cooperative agreement DTFH61-11-H-00025 as one of the four test data sets acquired by the USDOT Data Capture and Management program.The freeway data consists of two months of data (Sept 15 2011 through Nov 15 2011) from dual-loop detectors deployed in the main line and on-ramps of a Portland-area freeway. The section of I-205 NB covered by this test data set is 10.09 miles long and the section of I-205 SB covered by this test data set is 12.01 miles long The data includes: flow, occupancy, and speed.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.

The Belle Isle data was collected between May 1st, 2014 and September 16th, 2014 on the Belle Isle Park in Michigan. However, within the data file provided as part of this data environment, only data during the World Congress demonstration period from September 5, 2014 to September 11, 2014 is included. Several vehicles equipped with multiple sensors drove around the island collecting 572,030 readings of multiple variables. The uploaded data file lists all those observations and the pertaining details about the sensor equipment, the sensor platform and the status of quality checking performed for each observation.