Air quality control units (historical since 2017)

Open data API in a single place

Provided by Comune di Bologna

Get early access to Air quality control units (historical since 2017) API!

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

Dataset information

Catalog

Comune di Bologna catalog

Country of origin

Italy

Updated

2025.12.31 09:18

Created

2025.12.31

Available languages

English

Keywords

parchi, verde-urbano, ambiente

Datasource

Official portal for European data link

Quality scoring

Dataset description

Data on air quality from the year 2017 to 2022, relating to the three control units located in the municipality of Bologna. The data were processed starting from those made available by ARPAE Emilia Romagna available at [following address] (https://dati.arpae.it/dataset/quality-of-air-monitoring-network). The data shall be updated up to the year preceding the current year. If you want to see the data of the current year [click here](https://bologna.opendatasoft.com/explore/dataset/centraline-qualita-aria/information/)The control units are as follows:Giardini MargheritaVia ChiariniPorta San FeliceThe data are updated annually in January of each year.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

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

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service