geus-glaciology-and-climate / gcnet_positions Goto Github PK
View Code? Open in Web Editor NEWGCNet_positions
GCNet_positions
first, renamed folder from "2010 JAR1 gps" to "2009 JAR1" because the relevant data are from 2009
now, to resolve the offset of the red stars dots in the graphic below, I think we need to know a couple offsets:
An offset of -4.0 m would bring the red stars to the best guess magenta line in the figure... I don't believe the GPS antenna would be 4 m above ground.
By the way, GPS equipment is not featured in the photos archive (links below),
even though the horizontal position is uncertain, with 4 positions in the ./GCNet_positions/meta/GC-Net historical positions.xlsx, we have a large 39 m elevation change to incorporate from this repo, so it's worth approximating a changing horizontal position then running this file.
Also relevant is analyze_AWS_elevs_including_ATM_v4.py in this repo
I've taken the work forward by bringing in M. Stober's measurements at SWC and JAR, and may have some other updates, but am unable to push the updates!
Not everywhere, but at NSE, HUM, DY2, CP1, the 2023 geodetic field survey result (cyan circle) (data file link below) has an offset from the single frequency GPS result (red squares), suspect difference results from AWS single frequency GPSm has EGM96 embedded and returns elevation relative to EGM96. [email protected] understands the issue.
Examples below
Need to get some description of the GNSS set up from a field team member.
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
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
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
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.
or mostly ca. 40 m lower for single frequency GPS data at 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.
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?
Find all the plots in https://github.com/GEUS-Glaciology-and-Climate/GCNet_positions/tree/main/ATM/Figs
presently this code uses a static lat lon while variable lat lon data exist, from which we should get a better elevation measurement from ATM over time.
It would not be hard to have a variable position per year using the interpolated positions
we can/should improve the approximations *_info.csv (magenta line in figures) e.g. by
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.