search

GEUS-Glaciology-and-Climate / pypromice

Process AWS data from L0 (raw logger) through Lx (end user)
https://pypromice.readthedocs.io
GNU General Public License v2.0
14 stars 4 forks source link

Define station location #43

Closed mankoff closed 1 year ago

mankoff commented 3 years ago

See also v3 NetCDF file location definition: https://github.com/GEUS-Glaciology-and-Climate/AWS_v3/issues/7

PennyHow commented 1 year ago

Nominal fixed location remains defined in the NetCDF metadata as follows:

https://github.com/GEUS-Glaciology-and-Climate/pypromice/blob/2331c02e1e121648c06dd054d370f0b99a6a8f6d/src/pypromice/aws.py#L507-L517

So the mean latitude, longitude and altitude for the entire time-series is used as the fixed location. Instead, we could:

  1. Use the position defined in the station config .toml file, but these are usually not very exact
  2. Use the most recent position (i.e. the last data entry, however then the metadata would be forever changing
  3. Use set positions defined on a yearly basis, but then the position is subjective

So, I think it best to stick with the current solution approach for now. If an alternative idea comes up then this issue can be re-opened.