I have scalar time series from USGS and NOAA, both of which use an integer code
9414290 and a readable name "San Francisco, CA".
Any suggestions how to list them both and which is preferred for timeseries_id?
Can anyone give me an example of what typically goes in "station_info",
something that
A little note:
On Tue, Nov 1, 2016 at 9:43 AM, Chris Barker wrote:
> I'm on shakier ground about when you want to use a GeometryCollection vs a
> FeatureCollection, but I _think_ that the point of a geometrycollection is
> that you can group different types of geometry -- but still want them to
Hi Ajay,
The problem is that the offset representation is the CF standard for how
to record time, and that's what standards-aware software that displays
it quickly and easily relies upon. If you don't know how much time has
passed since the reference time, it's just plain not possible to record
i
Ajay,
It seems that you just contradicted yourself. First you asked how to
encode time coordinates when some measurements have time of day, but the
date is missing. Now you are saying that a valid date/time coordinate is
required. But a valid date/time coordinate is not possible without
complet
Dear Gwyn,
Many thanks for your query. You are right that there should not be any white
space within a standard name and if you do find examples of this, please
continue to report them to the mailing list and I will correct them as part of
the regular updates to the standard name table.
There
Thanks Gwyn,
That is what is known as an error in need of correction and should be dealt
with by aliasing in the next release.
I've also copied in a couple of colleagues in BODC so we can take steps to
prevent embedded blanks in Standard Names. We work in collaboration with CF and
run a seri
Right. But "rate_of_
hydroxyl_radical_destruction_due_to_reaction_with_nmvoc" is
an entry, not an alias.
On 11/01/2016 04:27 AM, Lowry, Roy K. wrote:
Aliasing is the mechanism used by CF to deprecate
Standard Names and was applied to
Thanks a lot for the suggestions, Dave, Ed and Seth.
Seth, here's the response from the team that's working on the data:
The first solution is not realistic. There are too many
missing times - separating out into another data variable
would give the user a bifurcated data set.
The second
A few comments, though you all seem to have this in hand :-)
I was asking whether this means that for each *collection* (of points,
> lines or
> polygons) there is a *single* timeseries.
I don't get why this matters -- any number of time series could be
associated with a single "entity" -- just
Hi Gwyn,
Many thanks for checking. I’m pleased that we seem to have managed to correct
all these errors now.
Best wishes,
Alison
--
Alison Pamment Tel: +44
1235 778065
Centre for Environmental Data Analysis Email:
alison.pamm..
That was the only one, found with the
following command:
grep -w entry cf-standard-name-table.xml | cut -s -d\" -f2 |
grep " "
On 11/01/2016 10:43 AM, alison.pamm...@stfc.ac.uk wrote:
there
should not be any white space with
Hi Roy,
Many thanks for this. The current version of the editor software that I use to
maintain the standard name table does check for stray white space, so hopefully
there won't be any more instances of this in the future, but I agree that it's
a good idea to check that they are being submitte
12 matches
Mail list logo
