Giter VIP home page Giter VIP logo

gcnet_positions's People

Contributors

baptistevandecrux avatar jasonebox avatar

Watchers

 avatar  avatar  avatar

gcnet_positions's Issues

Note on the files containing coords without year

output/GC-Net_info_incl_1999.csv

https://github.com/GEUS-Glaciology-and-Climate/GCNet_positions/blob/main/output/GC-Net_info_incl_1999.csv

SWC: same coords as 1990 (within rounding), discarding
CP1: different from other coords listed there, could be real obs from missing year
NASA-U: off the main track of other coords, discarding
GITS: off the main track of other coords, discarding
HUM: same coords as 1995, discarding
SUM: different from other coords listed there, could be real obs from missing year
TUN: different from other coords listed there, could be real obs from missing year, same as metadata_2000 (below)
DY2: different from other coords listed there, could be real obs from missing year
JAR1: same as 1996, discarding
SDO: different from other coords listed there, could be real obs from missing year
NAE: different from other coords listed there, could be real obs from missing year, same as metadata_2000 (below)
NSE: different from other coords listed there, could be real obs from missing year
PET: different from other coords listed there, could be real obs from missing year
NEM: different from other coords listed there, could be real obs from missing year
EGP: different from other coords listed there, could be real obs from missing year

metadata file from 2000

https://github.com/GEUS-Glaciology-and-Climate/GC-Net-level-1-data-processing/blob/main/metadata/Gc-net_documentation_Nov_10_2000_outdated.pdf

most of the coordinates have a year of measurements, but some are left without one

Saddle: coords off-track, discarding
TUN: same as GC-Net info_incl_1999.csv
NAE: same as GC-Net info_incl_1999.csv

WMO coordinates in 2012 report

https://github.com/GEUS-Glaciology-and-Climate/GCNet_positions/blob/main/data/GC_Net_SYNOP_status20120301.pdf

SWC: somewhere between 2005 and 2006 coordinates, discarding
CP1: different from other coords listed there, could be real obs from missing year
GITS; different from other coords listed there, could be real obs from missing year
HUM: same as 1995, discarding
SUM: different from other coords listed there, could be real obs from missing year
TUN: different from other coords listed there, could be real obs from missing year
DY2: different from other coords listed there, could be real obs from missing year
JAR1: same as 2005, discarding
SDL: different from other coords listed there, could be real obs from missing year
SDO: different from other coords listed there, could be real obs from missing year
NAE: different from other coords listed there, could be real obs from missing year
NSE: off track, discarding
NEM: different from other coords listed there, could be real obs from missing year

apparent bias between ATM data and single frequency GPS data compilation

according to the ATM data v1 user guide and the v2 data guide ATM heights are "above WGS84 ellipsoid", which I think is the same as for the single frequency GPS data compilation.

Yet, the single frequency GPS elevations are often lower than the ATM data.

Here's an example that includes both 'handheld' elevations, mainly from Koni Steffen's field notes, and monthly averages from the GEUS GC-Net data. The difference in this case is the single frequency GPS data are mostly ca. 60 m lower.

Crawford Point 1

or mostly ca. 40 m lower for single frequency GPS data at Saddle

Saddle

for Swiss Camp, the monthly averages of single frequency GPS data from the GEUS AWS are ca. 50 m lower. However the nearest point has moved downslope so I should search by an annually varying position.

Swiss Camp

Yet, it's not always that the single frequency GPS data are lower, e.g. Summit, below so I am thinking the single frequency data are unreliable BUT the monthly averages from single frequency should not be biased?

Summit

Find all the plots in https://github.com/GEUS-Glaciology-and-Climate/GCNet_positions/tree/main/ATM/Figs

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.