SNOTEL GOES Project

1. SNOTEL GOES Project A Cooperative Design Effort Rose Loehr - Portland John Weeks - Portland Austin Beard - Montana Richard Brown - Alaska

2. Seal Island - Prince William Sound, Alaska

3. Primary Design Goal • Add GOES data modems to the SNOTEL operational framework

4. Design Requirements • Automate retrieval of GOES data from NESDIS • Automatically import GOES data to SNOTEL in MBD message format • Accommodate popular GOES modem models • Do not impact SNOTEL structure • Eliminate recurring costs • Should be OS portable

6. Basic msiDCSdecode Functionality • Retrieve data message context from NESDIS • Associate GOES ID with SNOTEL ID • Decode and translate data message context to FP2 parameter format for each sensor value • Generate data messages in MBD format for direct import to SNOTEL • Generate and save GOES RMP messages

7. GOES Data Message Context • Text based system • Various binary encoding schemes are used • All data groups packed in one GOES message

8. SNOTEL GOES Data Message Rules • All sensor values exist in array[0..n-1] • Array[0] must be data julian date • Array[1] must be data time of day

9. Campbell Sci TX312 Simple Interface with CSI Modems FP2 data values Microcom GTX Flexible data value formatting Built in RMP values Supported GOES Data Modems

10. Campbell Sci TX312 Site Name GOES ID = SNOT ID GMT Offset Modem Type Group definitions Microcom GTX Site Name GOES ID = SNOT ID GMT Offset Modem Type Group definitions TPL File What to give to Rose for each site