[CF-metadata] [cf-convention/cf-conventions] Resolve some text/example ordering issues in Chap 3.5 (#239)
Also, fix broken link in List of Examples See issue #238 for discussion of these changes. Fixes #238. For consideration either before 1.8 docs are released or hopefully in a patch release subsequently if these have missed deadlines for inclusion in 1.8. You can view, comment on, or merge this pull request online at: https://github.com/cf-convention/cf-conventions/pull/239 -- Commit Summary -- * Resolve some text/ordering issues in Chap 3.5 -- File Changes -- M ch03.adoc (46) M toc-extra.adoc (3) -- Patch Links -- https://github.com/cf-convention/cf-conventions/pull/239.patch https://github.com/cf-convention/cf-conventions/pull/239.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/pull/239 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
[CF-metadata] [cf-convention/cf-conventions] Resolve some errors in the current master branch of CF 1.8 docs (#238)
# Title Resolve some errors in the current master branch of CF 1.8 docs # Moderator @mwengren # Requirement Summary This issue is simply a pointer to a PR to fix to some issues I found in new text added in Chapter 3.5 sometime since last release of the documentation. I separated these more minor fixes from my more in-depth PR on new QC flag documentation in Chapter 3.4 (#235) since they seem more likely to accepted on their own. #235 will require an update if these fixes are applied. # Technical Proposal Summary Just a few simple fixes to consider before 1.8 version of the docs are released (or hopefully shortly afterwards n a patch release?). At the moment, the docs are a bit misleading due to paragraph and example mis-ordering. # Benefits All readers of the CF docs # Status Quo Just a minor fix of some documentation errors # Detailed Proposal N/A -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/238 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Remove restrictions on netCDF object names (#237)
I had the same thoughts as @zklaus when thinking about the security implications of what I could only imagine was an `eval(var_name)`. I've even seen some of the matlab code which does exactly this to load all the variable into a matlab namespace. I'd even go so far as to recommend that the CF document itself warn against doing this... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/237#issuecomment-580397605 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] coord value order for CRS WKT (#224)
many thanks @davidhassell -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/pull/224#issuecomment-580330621 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Add missing revision history entries for CF-1.8 (#233)
Updated the history in the PR for #212 and #223. All being well, I shall merge these history changes tomorrow (and there shall be no more merges until 1.8 is released) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/233#issuecomment-580328189 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Inconsistent usage of false_easting and false_northing in grid mappings definitions and in examples (#212)
... Sorry, I see it now (#225) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/212#issuecomment-580326317 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Inconsistent usage of false_easting and false_northing in grid mappings definitions and in examples (#212)
@erget Was there a PR associated with this? Thanks -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/212#issuecomment-580324145 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Revision history 1.8 (#234)
@davidhassell pushed 1 commit. d254254ac79f795fddac4e531796847eaae59bed issue 223 -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/cf-convention/cf-conventions/pull/234/files/15c0ff6cd478b614292c886e8f2e8b860630d6d1..d254254ac79f795fddac4e531796847eaae59bed This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Axis Order for CRS-WKT grid mappings (#223)
Closed #223 via #224. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/223#event-2993901868 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] coord value order for CRS WKT (#224)
Merged #224 into master. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/pull/224#event-2993901856 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Remove restrictions on netCDF object names (#237)
I agree that it would be good to have use cases.
@ngalbraith is also right that not everyone is writing their CF code based on
naked netCDF access. Indeed, I consider such an approach foolish, since CF is
far too rich by now to stand a series chance of getting it right.
However, while using the netCDF variable name as a program variable name might
be excused in small, not reused code that only ever will deal with, say `tas`,
it is inexcusable in general-purpose library code. How would such a variable
enter the namespace without the program knowing its name beforehand?
Ultimately, the only way is via the equivalent of `eval(var_name)`. Such code
is prone to breakage no matter what restrictions we put on the character set
since it would always leave open the possibility of having reserved words of
the particular programming language as variable names. Another serious problem
is that it opens the possibility to maliciously crafted variable names: How
about `var_name='system("rm -rf .")'`?
Hence, I don't think the argument that all netCDF variable names should be
permissible program variable names in all programming languages should guide
the design of CF.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/issues/237#issuecomment-580147380
This list forwards relevant notifications from Github. It is distinct from
cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the
UCAR list will result in a subscription to this list.
To unsubscribe from this list only, send a message to
cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
