Differences

This shows you the differences between two versions of the page.

--- bufr.pm:start [2016-12-07 09:38:48]
pals [bufrextract.pl]
+++ bufr.pm:start [2022-05-31 09:29:31] (current)
@@ Line 11: / Line 11: @@
   * Before trying to install Geo::BUFR you should check that you have Perl installed.
-  * Installing Geo::BUFR will not install any BUFR tables. When invoking the utility programs you should use the option ''%%--%%tablepath'' to tell in which directory you keep your [[http://search.cpan.org/dist/Geo-BUFR/lib/Geo/BUFR.pm#BUFR_TABLE_FILES|BUFR table files]]. Alternatively, you can set the environment variable BUFR_TABLES, or you can change the value of the constant ''DEFAULT_TABLE_PATH'' in the source code of the utility programs (possibly you might want to change the values of ''DEFAULT_TABLE'' and ''DEFAULT_CTABLE'' also).
+  * Installing Geo::BUFR will not install any BUFR tables. When invoking the utility programs you should use the option ''%%--%%tablepath'' to tell in which directory you keep your [[http://search.cpan.org/dist/Geo-BUFR/lib/Geo/BUFR.pm#BUFR-TABLE-FILES|BUFR table files]], and possibly ''%%--%%tableformat'' to tell the table format. Alternatively, you can set the environment variable ''BUFR_TABLES'', or you can change the value of the constant ''DEFAULT_TABLE_PATH'' in the source code of the utility programs (possibly you might want to change the values of ''DEFAULT_TABLE_FORMAT'', ''DEFAULT_TABLE'' and ''DEFAULT_CTABLE'' also).
 ===== bufrread.pl =====
@@ Line 63: / Line 63: @@
 [[bufrresolve_flag|Example]]: Resolving flag value (option %%--%%flag)
+[[bufrresolve_bufrtable|Example]]: Illustrating use of options %%--%%bufrtable and %%--%%tablepath (for a local table B descriptor)
+[[bufrresolve_tableformat|Example]]: Illustrating use of option %%--%%tableformat ECCODES on a local table D descriptor
+[[bufrresolve_verbose|Example]]: Illustrating use of option %%--%%verbose 1 (to see which tables are loaded)
 ===== bufrencode.pl =====
@@ Line 121: / Line 128: @@
 A BUFR toolkit wouldn't be complete unless you have a way to dump the contents of BUFR files in a way which requires no prior knowledge whatsoever of the BUFR format. Therefore, the program bufrdump.pl is included even though it actually does not employ Geo::BUFR.pm, but rather is a wrapper around a Fortran program (named [[bufrdump|bufrdump]]) which uses the [[https://software.ecmwf.int/wiki/display/BUFR/BUFRDC+Home|ECMWF BUFRDC library]] for the BUFR decoding. The reason for this choice was that for this particular program speed might be important (expecting users to dump huge BUFR files and grep'ing on the output), besides the fact that the main part of the program would be equally boring to code whether in Fortran or Perl.
-The parameters are dumped in a ''name=value'' fashion according to what most users at Met Norway expects (see [[http://www.met.no/Parametere+i+Kvalobs-databasen.b7C_wlnG5w.ips|Parametere i Kvalobs-databasen]]), e.g. ''TA=-9.3'' for temperature at 2 m equal to -9.3 Celsius. If your users are accustomed to other symbols and/or units, this should be rather easy to modify in source code of bufrdump.F.
+The parameters are dumped in a ''name=value'' fashion according to what most users at Met Norway expects (see [[https://wiki.met.no/kvalobs/kvalobs/kvalobs-parametre_sortert_alfabetisk_etter_kode|Parametere i Kvalobs-databasen]]), e.g. ''TA=-9.3'' for temperature at 2 m equal to -9.3 Celsius. If your users are accustomed to other symbols and/or units, this should be rather easy to modify in source code of bufrdump.F.
 So far dumping of BUFR SYNOP, TEMP, AMDAR and BUOY have been implemented (probably works also for PILOT, BATHY and TESAC). More observation types are likely to be included in the future.
@@ Line 169: / Line 176: @@
 ===== Sorting BUFR TEMP =====
-According to B/C 25.7: "Temperature, dew-point and wind data at pressure levels obtained during the radiosonde ascent shall be included in descending order with respect to pressure. Data at each pressure level shall be included only once". This makes perfect sence, since it is hard to think of any application where you would not prefer to have this ordering and uniqueness of pressure levels. However, many data producers sin against this regulation, and even more astoundingly: in Note (1) to B/C 25.7 WMO has explicitely allowed violations of this regulation (for BUFR TEMP converted from TAC TEMP).
+According to B/C 25.7: "Temperature, dew-point and wind data at pressure levels obtained during the radiosonde ascent shall be included in descending order with respect to pressure. Data at each pressure level shall be included only once". This makes perfect sense, since it is hard to think of any application where you would not prefer to have this ordering and uniqueness of pressure levels. However, many data producers sin against this regulation, and even more astounding: in Note (1) to B/C 25.7 WMO explicitly allows violations of this regulation (for BUFR TEMP converted from TAC TEMP).
 Therefore [[sortbufrtemp.pl]] was created to do the necessary sorting of pressure levels and possible merging of duplicate levels (i.e. pressure levels having same value for pressure, time and position coordinates).
 [[sortbufrtemp.pl_help|Example]]: sortbufrtemp.pl %%--%%help