Another addition should be to have an intended and observed distinction for all 4 frequencies. In order not to break compatibility with existing usages of our DB we should add 4 frequency fields (down low/high, up low/high) for “published” (vs observed) frequencies. Thus we will be eliminating a lot of “drifted” transmitter entries.
One issue with the drifted transmitters is that currently on network we don’t save separately the observed frequency but we connect the observation with the transmitter.
This means that if we schedule observation with a transmitter at 145.800 MHz and in the future we change this to 145.850MHz, then the first ones will show falsely that the observation happened at 145.850MHz instead of the real frequency at 145.800MHz.
IMHO, there is no point in using the drift history parameter for any correlation. This is a value suggested by the user for future observations and does not necessarily match the actual drift observed. If we want to keep records of the actual drift, that should be an attribute related to the observations and not the transmitter (which just provides input for it).
I can find at least 4-5 uses cases which such information may used for scientific research. Do we want the SatNOGS DB to be the source for such cases? If yes, we should start to think about possible such cases.
User suggestion does not mean acceptance right? What is the process currently for accepting a drifting suggestion? Even if the user observed a drift, we cannot take it for sure (old TLE, mis-configured SDR, etc)
Now regarding the low and high frequency, I think that is a bit odd such naming. Which is the actual carrier frequency? (up - low)/2.0 ?
The most common AFAIK is the (center frequency, bandwidth) scheme.
@surligas historicity of frequencies will be derived by checking the past artifacts (since observed freq is one of their attribute). No need to track this in our model since this should be coming from actual observations done (and also vetting of them).
Can you expand on that a bit? How would that affect the proposed model changes?