Re: [CF Metadata] #159: charset attribute

2017-02-28 Thread CF Metadata
1999) version, with the mayor change of including the € sign. I prefer a strict default over ambiguity, and the UTF-8 default aligns with the NUG. -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/159#comment:1> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #159: charset attribute

2017-02-28 Thread CF Metadata
t:2> CF Metadata <http://cf-convention.github.io/> CF Metadata

[CF Metadata] #159: charset attribute

2017-02-27 Thread CF Metadata
older files with variables that don't specify a charset, the character set being used remains ambiguous.) -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/159> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #153: Requirements related to specific standard names

2016-11-07 Thread CF Metadata
not meeting these constraints as an error (i.e. breaking a requirement) or bad practice (i.e. not respecting a recommendation). Best wishes Jonathan -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/153#comment:7> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #82: Extend cell_methods attribute to document multi-step operations on a variable

2016-11-11 Thread CF Metadata
linked to a time concept I would suggest more general term like `size` or `window` which are been using on the mathematical concept of moving averages. My vote is for `size`. Antonio -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/82#comment:8> CF Metadata <http://cf-convention.

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2016-10-19 Thread CF Metadata
). This should be made clear, or the cell_methods should be changed to: cell_methods="area: mean where sea_ice over all_surface_types time: mean Karl -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/152#comment:11> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2016-10-19 Thread CF Metadata
s. Then the cell_methods attribute would be defined: cell_methods=”area: mean where sea_ice over sea time: mean” best regards, Karl -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/152#comment:9> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2016-11-21 Thread CF Metadata
ely, (-10 -6 -2)/3 = -6, (-10*.75 - 6*.5 -2*.25)/(.75+.5+.25) = -7.33 , and (-10*.75 - 6*.5 -2*.25)/3 = -3.667. The partial mean provides the contribution to the mean over the entire grid from a specified area type. The simple mean is weighting each time period equally, while the weighted mean provides equal weighting to each unit area of `sea_ice`. In example 7.8, `time` could be replaced by any other coordinate over which an average is taken, such as an ensemble index. -- -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/152#comment:18> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2016-11-21 Thread CF Metadata
e. The simple mean is weighting each time period equally, while the weighted mean provides equal weighting to each unit area of `sea_ice`. In example 7.8, `time` could be replaced by any other coordinate over which an average is taken, such as an ensemble index. -- -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/152#comment:16> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2016-11-21 Thread CF Metadata
rid from a specified area type. The simple mean is weighting each time period equally, while the weighted mean provides equal weighting to each unit area of `sea_ice`. In example 7.8, `time` could be replaced by any other coordinate over which an average is taken, such as an ensemble index. -- -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/152#comment:17> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2016-11-21 Thread CF Metadata
a missing value. The construct `area: mean where sea_ice time: mean where sea_ice` would be needed to average over the portions of the time series for which sea ice is present, Martin -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/152#comment:19> CF Metadata <http://cf-conven

Re: [CF Metadata] #108: Defining a domain for a cell_method

2016-11-22 Thread CF Metadata
method operation was conducted.__ == 5. Benefits == The community will benefit by having enhanced capabilities for defining cell_methods for data variables calculated across complex domains. [wiki:aggregateExampleMH] presents a use case for this capability. == 6. Status Quo == The capability to define complex domains for cell_methods will not be standardised. -- -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/108#comment:11> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #108: Defining a domain for a cell_method

2016-11-22 Thread CF Metadata
for defining cell_methods for data variables calculated across complex domains. [wiki:aggregateExampleMH] presents a use case for this capability. == 6. Status Quo == The capability to define complex domains for cell_methods will not be standardised. -- -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/108#comment:12> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2016-11-19 Thread CF Metadata
at it is clearer, syntactically, to keep this distinction, but would be interested to hear the views of others, regards, Martin -- Ticket URL: <http://cf-pcmdi.llnl.gov/trac/ticket/152#comment:14> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2016-11-19 Thread CF Metadata
|Version: Resolution: | Keywords: -+-- Changes (by taylor13): * Attachment "cell_methods_new2_clean.docx" added. proposed text (clean) -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/152> CF Met

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2016-11-19 Thread CF Metadata
|Version: Resolution: | Keywords: -+-- Changes (by taylor13): * Attachment "cell_methods_new2.docx" added. proposed text -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/152> CF Met

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2016-11-19 Thread CF Metadata
|Version: Resolution: | Keywords: -+-- Changes (by taylor13): * Attachment "cell_methods_new2.pdf" added. proposed text pdf -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/152> CF Met

Re: [CF Metadata] #149: correction of standard name in example 7.3

2016-11-21 Thread CF Metadata
-- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/149#comment:1> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #153: Requirements related to specific standard names (was: Requires related to specific standard names)

2016-11-03 Thread CF Metadata
'1'; float sig_bnds(2,sig); # required because of _atmosphere_layer }}} === Temporal change === Time rate of change or displacement over time require bounds on time coordinate: * ''change_over_time_*''; * ''*_displacement''; = Comments for discussion = In some cases the wording of standard_name definitions could be interpreted as a recommendation or suggestion rather than a requirement. If some of these are intended only as suggestions, that should be flagged. -- -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/153#comment:2> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #153: Requirements related to specific standard names

2016-11-03 Thread CF Metadata
would be useful. Best wishes Jonathan -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/153#comment:3> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #153: Requirements related to specific standard names

2016-11-03 Thread CF Metadata
<http://cf-trac.llnl.gov/trac/ticket/153#comment:4> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #153: Requirements related to specific standard names

2016-11-03 Thread CF Metadata
/cf-trac.llnl.gov/trac/ticket/153#comment:5> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #153: Requirements related to specific standard names

2016-11-04 Thread CF Metadata
ac/ticket/153#comment:6> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #111: New web site

2016-12-09 Thread CF Metadata
Thanks to Jeff, Matthew and others who migrated it. -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/111#comment:16> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2017-01-12 Thread CF Metadata
.50, .25. The values of the simple_mean, weighted_mean and partial mean are, respectively, (-10 -6 -2)/3 = -6, (-10*.75 - 6*.5 -2*.25)/(.75+.5+.25) = -7.33 , and (-10*.75 - 6*.5 -2*.25)/3 = -3.667. The partial mean provides the contribution to the mean over the entire grid cell from a specified area type. The simple mean is weighting each time period equally, while the weighted mean provides equal weighting to each unit area of `sea_ice`. In example 7.8, `time` could be replaced by any other coordinate over which an average is taken, such as an ensemble index. -- -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/152#comment:21> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #152: Time mean over area fractions which vary with time

2017-01-12 Thread CF Metadata
t;gridbox" to read "grid cell". That change was made to the sentence just before section 2. -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/152#comment:22> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #72: Adding the geostationary projection.

2016-12-02 Thread CF Metadata
suggested text added to v 1.7? Rob Kaiser (follow-on to Randy Horne in this area) -- Ticket URL: <http://cf-pcmdi.llnl.gov/trac/ticket/72#comment:22> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #100: Clarifications to the preamble of sections 4 and 5

2017-01-04 Thread CF Metadata
|Version: Resolution: | Keywords: -+-- Changes (by davidhassell): * owner: cf-conventions@… => davidhassell * status: new => accepted -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/100#comment:9> CF Me

Re: [CF Metadata] #123: clarification of "difference sources" in Section 3.3

2017-01-04 Thread CF Metadata
onventions |Version: Resolution: | Keywords: -+-- Changes (by davidhassell): * owner: cf-conventions@… => davidhassell * status: new => accepted -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/123#comment:2

Re: [CF Metadata] #143: Supplement the definitions of dimensionless vertical coordinates

2017-01-04 Thread CF Metadata
nt:14> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #145: Subconvention for associated files, proposed for use in CMIP6

2017-01-04 Thread CF Metadata
nt:53> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #89: standard names for vector components

2017-01-04 Thread CF Metadata
ticket/89#comment:11> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #87: Allow comments in coordinate variables

2017-01-04 Thread CF Metadata
: Resolution: | Keywords: -+-- Changes (by davidhassell): * owner: cf-conventions@… => davidhassell * status: new => accepted -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/87#comment:2> CF Metadat

Re: [CF Metadata] #87: Allow comments in coordinate variables

2017-01-04 Thread CF Metadata
gt; CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #139: Update to conformance document: standard_names of area_type & region

2017-01-04 Thread CF Metadata
139#comment:3> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #104: Clarify the interpretation of scalar coordinate variables

2017-01-04 Thread CF Metadata
-conventions |Version: Resolution: | Keywords: -+-- Changes (by davidhassell): * owner: cf-conventions@… => davidhassell * status: new => accepted -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/104#comment:70>

Re: [CF Metadata] #74: Allow sharing of ancillary variables among multiple data variables

2017-01-04 Thread CF Metadata
ner: cf-conventions@… => davidhassell * status: new => accepted -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/74#comment:58> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #75: fix documentation and definitions of 3 grid mapping definitions

2017-01-04 Thread CF Metadata
Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/75#comment:10> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #73: Rename Appendix G as Appendix Z

2017-01-04 Thread CF Metadata
: Resolution: | Keywords: -+-- Changes (by davidhassell): * owner: cf-conventions@… => davidhassell * status: new => accepted -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/73#comment:7> CF Metadat

Re: [CF Metadata] #80: Add missing CF parameters to translate Coordinate Reference System properties to/from OGC Well-Known Text format

2017-01-04 Thread CF Metadata
cepted -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/80#comment:30> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #77: Add sinusoidal projection

2017-01-04 Thread CF Metadata
: | Keywords: projection -+-- Changes (by davidhassell): * owner: cf-conventions@… => davidhassell * status: new => accepted -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/77#comment:13> CF Metadat

Re: [CF Metadata] #71: Correction of Vertical perspective projection

2017-01-04 Thread CF Metadata
|Version: Resolution: | Keywords: -+-- Changes (by davidhassell): * owner: cf-conventions@… => davidhassell * status: new => accepted -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/71#comment:5> CF Metadat

Re: [CF Metadata] #157: Clarification to Section 2.3 - Naming Conventions

2017-01-05 Thread CF Metadata
problems or misunderstandings? Heiko -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/157#comment:3> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #157: Clarification to Section 2.3 - Naming Conventions

2017-01-05 Thread CF Metadata
''or digit''' ... Are there many existing dataset which use leading underscores? David -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/157#comment:2> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #156: Extension to external_variables Syntax for Masks and Area Fractions

2017-01-02 Thread CF Metadata
compatible with the variable carrying the `cell_methods` attribute. -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/156#comment:2> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #156: Extension to external_variables Syntax for Masks and Area Fractions

2017-01-04 Thread CF Metadata
: cf-conventions |Version: Resolution: | Keywords: -+-- Comment (by jonathan): Dear Martin Thanks for the proposal. It seems to me that this is probably going a bit beyond the role of CF metadata, which

Re: [CF Metadata] #153: Requirements related to specific standard names

2016-12-21 Thread CF Metadata
of valid regions into the checker but it never got released - I'll include it in the next release. Regards, Ros. -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/153#comment:10> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #153: Requirements related to specific standard names

2016-12-20 Thread CF Metadata
present. On the other hand, it may be easier to just have a named test for these two, rather than using a complex schema like this. Cheers, Martin -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/153#comment:9> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #153: Requirements related to specific standard names

2016-12-20 Thread CF Metadata
to add these in in the next release. Cheers, Ros. -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/153#comment:8> CF Metadata <http://cf-convention.github.io/> CF Metadata

[CF Metadata] #154: Machine Readable Standardised Region List

2016-12-22 Thread CF Metadata
Names (under discussion: #153) There should be some common approach to structuring these documents. -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/154> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #154: Machine Readable Standardised Region List

2016-12-22 Thread CF Metadata
Jonathan -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/154#comment:3> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #72: Adding the geostationary projection.

2016-12-06 Thread CF Metadata
the document is now in a form which can be updated. Although it's not in the 1.7 working version yet, it ''will'' be included in 1.7, so please proceed as though it was already there. Best wishes Jonathan -- Ticket URL: <http://cf-pcmdi.llnl.gov/trac/ticket/72#comment:23> CF Metadata <

Re: [CF Metadata] #153: Requirements related to specific standard names

2016-12-22 Thread CF Metadata
es-1.1.xsd. This approach makes it easier to impose the schema rules on the names of the rules and the associated restrictions on the values (e.g. "requiredBoundAxis" should take a value "X", "Y", ...). cheers, Martin -- Ticket URL: <http://cf-trac.llnl.gov/trac/ti

Re: [CF Metadata] #153: Requirements related to specific standard names

2016-12-22 Thread CF Metadata
<http://cf-trac.llnl.gov/trac/ticket/153> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #153: Requirements related to specific standard names

2016-12-22 Thread CF Metadata
|Version: Resolution: | Keywords: -+-- Changes (by martin.juckes): * Attachment "CF_Standard_Name_Rules.xml" added. CF Standard Name Rules -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/153> CF Met

Re: [CF Metadata] #140: Clarifying the role of attributes on boundary variables.

2017-03-23 Thread CF Metadata
: <https://cf-trac.llnl.gov/trac/ticket/140#comment:8> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #140: Clarifying the role of attributes on boundary variables.

2017-03-23 Thread CF Metadata
ur valuable time, but I assure you if there is a compelling use case, then I'll favor including Jonathan's alternative. best regards, Karl -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:9> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #140: Clarifying the role of attributes on boundary variables.

2017-03-23 Thread CF Metadata
t:6> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #147: clarification of standard and correction of conformance doc: formula_terms

2017-03-23 Thread CF Metadata
:25> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #140: Clarifying the role of attributes on boundary variables.

2017-03-23 Thread CF Metadata
such mistakes. We have no general prohibition of or recommendation against using attributes from Appendix A in situations where CF doesn't describe their use. Best wishes Jonathan -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:7> CF Metadata <http://cf-convention.githu

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-30 Thread CF Metadata
a total switch to github with no e-mail alerts could alienate me from CF. Cheers, Roy. -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/160#comment:14> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #140: Clarifying the role of attributes on boundary variables.

2017-03-22 Thread CF Metadata
URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:3> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #140: Clarifying the role of attributes on boundary variables.

2017-03-22 Thread CF Metadata
for the coordinates and its bounds, but with different parametric variable names specified for any terms in the definition that depend on the vertical coordinate. -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:5> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-29 Thread CF Metadata
for not forwarding all Github issue discussion to email, but letting people watch or unwatch as they desire. (watch sends email notification, unwatch does not) https://help.github.com/articles/unwatching-repositories/ -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/160#comment:11> CF Me

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-29 Thread CF Metadata
a little while for people to become comfortable with the new system, and to work out kinks. We will then be in a good position to consider whether or not to move standard_name discussions too. -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/160#comment:12> CF Metadata <

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-29 Thread CF Metadata
to move the CF-metadata mailing list to github. To my mind, the current CF-metadata mailing list comprises general queries (how do I do this?), reconnaissance (would this be a good idea?) and standard name proposals (which do not impact on the conventions document). Coments on trac tickets

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-29 Thread CF Metadata
b. I think that the all github activity should be automatically copied to the CF metadata mailing list, just like the current Trac activity is. I believe that it is important for all potentially interested parties to get a chance to see all parts of a discussion. All the best, Daivd --

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-29 Thread CF Metadata
-to-github- issues Rich -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/160#comment:9> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-17 Thread CF Metadata
in the light of the forthcoming move of the definitive conventions document to github. I would have thought that the current CF-metadata email list should carry on as is, unchanged - many readers and participants do not want or need to contribute to changes, and so would not then need a github

Re: [CF Metadata] #147: clarification of standard and correction of conformance doc: formula_terms

2017-03-20 Thread CF Metadata
about option 3., which would at least give the author a hint that the attribute is not where it is expected? regards, Martin -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/147#comment:20> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #147: clarification of standard and correction of conformance doc: formula_terms

2017-03-20 Thread CF Metadata
_terms in the third line from the end.) Cheers Jonathan -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/147#comment:22> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-04-04 Thread CF Metadata
:20> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-04-04 Thread CF Metadata
by email, but they cannot post updates to trac by email. It seems that this hasn't caused confusion; people have very rarely replied to the email list about trac tickets. Cheers Jonathan -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/160#comment:19> CF Metadata <

[CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-07 Thread CF Metadata
/cf-trac.llnl.gov/trac/ticket/160> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-07 Thread CF Metadata
of committing themselves to a version not on the trunk; but beyond that I can very easily see a lot more flexibility builtin into a github-based approach. -- Ticket URL: <http://cf-pcmdi.llnl.gov/trac/ticket/160#comment:1> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #159: charset attribute

2017-03-02 Thread CF Metadata
gt; CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #159: charset attribute

2017-03-03 Thread CF Metadata
? They're practically equivalent, I would have thought. Are there any other cases where CF is ambiguous about whether a variable is a char array or a string? Best wishes and thanks Jonathan -- Ticket URL: <http://cf-pcmdi.llnl.gov/trac/ticket/159#comment:6> CF Metadata <

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-07 Thread CF Metadata
ided? -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/160#comment:3> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-08 Thread CF Metadata
decouple any discussions on the Standard Name process and possible alternatives from this ticket. -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/160#comment:4> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-07 Thread CF Metadata
be enough of a challenge that they'd simply bypass the process altogether. -- Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/160#comment:2> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-04-07 Thread CF Metadata
rac/ticket/160#comment:21> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-31 Thread CF Metadata
ket/160#comment:16> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-31 Thread CF Metadata
ket/160#comment:17> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #160: Proposal to use GitHub instead of trac

2017-03-31 Thread CF Metadata
convenient -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/160#comment:15> CF Metadata <http://cf-convention.github.io/> CF Metadata

[CF Metadata] #163: Bibliography Entry OGP-EPSG_GN7_2

2017-08-01 Thread CF Metadata
and suitable content. This bibliography entry is referenced only two places, both in Appendix F. -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/163> CF Metadata <http://cf-convention.github.io/> CF Metadata

[CF Metadata] #164: Simple Geometries in CF

2017-08-15 Thread CF Metadata
: <https://cf-trac.llnl.gov/trac/ticket/164> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #164: Simple Geometries in CF

2017-08-16 Thread CF Metadata
gt; CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #162: OGC WKT-CRS reference

2017-08-11 Thread CF Metadata
l the best, David -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/162#comment:5> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #162: OGC WKT-CRS reference

2017-08-10 Thread CF Metadata
y in tools is expected. It may even be viewed that this is an exercise better approached in a future publication of CF, rather than this one. all the best mark -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/162#comment:4> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #162: OGC WKT-CRS reference

2017-08-10 Thread CF Metadata
think that we should simply delete that statement, it does not add much in any case. -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/162#comment:3> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #162: OGC WKT-CRS reference

2017-08-14 Thread CF Metadata
this ticket is complete now, I am happy for this to be closed -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/162#comment:7> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #162: OGC WKT-CRS reference

2017-08-14 Thread CF Metadata
//cf-trac.llnl.gov/trac/ticket/162#comment:6> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #146: Decisions by the CF conventions committee about management of versions of CF

2017-07-18 Thread CF Metadata
leased, including all accepted changes, so this ticket can now be closed. [https://cf- trac.llnl.gov/trac/ticket/160 ticket 160] we are discussing how to manage proposals for future changes. -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/146#comment:1> CF Metadata <http://cf-conve

Re: [CF Metadata] #154: Machine Readable Standardised Region List

2017-07-19 Thread CF Metadata
. And I've just noticed that it is missing a closing standardized_region_names tag. regards, Martin -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/154#comment:5> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #162: OGC WKT-CRS reference

2017-07-19 Thread CF Metadata
: | Keywords: -+-- Comment (by davidhassell): Hi Mark, Thanks for this - your suggested web site looks fine to me. All the best, David -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/162#comment:1> CF Me

[CF Metadata] #162: OGC WKT-CRS reference

2017-07-19 Thread CF Metadata
swift response on whether this approach is deemed suitable by document maintainers? many thanks mark -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/162> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #153: Requirements related to specific standard names

2017-07-20 Thread CF Metadata
|Version: Resolution: | Keywords: -+-- Changes (by martin.juckes): * Attachment "CF_Standard_Name_Rules.json" added. Updated JSON list of rules -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/153

Re: [CF Metadata] #153: Requirements related to specific standard names

2017-07-20 Thread CF Metadata
|Version: Resolution: | Keywords: -+-- Changes (by martin.juckes): * Attachment "CF_Standard_Name_Rules.2.xml" added. Updated XML list of rules -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/153

Re: [CF Metadata] #154: Machine Readable Standardised Region List

2017-07-20 Thread CF Metadata
these to the main CF web pages too. Best wishes, Alison -- Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/154#comment:6> CF Metadata <http://cf-convention.github.io/> CF Metadata

Re: [CF Metadata] #153: Requirements related to specific standard names

2017-07-20 Thread CF Metadata
153#comment:14> CF Metadata <http://cf-convention.github.io/> CF Metadata

  1   2   3   >