Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapping between Data sets in archives and Deployment in OSCAR is undetermined #14

Open
tomkralidis opened this issue Oct 2, 2019 · 2 comments
Labels
discussion needed Issue needs further discussion within the team documentation Improvements or additions to documentation OSCAR/Surface Issue addresses OSCAR/Surface feature

Comments

@tomkralidis
Copy link
Contributor

(moved from wmo-cop/wmo-oscar#23)

Mapping between data sets in archives and Deployment in OSCAR is undetermined.

@joergklausen joergklausen added discussion needed Issue needs further discussion within the team documentation Improvements or additions to documentation OSCAR/Surface Issue addresses OSCAR/Surface feature question Further information is requested and removed question Further information is requested labels Apr 23, 2021
@joergklausen
Copy link
Contributor

This is very true. The concept of deployment in WMDR is one of a homogeneous time series generated with one instrument, at least with only one method method. Expert judgement is required to decide if an observation should be documented as one or several deployments. The WMDS does not require that a homogeneous time series needs to be described with only one deployment, so annual datasets can in principle be described with multiple deployments.

I see various approaches depending on the situation:

  1. OSCAR/Surface has nothing yet.
    I would suggest to create as many deployments as there are individual data sets /files /URLs in the archive.
  2. OSCAR/Surface already has an observation with 1 deployment
    If the archive has only 1 data set, I suggest to update the existing one in OSCAR/Surface.
    If the archive has several data sets, I suggest to follow option 1 and (manually) migrate any existing additional information in OSCAR/Surface as far as possible, and then delete the existing deployment from OSCAR/Surface. This will require involvement of the station PI.
  3. OSCAR/Surface already has an observation with several deployments
    This will require involvement of the station PI and a treatment on a case-by-case basis, I think.

@tomkralidis @NunesL How do you see this? What is the right forum to discuss and decide?

@tomkralidis
Copy link
Contributor Author

Probably a good discussion for ET-ACDM to get an idea of how data centres model deployments and granularity.

@amilan17 amilan17 moved this to Submitted in OSCAR/Surface Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion needed Issue needs further discussion within the team documentation Improvements or additions to documentation OSCAR/Surface Issue addresses OSCAR/Surface feature
Projects
Status: Submitted
Development

No branches or pull requests

2 participants