AVERAGE DAILY TRAFFIC AND OTHER 2021 SVR DATA ON BDTRE ROAD ELEMENT

Traffic data and other transport attributes of the Piedmontese road network by regional road graph arc (road element of the GDF1 traffic graph) of the Territorial Reference Database of Bodies (BDTRE). ========================= ATTENTION!! As detailed in the Model_SVR.pdf file contained in the unloaded material, the TGM and average speed data represented on the regional graph, are calculated starting from the estimates of the traffic models of the Regional Supervisory system which, considering the road offer of the region and the origin-destination journeys by road, estimates, through specific assignment algorithms, the traffic flows and speeds averages to the arcs of the reference network. These basic estimates are corrected by traffic measurements from the regional sensor network, where present: the closer the arcs of the network are to a traffic measurement station, the more the estimates adhere to reality. In 2020 the models of traffic of the Regional Supervisory System have been subject to an overall review: in particular, the reference road graph has been updated, which now includes the changes to the road system introduced in recent years, and the origin-destination matrices, which include more recent information on travel, PRIOR TO THE PERIOD OF HEALTH EMERGENCY. Therefore, given the recent revisions on traffic models, it IS NOT RECOMMENDED to use the present data to make comparisons between the GMT estimated in 2020 and that of previous years, as part of the differences could be caused not by actual traffic variations, but by model adjustments. It should also be noted that the demand model used for the 2020 traffic estimates describes a standard situation, i.e. it does not take into account the variations in mobility demand strictly linked to the emergency period for the spread of COVID-19. Only for the arcs of the network near the metering stations are the variations in vehicular mobility detected during the most critical moments of the pandemic visible. ========================= Some of the attributes are derived, through "geometric projection" procedures, from the Regional Traffic Supervisor Graph (SVR) managed by 5T srl on behalf of the Piedmont Region. Update 2021, annual frequency.Description of the attributesThe attributes of the BDTRE graph are:uuid text, unique identifier of the elementfk_metaope and integer, id that refers to the information of subsequent operational metadatadata_acq text, data acquisition date (operational metadata)data_agg text, date of update of the data (operational metadata) data_fin text, end date of data validity (operational metadata) entity_for text, entity supplying the data (operational metadata) entity_prod text, entity producing the data (operational metadata) mode_prod text, method of production of the data (operational metadata)sc_acq text, data acquisition scale (operational metadata)el_str_ty text, road type descriptioncod_el_str_ty text, road type codeel_str_cf text, technical-functional classification description cod_el_str_cf text, technical-functional classification codeel_str_sta text, state descriptioncod_el_str_sta text, state codeel_str_fon text, fund descriptioncod_el_str_fon text, fund codeel_str_cl text, width class descriptioncod_el_str_cl text, width class codeel_str_sed text, roadway description cod_el_str_sed text, roadway codeel_str_liv text, level descriptioncod_el_str_liv text, level codeel_str_nc integer, number of lanesel_str_frc character varying(80), description Functional Road Classcod_el_stro_frc Character Varying (20), Code Functional Road Classfk_l2 Integer, ID of the toponym roadfk_l3 Integra, ID of the extended AdministrativeS_Mam_nom Text, Extended Name Administrativatp_st_nom Text, Toponym StradaTP_STR_LLOC TEXT, Location/FRAZIONETP_STRAP_STRA _el_str numeric (1000,500 ), length in meters of the element istat_comu text, istat code of the municipality to which it belongs geometry (Geometry,32632), geometry The attributes that come from the Regional Traffic Supervisor (SVR) are: hier_svr integer, Functional class of the arc patr_svr text, Patrimony of the arc ( A=motorway, S=state, R=regional, P=provincial, C=municipal)nlan_svr integer, Number of lanes in the arc capa_sum integer, Total capacity of the road arc. Expressed in vehicles/hour. Derived as the sum of the values ​​of the two directions sped_med integer, Zero flow speed, i.e. travel speed values ​​on the road arch with unloaded network in the two directions. Expressed in km/h. aspd_a double precision, Average daily travel speed in the reference year on the arc in direction a. Expressed in km/h. aspd_b double precision, Average daily traveling speed in the reference year over the arc direction b. Expressed in km/h. aspd_max double precision, Average daily travel speed in the reference year on the arc in the two directions. Expressed in km/h. aspd_med double precision (to be deleted from the record track) reference year. Expressed in number of vehicles/day. The data is broken down by type of vehicle, light (mfwl) or heavy (mfwp) and by direction of travel (defined as "a" and "b") and as the sum of the two directions of travel. The "light" category includes all vehicles up to 3.5 t and 9 passengers, the "heavy vehicles" category includes vehicles with a higher mass. In detail: mfwl_dir_a integer, Average daily traffic Light in direction a mfwl_dir_b integer, Average daily traffic Light on the arc in direction b mfwl_sum integer, Average daily traffic Light on the arc in both directions mfwp_dir_a integer, Average daily traffic Heavy on the arc in direction a mfwp_dir_b integer, Heavy daily average traffic on the arc in direction b mfwp_sum integer, Heavy heavy daily traffic on the arc in both directions mfw_sum integer, Average daily traffic Total vehicles on the arc in both directions Traffic status relative to morning rush hour: traffic outflow conditions on a road arc between 8 and 9 on a weekday conventionally in the month of November of the reference year, expressed as a value of the Congestion Index (cong_m) and attributed to one specific traffic level (traf_m) In detail: traf_m_a character varying (20), dry value on the traffic status, based on the IC ranges indicated below traf_m_b character varying (20), dry value on the traffic status, based on the ranges of CI below indicated traf_m_max character varying (20), dry value on the state of traffic, based on the range of CI indicated below cong_m_a double precision, punctual value of the congestion index in the direction a cong_m_b double precision, punctual value of the congestion index in the direction bcong_m_max double precision, punctual value of the congestion index in the two directions Traffic Status for the afternoon rush hour: traffic outflow conditions on a road arc, between 5 and 6 pm on a weekday, conventionally in the month of November of the reference year, expressed as a value of the Congestion Index (cong_p_m) and attributed to a specific level of traffic (traf_p) In detail: traf_p_a character varying (20), straight value on the state of traffic, based on the IC below indicated traf_p_b character varying (20), dry value on the state of traffic, based on the ranges of ICs indicated below traf_p_max character varying (20), dry value on the state of traffic, based on the ranges of ICs indicated below cong_p_a double precision, punctual value of the congestion index in the direction a cong_p_b double precision, punctual value of the congestion index in the direction bcong_p_max double precision, punctual value of the congestion index in the two directions. By Congestion Index (CI) we mean the ratio between the average speed of mileage in the reference period and the speed at zero flow on the same road arc. In particular, the levels (range) considered are the following:• free (CI >= 0.91)• intense (CI between 0.91 and 0.77)• slowed down (CI between 0.77 and 0.50)• tail (CI <= 0.50)Description of dressing of the layers The traffic status is represented with colors and thicknesses relating to the most critical value of the traffic status in the two directions and in correspondence with each arc both the values ​​of the congestion index of the two directions are reported (dir a and dir b, without indicate which is the dir a and the dir b).

Data and Resources

Additional Info

Field Value
Last Updated May 3, 2023, 16:09 (UTC)
Created May 3, 2023, 16:09 (UTC)
GUID r_piemon:bf9a567b-2b25-4b6e-945e-07a9344919e6
access_constraints ["https://creativecommons.org/licenses/by/4.0/deed.it"]
bbox-east-long 9.21
bbox-north-lat 46.46
bbox-south-lat 44.06
bbox-west-long 6.62
contact-email controllo.trasporti@regione.piemonte.it
coupled-resource []
dataset-reference-date [{"type": "creation", "value": "2022-06-28"}]
frequency-of-update annually
harvest_object_id dc627994-2040-410d-8810-52166d76954b
harvest_source_id 5045f9a0-4055-43f6-b140-9cd49466666b
harvest_source_title GeoDatiGovIt RNDT
licence []
lineage Data production method: in the SVR Graph (Regional Supervisor graph) the information is distinguished by direction of travel. The BDTRE graph does not provide for this distinction so that the SVR data before being attributed to the elements of the BDTRE graph are aggregated (summed or averaged as appropriate). The tracing of the two graphs does not exactly coincide as they come from different sources so that the transfer of information takes place through the transformation of the SRV graph into points at a regular distance (1 metre) and their association to the arcs of the BDTRE graph based on the criterion of nearness. For each set of points associated with a single BDTRE arc, the mode of the values ​​of the attribute to be transferred is statistically calculated, which represents the value of the data made available. Furthermore, the SVR Graph represents a subset of the complete Piedmont road network. Therefore, on the BDTRE graph, only the arcs corresponding to the subnetwork represented in the SVR graph are valued with the TGM.
metadata-date 2022-07-06
metadata-language ita
progress
resource-type dataset
responsible-party [{"name": "Regione Piemonte - A1810A - Control over transport and infrastructure management", "roles": ["pointOfContact"]}]
spatial {"type": "Polygon", "coordinates": [[[6.62, 44.06], [9.21, 44.06], [9.21, 46.46], [6.62, 46.46], [6.62, 44.06]]]}
spatial-data-service-type
spatial-reference-system
spatial_harvester true
temporal-extent-begin 2021-01-01
temporal-extent-end 2021-12-31