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
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
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
). 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
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
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
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
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
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
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
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
|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
|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
--
Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/149#comment:1>
CF Metadata <http://cf-convention.github.io/>
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
<http://cf-trac.llnl.gov/trac/ticket/153#comment:4>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
ac/ticket/153#comment:6>
CF Metadata <http://cf-convention.github.io/>
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
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
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
|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
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
nt:14>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
nt:53>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
ticket/89#comment:11>
CF Metadata <http://cf-convention.github.io/>
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
-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>
Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/75#comment:10>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
cepted
--
Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/80#comment:30>
CF Metadata <http://cf-convention.github.io/>
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
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
''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
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
: 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
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
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
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
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 <
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
<http://cf-trac.llnl.gov/trac/ticket/153>
CF Metadata <http://cf-convention.github.io/>
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
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
:25>
CF Metadata <http://cf-convention.github.io/>
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
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
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
_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
:20>
CF Metadata <http://cf-convention.github.io/>
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-trac.llnl.gov/trac/ticket/160>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
ket/160#comment:17>
CF Metadata <http://cf-convention.github.io/>
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
: <https://cf-trac.llnl.gov/trac/ticket/164>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
gt;
CF Metadata <http://cf-convention.github.io/>
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
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
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
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
//cf-trac.llnl.gov/trac/ticket/162#comment:6>
CF Metadata <http://cf-convention.github.io/>
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
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
|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
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
153#comment:14>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
le to find such an example. Could someone point out where
it is, or should we simply delete that statement?
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/162#comment:2>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
his ticket. (If you want to comment on Dave's
proposal, that would belong on the !GitHub issue.)
Best wishes
Jonathan
--
Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/160#comment:22>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
part.
Are you, Karl?
In addition, if we accept this ticket, we can close ticket 147, since this
one has dealt with the issue. It's a long-standing issue in CF, and it's
good to have it resolved!
Best wishes
Jonathan
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:15&
ac/ticket/140#comment:17>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
if present.
or leaving the whole sentence out and moving it to the conformance doc.
I shall re-check and re-post the example.
Many thanks,
David
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:16>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
should be PS:units).
What a shame we're done with this. Now we'll have to busy ourselves with
less important stuff.
cheers,
Karl
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:27>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
an
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:24>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
Boundary variables should not have the `_FillValue`, `missing_value`,
`units`, `standard_name`, `axis`, `positive`, `calendar`, `leap_month`,
`leap_year` or `month_lengths` attributes.
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:30>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
of the boundary
variable of the parametric vertical coordinate variable.
best,
Karl
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/140#comment:29>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
,
and any subsequent ticket that clarifies signedness must also clarify it
for shorts.
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/166#comment:5>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
are of instances in the examples, not the rules
themselves.
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/166#comment:4>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
ot; as you
suggest. I will leave it to others (Dave?) to formulate ticket(s) to
clarify implementation of signedness in classic files, and integer
interchangability, if they are interested.
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/166#comment:6>
CF Metadata <http://cf-conven
etCDF Classic format does not support a character string type, so these
must be represented as character arrays. ...
[Remainder of former paragraph on strings, unchanged]
}}}
--
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/166#comment:7>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
:
Resolution: | Keywords: integer unsigned CDF5
-+---
Changes (by zender):
* cc: zender@… (added)
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/166#comment:8>
CF Metadata <http://cf-convention.githu
to allow the string
type in NetCDF-4 files, but that's certainly not in the scope of this
ticket.
Best wishes
Jonathan
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/166#comment:3>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
minor point: A table defining each of the geometry types would be useful
- it seems that currently they are introduced with the assumption that
you arlready know what they are.
All the best,
David
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/164#comment:3>
CF Metadata <http:/
t/166#comment:9>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
the best, David
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/164#comment:2>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
lt;https://cf-trac.llnl.gov/trac/ticket/165>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
cmdi.llnl.gov/trac/ticket/166>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
pport unsigned types.
2.2.2 Character Strings
NetCDF Classic format does not support a character string type, so these
must be represented as character arrays. ...
[Remainder of former paragraph on strings, unchanged]
}}}
--
Comment (by zender):
Jim, good catch, thanks for proofr
s unsigned by using the NUG convention of
indicating the unsigned range using the valid_min,
valid_max, or valid_range attributes.
}}}
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/166#comment:11>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
e coincident".
Why is this recommended? It's redundant and it doesn't seem preferable to
me. I think David is also suggesting omitting this.
Best wishes and thanks again
Jonathan
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/164#comment:8>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
s me like an "Assembler is faster
than Fortran so we stick with Assembler" kind of debate.
>
> Chris, running for cover.
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/164#comment:4>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
b8e015c9eb/ch07.adoc]
If that is so, we ought to be close to wrapping this ticket up (subject to
modifications to the conformance document).
Many thanks,
David
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/164#comment:5>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
of geometry node coordinates here:
https://github.com/twhiteaker/Conformance/blob/Geometry_Conformance/conformance.adoc#4
-coordinate-types
Does that address all outstanding issues on this proposal?
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/164#comment:6>
CF Metadata <
should be made
consistent with paragraph 2, and the recommendation should be removed.
All the best,
David
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/164#comment:7>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
of CF version
1.8. Unsigned integer data should be stored with a signed
numeric type of sufficient range and precision, or with native unsigned
integers in one of the newer netCDF file formats.
}}}
--
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/167#comment:1>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
omply with Dave's suggestion to move
all discussion of, and any changes to, treatment of unsigned types in CDF1
and CDF2 to new ticket #167.
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/166#comment:12>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
e:104464",
"urn:lsid:marinespecies.org:taxname:104466"
}}}
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/99#comment:19>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
other non-breaking
changes requested by David.
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/164#comment:22>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
/cf-trac.llnl.gov/trac/ticket/170#comment:2>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
: fixed | Keywords:
-+--
Changes (by nadeau1):
* status: new => closed
* resolution: => fixed
--
Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/174#comment:1>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
: |
+--
This is not a real ticket
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/174>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
: |
+--
test creating a ticket.
--
Ticket URL: <https://cf-trac.llnl.gov/trac/ticket/175>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
<https://cf-trac.llnl.gov/trac/ticket/172#comment:4>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
1 - 100 of 150 matches
Mail list logo
