tools:eionet-utdretriever
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
tools:eionet-utdretriever [2016/01/27 11:35] jcuadrad Added new mode of operation (download_no_filters) |
tools:eionet-utdretriever [2016/12/29 09:09] (current) kserrade [Repository] |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| This tool provides automated data collection from the [[http:// | This tool provides automated data collection from the [[http:// | ||
| - | The aim is to further improve the gathering of air quality observations across Europe by using the [[http:// | + | The aim is to further improve the gathering of air quality observations across Europe by using the [[http:// |
| ==== Description ==== | ==== Description ==== | ||
| Line 11: | Line 11: | ||
| The functionality provided is a retriever of (near real time) air quality observations from stations adhered to EIONET network. | The functionality provided is a retriever of (near real time) air quality observations from stations adhered to EIONET network. | ||
| - | The tool is able to connect to EIONET servers, download the required data, parse it, check for validity of observations and store them in the Air Quality Forecast Evaluation (eval_new) database.\\ This tool also inserts new stations in the " | + | The tool is able to connect to EIONET servers, download the required data, parse it, check for validity of observations and store them in the Air Quality Forecast Evaluation (eval_new) database. |
| The validity checks performed on the retrieved data are the ones described in this PDF: | The validity checks performed on the retrieved data are the ones described in this PDF: | ||
| Line 43: | Line 43: | ||
| The EIONET (up-to-date) air quality data is available for the following geographic areas/ | The EIONET (up-to-date) air quality data is available for the following geographic areas/ | ||
| ^ Code ^ Name ^ Code ^ Name ^ | ^ Code ^ Name ^ Code ^ Name ^ | ||
| - | | AT| Austria | + | | AD| Andorra |
| - | | BE| Belgium | + | | AT| Austria |
| - | | DE| Germany | + | | BE| Belgium |
| + | | DE| Germany | LV| Latvia | ||
| | DK| Denmark | MK| Macedonia | | | DK| Denmark | MK| Macedonia | | ||
| | ES| Spain | MT| Malta | | | ES| Spain | MT| Malta | | ||
| Line 54: | Line 55: | ||
| | HR| Croatia | SE| Sweden | | | HR| Croatia | SE| Sweden | | ||
| | HU| Hungary | SI| Slovenia | | | HU| Hungary | SI| Slovenia | | ||
| + | | | | SK| Slovakia | | ||
| - | To see the **current status on data delivery**, which countries are delivering data and what they deliver, please see this [[https:// | + | To see the **current status on data delivery**, which countries are delivering data and what they deliver, please see this **[[https:// |
| + | For further information about stations definitions used by EIONET please refer to: [[tools: | ||
| - | Please refer to the " | + | Please note that EIONET reports the different network_timezone for each station in which the reported observations are. This tool automatically translates all observations to UTC. All observations stored in the eval_new database are in UTC. \\ |
| + | ** Since 20/apr/2016 EIONET is reporting the metadata for the time zone of observations in Spain, Lithuania, Macedonia and Slovenia (that was previously missing). Therefore, all observations since 20/apr/2016 should be as correct as the information provided by the Member States to EIONET. To date, 05/may/2016 we are still troubleshooting (in contact with Generalitat de Catalunya and EIONET) a discrepancy of 1h of difference in observations for Catalunya. ** \\ | ||
| + | Until 20/apr/2016 it was assumed that observations were in UTC, when no metadata was provided. | ||
| + | |||
| + | Please refer to the " | ||
| ==== Requirements ==== | ==== Requirements ==== | ||
| Line 81: | Line 88: | ||
| The two available commands are: | The two available commands are: | ||
| * download: Normal operation, automated data download data uses the UpdatedSince and CreatedSince filters. In this mode, the retriever will keep track of the dates of last successful download for each pollutant and country, storing it in the DOWNLOAD_DATE table in the database. | * download: Normal operation, automated data download data uses the UpdatedSince and CreatedSince filters. In this mode, the retriever will keep track of the dates of last successful download for each pollutant and country, storing it in the DOWNLOAD_DATE table in the database. | ||
| - | * download_no_filters: | + | * download_no_filters: |
| + | * download_sliding_no_filters: | ||
| In the " | In the " | ||
| < | < | ||
| In this example, all observations of the countries (de,at,pl) and pollutants defined in the " | In this example, all observations of the countries (de,at,pl) and pollutants defined in the " | ||
| + | |||
| + | Example for " | ||
| + | If today is 2016-01-27 and we want to download the observations of days 2016-01-12 and 2016-01-13 we can get them in two ways: | ||
| + | < | ||
| + | python3 EIONETretriever.py download_sliding_no_filters ES --fromDaysAgo 15 --toDaysAgo 13 > logs/ | ||
| + | Please note that in this mode, if the option --toDaysAgo is not provided the download will be until to date (now). \\ | ||
| + | |||
| As usual, the --help (or -h) option will also display the command-line manual/ | As usual, the --help (or -h) option will also display the command-line manual/ | ||
| Please note that this article always refers to the ' | Please note that this article always refers to the ' | ||
| Line 107: | Line 122: | ||
| Please note that when FromDate is used, then ToDate is mandatory to obtain a response from the service. (When using the command-line options if ToDate is not defined it will be ' | Please note that when FromDate is used, then ToDate is mandatory to obtain a response from the service. (When using the command-line options if ToDate is not defined it will be ' | ||
| Due to the different upload and update patterns of the data providers it is needed to request at least a couple of days of observations for the FromDate field, and at the same time, use the UpdatedSinceDate and InsertedSinceDate filters (see " | Due to the different upload and update patterns of the data providers it is needed to request at least a couple of days of observations for the FromDate field, and at the same time, use the UpdatedSinceDate and InsertedSinceDate filters (see " | ||
| - | The recommended value for ' | + | The recommended value for ' |
| == Filters on data download == | == Filters on data download == | ||
| Line 120: | Line 135: | ||
| == Further documentation == | == Further documentation == | ||
| - | **Internal request fields (to the EIONET service) used in this tool can be found here: http:// | + | * Slides presenting the tool, including information about the number of stations, the rationale behind the different config files and for the chosen update patterns used in the cron, etc. {{tools: |
| - | More technical documentation (Sphinx-generated) can be found under the directory docs in the repository. | + | * **Internal request fields (to the EIONET service) used in this tool** can be found here: http:// |
| + | | ||
| ==== Repository ==== | ==== Repository ==== | ||
| - | The link to the GIT repository is:\\ < | + | The link to the GIT repository is:\\ < |
tools/eionet-utdretriever.1453894500.txt.gz · Last modified: 2016/01/27 11:35 by jcuadrad
Page Tools
