Automotive distribution points and values Koeln

Open data API in a single place

Provided by GKSt GovData Freie und Hansestadt Hamburg

Get early access to Automotive distribution points and values Koeln API!

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

Dataset information

Catalog
Country of origin
Updated
2023.02.15 13:56
Created
2023.03.24
Available languages
German
Keywords
transport-und-verkehr
Quality scoring
330

Dataset description

Overview of the car counting points of the vintages 2010 to 2016 (1st half year). 2016 to 2019 For reasons of coronavirus, no extensive censuses took place in 2020 and 2021. The count data is collected on a representative reference date (Monday — Friday, not on public holidays and outside school holidays) as node current counts. For example, 12 node currents (turners) are recorded at a 4-arm node point. The counting is carried out with an extra attached video camera. The traffic count is evaluated in 3 time blocks (6-10 o'clock, 11 p.m. and 3 p.m. to 7 p.m.). From the time blocks, the daily traffic is extrapolated by specific factors. The values can be seen analogous to the technical term DTVw (average daily traffic on weekdays). The unit is car/24h. The values give rise to the track loads on the roads approaching to the respective junction. The aim is to gradually integrate all routes in the main road network. Routes without values were not counted from 2010 to 2016. Fields Traffic counting Routes: 1) Route to — direction: NO: Route number FROMNODENO: from node number TONODENO: to node number LENGTH: Length of the track K_2016_24H: DTVw load 2016 on the relevant route K_2017_24H: DTVw 2017 load on the relevant route K_2018_24H: 2018 DTVw load on the relevant route K_2019_24H: 2019 DTVw load on the relevant route STR_NAME: Street name 2) Route to/back — direction: R_NO: Route number R_FROMNO~1: from node number R_TONODENO: to node number R_LENGTH: Length of the track R_K_2016~2: DTVw load 2016 on the relevant route R_K_2017~3: DTVw 2017 load on the relevant route R_K_2018~4: 2018 DTVw load on the relevant route R_K_2019~5: 2019 DTVw load on the relevant route R_STR_NAME: Street name Example: On the 2071 route, in 2016 from node 16545002 to node 16545007 in one direction 18,504 car/24h were raised. This section of Aachener Straße has a length of 173 metres in the traffic model. In the opposite direction run on the same route (2071, from knot 16545007 to node 16545002) 22.153 car/24h. Fields Traffic Counting Nodes: NO: Node Nuer XCOORD: X-coordinate of the node in the Gauss-Krüger system YCOORD: Y-coordinate of the node in the Gauss-Krüger system The resource “Measuring Lines 2010-2016” shows the nodes counted during this period. Due to their age, these data are not suitable for current noise and immission calculations.
Build on reliable and scalable technology
Revolgy LogoAmazon Web Services LogoGoogle Cloud Logo
FAQ

Frequently Asked Questions

Some basic informations about API Store ®.

Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.

Didn't find the API you need?

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

API Store provides access to European Open Data via scalable and reliable REST API interface.
Copyright © 2024. Made with ♥ by Apitalks