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

Model for DataGeneration needs to be improved #48

Open
joergklausen opened this issue Apr 1, 2022 · 3 comments
Open

Model for DataGeneration needs to be improved #48

joergklausen opened this issue Apr 1, 2022 · 3 comments
Labels
discussion needed Issue needs further discussion within the team enhancement New feature or request help wanted Extra attention is needed

Comments

@joergklausen
Copy link
Contributor

Motivation

The current FeatureType 'DataGeneration' defines a DataType 'Schedule' without specifying whether this schedule actually describes the 'Sampling' or the 'Reporting', both of which can reasonably be assumed to be implied. This leads to ambiguities and makes it difficult to correctly describe the procedures involved in generating and distributing data. An example are manual observations of total ozone using the Dobson instrument. Typically, such observations are made a few times per day, the data are aggregated to a daily value, and they are reported to a data centre on more or less regular basis, but potentially only every (few) year(s) in the worst case. Other examples are presumably observations from the polar regions that may not be possible during polar night, but may be fairly frequently made during polar day; or observations from mobile marine platforms. The original intention of 'schedule' was thus more to describe the sampling (the actual generation of data), but the UML model is ambiguous. Also, if 'schedule' is used for the sampling, it is not available to describe the reporting (distribution) aspects.

Stakeholder

WOUDC (@tomkralidis ), WDCA/WDCRG (@markusfiebig), OceanObs (@anthoninlize ), others

Proposal

Review the model of DataGeneration. Presumably, remove DataType 'Schedule' from 'DataGeneration' and include it both as an element of 'Sampling' and 'Reporting'. Test any proposed solution specifically with examples from typical application areas (regular meteorological observations from land-based stations; radar; ocean; GCW; GAW; polar observations; on demand observations)

@joergklausen joergklausen added enhancement New feature or request help wanted Extra attention is needed discussion needed Issue needs further discussion within the team labels Apr 1, 2022
@fstuerzl
Copy link
Member

The schedule problem was already mentioned in an older issue (#39) by @nuneslf and @KarlBureau, who also provided useful examples.

@amilan17
Copy link
Member

This has been under discussion recently. We should look at solutions with current standard and determine if it's just a matter of guidance or if the standard needs to evolve.

@joergklausen
Copy link
Contributor Author

Cf. https://github.com/wmo-im/wmdr2/wiki/WMDRRoadmap where this is taken up as well.

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 enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants