Hi Aleksandar,
I was wondering if it is possible to describe the pixel geometry of
satellite measurements in CF. In atmospheric trace gas remote sensing,
an individual measurement's location is often described by the center
point's lat/lon coordinates plus the four pixel corner points'
The standard way CF deals with time is one of its most attractive
features; time is most difficult thing to understand in a 'generic'
NetCDF file.
My concern is that - as John G and at least 1 other person on this
thread have indicated - the addition of ISO string times is just the
beginning of
Andreas,
The coordinate bounds concept can cover this situation. See Section 7.1 of
the CF Conventions
documenthttp://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/cf-conventions.html#cell-boundaries
and
read the bit about 2D coordinates with 4-sided cells.
Grace and peace,
Jim
On Wed, Mar
Dear all,
as I am the at least one other person to whom Nan refered, let me
clarify my position:
1) I would strongly argue against adding another way of formatting time through
the backdoor via a standard_name.
2) I do see quite a bit of sense in re-modeling the date and time handling in
Dear all,
building on what Martin said here I want to clarify my views on this in
less words than last time.
Essentially, I can fully agree with Martin. And the date handling of
CF/NetCDF could probably be improved. However, this should be done in a
way that does not introduce redundancies into
On 3/21/2013 8:25 AM, John Caron wrote:
Probably my proposal comes down to 2 parts, which are separable:
1. Find a suitable replacement for udunits as a reference library for
CF calendar dates. Unfortunately, udunits used a slightly non-standard
syntax, which we need to still be legal for
On 3/21/2013 9:41 AM, Steve Hankin wrote:
On 3/21/2013 8:25 AM, John Caron wrote:
Probably my proposal comes down to 2 parts, which are separable:
1. Find a suitable replacement for udunits as a reference library for
CF calendar dates. Unfortunately, udunits used a slightly
non-standard
Hi John,
I'm probably repeating what others have said, but allowing strings as
actual (rather than ancillary) coordinate values would break lots of
quick look software which can't plot variables which are functions
of a string representation of the independent variable (i.e, time). If
I'm
John,
On 03/21/2013 09:25 AM, John Caron wrote:
1. ... Unfortunately, udunits used a slightly non-standard
syntax ...
More correctly, the UDUNITS packages accept the ISO standard syntax as
well as some non-standard syntaxes.
I believe this is an example of no good deed (being generous in what
On Tue, Mar 19, 2013 at 5:21 PM, Dave Allured - NOAA Affiliate
dave.allu...@noaa.gov wrote:
You are making a set of technical
use specifications, with significant departures from the reference
standard ISO 8601.
If we do anything with this -- PLEASE, PLEASE, PLEASE simply use the
ISO
Peter:
Following is some actionable feedback and questions on “Satellite Names and
Phrases”:…
(1)
A nit …
The alternative name for satellite, platform, could be an airplane, buoy, etc.
Recommend using “space_based_platform” or “space_platform” if there is a desire
to make it satellite
Aloha CF group,
I would like to propose the following standard names related to water
quality measurements of the bacteria *Enterococcus *and *Clostridium
perfringens*:
number_concentration_of_enterococcus_in_sea_water
number_concentration_of_clostridium_perfringens_in_sea_water
These are
12 matches
Mail list logo
