
SNOTEL GOES Manual Revision 2b - February 17, 2011 page 4 of 10
Micro Specialties, Inc. Wasilla, Alaska
GOES.py rev 2.2.2010 – Objects and methods pertaining to NESDIS GOES
message structure.
Configuration Files
The operation of msiDCSdecode and its supporting modules is controlled and
configured by several configuration files. All configuration files are simple, plain-text
files, which may be edited by any plain-text editor such as vi or notepad.
sitedefs.txt – Defines the site specifics and message grouping for all sites defined
within the application.
This configuration file uses keyword:value mapping to define configuration values. The
following keywords are valid:
Keyword Values
site: A generic name for the data site, ie: Sidney, Montana
snotID: The site‟s SNOTEL site ID, ie: 2120
goesID: The site‟s GOES DCP address, ie:DA5014EA
gmtOffset: The time offset from GMT for this site, ie: -8 (PST)
modemType: The GOES modem used, ie: tx312 or gtx
group: SNOTEL group definition: grpNum, startIndex..endIndex ie:
group:1,2..17
enabled Enables data collection for this site
SiteDef Notes:
Lines beginning with the pound character (#) are ignored.
The scope of each site definition is from the site keyword, to the next site keyword.
The order of keywords is not important, except that all keywords following a “site”
keyword, apply to that site. Groups, for instance, may be defined in any order.
Each site may have multiple group definitions.
GTX sensor labels, defined within the GTX TPL file can now be used freely and
interchangeably with sensor array indices to define sensor groups.
Group definitions may contain multiple sensor sequences like 3..6 which is equivalent to
3,4,5,6 or batt..pill, or 3..pill.
The sensor sequence in a Group Definition may be in any random order now. For
example a group may be defined with this order: 8..10,7,2,3..6,12.
If a group definition has the added parameter of “midnight”, that group is expected only
at the midnight (0000) hour. Each GOES message is expected to contain in its data
array[0], the Julian Date produced by the data logger, and in array[1], the local standard
time produced by the data logger. Midnight groups are only processed when
array[1] is 0000 (midnight). At all other times, midnight groups are ignored,
whether or not the values are present in the array.
The gmtOffset is used to calculate the site‟s Local Standard Time. Daylight Time is not
supported. The MBD data message‟s reception time is delivered as Local Standard
Time, as well as the message‟s data time. Note that the reception time is based on
the DCP’s GOES transmission-time window, and will always be the same time of
the hour. For this reason, the difference between the reception time and the data
time cannot be utilized as a measure of the site’s communication performance.
Commenti su questo manuale