#
# Also note that the current Auto Wx InfoEx documentation shows these
# keys in a graphical table with the "index" beginning at 1, but here we
-# are sanely indexing beginning at 0.
+# sanely index beginning at 0.
fmap = {} ; final_data = [None] * 29
fmap['Location UUID'] = 0 ; final_data[0] = infoex['location_uuid']
fmap['obDate'] = 1 ; final_data[1] = None
# sort and isolate the most recent, see note above in NRCS for how and
# why this is done
#
- # NOTE: Unlike in the NRCS case, the MesoWest API respones contains all
+ # NOTE: Unlike in the NRCS case, the MesoWest API response contains all
# data (whereas with NRCS, we have to make a separate request for
- # each element we want. This is nice for network efficiency but
+ # each element we want). This is nice for network efficiency but
# it means we have to handle this part differently for each.
#
# NOTE: Also unlike NRCS, MesoWest provides more granular data; NRCS
# any possible elementCds we may want are any other data
# type than float.
#
- # Another possibility is to query the API with
+ # Another possibility is to query the API with
# getStationElements and temporarily store the
# storedUnitCd. But that's pretty network-intensive and
# may not even be worth it if there's only e.g. one or two
f.close()
if not options.dry_run:
- # not a dry run
with open(infoex['csv_filename'], 'rb') as f:
log.debug("uploading FTP file '%s'" % (infoex['host']))
ftp = FTP(infoex['host'], infoex['uuid'], infoex['api_key'])