Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As traffic / air quality analyst, I would like to have some additional elaborations computed on top of the data provided by traffic cameras #39

Open
5 tasks
rcavaliere opened this issue Oct 18, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@rcavaliere
Copy link
Member

rcavaliere commented Oct 18, 2024

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.

associaz_prob_euro_targa_AV_2023.csv

The request is therefore to:

  • compute the EURO types for each raw data record
  • 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:

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:

  • 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)

@rcavaliere rcavaliere added the enhancement New feature or request label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant