Replies: 3 comments 5 replies
-
Has this progressed to any degree? Is this to be a separate tool or is it suitable to be included an existing compliance checker? I also raised this an an issue on the compliance-checker repo to see if there are any opinions there. I cross linked this discussion in that issue. @castelao |
Beta Was this translation helpful? Give feedback.
-
It would be great to have a gold standard example netCDF files to test the checker against much like NCEI has for their templates. There are two initial examples that can be found in the manual for reference: It would be best to have several examples to exercise as much of the template as possible. |
Beta Was this translation helpful? Give feedback.
-
Yes please open a PR @jcermauwedu . Would this sensor data come back off the glider in real time? I only ask as the format has been built with real time data in mind and not for a delayed dataset which we will need to consider next. Thanks, |
Beta Was this translation helpful? Give feedback.
-
There will be a need for OG1.0 checker that will also check the cf compliance.
OG1.0 is cf.1.10 compliante, but cf.1.10 do not offer any complient checker yet. However, cf1.8 can be checked.
The change from cf.1.8 to cf1.10 does not affect OG1.0
It is being discussused here that the OG1.0 checker will, amongst other verification, check compliance with cf1.8 using what exist and assuming that OG1.0 is compliant with cf.1.10 is compliant with cf1.8.
@castelao is working on this particular topic.
Beta Was this translation helpful? Give feedback.
All reactions