* The metadata are provided in a separate file. This comma delimited file can contain comments (same syntax as for the configuration files) and must contain
*
* The metadata are provided in a separate file. This comma delimited file can contain comments (same syntax as for the configuration files) and must contain
* first the station ID (as used in the meteo data file name and in the configuration file), a full name, the decimal latitude, decimal longitude and the altitude.
* @code
* #ID,name,lat,lon,alt
...
...
@@ -50,7 +50,7 @@ namespace mio {
* @endcode
*
* @section alpug_units Units
* Temperatures are in Celsius, relative humidity between 0 and 100%, snow heights in cm. The timestamp is formatted as <a href="https://de.wikipedia.org/wiki/DIN_1355-1">DIN 1355</A>,
* Temperatures are in Celsius, relative humidity between 0 and 100%, snow heights in cm. The timestamp is formatted as <a href="https://de.wikipedia.org/wiki/DIN_1355-1">DIN 1355</A>,
* that is as "DD.MM.YYYY HH:MIN".
*
* @section alpug_keywords Keywords
...
...
@@ -62,7 +62,7 @@ namespace mio {
* - ALPUG_FIELDS: comma delimited list of fields. The fields <b>MUST</b> use the \ref meteoparam "MeteoData" naming scheme. Unknown or ignored fields are replaced by "%".
* - WRAP_MONTH: which month (numerical) triggers the start of a new file (belonging to the next year. Default: 10); [Input] section
* - METAFILE: file within METEOPATH that contains the stations' metadata; [Input] section
*
*
* @code
* METEO = ALPUG
* METEOPATH = ./Met_files
...
...
@@ -73,12 +73,12 @@ namespace mio {
* @endcode
*/
conststd::stringALPUG::dflt_extension=".met";
constchar*ALPUG::dflt_extension=".met";
constdoubleALPUG::plugin_nodata=-999.;//plugin specific nodata value. It can also be read by the plugin (depending on what is appropriate)
constsize_tALPUG::max_buffered_lines=4;//how many lines to keep in buffer in order to detect and silently skip duplicates
conststd::stringmsg="No data file found for station "+station_id+" in \'"+inpath+"\'"+". Files should be named as {YY}{station_id}"+dflt_extension+" with {YY} the last two digits of the year.";
* The Station meteo data files is a station centered, ascii file format that has been designed with flexibility and ease of use in mind. Please refer to its
* <a href="../SMET_specifications.pdf">official format specification</a> for more information (including the list of standard parameters: TA, TSS, TSG,
* The Station meteo data files is a station centered, ascii file format that has been designed with flexibility and ease of use in mind. Please refer to its
* <a href="../SMET_specifications.pdf">official format specification</a> for more information (including the list of standard parameters: TA, TSS, TSG,
* RH, VW, DW, ISWR, OSWR, ILWR, OLWR, PINT, PSUM, HS). For PINT, it is assumed that the intensity (in mm/h) is valid for the whole period between the actual
* time step and the previous one.
*
*
* This plugin can also provide Points Of Interest, given as a SMET file containing either latitude/longitude/altitude or easting/northing/altitude. For the latter,
* the header must contain the epsg code (see example below).
*
* Non-standard parameters can also be given, such as extra snow temperatures. These parameters will then take the name that has been given in "fields", converted to uppercase.
* Non-standard parameters can also be given, such as extra snow temperatures. These parameters will then take the name that has been given in "fields", converted to uppercase.
* It is usually a good idea to number these parameters, such as TS1, TS2, TS3 for a serie of temperatures at various positions.