8349654b7c
* Release 1.4. * (all): Updated the copyright years for 2008 on some of the files in the current release and added a copyright statement to any files previously lacking one. * LICENSE: Replaced the previous BSD-like license with the one used by the OpenBSD project (modeled after the Internet Software Consortium's, a two-clause BSD license removing language made unnecessary by the Berne convention); this new license is functionally identical to the old one, just more terse and openly recognized. * weather: Clarified function parameters in calls from the wrapper script to ease future ABI changes in the underlying module. * weather, weather.py: Some extra comments were added to the source, indentation style was updated from tab characters to three-space, and lines longer than 79 columns were refactored or otherwise split. * weather.1, weather.5, weather.py: Added an flines option to allow the maximum number of forecast output lines to be shortened. Added furl and murl options to allow overriding of the default current conditions and forecast data retrieval URLs. Added a headers option to allow overriding the default list of header names for current conditions data filtering. Added a quiet option to suppress the preamble lines and indentation for both current conditions and forecast output. * weather.py: Replaced the hardcoded fallback default METAR station ID and forecast city/state abbreviation with error messages to minimize confusion when necessary values are omitted. Adjusted a couple of hard-coded error message strings to be consistent with the output format of the option_parser module. Switched from urllib to urllib2 for retrieving data, providing a simpler means to detect and report retrieval errors. Upped the version to 1.4.
72 lines
2.7 KiB
Plaintext
72 lines
2.7 KiB
Plaintext
FREQUENTLY ASKED QUESTIONS ABOUT THE WEATHER UTILITY
|
|
|
|
Copyright (c) 2006-2008 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.
|
|
|
|
|
|
Table of Contents:
|
|
|
|
1. Can I help?
|
|
2. How do I figure out my local METAR station ID?
|
|
3. How do I figure out my local city name and state abbreviation?
|
|
4. I live outside the USA--can this be made to work for me
|
|
anyway?
|
|
5. Why do I get the wrong forecast when specifying -i or --id?
|
|
|
|
|
|
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. One big way anyone can
|
|
help is to provide me with some additional mappings of METAR
|
|
station ID, city name and state abbreviation for inclusion in the
|
|
default /etc/weatherrc file.
|
|
|
|
|
|
2. How do I figure out my local METAR station ID?
|
|
|
|
The list of stations is found at
|
|
http://weather.noaa.gov/data/nsd_cccc.gz (it's thousands of lines
|
|
long, so I recommend keyword searching in your browser or using
|
|
grep(1) to find what you're looking for).
|
|
|
|
|
|
3. How do I figure out my local city name and state abbreviation?
|
|
|
|
The forecasts can be located starting from
|
|
http://weather.noaa.gov/pub/data/forecasts/city/ (choose the
|
|
state abbreviation to get to a list of cities in that state).
|
|
|
|
|
|
4. I live outside the USA--can this be made to work for me
|
|
anyway?
|
|
|
|
METAR station IDs can be found for cities and airports worldwide,
|
|
but forecast data is harder to come by. If you have any
|
|
recommendations of forecast data for other countries available in a
|
|
format like NOAA's, I will be happy to try and find a way to
|
|
integrate it into the weather utility, but I suspect that some
|
|
serious modification would be necessary given that the data is
|
|
likely to be published in a non-English language, requiring 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?
|
|
|
|
The -i or --id switch (or the id parameter in an alias definition),
|
|
only tells weather(1) what current conditions to retrieve. If you
|
|
specify -f or --forecast on the command line (or forecast=True in
|
|
an alias) without providing a city name and state abbreviation
|
|
(-c/--city and -s/--st, or city and st in an alias) and are seeing
|
|
an actual forecast, then you probably have a default city and state
|
|
abbreviation set in your config. See question 3 above for
|
|
information on figuring out what city name and state abbreviation
|
|
to use, and the manual for weatherrc(5) for information on defining
|
|
aliases.
|