File: FAQ

package info (click to toggle)
weather-util 2.5.0-1
  • links: PTS
  • area: main
  • in suites: sid, trixie
  • size: 36,120 kB
  • sloc: python: 2,196; makefile: 15
file content (78 lines) | stat: -rw-r--r-- 3,634 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
======================================================
 Frequently Asked Questions About the Weather Utility
======================================================

:Copyright: (c) 2006-2024 Jeremy Stanley <fungi@yuggoth.org>. Permission
            to use, copy, modify, and distribute this software is
            granted under terms provided in the LICENSE file distributed
            with this software.

.. contents::

1. Can I help?
--------------
Sure! Bug reports and feature suggestions are always welcome, but fixes
and patches are of course preferred. Contact fungi@yuggoth.org if
desired, but please read this FAQ and the included manuals for
weather(1) and weatherrc(5) before asking questions that might be
answered therein.

2. How do I figure out my local METAR station ID?
-------------------------------------------------
The list of stations included in the "stations" file is comprised of
thousands of entries, so if you're within the USA it's recommended to
use weather's built-in Census place name and ZCTA (postal ZIP code)
searching capabilities. Otherwise, using its latitude,longitude
coordinate search feature is probably your best bet. See the weather(1)
manual for examples.

3. How do I figure out my local city name and state abbreviation?
-----------------------------------------------------------------
As of the 2.0 release, this is no longer necessary. In Spring of 2011
the NWS switched away from city-named forecast zone IDs to the numeric
state zone IDs also used for alerts. As a result, weather now comes with
pregenerated correlations between airports/stations and zones along with
USA Census (FIPS and ZCTA/ZIP code) and global latitude,longitude
coordinates and can search among them in a flexible and intuitive
manner. See the weather(1) manual for examples.

4. I live outside the USA--can this be made to work for me anyway?
------------------------------------------------------------------
ICAO codes for METAR stations can be found for cities and airports
worldwide, but forecast and alert data is harder to come by. If you have
any recommendations of plaintext data for other countries available in a
format like NOAA's, I will be happy to start incorporating it into the
weather utility. If the data is published in a non-English language,
I'll require some additional input from speakers of that language for
how to handle filtering and formatting of the text.

5. Why do I get the wrong forecast when specifying -i or --id?
--------------------------------------------------------------
As of the 2.0 release, this question is no longer relevant.

6. Where can I get a list of the NWS advisory zones for alerts?
---------------------------------------------------------------
As of the 2.0 release, this is no longer necessary. See FAQ entries #2
and #3 for more detail.

7. What values are valid for a --headers list?
----------------------------------------------
The default set it uses if you don't override it yourself on the command
line or in configuration is as follows::

  heat_index
  precipitation_last_hour
  relative_humidity
  sky_conditions
  temperature
  weather
  wind
  windchill

These are a case-insensitive match against the start of lines in a
decoded METAR up to the first colon (:) with spaces optionally replaced
by underscores (_). You can see the full METAR for a given condition
report by passing --verbose or by observing one directly (perhaps by
looking in your *datacache* directory). Unfortunately I haven't found
any proper specification for the decoded METAR format used by the NWS so
know of no comprehensive list of what lines might appear.