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

Open data API in a single place

Provided by Dublin City Council

Get early access to Volume Data Jan – April 2012 for Dublin City, from Traffic Department’s SCATS System 1st Jan to 30th April 2012 DCC API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2025.06.19 16:33
Created
2012.01.01
Available languages
English
Keywords
traffic-management, transportation-infrastructure, Transport and Infrastructure
Quality scoring

Dataset 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.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks