Quick fix removing the gap-filling of missing GPS data with coordinates from the Iridium emails.
Those bad coordinates are causing the issues reported in #152.
I am suspecting that some stations' position are heavily relying on the (bad) coordinates from the Iridium messages. This update will probably mean that those stations will not have coordinates in AWS_latest_locations.csv anymore. But this should be fixed (later) by linear fits of lat, lon and altitude from the entire record. This also means that it needs to be done elsewhere than in the function "getBUFR" which currently only looks at transmission.
Quick fix removing the gap-filling of missing GPS data with coordinates from the Iridium emails. Those bad coordinates are causing the issues reported in #152.
I am suspecting that some stations' position are heavily relying on the (bad) coordinates from the Iridium messages. This update will probably mean that those stations will not have coordinates in AWS_latest_locations.csv anymore. But this should be fixed (later) by linear fits of lat, lon and altitude from the entire record. This also means that it needs to be done elsewhere than in the function "getBUFR" which currently only looks at transmission.