issue #287 adding new radar entried in code table 4.2.0.15 and creati…

…ng new code table 4.106

GRIB2_CodeFlag_4_106_CodeTable_en.csv

@@ -0,0 +1,17 @@
+Title_en,SubTitle_en,CodeFlag,Value,MeaningParameterDescription_en,Note_en,noteIDs,UnitComments_en,Status
+Radar data quality flags,,0,,Normal operating data,,,,Operational
+Radar data quality flags,,1,,No data,(see Note 1),287b,,Operational
+Radar data quality flags,,2,,Undetected,(see Note 2),287c,,Operational
+Radar data quality flags,,3,,Implausible data/outliers,(see Note 3),287d,,Operational
+Radar data quality flags,,4,,Beam overshooting,,,,Operational
+Radar data quality flags,,5,,Beam blocking,,,,Operational
+Radar data quality flags,,6,,Ground clutter,,,,Operational
+Radar data quality flags,,7,,Sea clutter,,,,Operational
+Radar data quality flags,,8,,Beam attenuation,,,,Operational
+Radar data quality flags,,9,,Wet radome attenuation,,,,Operational
+Radar data quality flags,,10,,Wind turbines,,,,Operational
+Radar data quality flags,,11,,Insects/birds,,,,Operational
+Radar data quality flags,,12,,Ships/aircrafts,,,,Operational
+Radar data quality flags,,13-189,,Reserved,,,,Operational
+Radar data quality flags,,192-254,,Reserved for local use,,,,Operational
+Radar data quality flags,,255,,Missing,,,,Operational

GRIB2_CodeFlag_4_2_0_15_CodeTable_en.csv

@@ -16,6 +16,8 @@ Parameter number by product discipline and parameter category,"Product disciplin
 Parameter number by product discipline and parameter category,"Product discipline 0 - Meteorological products, parameter category 15: radar",14,,Reflectivity of hail,,,dB,Operational
 Parameter number by product discipline and parameter category,"Product discipline 0 - Meteorological products, parameter category 15: radar",15,,Hybrid scan reflectivity,,,dB,Operational
 Parameter number by product discipline and parameter category,"Product discipline 0 - Meteorological products, parameter category 15: radar",16,,Hybrid scan reflectivity height,,,m,Operational
-Parameter number by product discipline and parameter category,"Product discipline 0 - Meteorological products, parameter category 15: radar",17-191,,Reserved,,,,Operational
+Parameter number by product discipline and parameter category,"Product discipline 0 - Meteorological products, parameter category 15: radar",18,,Radar data quality index,(see Note 1),287a,proportion,Operational
+Parameter number by product discipline and parameter category,"Product discipline 0 - Meteorological products, parameter category 15: radar",19,,Radar data quality flag,,,Code Table 4.106,Operational
+Parameter number by product discipline and parameter category,"Product discipline 0 - Meteorological products, parameter category 15: radar",20-191,,Reserved,,,,Operational
 Parameter number by product discipline and parameter category,"Product discipline 0 - Meteorological products, parameter category 15: radar",192-254,,Reserved for local use,,,,Operational
 Parameter number by product discipline and parameter category,"Product discipline 0 - Meteorological products, parameter category 15: radar",255,,Missing,,,,Operational

notes/CodeFlag_notes.csv

@@ -159,4 +159,8 @@ noteID,note
 162,"Ben Bouallègue, Z. (2021). On the verification of the crossing-point forecast. Tellus A: Dynamic Meteorology and Oceanography, 73(1), 1–10. [https://doi.org/10.1080/16000870.2021.1913007]"
 163,In relation to local coordinate axes at a (grid) cell edge.
 164,"When using entry 10, the lower limit is used to encode the quantile q (must be an integer between 0 and Q) while the upper limit is used to encode the total number of quantiles Q. This defines the probability of the parameter falling within quantile q. For instance, to encode the probability of falling within the 10th percentile, then q=10 and Q=100; to encode the probability of falling within the 1st tercile, then q=1 and Q=3."
-165,"Model physics are perturbed (for example, with methods like SPPT, SPP and SKEB."
+165,"Model physics are perturbed (for example, with methods like SPPT, SPP and SKEB."
+287a,"Spatially analyzed quality indicator, according to OPERA II (Holleman I., Michelson D., Galli G., Germann U., and Peura M., 2006: Quality information for radars and radar data. OPERA II deliverable OPERA_2005_19), normalized to between 0 (poorest quality) to 1 (best quality)."
+287b,"'Undetected' means that the received radar signal is at or below noise level."
+287c,"‘No data’ describes that a data point is out of range or in a blanked sector."
+287d,"‘Implausible data / outliers’ refers to values that are not physically plausible."