Skip to content

Volume Data Jan - April 2012 for Dublin City, from Traffic Department's SCATS System 1st Jan to 30th April 2012 DCC

Traffic volume data Volume data across Dublin City, from DCC's SCATS system, in csv format. ''The volume data is aggregated over 5 minute intervals for each approach into an instrumented intersection. There are separate files for each region (CCITY, SCITY, NCITY, WCITY1) and for each day. For each day two files are supplied: ''.gps has the following columns: 'streetSegId: a unique identifier for a street segment ID 'armNumber: an ID for the arm on a street segment 'armAngle: bearing of the arm 'lato: latitude in WGS84 20 meters into the arm 'longo: longitude in WGS84 20 meters into the arm 'latd: latitude in WGS84 of the centroid of the intersection 'longd: longitude in WGS84 of the centroid of the intersection ''.dis has the following columns 'streetSegId: identifies the street segment from the corresponding .gps file 'upperTime: timestamp of the 5 minute interval 'armNumber: identifies the arm of the street segment from the corresponding .gps file 'aggerateCount: aggregated volume count on that arm 'flow: flow ratio calculated as the volume divided by the highest volume that 'has been measured in a sliding window of a week. ''Note that the flow ratio requires some burn in time of a week from the start of the recording period.

About this dataset


Organization

Dublin City Council

The authority responsible for local government in the city of Dublin read more

Followers
0
Datasets
130

Created on

2012-01-01

Last updated

2022-01-18

Date range

2012-01-01 to 2012-04-30

Update Frequency

As Required

Metadata

Title Volume Data Jan - April 2012 for Dublin City, from Traffic Department's SCATS System 1st Jan to 30th April 2012 DCC
Description

Traffic volume data Volume data across Dublin City, from DCC's SCATS system, in csv format. ''The volume data is aggregated over 5 minute intervals for each approach into an instrumented intersection. There are separate files for each region (CCITY, SCITY, NCITY, WCITY1) and for each day. For each day two files are supplied: ''.gps has the following columns: 'streetSegId: a unique identifier for a street segment ID 'armNumber: an ID for the arm on a street segment 'armAngle: bearing of the arm 'lato: latitude in WGS84 20 meters into the arm 'longo: longitude in WGS84 20 meters into the arm 'latd: latitude in WGS84 of the centroid of the intersection 'longd: longitude in WGS84 of the centroid of the intersection ''.dis has the following columns 'streetSegId: identifies the street segment from the corresponding .gps file 'upperTime: timestamp of the 5 minute interval 'armNumber: identifies the arm of the street segment from the corresponding .gps file 'aggerateCount: aggregated volume count on that arm 'flow: flow ratio calculated as the volume divided by the highest volume that 'has been measured in a sliding window of a week. ''Note that the flow ratio requires some burn in time of a week from the start of the recording period.

Landing Page
Publisher Dublin City Council
Author Dublin City Council
Maintainer Dublin City Council
Region Dublin City
Category Transport and Infrastructure
Star Rating
License Creative Commons Attribution
Target NA
Tags
Language en
Version 1.0