1METAR_LS(1) User Commands METAR_LS(1)
2
3
4
6 metar_ls - manual page for metar_ls
7
9 NAME metar_ls
10
11 DESCRIPTION
12
13 List content of METAR files printing values of some keys. It
14 does not fail when a key is not found.
15
16 USAGE
17
18 metar_ls [options] file file ...
19
20 OPTIONS
21
22 -p key[:{s|d|i}],key[:{s|d|i}],...
23
24 Declaration of keys to print. For each key a string (key:s), a
25 double (key:d) or an integer (key:i) type can be requested. De‐
26 fault type is string.
27
28 -F format
29
30 C style format for floating-point values.
31
32 -P key[:{s|d|i}],key[:{s|d|i}],...
33
34 As -p adding the declared keys to the default list.
35
36 -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,...
37
38 Where clause. Messages are processed only if they match all the
39 key/value constraints. A valid constraint is of type key=value
40 or key!=value. For each key a string (key:s), a double (key:d)
41 or an integer (key:i) type can be specified. Default type is
42 string. In the value you can also use the forward-slash charac‐
43 ter '/' to specify an OR condition (i.e. a logical disjunction)
44 Note: only one -w clause is allowed.
45
46 -j json output
47
48 -B 'order by' directive
49
50 Order by. The output will be ordered according to the 'order by'
51 directive. Example: "step:i asc, centre desc" (step numeric as‐
52 cending and centre descending) Default sort mode is 'asc'
53
54 -s key[:{s|d|i}]=value,key[:{s|d|i}]=value,...
55
56 Key/values to set. For each key a string (key:s), a double
57 (key:d) or an integer (key:i) type can be defined. By default
58 the native type is set.
59
60 -n namespace
61
62 All the keys belonging to namespace are printed.
63
64 -m Mars keys are printed.
65
66 -V Version.
67
68 -W width
69
70 Minimum width of each column in output. Default is 10.
71
72 -g Copy GTS header.
73
74 -7 Does not fail when the message has wrong length
75
76 NAME metar_ls
77
78 DESCRIPTION
79
80 List content of METAR files printing values of some keys. It
81 does not fail when a key is not found.
82
83 USAGE
84
85 metar_ls [options] file file ...
86
87 OPTIONS
88
89 -p key[:{s|d|i}],key[:{s|d|i}],...
90
91 Declaration of keys to print. For each key a string (key:s), a
92 double (key:d) or an integer (key:i) type can be requested. De‐
93 fault type is string.
94
95 -F format
96
97 C style format for floating-point values.
98
99 -P key[:{s|d|i}],key[:{s|d|i}],...
100
101 As -p adding the declared keys to the default list.
102
103 -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,...
104
105 Where clause. Messages are processed only if they match all the
106 key/value constraints. A valid constraint is of type key=value
107 or key!=value. For each key a string (key:s), a double (key:d)
108 or an integer (key:i) type can be specified. Default type is
109 string. In the value you can also use the forward-slash charac‐
110 ter '/' to specify an OR condition (i.e. a logical disjunction)
111 Note: only one -w clause is allowed.
112
113 -j json output
114
115 -B 'order by' directive
116
117 Order by. The output will be ordered according to the 'order by'
118 directive. Example: "step:i asc, centre desc" (step numeric as‐
119 cending and centre descending) Default sort mode is 'asc'
120
121 -s key[:{s|d|i}]=value,key[:{s|d|i}]=value,...
122
123 Key/values to set. For each key a string (key:s), a double
124 (key:d) or an integer (key:i) type can be defined. By default
125 the native type is set.
126
127 -n namespace
128
129 All the keys belonging to namespace are printed.
130
131 -m Mars keys are printed.
132
133 -V Version.
134
135 -W width
136
137 Minimum width of each column in output. Default is 10.
138
139 -g Copy GTS header.
140
141 -7 Does not fail when the message has wrong length
142
143
144
145metar_ls December 2022 METAR_LS(1)