X-Git-Url: https://www.yuggoth.org/gitweb?p=weather.git;a=blobdiff_plain;f=INSTALL;h=6e64ce2063f4bcccfd9e241d2a3718378db66c07;hp=9e2eeedd4b833312339402a87d14b0076d4dfb66;hb=49a6ebe7607034a3a51782c3e97fa8d2bf123aeb;hpb=93f58b4538974d6c1d0161cf1d273fe7576c74dd diff --git a/INSTALL b/INSTALL index 9e2eeed..6e64ce2 100644 --- a/INSTALL +++ b/INSTALL @@ -2,7 +2,7 @@ Basic Unix Installation Instructions for the Weather Utility ============================================================== -:Copyright: (c) 2006-2012 Jeremy Stanley . Permission +:Copyright: (c) 2006-2014 Jeremy Stanley . Permission to use, copy, modify, and distribute this software is granted under terms provided in the LICENSE file distributed with this software. @@ -47,7 +47,7 @@ your path (/usr/local/bin/ or ~/bin/ for example). Similarly, weather.py needs to be somewhere in Python's include path. You can see your Python interpreter's default include path by running:: - python -c "import sys ; print sys.path" + python -c 'import sys ; print(sys.path)' If the correlation data files are to be used (airports, places, stations, zctas, zones), they need to be in your current working @@ -66,3 +66,41 @@ Manuals Optionally, the weather.1 and weatherrc.5 files can be placed in sane locations for TROFF/NROFF manual files on your system (for example, /usr/local/share/man/ or ~/man/). + +Updating Correlation Sets +------------------------- +The version control repository and tarballs are occasionally updated +with refreshed correlation sets (the files which track what the nearest +stations and weather zones are to various places). If you find you need +to generate updated correlation sets yourself, however, it can be done. + +You'll need to retrieve the most recent source databases from the +different sites mentioned in the comments at the top of a recent +correlation data file--each one includes a comment block with a list of +the origins and checksums of the data files used along with the date and +time they were built. You'll also want to generate recent slist and +zlist files (look at the comments at the top of each for the shell +commands used to generate them). You probably also need the most recent +overrides.conf from the weather source repository or tarball, since that +contains known corrections for errors in the original data. Put all of +these files in your current working directory and then call:: + + weather --build-sets + +Then wait, and wait, and wait some more. After loading and analyzing the +source data, it will guess an upper-bound for the number of great-arc +distance calculations it may have to perform and attempt to give you a +progress bar indicating percent completion. If you're lucky, it will +finish successfully also generate some automated quality assurance +analysis of the results (mostly checking for obviously bad airports, +stations, zones). If you are UNlucky, it will break, which is not +terribly uncommon because the government-provided source data is often +misformatted or gets sudden schema changes requiring updates to the +parsing routines in weather. + +If you're using a system-wide (for example, distribution packaged) copy +of weather and its data, you may want to place the new airports, +stations, places, zctas and zones files into your ~/.weather directory +and make use of the setpath configuration or command-line options to +override where weather looks for them. See the weather(1) and +weatherrc(5) manpages for details.