See also a handheld gps measurement of NUK_L position in 2007 and 2008 from a maintenance report:
Knowing the expected degree of the latitude and degree of longitude (given in the config file), pypromice L0toL1 reformats to decimal degree coordinates:
@PennyHow I don't have the overview of the reformatting needed from at AWS. It looks like it's interpreting some coordinates as mm.ss (minutes.second).
probably the cause of https://github.com/GEUS-Glaciology-and-Climate/PROMICE-AWS-data-issues/issues/90
Prior to 2009, GPS was only saving the decimal minutes to the logger file.
Example here from NUK_L 2008 file
See also a handheld gps measurement of NUK_L position in 2007 and 2008 from a maintenance report:![image](https://github.com/GEUS-Glaciology-and-Climate/pypromice/assets/35140661/400fc330-ff25-441b-8c77-16414323c101)
Knowing the expected degree of the latitude and degree of longitude (given in the config file), pypromice L0toL1 reformats to decimal degree coordinates:
https://github.com/GEUS-Glaciology-and-Climate/pypromice/blob/50bab76d7199ed541aa663c92a008704c62de13c/src/pypromice/process/L0toL1.py#L74-L76
https://github.com/GEUS-Glaciology-and-Climate/pypromice/blob/50bab76d7199ed541aa663c92a008704c62de13c/src/pypromice/process/L0toL1.py#L363-L384
In this function and in this case, it should read more like:
@PennyHow I don't have the overview of the reformatting needed from at AWS. It looks like it's interpreting some coordinates as mm.ss (minutes.second).