This subpage contains different sections that analyse the source datasets:
The technical analysis also contains further details about the created mashup datasets.
| To check: | DS1 | DS2 | DS3 | DS4 | DS5 | DS6 | DS7 | DS8 | DS9 |
|---|---|---|---|---|---|---|---|---|---|
| 1.1 Is the dataset free of any personal data as defined in the Regulation (EU) 2016/679 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 1.2 Is the dataset free of any indirect personal data that could be used for identifying the natural person? If so, is there a law that authorize the PA to release them? Or any other legal basis? Identify the legal basis. | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 1.3 Is the dataset free of any particular personal data (art. 9 GDPR)? If so is there a law that authorize the PA to release them ? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 1.4 Is the dataset free of any information that combined with common data available in the web, could identify the person? If so, is there a law that authorize the PA to release them? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 1.5 Is the dataset free of any information related to human rights (e.g. refugees, witness protection, etc.)? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 1.6 Do you use a tool for calculating the range of the risk of deanonymization? Do you anonymize the dataset? With which technique? Did you check the three mandatory parameters: singling out, linking out, inference out? | There aren’t any data to be anonymized | There aren’t any data to be anonymized | There aren’t any data to be anonymized | There aren’t any data to be anonymized | There aren’t any data to be anonymized | There aren’t any data to be anonymized | There aren’t any data to be anonymized | There aren’t any data to be anonymized | There aren’t any data to be anonymized |
| 1.7 Are you using geolocalization capabilities ? Do you check that the geolocalization process can’t identify single individuals in some circumstances? | Yes, the process cannot identify single individuals as it measures air quality metrics | Yes, the process cannot identify single individuals | No | Yes, the process cannot identify single individuals | Yes, the process cannot identify single individuals as it measures air quality metrics | No | No | Yes, the process cannot identify single individuals | No |
| 1.8 Did you check that the open data platform respect all the privacy regulations (registration of the end-user, profiling, cookies, analytics, etc.)? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 1.9 Do you know who are in your open data platform the Controller and Processor of the privacy data of the system? | Yes, Municipality of Bologna | Yes, Municipality of Bologna | Yes, Municipality of Bologna and Metropolitan City of Bologna | Yes, Municipality of Bologna and Metropolitan City of Bologna | Yes, Municipality of Milan | Yes, Municipality of Milan | Yes, Municipality of Milan | Yes, Municipality of Milan | Yes, Municipality of Milan |
| 1.10 Where the datasets are physically stored (country and jurisdiction)? Do you have a cloud computing platform? Do you have checked the privacy regulation of the country where the dataset are physically stored? (territoriality) | Stored online and accessible through the Explore API - Germany, Frankfurt am Main | Stored online and accessible through the Explore API - Germany, Frankfurt am Main | Stored online - Italy, Bologna | Stored online - Italy, Bologna | Stored online and accessible through the CKAN API - Italy, Milan | Stored online and accessible through the CKAN API - Italy, Milan | Stored online and accessible through the CKAN API - Italy, Milan | Stored online and accessible through the CKAN API - Italy, Milan | Stored online and accessible through the CKAN API - Italy, Milan |
| 1.11 Do you have non-personal data? Are you sure that are not “mixed data”? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| To check: | DS1 | DS2 | DS3 | DS4 | DS5 | DS6 | DS7 | DS8 | DS9 |
|---|---|---|---|---|---|---|---|---|---|
| 2.1 Do you have created and generated the dataset? | No | No | No | No | No | No | No | No | No |
| 2.2 Are you the owner of the dataset? How is the owner? | No, Municipality of Bologna | No, Municipality of Bologna | No, Municipality of Bologna | No, Municipality of Bologna | No, Municipality of Milan | No, Municipality of Milan | No, Municipality of Milan | No, Municipality of Milan | No, Municipality of Milan |
| 2.3 Are you sure to not use third party data without the proper authorization and license? Are the dataset free from third party licenses or patents? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 2.4 Do you have checked if there are some limitations in your national legal system for releasing some kind of datasets with open license? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| To check: | DS1 | DS2 | DS3 | DS4 | DS5 | DS6 | DS7 | DS8 | DS9 |
|---|---|---|---|---|---|---|---|---|---|
| 3.1 Do you release the dataset with an open data license? In case of the use of CC0 do you check that you have all the right necessary for this particular kind of license (e.g., jurisdiction)? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 3.2 Do you include the clause: "In any case the dataset can’t be used for re-identifying the person"? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 3.3 Do you release the API (in case you have) with an open source license? | No | No | No | No | No | No | No | No | No |
| 3.4 Do you check that the open data/API platform license regime is compliance with your IPR policy? Do you have all the licences related to the open data platform/API software? | API is under copyright Opendatasoft, data is released under CC-BY-SA 4.0 | API is under copyright Opendatasoft, data is released under CC-BY-SA 4.0 | No API, all data is released under CC-BY-SA 4.0 | No API, all data is released under CC-BY-SA 4.0 | API is released under CC-BY-SA 3.0, data is released under CC-BY-SA 4.0 | API is released under CC-BY-SA 3.0, data is released under CC-BY-SA 4.0 | API is released under CC-BY-SA 3.0, data is released under CC-BY-SA 4.0 | API is released under CC-BY-SA 3.0, data is released under CC-BY-SA 4.0 | API is released under CC-BY-SA 3.0, data is released under CC-BY-SA 4.0 |
| To check: | DS1 | DS2 | DS3 | DS4 | DS5 | DS6 | DS7 | DS8 | DS9 |
|---|---|---|---|---|---|---|---|---|---|
| 4.1 Do you check that the dataset concerns your institutional competences, scope and finality? Do you check if the dataset concerns other public administration competences? | Yes, Yes | Yes, Yes | Yes, Yes | Yes, Yes | Yes, Yes | Yes, Yes | Yes, Yes | Yes, Yes | Yes, Yes |
| 4.2 Do you check the limitations for the publication stated by your national legislation or by the EU directives? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 4.3 Do you check if there are some limitations connected to the international relations, public security or national defence? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 4.4 Do you check if there are some limitations concerning the public interest? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 4.5 Do you check the international law limitations? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 4.6 Do you check the INSPIRE law limitations for the spatial data? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| To check: | DS1 | DS2 | DS3 | DS4 | DS5 | DS6 | DS7 | DS8 | DS9 |
|---|---|---|---|---|---|---|---|---|---|
| 5.1 Do you check that the dataset could be released for free? | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 5.2 Do you check if there are some agreements with some other partners in order to release the dataset with a reasonable price? | No other partners | No other partners | No other partners | No other partners | No other partners | No other partners | No other partners | No other partners | No other partners |
| 5.3 Do you check if the open data platform terms of service include a clause of “non liability agreement” regarding the dataset and API provided? | Terms and condition specify the possible use of any data if the licence of the dataset is respected | Terms and condition specify the possible use of any data if the licence of the dataset is respected | No specific mention of this clause | No specific mention of this clause | No specific mention of this clause | No specific mention of this clause | No specific mention of this clause | No specific mention of this clause | No specific mention of this clause |
| 5.4 In case you decide to release the dataset to a reasonable price do you check if the limitation imposed by the new directive 2019/1024/EU are respected ? Are you able to calculate the “marginal cost”? Are you able to justify the “reasonable return on investment”? | Not Stated | Not Stated | Not Stated | Not Stated | Not Stated | Not Stated | Not Stated | Not Stated | Not Stated |
| 5.5 In case you decide to release the dataset to a reasonable price do you check the e-Commerce directive1 and regulation? | Not Stated | Not Stated | Not Stated | Not Stated | Not Stated | Not Stated | Not Stated | Not Stated | Not Stated |
| To check: | DS1 | DS2 | DS3 | DS4 | DS5 | DS6 | DS7 | DS8 | DS9 |
|---|---|---|---|---|---|---|---|---|---|
| 6.1 Do you have a temporary policy for updating the dataset? | Updated Annually | Updated Annually | Updated Annually | Updated Annually | Updated Annually | Updated Annually | Updated Annually | Updated Annually | Updated Annually |
| 6.2 Do you have some mechanism for informing the end-user that the dataset is updated at a given time to avoid mis-usage and so potential risk of damage? | Dataset information – Last Processing | Dataset information – Last Processing | Not mentioned | Not mentioned | Dataset Information – Last Update | Dataset Information – Last Update | Dataset Information – Last Update | Dataset Information – Last Update | Dataset Information – Last Update |
| 6.3 Did you check if the dataset for some reason can’t be indexed by the research engines (e.g. Google, Yahoo, etc.)? | Indexed | Indexed | Indexed | Indexed | Indexed | Indexed | Indexed | Indexed | Indexed |
| 6.4 In case of personal data, do you have a reasonable technical mechanism for collecting request of deletion (e.g. right to be forgotten)? | Any privacy issues are handled by the author via contact details | Any privacy issues are handled by the author via contact details | Not explicitly mentioned | Not explicitly mentioned | Any privacy issues are handled by the author via contact details | Any privacy issues are handled by the author via contact details | Any privacy issues are handled by the author via contact details | Any privacy issues are handled by the author via contact details | Any privacy issues are handled by the author via contact details |
The ethical analysis of the datasets used in this project is based on two key frameworks: the principles outlined by the Data Ethics Institute document and the questions posed in the Data Ethics Canvas developed by the Open Data Institute (ODI). These frameworks help examine aspects such as transparency, privacy, bias, and public benefit. In several instances, however, the absence of critical metadata or methodological documentation has limited the depth and clarity of the ethical evaluation.
This dataset, sourced from Arpae (Agenzia regionale per la prevenzione, l’ambiente e l’energia dell’Emilia-Romagna), is accessible via the Bologna City Council’s Open Data platform. It contains no personal or human-related data, as it is collected through environmental monitoring instruments at three fixed stations. The data is openly licensed under CC BY 4.0 and updated annually.
From an ethical perspective, the dataset demonstrates strong transparency and public accessibility. Its release supports public awareness, academic research, and policy decisions. However, being limited only to three stations and neighbourhoods in Bologna, raises potential concerns about spatial representation and environmental justice, as some zones of the city may be underrepresented in the data. Overall, the dataset aligns well with the principles of openness and public benefit, though further clarification on data coverage could enhance equity considerations.
This dataset is published on Bologna’s Open Data website and originates from the Automobile Club of Italy (ACI). It details vehicle registrations by postal code and includes anonymized demographic information such as sex, age group, and vehicle fuel type. The data is updated annually and made available under a CC BY 4.0 license.
Although the dataset is presented as anonymized and it is grouped under numbers of different groups in postal code area. So, there is no theoretical risk of re-identification of the data. In this dataset, being free from bias and discrimination requires critical examination. For example, how vehicle data is aggregated and categorized could inadvertently reflect or reinforce socioeconomic inequalities [Less wealthier zones, have fewer electric cars, and this may interpret as they are responsible for air pollution more than the others]. This dataset is useful for environmental research and mobility planning but may also be exploited for commercial interests, such as targeted marketing. Overall, while the dataset serves important functions, it would benefit from enhanced documentation regarding privacy safeguards and data processing methods.
Collected and published by the Bologna City Council and TPER (Emilia-Romagna’s public transport provider), this dataset includes information about the types of fuels used in the city’s public bus fleet. It contains no personal data.
The dataset appears ethically sound, promoting sustainability and enabling researchers and policymakers to assess progress toward low-emission mobility goals. However, the licensing terms are not explicitly stated. While the data is freely accessible, clearer legal guidance on reuse would enhance its ethical transparency and utility. The dataset does not introduce any evident risk of harm or discrimination and supports public interest objectives well.
This dataset reports the number of public transport trips in Bologna by month and year and is published by the Bologna City Council and TPER. It captures aggregated human activity but contains no personal or identifiable data.
Ethically, the dataset poses minimal privacy risks and holds significant potential for improving urban mobility and infrastructure planning. However, the absence of detailed information on how data is collected (e.g., through ticketing systems or automated sensors) limits full transparency. Additionally, while the dataset does not appear biased, it would be helpful to analyze it in conjunction with socioeconomic data to assess transport equity. The lack of a clearly stated license is another area for improvement, though the dataset is available for public use with attribution.
This dataset is maintained by AMAT (Agenzia Mobilità Ambiente Territorio) and published by the Metropolitan City of Milan. It consists of environmental air quality measurements and does not include any personal or sensitive data.
The data is updated annually and is publicly accessible, reflecting a high level of transparency. The data is derived from seven stations in Milan, which is quite fair but as with Bologna’s air quality data, a more detailed explanation of the station network would help assess whether all neighborhoods are equally represented. The dataset supports public health and environmental policy and aligns well with ethical principles of transparency, beneficence, and sustainability.
This dataset contains statistics on the number of low-emission buses operating in Milan. It is non-personal in nature and does not include sensitive data.
The data contributes positively to understanding urban environmental progress and supports research and public policy.
Published by the Council of Milan, this dataset categorizes buses used for local public transport by emission class. It is non-personal and regularly updated.
This dataset has a clear environmental and administrative purpose. It does not raise ethical concerns regarding privacy or discrimination. Its utility in policy-making, sustainability tracking, and infrastructure planning makes it ethically robust, although greater methodological detail would be welcome.
This dataset presents the number of annual public transport trips per inhabitant in Milan. While it is a high-level indicator, it lacks transparency regarding its construction and data sources.
From an ethical standpoint, the absence of methodological clarity limits its trustworthiness. Misinterpretation of such indicators can lead to misleading conclusions about mobility access or public transport usage. To enhance transparency and accountability, the data providers should publish a clear explanation of how the indicator is calculated.
This dataset, produced by ACI and published by the City of Milan, shows the number and types of vehicles registered in the city. It is derived from personal registration data but has been fully anonymized.
Ethically, the dataset appears to pose no direct privacy risks if proper anonymization protocols are in place. The dataset is valuable for urban planning, environmental analysis, and transportation policy, but safeguards should be in place to prevent misuse, such as commercial profiling or discriminatory policy applications.
Across both cities, most datasets align well with key ethical principles such as transparency, openness, sustainability, and beneficence. However, common areas for improvement include clearer licensing, detailed methodological documentation, and transparency about anonymization processes. Applying the Data Ethics Principles from DataEthics.eu and the ODI Data Ethics Canvas reveals that while these public data initiatives are generally well-intentioned and valuable, greater critical reflection and improved documentation could significantly enhance their ethical robustness and trustworthiness.
All of the datasets we used in our project are time dependent and represent data over time. This obliged them to be updated yearly. Unfortunately, some of the datasets are not being updated very regularly.
The data is annual and is being updated every January with care. Therefore, the dataset is up-to-date until 2024. Good to know that the daily data is also available in another dataset, provided by the city council of Bologna.
This data set is being updated yearly and by the end of each year, and it is up-to-date until 2024.
It is mentioned in the information section of the dataset that data shows the situation on 31/12 of each year. Unfortunately, the data for 2024 is not updated and it is up-to-date until 2023.
It is mentioned in the information section of the dataset that data shows the situation on 31/12 of each year. The data for 2024 is not updated and it is up-to-date until 2023.
The data is being updated by the information released by Arpa Lombardia on a daily basis. The data is maintained well and is updated regularly. Although due to a reason mentioned in the source website the data from 1 May to 30 September in 2024 is not available.
The dataset has not been updated since 2018, and due to unknown reasons the new data on Bus Fleet in Milan is not inserted into the dataset.
The dataset has not been updated since 2018, therefore, the dataset will get a poor score with respect to sustainability of the update over time.
The dataset contains data until 2018 and has not been updated ever since.
This dataset should be updated every year and it is up-to-date until the end of 2022 and the last two years are not inserted in the dataset. The data is provided by ACI and their open policy but it is not updated by the city council of Milan.
The quality analysis of these datasets has been carried out following the europan standards applied by Italy UNI ISO/IEC 25012:2014.
| ACCURACY | COMPLETENESS | COHERENCE | TIMELINESS | |
|---|---|---|---|---|
| DS1 | Satisfied. The data and metadata describe precisely and extensively the values. | 100% There aren’t empty cells. | Satisfied. Data formats and values are consistent as well as syntactic expression. | Satisfied. Hourly updates. |
| DS2 | Satisfied. The data and metadata describe precisely and extensively the values. | 100% Some cells (18%) are empty because the value is 0, not because they’re missing values. | Satisfied. Data formats and values are consistent as well as syntactic expression. | Satisfied. Yearly updates from 2019. |
| DS3 | Satisfied. The data and metadata describe precisely and extensively the values. | 100% Some cells (1%) are empty because the value is 0, not because they’re missing values. | Satisfied. Data formats and values are consistent as well as syntactic expression. | Partially satisfied. Yearly updates from 2012 on 31/12; not present year 2024 yet. |
| DS4 | Satisfied. The data and metadata describe precisely and extensively the values. | 100% There aren’t empty cells. | Satisfied. Data formats and values are consistent as well as syntactic expression. | Partially satisfied. Yearly updates from 2016 on 31/12; not present year 2024 yet. |
| DS5 | Satisfied. The data and metadata describe precisely and extensively the values. | 48%. There are 227 days of evaluation missing. | Satisfied. Data formats and values are consistent as well as syntactic expression. | Limited. Relevation only on working days; suspended from 1st May to 30th Sep 2024 |
| DS6 | Satisfied. The data and metadata describe precisely and extensively the values. | 100% There aren’t empty cells. | Satisfied. Data formats and values are consistent as well as syntactic expression. | Limited. Yearly updates from 2014 to 2018; not updated anymore. |
| DS7 | Satisfied. The data and metadata describe precisely and extensively the values. | 100% There aren’t empty cells. | Satisfied. Data formats and values are consistent as well as syntactic expression. | Limited. Yearly updates from 2015 to 2018; not updated anymore. |
| DS8 | Satisfied. The data and metadata describe precisely and extensively the values. | 100% There aren’t empty cells. | Satisfied. Data formats and values are consistent as well as syntactic expression. | Limited. Yearly updates from 2013 to 2018; not updated anymore. |
| DS9 | Satisfied. The data and metadata describe precisely and extensively the values. | 100% Some cells (6.4%) are empty because the value is 0, not because they’re missing values. | Satisfied. Data formats and values are consistent as well as syntactic expression. | Limited. Yearly updates from 2004 to 2022; not updated anymore. Missing 2009 data. |
Following is the evaluation of the source datasets based on the AGID metadata model, classifying metadata quality on a range from 1 to 4, based on the detail level, and the bond between data and metadata.
| ID | Provenance | Format | Metadata | URI | License |
|---|---|---|---|---|---|
| DS1 | Open Data di Comune di Bologna | CSV, JSON, Excel, GeoParquet | 2 - data is accompanied by external metadata, included on the information subpage of the dataset | URI | CC BY-SA 4.0 |
| DS2 | Open Data di Comune di Bologna | CSV, JSON, Excel, GeoParquet | 2 - data is accompanied by external metadata, included on the information subpage of the dataset | URI | CC BY-SA 4.0 |
| DS3 | I numeri di Bologna metropolitana | CSV, PDF, PNG | 1 - no metadata provided | URI | freely reusable statistical data with attribution, per the Comune di Bologna's terms |
| DS4 | I numeri di Bologna metropolitana | CSV, PDF, PNG | 1 - no metadata provided | URI | freely reusable statistical data with attribution, per the Comune di Bologna's terms |
| DS5 | Open Data - Comune di Milano | CSV, JSON | 2 - data is accompanied by external metadata, included on the information subpage of the dataset | URI | CC BY-SA 4.0 |
| DS6 | Open Data - Comune di Milano | CSV, JSON | 2 - data is accompanied by external metadata, included on the information subpage of the dataset | URI | CC BY-SA 4.0 |
| DS7 | Open Data - Comune di Milano | CSV, JSON | 2 - data is accompanied by external metadata, included on the information subpage of the dataset | URI | CC BY-SA 4.0 |
| DS8 | Open Data - Comune di Milano | CSV, JSON | 2 - data is accompanied by external metadata, included on the information subpage of the dataset | URI | CC BY-SA 4.0 |
| DS9 | Open Data - Comune di Milano | CSV, JSON | 2 - data is accompanied by external metadata, included on the information subpage of the dataset | URI | CC BY-SA 4.0 |
All producedd mashup datasets have been described with metadata following the specification of DCAT-AP. While a point may be made, that since all our data are Italian in origin, we could use DCAT-AP_IT instead, we decided on using more flexible (and an European standard) DCAT-AP instead. Additionally, PROV-O, the provenance ontology, is used to described sources and activities.
The metadata for the source datasets has been gathered directly from the original sources. Where information was missing, it was inferred and supplemented following the same guidelines used for mashup datasets (e.g., assigning a theme to a source dataset was done according to the same European authority).
| Title | Vehicular Research on Output and Outcomes in Milan/Bologna - Catalogue |
|---|---|
| Identifier | vroomCatalogue |
| Description | Catalogue containing the mashup datasets for the project Vehicular Research on Output and Outcomes in Milan/Bologna |
| Publisher | VROOM |
| Issued | 2025-06-06 |
| Modified | 2025-06-06 |
| Datasets | MD1, MD2, MDS1_2 |
| Homepage | VROOM |
| Language | English |
| Theme taxonomy | European vocabulary for Data theme |
| License | CC BY-SA 4.0 |
| RDF assertion of metadata |
| Dataset | Title | Identifier | Description | Theme | Subject | Issued | Modified | Accrual periodicity | Rights holder | Creator | Publisher | Distribution | Language | Derived from | License | RDF assertion of the metadata |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS1 | Quality of air in station (historical from 2017) | dati-centraline-bologna-storico | Air quality data from 2017 to 2024, relating to the three monitoring stations located in the municipality of Bologna. | Environment | 5206 politica dell'ambiente | X | April 7, 2025 10:26 AM | Annual | Comune di Bologna | Comune di Bologna | Comune di Bologna | API endpoint | Italian | ARPAE | CC-BY-SA 4.0 | DS1.ttl |
| DS2 | Vehicle fleet in circulation | parco-circolante-veicoli | Vehicle fleet of the Municipality of Bologna divided by postal code of residence of the owners | Transport | 4806 politica dei trasporti | December 22, 2020 | December 31, 2024 10:45 PM | Annual | Comune di Bologna | ACI | Comune di Bologna | API endpoint | Italian | CC-BY-SA 4.0 | ACI | DS2.ttl |
| DS3 | TPER Spa. Vehicle fleet - Number of urban vehicles by fuel - historical series | X | TPER Spa. Vehicle fleet - Number of urban vehicles by fuel - historical series | Transport | 4816 trasporti terrestri | ? | ? | ? | Comune di Bologna | Comune di Bologna | Citta` Metropolitana di Bologna | Tableau | Italian | freely reusable statistical data with attribution, per the Comune di Bologna's terms | ? | DS3.ttl |
| DS4 | TPER Spa. Number of passengers transported - Bologna area - historical series | X | TPER Spa. Number of passengers transported - Bologna area - historical series | Transport | 4806 politica dei trasporti | ? | ? | ? | Comune di Bologna | Comune di Bologna | Citta Metropolitana di Bologna | Tableau | Italian | freely reusable statistical data with attribution, per the Comune di Bologna's terms | ? | DS4.ttl |
| DS5 | Air quality detection | DS407 | The dataset shows the data of the Daily Air Quality Report of the Municipality of Milan drawn up by AMAT, based on the data measured and validated daily by Arpa Lombardia from the institutional air quality stations present in the municipal territory. | Environment | 5206 politica dell'ambiente | X | 24-12-2024 | Daily | Comune di Milano | Comune di Milano | Comune di Milano | API endpoint | Italian | CC-BY-SA 4.0 | AMAT | DS5_1.ttl, DS5_2.ttl, DS5_3.ttl, DS5_4.ttl, DS5_5.ttl, DS5_6.ttl, DS5_7.ttl, DS5_8.ttl |
| DS6 | Low emission buses used for local public transport - indicator per 100 buses and absolute value - Historical series | DS1570 | The dataset shows, starting from 2014, the low-emission buses used for local public transport in the Municipality of Milan (indicator per 100 buses used and absolute value). | Transport | 4816 trasporti terrestri | X | 31-05-2021 | Irregular | Comune di Milano | Unità Servizi Statistici | Comune di Milano | API endpoint | Italian | CC-BY-SA 4.0 | ISTAT | DS6.ttl |
| DS7 | Buses used for local public transport by emission class - Percentage composition - Historical series | DS1568 | The dataset shows, starting from the year 2015, the buses used for local public transport in the municipality of Milan (percentage composition) by emission class (Euro 4 or lower, Euro 5, Euro 6). | Transport | 4816 trasporti terrestri | X | 31-05-2021 | Irregular | Comune di Milano | Comune di Milano | Comune di Milano | API endpoint | Italian | CC-BY-SA 4.0 | ISTAT | DS7.ttl |
| DS8 | TPL demand - Annual passengers per inhabitant - historical series | DS1547 | The dataset shows, starting from 2013, the demand for local public transport, quantified in annual passengers per inhabitant, in the Municipality of Milan | Transport | 4806 politica dei trasporti | X | 26-04-2021 | Irregular | Comune di Milano | Unità Servizi Statistici | Comune di Milano | API endpoint | Italian | CC-BY-SA 4.0 | ISTAT | DS8.ttl |
| DS9 | Vehicle fleet 2004-2022 | DS721 | The dataset includes the number of vehicles in circulation since 2004 | Transport | 4806 politica dei trasporti | X | 12-07-2023 | Never | Comune di Milano | Unità Open Data | Comune di Milano | API endpoint | Italian | CC-BY-SA 4.0 | ASR Lombardia | DS9.ttl |
| Dataset | Title | Identifier | Description | Theme | Subject | Issued | Modified | Accrual periodicity | Rights holder | Creator | Publisher | Distribution | Language | Derived from | License | RDF assertion of the metadata |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| MD1 | MD1 - air quality and vehicle data for Bologna (2017-2024) | MD1 | Masuhp dataset with air quality and various vehicle data (power types of private vehicles, public transport buses efficiency, etc.) for Comune di Bologna, years 2017-2024 | Transport, Environment | 5206 environment policy, 4806 transport policy, 4816 terrestrial transport | 06-06-2025 | 06-06-2025 | Annual | VROOM | VROOM - Ahmadreza Nazari | VROOM | CSV | English | DS1, DS2, DS3, DS4 | CC-BY-SA 4.0 | MD1.ttl |
| MD2 | MD2 - air quality and vehicle data for Milan (2017-2024) | MD2 | Masuhp dataset with air quality and various vehicle data (power types of private vehicles, public transport buses efficiency, etc.) for Comune di Milano, years 2017-2024 | Transport, Environment | 5206 environment policy, 4806 transport policy, 4816 terrestrial transport | 06-06-2025 | 06-06-2025 | Annual | VROOM | VROOM - Hubert Krzywonos | VROOM | CSV | English | DS5, DS6, DS7, DS8, DS9 | CC-BY-SA 4.0 | MD2.ttl |
| MDS1_2 | MDS1_2 - air quality and vehicle registration data per CAP for Bologna (2019-2024) | MDS1_2 | Masuhp dataset with air quality and registration of vehicles per CAP for Comune di Bologna, years 2019-2024 | Transport, Environment | 5206 environment policy, 4806 transport policy, 4816 terrestrial transport | 06-06-2025 | 06-06-2025 | Annual | VROOM | VROOM - Ahmadreza Nazari | VROOM | CSV | English | DS1, DS2 | CC-BY-SA 4.0 | MDS1_2.ttl |
As a part of the technical analysis, we have performed an analysis of the FAIR principles of all the source datasets. These are a set of recommendations proposed by the GO FAIR Initiative, a consortium of scientists and organisations aimed to support Findability, Accessibility, Interoperability and Reusability of digital data.
| DS1 | DS2 | DS3 | DS4 | DS5 | DS6 | DS7 | DS8 | DS9 | |
|---|---|---|---|---|---|---|---|---|---|
| F1. (meta)data are assigned a globally unique and persistent identifier | V | V | X | X | V | V | V | V | V |
| F2. data are described with rich metadata (defined by R1 below) | V | V | X | X | V | V | V | V | V |
| F3. metadata clearly and explicitly include the identifier of the data it describes | V | V | X | X | V | V | V | V | V |
| F4. (meta)data are registered or indexed in a searchable resource | V | V | V | V | V | V | V | V | V |
| DS1 | DS2 | DS3 | DS4 | DS5 | DS6 | DS7 | DS8 | DS9 | |
|---|---|---|---|---|---|---|---|---|---|
| A1. (meta)data are retrievable by their identifier using a standardized communications protocol | V | V | X | X | V | V | V | V | V |
| A1.1. the protocol is open, free, and universally implementable | V | V | X | X | V | V | V | V | V |
| A1.2. the protocol allows for an authentication and authorization procedure, where necessary | V | V | X | X | V | V | V | V | V |
| A2. metadata are accessible, even when the data are no longer available | V | V | X | X | V | V | V | V | V |
| DS1 | DS2 | DS3 | DS4 | DS5 | DS6 | DS7 | DS8 | DS9 | |
|---|---|---|---|---|---|---|---|---|---|
| I1. (meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation. | V | V | V | V | V | V | V | V | V |
| I2. (meta)data use vocabularies that follow FAIR principles | V | V | X | X | V | V | V | V | V |
| I3. (meta)data include qualified references to other (meta)data | X | X | X | X | V | V | V | V | V |
| DS1 | DS2 | DS3 | DS4 | DS5 | DS6 | DS7 | DS8 | DS9 | |
|---|---|---|---|---|---|---|---|---|---|
| R1. meta(data) are richly described with a plurality of accurate and relevant attributes | V | V | X | X | V | V | V | V | V |
| R1.1. (meta)data are released with a clear and accessible data usage license | V | V | X | X | V | V | V | V | V |
| R1.2. (meta)data are associated with detailed provenance | V | V | X | X | V | V | V | V | V |
| R1.3. (meta)data meet domain-relevant community standards | V | V | X | X | V | V | V | V | V |
As can be seen, the datasets are practically grouped in three groups, corresponding to where they were originally published. Datasets DS5 to DS9, coming from the Open Data service of Comune di Milano, comply with all FAIR principles. Datasets DS1 and DS2, coming from the Open Data service of Comune di Bologna, comply with all but one FAIR principle, as they and their metadata lack qualified references to other (meta)data. Datasets DS3 and DS4, on the other hand, are very lackluster when it comes to compliance with FAIR principles. These two datasets come from the metropolitan statistical portal made as part of an agreement between Comune di Bologna and Citta’ Metropolitana di Bologna. The datasets are basically provided as is, with no metadata, no API access and lackluster licensing information; as they are only provided with a copyright saying that the data comes from Comune di Bologna and can be freely consulted, used and reproduced on condition of citing the source. Worth noting is the fact that these two datasets are not available on the Open Data service of the Comune.