Use GPS ref. time to sync profiles
- Dominant language
- Python
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the change**
@thaifoon makes the following comment:
> I would urge to switch the profile synchronization, whenever possible, to GPS time-based synchronization. I am becoming more and more convinced, that profile synchronization based on the analysis of the measurands is biasing the results in the end. As far as I have seen, every radiosonde is providing relative time referencing with available conversion to a universal timeline, be it GPS time, UTC or local.
To implement this in dvas, we need to include those reference times in the metadata.
**Open questions:**
1) For GDPs, what are the attributes we have to extract ?
2) For constructor data, will this reference time be included in the data file, or should it be added to the metadata .yml ?
Contributor guide
Assessment
This issue has not been assessed yet.