A vigilance bulletin relating to air pollution in the Auvergne-Rhône-Alpes region is generated during each activation of a vigilance. It stems from the recommendations of the Zonal Framework Order on Prefectural Procedures in the Event of Ambient Air Pollution. This vigilance bulletin is produced on the basis of information from the forecasting chain and the expertise of a forecaster. It mainly deals with the situation planned for the next 24 hours. As a rule, it is broadcast before 2 p.m. To take into account the exposure of the population, it incorporates criteria of area, number of inhabitants exposed or specific situations. It indicates the pollutant concerned, the date of the episode, the areas involved, and the level of vigilance (yellow, orange, red). It includes health messages adapted to the pollutant corresponding to the current pollution episode, as well as behavioural recommendations. Depending on the circumstances, it may be followed by an activation of a prefectural information or alert device.
Link to the WFS feed (last 3 days episodes): [https://dservices3.arcgis.com/o7Q3o5SkiSeZD5LK/arcgis/services/alrt3j_aura/WFSServer?service=wfs&request=getcapabilities](https://dservices3.arcgis.com/o7Q3o5SkiSeZD5LK/arcgis/services/alrt3j_aura/WFSServer?service=wfs&request=getcapabilities)
The level of vigilance air pollution observed for the air basins of the Auvergne-Rhône-Alpes region for the past year and until the day before is available in csv format. <HTTP://DEPOT.ATMO-AURA.FR/VIGILANCE/>
Link to the metadata sheet: [https://ids.craig.fr/geocat/srv/fre/catalog.search#/metadata/171e406c-df1f-47e3-b241-33f938f49951 ](https://ids.craig.fr/geocat/srv/fre/catalog.search#/metadata/171e406c-df1f-47e3-b241-33f938f49951)
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.