joergklausen
commented
3 years ago The DataTypes "Schedule" (which is really a coverage) and "Reporting" are currently mandatory attributes of the FeatureType "DataGeneration" (cf. https://schemas.wmo.int/wmdr/1.0RC9/html/). So, logically, for each DataGeneration validPeriod, a Schedule and Reporting need to be defined. This allows for changes over time. The example given by @nuneslf can be partially translated using elements as follows:
- collect data every minute all year round: temporalSamplingInterval + Schedule
- send data to central system every 30': this cannot be explicitly expressed. Using aggregationPeriod, the aggregation to 30' data can be described, but it is only implicitly assumed that these data are available locally.
- reports are disseminated to GTS/WIS every hour: This can be expressed with the elements under "Reporting", although the target "GTS/WIS" cannot be stated. If internationalExchange=True, the Reporting is to some international target, if internationalExchange=False, the Reporting is to some national target.
If a more explicit differentiation between national and international reporting is really needed, it appears that changing the cardinality of the "Reporting" attribute of DataGeneration from currently 1 to 1..2 is the most appropriate way to go. The existing flag internationalExchange would indicate if exchange is international or not. This would also create the flexibility to specify different dataFormat, dataPolicy, officialStatus etc. for national and international reporting. A specific recipient would still not be specified.
@nuneslf and other interested stakeholders: Please comment if this meets the requirements.
nuneslf
KarlBureau
amilan17
david-i-berry
Rationale: The WMDS should allow for three levels of schedule: i) observation (6-08 Schedule of observation), ii) reporting to a central location, e.g. NMHS headquarters (7-03 Temporal reporting period) iii) international reporting (7-14 Schedule of international exchange) When ii and iii are the same, it is okay that 7-14 is a binary element (Y/N); the issue is when they are different, then 7-14 needs to be allow providing the actual schedule.
Element 7-14 was introduced to distinguish international reporting from non-international reporting, i.e. from the first level of reporting, for which 7-03 is used; So, in the WMDS element 7-14 should be "detached" from the non-international level of reporting to allow describing a different schedule if needed. Example: an AWS is configured to collect data every minute all-year-round (schedule of observation); it sends data to a central system every 30 minutes; reports are disseminated to GTS/WIS every hour.
Below are the current WMDS definition and note, with some suggestions: Current definition = Allows distinction if/when observations are made/not made available internationally; Suggested new definition = Schedule of observations reported internationally Current NOTE: A binary element (yes/no), that should be associated with the observed variable for each declared observing schedule (7-03 Temporal reporting period) Suggestion to remove the current NOTE.