Transmitter "drifted" field and changes

network
db

#1

Recently, changes were made in db and network to better handle the concept of a published frequency versus an observed or “drifted frequency”.

In db, you can now suggest a drifted frequency for a transmitter, and observations will be scheduled with that drift taken into consideration:

image

With this in mind, we will be going through and adding downlink drifts to the original transmitter entries where applicable, and duplicate entries that were made for drifted downlinks will be marked as ‘invalid’ - they will remain in the db tables and api for consistency and history but will not show in the UI and will not appear when scheduling new observations.

Old observations will not be impacted, this will make for a cleaner experience across both db and network.

SO-50 is a good example where this was just done today.

cheers!