However the logger files up to 2012 at SCO_U and up to 2016 at SCO_L do contain coordinates that could be used to estimate the current position. But that would require few changes because the estimation of the latest position is currently done in the find_position function, itself called in the BUFR processing step which is run on the transmission data only.
So we could either:
feed the historical data to the getBUFR function
or
make a separate function for estimating the latest coordinates on both transmission and logger data.
This is an expected consequence from not using the latitude and longitude contained in the Iridium emails which were of very poor quality. At these sites, the transmissions do not contain any coordinates from which the current position could be extrapolated.
However the logger files up to 2012 at SCO_U and up to 2016 at SCO_L do contain coordinates that could be used to estimate the current position. But that would require few changes because the estimation of the latest position is currently done in the find_position function, itself called in the BUFR processing step which is run on the transmission data only.
So we could either:
This could be related to #142, #152, https://github.com/GEUS-Glaciology-and-Climate/PROMICE-AWS-data-issues/issues/46.