AWS data checklist whilst in the field
For the field teams
Recent posts
Using the Synoptic API service to retreive GEUS data
Overview Synoptic Data PBC operates several services to access and view surface mesonet data. The GEUS AWS network (network=281) is accessible via these serv...
Procedures for GEUS Dataverse AWS data releases
We release up-to-date PROMICE/GC-Net automated weather station data on our GEUS Dataverse at the beginning of each month. This repository can be found here.
Things to do before and after a new pypromice release
Most of our continual integration is automated, as shown below. But there are a couple of things that need to be checked at each step to ensure that everythi...
Monitoring and alerting
Our python monitoring scripts are located at the aws-monitor-alert Github repo. See the README for a description of the monitoring methods. These scripts are...
Accessing data at the THREDDS Data Server
The GEUS Glaciology and Climate THREDDS data server (TDS) is located here: https://thredds.geus.dk This guide should be updated with any additional data ac...
THREDDS Data Server: background and guide
THREDDS background The GEUS Glaciology and Climate THREDDS data server (TDS) is located here: https://thredds.geus.dk This web server is intended to provi...
Re-mounting the Glaciologi drive for AWS data syncing
Where does our Level 3 AWS data reside? The Level 3 automated weather station (AWS) datasets from the PROMICE and GC-Net monitoring programmes live in numer...
WMO BUFR processing: background and guide
The following is a background and guide to the processing of BUFR files for submission of PROMICE and GC-Net data to the World Meteorological Organization (W...
Retrieving Level 0 transmission data (L0 TX) from a weather station
Fetching L0 TX messages Level 0 transmission messages, L0 TX, are collected and transmitted in near-real-time every hour to a designated account space. We c...