Topic
 

climatologyMeteorologyAtmosphere

31 record(s)
 
Type of resources
Available actions
Topics
INSPIRE themes
federalThemes
Keywords
Contact for the resource
Provided by
Years
Formats
Representation types
Update frequencies
status
Scale
Resolution
From 1 - 10 / 31
  • Hail products are derived from the observed vertical profiles of radar reflectivity and the NWP vertical profiles of temperature. Three types of products are generated. poh : probability of hail of any size (larger than 0.5 cm diameter)expressed in %. posh : probability of severe hail(larger than 2cm)expressed in %. mesh : maximum expected size of hailexpressed in mm of hailstone diameter. All products are generated every 5 minutes. This product is not publically available yet.

  • Polar volume reflectivity data from the Jabbeke weather radar. Volume data files are produced every 5 minutes from a multiple elevation scan. This product is not publicly available yet.

  • Bird density profiles are derived from weather radar volume data in real time, by the vol2bird algorithm as described in Dokter et al. (2011, 2019). The vol2bird algorithm exploits the radar reflectivity characteristics of different scatterers in the atmosphere, in order to distinguish biological from non-biological radar echoes. Once biological scatterers are isolated in the volume files, the reflectivity of these scatterers is converted in an estimate of the bird density per vertical layer of 200m, using a mean cross section of 11 cm2. The vbird profiles are provided for the following radars, with the radar owner in parentheses: Jabbeke (RMI), Wideumont (RMI), Helchteren (VMM), Zaventem (Skeyes), Herwijnen (KNMI), Den Helder (KNMI), Neuheilenbach (DWD), Essen (DWD), Abbeville (Météo-France) and Avesnois (Météo-France). References: - Dokter A.M., Liechti F., Stark H., Delobbe L., Tabary P., Holleman I., Bird migration flight altitudes studied by a network of operational weather radars, J. R. Soc. Interface, 8, 30–43, 2011, DOI 10.1098/rsif.2010.0116 - Dokter A.M., Desmet P., Spaaks J.H., van Hoey S., Veen L., Verlinden L., Nilsson C., Haase G., Leijnse H., Farnsworth A., Bouten W., Shamoun-Baranes J., bioRad: biological analysis and visualization of weather radar data, Ecography, 42, 852-860, 2019, DOI 10.1111/ecog.04028

  • RADQPE provides high resolution radar-based quantitative precipitation estimation in realtime for Belgium and its surroundings. This product is not publically available yet.

  • Hail products are derived from the observed vertical profiles of radar reflectivity and the NWP vertical profiles of temperature. Three types of products are generated. poh : probability of hail of any size (larger than 0.5 cm diameter)expressed in %. posh : probability of severe hail(larger than 2cm)expressed in %. mesh : maximum expected size of hailexpressed in mm of hailstone diameter. All products are generated every 5 minutes. This product is not publically available yet.

  • Polar volume reflectivity data from the Wideumont weather radar. Volume data files are produced every 5 minutes from a multiple elevation scan. This product is not publicly available yet.

  • UV Index derived from spectral measurements with a Brewer UV spectrophotometer. This product is not publically available yet.

  • The data consists in tables of estimated extreme precipitation quantities for precipitation durations ranging from 10 minutes to 30 days and return periods ranging from 2 to 200 years for each Belgian municipality.

  • Hail products are derived from the observed vertical profiles of radar reflectivity and the NWP vertical profiles of temperature. Three types of products are generated. poh : probability of hail of any size (larger than 0.5 cm diameter)expressed in %. posh : probability of severe hail(larger than 2cm)expressed in %. mesh : maximum expected size of hailexpressed in mm of hailstone diameter. All products are generated every 5 minutes. This product is not publically available yet.

  • Total lightning observations, i.e., cloud-to-ground (CG) strokes and intra/inter-cloud (IC) pulses, in Belgium. BELLS data is given in Universal Time! (local time winter = UT +1; local time summer = UT + 2). Each record contains following fields: 1. Network type, 0 = LF, 1 = VHF-TOA, 2 = VHF-ITF, 3 = VLF 2. Year, 1970 to 2032. 3. Month, with January as 1 and December as 12. 4. Day of the month, 1 to 31. 5. Hour, 0 to 23. 6. Minute, 0 to 59. 7. Second, 0 to 60. 8. Nanosecond, 0 to 999999999. 9. Latitude of the calculated location in decimal degrees, to 4 decimal places, -90.0 to 90.0. 10. Longitude of the calculated location in decimal degrees, to 4 decimal places, -180.0 to 180.0. 11. Altitude in meters, -4950 to +60535. This field will be 0 if the altitude is not provided in the lightning data. 12. The altitude uncertainty in meters. This field will be 0 if the altitude uncertainty is not provided in the lightning data. 13. Estimated peak current in kiloamps, -9999 to 9999. 14. VHF Range normalized power, -9999.0 to 9999.0 15. Multiplicity for flash data (1 to 99) or 0 for strokes. 16. Cloud pulse count for the lightning record. This field will be -1 if the lightning did not contain the cloud pulse count attribute. 17. Number of sensors participating in the solution, 2 to 99. 18. Degrees of freedom when optimizing location, 0 to 99. 19. The error ellipse angle as a clockwise bearing from 0 degrees north, 0 to 180.0 degrees 20. The error ellipse semi-major axis length in kilometers, 0 to 50.0km. 21. The error ellipse semi-minor axis length in kilometers, 0 to 50.0km. 22. Chi-squared value from location optimization, 0 to 999.99 23. Rise time of the waveform in microseconds, 0 to 99.9 24. Peak-to-zero time of the waveform in microseconds, 0 to 999.9 25. Maximum rate-of-rise of the waveform in kA/usec (will be a negative rate if discharge is negative), -999.9 to 999.9 26. Cloud indicator, 1 if Cloud-to-cloud discharge, 0 for Cloud-to-ground 27. Angle indicator, 1 if sensor angle data used to compute position, 0 otherwise 28. Signal indicator, 1 if sensor signal data used to compute position, 0 otherwise 29. Timing indicator, 1 if sensor timing data used to compute position, 0 otherwise 30. Flash ID, a unique integer value identifying the flash grouping a stroke belongs to or 0 if not set. This product is not publically available yet.