CDMS-issue-tracker
CDMS Issue Tracker
| Identifier | Action | Stage Reached | Asked by | Date of request | CDMS Parent Component (if applicable) | Procedure | Decision | Description | Coordinator | LastModif | Deadline | Status | Completness | Comments | atts |
| 1 | WWR guidelines | Proposal received | Bill Wright | 2016-04-26 | 4.4 WMO standard products | Undecided | We will assess and revise as required | Updating the existing WMO publication Guidelines on Submission of the World Weather Records Tenth Series (2001-2010), WCDMP-N°77 | 2016-04-25 | Waiting | Wait for the final version of the new WWR guidelines | ||||
| 2 | Normals data computing | Proposal received | Denis | 2016-04-26 | 6.1 Analysis | Agreed | Liaise with IPET-CDMP to define process and algorithms to be used. Computation for normals is a type of Analysis process. Therefore the components that generate the normals (in accordance with IPET-CDMP guidance) should be placed under 6.1 Climate Data Analysis. Resolve at next version. Use best available advice if IPET-CDMP process has not been resolved. | Normals and Technical Regulations | 2017-05-22 | Waiting | Normals data computing practices should be gathered in one place (may be the Guide to Climatological Practices or others documents). WMO Guidelines Calculation of climate normals (Currently draft version): This document replaces the WMO Technical Document WMO/TD-N° 341 (WCDP-10), Calculation of monthly and annual 30-year standard normals of March 1989 and addresses climate normal calculation practices from 2017. | ||||
| 3 | Rounding calculations | Proposal received | 6.1 Analysis | Agreed | Liaise with IPET-CDMP to define process and algorithms to be used. Rounding is a type of Analysis process. Therefore the components that generate the normals (in accordance with IPET-CDMP guidance) should be placed under 6.1 Climate Data Analysis. Resolve at next version. Use best available advice if IPET-CDMP process has not been resolved. | Principles of rounding calculations | 2016-08-05 | Waiting | |||||||
| 4 | Time Series Quality assessment | Proposal received | Manola Brunet (co-chair OPACE 2) | 2016-09-20 | 3. Governance 4. Time-series climate data 5. Climate data management 5.3 Observations Quaility Control 6. Climate data Analysis 7. Climate data presentation 8. Climate data delivery | Undecided | Ensure that issues relating to time-series data, its management, analysis, delivery, presentation etc are explicitly discussed in WMO #1131. Explicitly discuss time-series QC | Time series QC | 2016-09-19 | Waiting | Changes required to the CDMS Spec: A request from Manola Brunet (co-chair OPACE 2) on CDMS specs. Essentially they would like to see time series QC (what we would call historical QC) as a mandatory function. | ||||
| 5 | Validate links | Proposal received | Bruce | 2016-10-01 | All | Agree | Ensure that all URLs resolve in the next version of #1131 | Some of the links to URLs not be working | 2016-10-18 | Waiting | These will need to be validated for the next version of the document WMO 1131 | ||||
| 6 | Where : 4.1 Observations data, what : There is part 4.1.1 Climate observations suggestion, Add “optional” part 4.1.2 Phenological observations why : Very close to climate and climate change. Some of NMHSs have responsibility about it. In fact, it is no atmospheric or terrestrial. | Proposal received | Radim | 2016-04-25 | 4.6 Ancilliary data | Agree with problem, but not solution. | Phenological observations relate to the study of plant and animal life cycle and how they influenced by climate and habitat factors. Therefore this would better fit under 4.6.1.5 Environnemental or 4.6.1.7 Impacts data. | 2016-11-22 | Waiting | ||||||
| 7 | Where: 4.1. Observation data, what There are atmospheric, terrestrial an ocean observation. But the PARAMETR is missing. Where is definition of parameters (temperature, precipitation, etc.)? There is just a list of recommended/required parameters, but definition of parameter (its metadata) is missing. Suggestion I add the Parameter to the mind map as 4.1.1.4 . | Proposal received | Radim | 2016-04-25 | 4. Time-series climate data | Agree with problem, but not solution. | Agree that we need some formal data product definition that ties the observed variables (parameter) right through to the delivered data products. We need to make sure that all NMHSs and CDMSs manage the same variables and deliver the same products. The goal needs to be consistent global data products that support dynamic analysis with each NMHS contributing their piece. Therefore we will need a process to develop formal data product definition in the long term. In the short term for the next version of the CDMS specs let us include an Appendix that defines what we currently know as the required parameters for each variable. This will require a sub-team of ET-CDMS to review existing WMO documentation and summarize. | 2016-11-22 | Waiting | ||||||
| 8 | where 4.3.2 Dataset discovery metadata what There is not many info about it in the CDMS specification. I did remember my deep discussion about DATASET many years ago with Steve Palmer (my regards). For me the datasets are redundant in CDMS. The CLICOM used it because of space data limit in DataEase dtb. The modern CDMS should divided the data on-line according to the users wish. Suggestion : Delete the information about datasets? Or to precise what authors mean by it? | Radim | 2016-04-25 | 4.3.2 Dataset discovery metadata | Disagree | 4.3.2 merely sumarises ISO 19115 Discovery Metadata. This is also known as WIS Metadata. Therefore as this is well documented elsewhere, there was no need to repeat it in WMO #1131. A CDMS typically stores most records as collections within a database, and as these collections are typically provided as datasets. Rather than follow the current WIS practice of having one Discovery Metadata record per observation, a CDMS only requires one Discovery Metadata record per data collection / data set. As an example: - the CDMS has a collection of all sensors that observe 'Temperature' within the NMHS region of interest. - a spatial view called 'Daily Maximum Temperature' has been defined based on this collection. - the spatial view is available externally via a Web Map Service for people to include as a map within their applications. A discovery metadata record is required that describes the data products: - 'Temperature' - 'Daily Maximum Temperature' An example of the type of Discovery Metadata recor expected is at: http://www.bom.gov.au/metadata/catalogue/view/ANZCW0503900396_vic.shtml?template=full | 2016-04-25 | ||||||||
| 9 | where 5.1 Ingest and extract what The management of generated data are missing suggestion change the 5.1 name to Ingest, generate and extract and add part 5.1.3 Data generation into the mind map | Radim | 2016-04-25 | 6.1 Climate Data Analysis | Disagree | Noted. For consistancy, it will better to keep the functionality of ingest and extract to being just that, not to also modify the data in the database as well. This will be better handled with a set of consistent routines that can be used by many components. The type of functionality suggested is really about analysing data and writing the results to the database. By having these tasks running as a regularly scheduled job, we will be able to achieve the same aim. Therefore this type Data Generation functionality should be added under 6.1 Climate Data Analysis. | 2016-04-25 | ||||||||
| 10 | where 5.3 Observation quality control what Some user action is missing in the CDMS description. The system used many tests (5.3.1 Quality management), the system monitor data, but somewhere the user should decide about flagged data. Suggestion I add the part “Assessment by user” to the mind map 5.3. | Radim | 2016-04-25 | 5.3 Observations Quality control | Disagree | Component 5.3.1.6 Data Recovery is currently filling this role. Perhaps we should rename this component to better reflect its intent. | 2016-04-25 | ||||||||
| 11 | Where 5.2.2.1 Data Rescue metrics what To be able to compute these metrics there is a need to have a Metadata about Data rescue otherwise it will be difficult to have these metrics. Suggestion Add in 4.1. Climate Metadata a component that will describe data rescue activities. | Rachid | 2016-04-25 | 5.2 Data rescue | Disagree | Unlike Data Discovery, Observations Metadata and Data Provenance, there is no formal standard that covers this type of data. This will be better maintained as a set of records within a database table(s) within the Climate Database. | |||||||||
| 12 | Where 5.5.1 Manage climate metadata what Observations metadata and data discovery metadata are Required but Managing them is Recommended. This is inconstant. Suggestion Create, Maintain and quality control in 5.5.1 should be REQUIRED | Rachid | 2016-04-25 | 5.5.1 Manage climate metadata | Agreed | Agreed. Resolve at next version. | |||||||||
| 13 | Where 5.5.1 Manage climate metadata what WMO data products should move to metadata part. Suggestion WMO data products should move to metadata part. | Rachid | 2016-04-25 | 4.4 WMO standard products | Disagree | There is no formal metadata standard that covers this type of 'data'. | |||||||||
| 14 | Made the Component Automated with self recovery a required function | Proposal received | Bruce | 2016-11-21 | 5.1 Ingest and extract | Agree | Agreed. Resolve at next version. | Made the Component Automated with self recovery a required function | ET | 2016-11-21 | Waiting | ||||
| 15 | Make sure that Ingest component applied to Data Extraction | Proposal received | Denis | 2016-11-21 | 5.1 Ingest and extract | Agree | Agreed. Resolve at next version. | Make sure that Ingest component applyed to Data Extraction | ET | 2016-11-21 | Waiting | ||||
| 16 | Change name of 5.3.1.6 Data recovery to something that better reflects the Manual Quality assessment process that is undertaken on flagged records. | Proposal received | Radim, Bruce, Denis | 2016-11-21 | 5.3 Observations Quality control | Agree | Agreed. Resolve at next version. | ||||||||
| 17 | Update the WMO 1131 with the new WMO publications | Denis | 2017-05-19 | All | Undecided | Update the WMO 1131 with the new WMO publications and in particular the WMO Manual on Codes International Codes, Volume I.3, Annex II to the WMO Technical Regulations Part D – Representations derived from data models links with METCE | |||||||||
| 18 | Contact CCl secretariat and the OPACE 1 chairs | Denis, Bruce | 2017-06-12 | All | Undecided | Contact CCl secretariat and the OPACE 1 chairs to add to the Terms of Reference for each relevant new CCl expert team to review the CDMS Specifications (WMO 1131) in their area of expertise and report any required changes to ET-CDMS chairs. This is needed in the first year of the next intersessional period. e.g. with the Expert Team on National Climate Monitoring Products (ET-NCMP) to add the shortlist of National Climate Monitoring Products in the CDMS Specifications. | Waiting | ||||||||