The fields provided contain the __maps of reflectivity in dBZ__ reported at the surface level, obtained from the radar systems of the sites of San Pietro Capofiume (BO) and Gattatico (RE), managed by ARPAE.
The area covered by the acquisition can change depending on the specific scanning modes applied, covering up to 250 km of range from the radar.
The raw data, measured by the systems, are processed for the removal of clutter (static and abnormal propagation) and interference sources (through the use of a static map, a filter on the spatial consistency of the measured reflectivity and reflectivity fields), are therefore corrected for partial concealment, due to the Apennine chain.
Further algorithms such as reflectivity profile correction and rectification due to stratiform-convective classification of current precipitation may also be applied.
The algorithms applied in each map are reported in the “task” attribute. The field is encoded according to the following rule: each algorithm is associated with a key, the keys are separated by the character “_” (underscore).
<TABLE>
<THEAD>
<TR>
<td>__Key_<\td><td> — <\td><td>_Algoritmo_<\td>:
<\TR>
<\THEAD>
<TR>
<td>__ZLR_<\td><td> — <\td><td>_Algorithm not specified_<\td>
<\TR>
<TR>
<td>___<\td><td> — <\td><td>_Static map clutter_<\td>
<\TR>
<TR>
<td>__AP_<\td><td> — <\td><td>_Spatial coherence filter for abnormal propagation and interference_<\td>
<\TR>
<TR>
<td>__BB__<\td><td> — <\td><td>_BeamBlocking_<\td>
<\TR>
<TR>
<td>__VPR_<\td><td> — <\td><td>_Vertical reflectivity profile_<\td>
<\TR>
<TR>
<td>__CLASS__<td><td> — <\td><td>_layer-convective classification_<\td>
<\TR>
<\TABLE>
The generated reflectivity field can be accompanied by a quality map, normalised between 0 and 1. This map is to be understood as a relative indication of the intrinsic quality of the measured data (due among other causes to the distance from the radar, the attenuation suffered in the path) and the application of the algorithms mentioned.
The timing of data acquisition varies depending on the presence of precipitation in progress. The maximum frequency is reached under disrupted time conditions with one acquisition every 5’.
As a rule, for every hour, the following acquisitions are available:
<TABLE>
<TR>
<td>__Condition__<td><td> — <\td><td>_Minuti start volumetric acquisition_<\td>
<\TR>
<TR>
<td>__Undisturbed time__<td><td> — <\td><td> 00; 10; 15; 25; 30; 40; 45; 55<\TD>
<\TR>
<TR>
<td>__disturbed time__<td><td> — <\td><td> 00; 05; 10; 15; 20; 25; 30; 35; 40; 45; 50; 55<\TD>
<\TR>
</TABLE>
The data provided are encoded in [Odimh5v2.1 format](https://drive.google.com/file/d/1OKJ7FHcKThf4eIfvEzqIJWL6tBJX_He6/view?usp=sharing).
Arpae also shared on Github the [library](https://github.com/ARPA-SIMC/radarlib) with the radar data volume management package and results written in ODIMH5 format (v 2.0 and 2.1).
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.