A few things here, might need to be split into multiple issues.
This all relates to sondehub-amateur telemetry.
Add upload_time field into uploaded packets, which will assist in diagnosing these kind of issues when they occur.
Compare the upload_time field, and the client-submitted datetime field. If datetime is more than 24 hours away from upload_time (either older or newer), set 'telemetry_hidden':Trueunless there is a 'historical':True flag included in the uploaded. This approach allows users the opportunity to 'fill-in' old payload track data if that's what they really want to do.
If the telemetry_hidden flag is set, respond with an appropriate HTTP return code (not 500 or 200) and a response message, which will be shown to the client (for pysondehub, horusdemodlib and Horus-GUI anyway).
A few things here, might need to be split into multiple issues.
This all relates to sondehub-amateur telemetry.
Add upload_time field into uploaded packets, which will assist in diagnosing these kind of issues when they occur.
Compare the upload_time field, and the client-submitted datetime field. If datetime is more than 24 hours away from upload_time (either older or newer), set
'telemetry_hidden':Trueunless there is a'historical':Trueflag included in the uploaded. This approach allows users the opportunity to 'fill-in' old payload track data if that's what they really want to do.If the telemetry_hidden flag is set, respond with an appropriate HTTP return code (not 500 or 200) and a response message, which will be shown to the client (for pysondehub, horusdemodlib and Horus-GUI anyway).