Road traffic — Counting points — Département du Loiret — 2020

Open data API in a single place

Provided by etalab

Get early access to Road traffic — Counting points — Département du Loiret — 2020 API!

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

Dataset information

Country of origin
Updated
2022.01.22 01:11
Created
2022.01.22
Available languages
French
Keywords
infrastructures, transports, donnees-ouvertes, points-de-comptage, mobilite, 2020, route
Quality scoring
215

Dataset description

Geolocation of road counting points accompanied by annual traffic indicators (TMJA All Vehicles/Part of Trucks as Percentage/LightweightsTMJA) — 2020 Edition **Collection context** Knowledge of the total traffic to be flowed on a road (all vehicles combined) is essential in order to give the track geometric characteristics in relation to its importance and the speeds used, to draw up accident checks and to propose route or safety arrangements. It is also essential to calculate the road structure necessary for rehabilitation or development projects, based on heavy goods traffic. **Collection method** The departmental road network has been divided into homogeneous traffic sections. In addition to permanent stations, temporary counts are carried out by DI teams each year to complete the road traffic base. Each year, nearly 500 meter installation and deposit have been carried out on a time-by-day basis. In order to consolidate and secure the road traffic base, it was decided to count at least once every 5 years the traffic of each section. The counting frequency is calculated according to predefined criteria. For permanent traffic counting points (117 equipment), data collection and exploitation can be carried out with time steps, vehicle discrimination is effective on all these sites (TV/PL or VL/PL). Permanent traffic counting stations can be characterised by the type of data available: . 48 positions are able to return flow-type data with vehicle discrimination according to length. . 69 stations are able to return data of type flow + speed with discrimination of vehicles according to length. Of the latter 69, real-time data visualisation/collection is a priori possible, but this requires a permanent connection for each equipment (RTC, GSM or Internet IP). Thus road congestion can be visualised/analysed at these points of the network. An automatic data collection procedure at regular intervals may also be set up to avoid permanent occupancy of BTI, GSM or IP lines. **Attributes** | Champ | Alias | Type | | — | — | | — | | ‘ObjectID’ | FID | ‘integer’ | | ‘ROUTE’ | Road name (long) | ‘char’ | | ‘PR’ | Reference point | ‘integer’ | | ‘ABS’ | Abscisse | ‘integer’ | | ‘CUMUL’ | Cumul | ‘integer’ | | ‘ID_ROUTE’ | Road name (short) | ‘char’ | | ‘PR_DEB’ | PR+ABS Counting Section Starts | ‘char’ | | ‘PR_FIN’ | PR+ABS End of the counting section | ‘char’ | | ‘CATEGORIA’ | Category | ‘integer’ | | ‘ID_TRAFIC’ | Traffic ID | ‘char’ | ‘ID_TRAFIC’ | ‘ID_SITE’ | Site ID | ‘char’ | | ‘NOM_SITE’ | Site Name | ‘char’ | | ‘LIEU’ | Location | ‘char’ | ‘LIEU’ | ‘TYPE’ | Equipment type | ‘char’ | ‘TYPE’ | ‘CPTGE_YEAR’ | Year | ‘integer’ | | ‘VALUE_TYPE’ | Value Type | ‘char’ | | ‘MJA_TV’ | Average Annual Daily All Vehicles | ‘integer’ | | ‘MJA_PL’ | Annual Daily Average Heavy Weights | ‘integer’ | | ‘P_PL’ | Percent Heavy Weights | ‘double’ | | ‘X’ | Longitude | ‘double’ | | ‘Y’ | Latitude | ‘double’ | | ‘SECTION_IN’ | Index Section | ‘char’ | ‘SECTION_IN’ For more information, see [the metadata on the Isogeo catalog](https://open.isogeo.com/s/1742fb942d7b4756b9778c3b3cbc992e/HWglEr-z4Bry_rKQOTINX9gAH4Yu0/r/6aafb961488b46e59b59be016cf09c73).
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