You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This implementation can be carried out once the developments in noi-techpark/bdp-commons#673 are completed.
In particular, based on the new fields idNazionalita and targaIniziali.
The first elaboration is the EURO class elaboration, which is based on a simple algorithm applied to the content of the field targaIniziali. Actually the idea is to apply a probabilistic / fuzzy approach, and not a deterministic one. The idea is to have new types, e.g.:
EURO 1
EURO 2
EURO 3
EURO 4
EURO 5
EURO 6
Electric
and to associated a probability to each of them, according to the mapping table provided as annex.
include the same EURO types also on the aggregated data in the measurement table. Here we should compute the average of all data records associated.
Please note that for all traffic records we could make a computation, if no targaIniziali is provided or if the values does not match with one of these values, we should not provide the elaboration (field should be there, but without values associated).
The second elaboration is related to a new way to compute the elaboration of the vehicles classification for the aggregated data, that are then put in the measurement table. The current elaboration is described in this specification document:
The classification information is provided in the field classe. According to the new specifications of A22 (see 240710_Softech_SpecificheAPI_V22_v12.pdf there is a detailed classification scheme with 7 possible values, where:
classe = 1 -> "AUTOVETTURA"
classe = 2 -> "FURGONE"
classe = 3 -> "AUTOCARRO"
classe = 4 -> "AUTOARTICOLATO"
classe = 5 -> "AUTOTRENO"
classe = 6 -> "PULLMAN"
classe = 7 -> "MOTO O MOTOCICLO"
For the aggregated information, we have types referred to three macro classes: HEAVY VEHICLES, LIGHT VEHICLES, BUSES. According to this new classification scheme, we should consider the following mapping:
HEAVY VEHICLES: AUTOARTICOLATO or AUTOTRENO or AUTOCARRO if lunghezza >= 890 cm
LIGHT VEHICLES: AUTOVETTURA or FURGONE or MOTO O MOTOCICLO
BUSES: AUTOCARRO if lunghezza < 890 cm or PULLMAN
Please note that lunghezza is a field provided by the A22 API.
In practice, the work to do is:
change the way the aggregation is done for traffic data, i.e. change the way single vehicles are classified as HEAVY VEHICLES, LIGHT VEHICLES, BUSES.
adapt the computations for the types associated to the aggregated traffic data that are based on this basic classification, which are:
average speed light vehicles
average speed buses
average speed heavy vehicles
nr. buses
nr. heavy vehicles
nr. light vehicles
nr. equivalent vehicles
variance speed buses
variance speed heavy vehicles
variance speed light vehicles
cancel all the elaborations associated to these data types since 10.07.2024 included, and restart the calculations as described (10.07.2024 is the data in which A22 changed the classification scheme)
The third elaboration is related to the count of the vehicles based on their nationality. We should foresee here new data types, according to all possible nationalities currently available.
The text was updated successfully, but these errors were encountered:
Resolve "Implement DAG for pollution dispersal"
Closesnoi-techpark#39, noi-techpark#41, and noi-techpark#42
See merge request u-hopper/projects/industrial/open-data-hub-bz/bdp-elaborations!28
This implementation can be carried out once the developments in noi-techpark/bdp-commons#673 are completed.
In particular, based on the new fields
idNazionalita
andtargaIniziali
.The first elaboration is the EURO class elaboration, which is based on a simple algorithm applied to the content of the field
targaIniziali
. Actually the idea is to apply a probabilistic / fuzzy approach, and not a deterministic one. The idea is to have new types, e.g.:and to associated a probability to each of them, according to the mapping table provided as annex.
associaz_prob_euro_targa_AV_2023.csv
The request is therefore to:
Please note that for all traffic records we could make a computation, if no targaIniziali is provided or if the values does not match with one of these values, we should not provide the elaboration (field should be there, but without values associated).
The second elaboration is related to a new way to compute the elaboration of the vehicles classification for the aggregated data, that are then put in the measurement table. The current elaboration is described in this specification document:
190401_SpecificheIntegrazione_A22_Traffico.pdf
The classification information is provided in the field
classe
. According to the new specifications of A22 (see 240710_Softech_SpecificheAPI_V22_v12.pdf there is a detailed classification scheme with 7 possible values, where:For the aggregated information, we have types referred to three macro classes: HEAVY VEHICLES, LIGHT VEHICLES, BUSES. According to this new classification scheme, we should consider the following mapping:
Please note that
lunghezza
is a field provided by the A22 API.In practice, the work to do is:
change the way the aggregation is done for traffic data, i.e. change the way single vehicles are classified as HEAVY VEHICLES, LIGHT VEHICLES, BUSES.
adapt the computations for the types associated to the aggregated traffic data that are based on this basic classification, which are:
average speed light vehicles
average speed buses
average speed heavy vehicles
nr. buses
nr. heavy vehicles
nr. light vehicles
nr. equivalent vehicles
variance speed buses
variance speed heavy vehicles
variance speed light vehicles
cancel all the elaborations associated to these data types since 10.07.2024 included, and restart the calculations as described (10.07.2024 is the data in which A22 changed the classification scheme)
The third elaboration is related to the count of the vehicles based on their nationality. We should foresee here new data types, according to all possible nationalities currently available.
The text was updated successfully, but these errors were encountered: