4 This program fetches data from an NRCS SNOTEL or MesoWest station and
5 pushes it into the InfoEx system using the new automated weather system
8 License under the ISC license (see file: LICENSE).
13 Your usage of the NRCS, MesoWest, and/or InfoEx systems is bound by
14 their respective terms and this software makes no attempt or claim to
15 abide by any such terms.
20 It's recommended to use venv and pip with this program. Here's a typical
21 sequence of commands for a new setup:
24 `$ python3 -m venv env`
25 `$ . env/bin/activate`
26 `$ pip install -r requirements.txt`
31 This program is designed to be run from the command line (or via
32 cron(8)) and administered via a simple, concise configuration file.
34 This design allows you to run a separate program instance for each NRCS
35 or MesoWest weather station from which you'd like to automate the
36 importation of data into your InfoEx subscriber account.
38 To run ad-hoc (be sure to activate the virtual environment, as detailed in the
39 Installation section):
41 `./infoex-autowx.py --config [path/to/config-file.ini] [--dry-run]`
43 **NOTE: Specifying --dry-run will also not clean up the generated CSV
44 file.** This is so that you can debug any issues more easily.
46 Here's an example of a crontab(5) with two SNOTEL sites, each of which
47 will run once per hour (note that this will activate the virtual environment
50 `2 * * * * /usr/bin/env bash -c 'cd /home/user/infoex-autowx && source env/bin/activate && ./infoex-autowx.py --config laurance-lake.ini'`
51 `4 * * * * /usr/bin/env bash -c 'cd /home/user/infoex-autowx && source env/bin/activate && ./infoex-autowx.py --config mud-ridge.ini'`
56 The configuration file is separated into two parts, the [station]
57 portion, and the [infoex] portion.
59 The [station] values describe which weather station's data you're after.
60 See the next section in this README for instructions on obtaining these
63 The [infoex] values describe your credentials for the InfoEx automated
64 weather station FTP server and other InfoEx-related configuration
68 `type = # either mesowest or nrcs #`
69 `token = # MesoWest API token -- ignored when type is nrcs #`
70 `station_id = # the NRCS/MesoWest identifier for a particular station #`
71 `desired_data = # a comma-delimited list of fields you're interested in #`
72 `units = # either english or metric -- ignored when type is nrcs #`
75 `host = # InfoEx FTP host address #`
76 `uuid = # InfoEx-supplied UUID #`
77 `api_key = # InfoEx-supplied API Key #`
78 `csv_filename = # arbitrary name of the file that will be uploaded to InfoEx #`
79 `location_uuid = # the UUID used by InfoEx to identify your automated Wx site #`
81 Finding Your NRCS `station` values
82 ----------------------------------
84 To complete the [station] configuration section for an NRCS station, you
85 must fill in the attributes of the NRCS SNOTEL site from which you want
88 Here are the steps to do that:
90 1. Find your station by clicking through this website:
92 https://www.wcc.nrcs.usda.gov/snow/sntllist.html
94 Or by using the interactive map:
96 https://www.nrcs.usda.gov/wps/portal/wcc/home/quicklinks/imap
98 2. Once you've found your station, look for the "Station ID" (a 3- or
101 3. Combine your Station ID, state abbreviation, and the network type
102 "SNTL" to get your NRCS station triplet (`station_id`, in the
103 configuration file). For example:
107 would represent the Mud Ridge station (Station ID 655) in the state
108 of Oregon (OR). SNTL just represents that the station is in the
109 SNOTEL network and is used internally by NRCS.
111 Once you have your station ID, fill in the field in your configuration
112 file. Now you must select which data you'd like to pull from NRCS to
115 For that, visit the NRCS web service:
117 https://wcc.sc.egov.usda.gov/awdbWebService/webservice/testwebservice.jsf?webserviceName=/awdbWebService
119 Click "getElements" on the left, and then click, "Test Operation." This
120 will return a long list of elements to your web browser from which you
121 can choose. Each returned element has its identifier and a description.
123 Once you've chosen your elements, combine all of their respective
124 "elementCd" values into a comma-delimited string and put that into your
125 configuration file as the `desired_data` value.
131 `station_id = 655:OR:SNTL`
132 `desired_data = TOBS,PREC`
134 indicates that I'd like to import "AIR TEMPERATURE OBSERVED" and
135 "PRECIPITATION ACCUMULATION" from the NRCS SNOTEL site at Mud Ridge, OR,
138 Finding your MesoWest `station` values
139 --------------------------------------
141 MesoWest has great documentation which can be found here:
143 https://developers.synopticdata.com/mesonet/v2/getting-started/
145 To complete the [station] configuration section for a MesoWest station,
146 you must fill in the attributes of the MesoWest station ID from which
147 you want to import data. Here are the steps to do that:
149 1. Firstly, get set up with MesoWest's API by going to the above
150 'Getting Started' link. Once you're set up, you can copy a token from
151 the MesoWest web portal into your configuration file's `token` value.
153 2. Next, you will want to find the Station ID for the MesoWest weather
154 station of interest and copy it to the `station_id` value.
156 3. Finally, you must choose what data types you want to push into
157 InfoEx and compile them into a comma-separated list. MesoWest refers
158 to these as 'field names' or 'station variables' and a list is
161 https://developers.synopticdata.com/about/station-variables/
163 The MesoWest API supports on-the-fly unit conversion, so that can be
164 specified to infoex-autowx via the configuration option `units`. This
165 can be either 'english' or 'metric', with 'english' meaning imperial
166 units as used in the United States.
172 `token = # token id copied from MesoWest web account #`
174 `desired_data = air_temp,snow_depth`
177 indicates that I'd like to import "Temperature" and "Precipitation
178 accumulated" from the MesoWest station at Santiam Pass, OR, into InfoEx,
179 and that I want that data in imperial units.
186 Implement MesoWest integration.
188 This release also makes significant changes to the configuration file,
189 hence the major version bump. Such changes are not taken lightly but
190 given the desire to support multiple data sources, were necessary.
194 First released version. Cleaned up the program and design.
195 Implemented configuration file, added LICENSE, README, docs, etc.
199 First finished (unreleased) version.
201 - pre-0.8.0 (Apr 2020)
203 First (private) finished implementation with successful importation of
204 NRCS data into InfoEx.