1METAR_GET(1) User Commands METAR_GET(1)
2
3
4
6 metar_get - manual page for metar_get
7
9 NAME metar_get
10
11 DESCRIPTION
12
13 Get values of some keys from a METAR file. It is similar to
14 metar_ls, but fails returning an error code when an error occurs
15 (e.g. key not found).
16
17 USAGE
18
19 metar_get [options] file file ...
20
21 OPTIONS
22
23 -f Force. Force the execution not to fail on error.
24
25 -p key[:{s|d|i}],key[:{s|d|i}],...
26
27 Declaration of keys to print. For each key a string (key:s), a
28 double (key:d) or an integer (key:i) type can be requested. De‐
29 fault type is string.
30
31 -F format
32
33 C style format for floating-point values.
34
35 -P key[:{s|d|i}],key[:{s|d|i}],...
36
37 As -p adding the declared keys to the default list.
38
39 -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,...
40
41 Where clause. Messages are processed only if they match all the
42 key/value constraints. A valid constraint is of type key=value
43 or key!=value. For each key a string (key:s), a double (key:d)
44 or an integer (key:i) type can be specified. Default type is
45 string. In the value you can also use the forward-slash charac‐
46 ter '/' to specify an OR condition (i.e. a logical disjunction)
47 Note: only one -w clause is allowed.
48
49 -n namespace
50
51 All the keys belonging to the given namespace are printed.
52
53 -s key[:{s|d|i}]=value,key[:{s|d|i}]=value,...
54
55 Key/values to set. For each key a string (key:s), a double
56 (key:d) or an integer (key:i) type can be defined. By default
57 the native type is set.
58
59 -V Version.
60
61 -W width
62
63 Minimum width of each column in output. Default is 10.
64
65 -m Mars keys are printed.
66
67 -M Multi-field support off. Turn off support for multiple fields in
68 a single GRIB message.
69
70 -7 Does not fail when the message has wrong length
71
72 NAME metar_get
73
74 DESCRIPTION
75
76 Get values of some keys from a METAR file. It is similar to
77 metar_ls, but fails returning an error code when an error occurs
78 (e.g. key not found).
79
80 USAGE
81
82 metar_get [options] file file ...
83
84 OPTIONS
85
86 -f Force. Force the execution not to fail on error.
87
88 -p key[:{s|d|i}],key[:{s|d|i}],...
89
90 Declaration of keys to print. For each key a string (key:s), a
91 double (key:d) or an integer (key:i) type can be requested. De‐
92 fault type is string.
93
94 -F format
95
96 C style format for floating-point values.
97
98 -P key[:{s|d|i}],key[:{s|d|i}],...
99
100 As -p adding the declared keys to the default list.
101
102 -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,...
103
104 Where clause. Messages are processed only if they match all the
105 key/value constraints. A valid constraint is of type key=value
106 or key!=value. For each key a string (key:s), a double (key:d)
107 or an integer (key:i) type can be specified. Default type is
108 string. In the value you can also use the forward-slash charac‐
109 ter '/' to specify an OR condition (i.e. a logical disjunction)
110 Note: only one -w clause is allowed.
111
112 -n namespace
113
114 All the keys belonging to the given namespace are printed.
115
116 -s key[:{s|d|i}]=value,key[:{s|d|i}]=value,...
117
118 Key/values to set. For each key a string (key:s), a double
119 (key:d) or an integer (key:i) type can be defined. By default
120 the native type is set.
121
122 -V Version.
123
124 -W width
125
126 Minimum width of each column in output. Default is 10.
127
128 -m Mars keys are printed.
129
130 -M Multi-field support off. Turn off support for multiple fields in
131 a single GRIB message.
132
133 -7 Does not fail when the message has wrong length
134
135
136
137metar_get November 2023 METAR_GET(1)