[Esip-documentation] Let's get rid of spatial and temporal bounds in ACDD
Nan Galbraith
ngalbraith at whoi.edu
Sat Mar 8 06:13:11 EST 2014
Hows about adding an attribute that contains the URL of the data
file to which the bounds apply? If your aggregator/sub-setter
has misled you by failing to update the bounds attribute, he's also
provided you with the link to the data you actually wanted.
For programs that collect lots of data and don't molest it, this would
let them continue to use the bounds atts; for programs that slice
and dice, they'd be motivated to either update the fields dynamically
or remove them.
Cheers - Nan
Is it really Friday? I'm at sea (yes, people still do that, sometimes)
and I've lost all sense of time and place (no geospatial and temporal
bounds information).
On 3/7/14 6:47 PM, David Neufeld - NOAA Affiliate wrote:
>
> Ok, since it's Friday and we are in rant mode, I'm going to have a
> little fun with this one...
>
> Recommended Attribute Disclaimer:
>
> Suggested text: "When using geospatial and temporal bounds information
> in your global attributes, please know that it introduces a likely
> source of error and that you are far better off reading these values
> from the data stored in the file. If you do choose to use the
> attributes please also include a global checksum attribute that humans
> can look at to decide whether the file has changed since you
> originally recorded these values."
>
> On Fri, Mar 7, 2014 at 2:02 PM, Nan Galbraith <ngalbraith at whoi.edu
> <mailto:ngalbraith at whoi.edu>> wrote:
>
>
>
> Maybe we should add some text about which attributes should be
> considered fragile and under what conditions they need to be
> recalculated or removed, but I'm not in favor of removing the
> terms from ACDD.
>
>
--
*******************************************************
* Nan Galbraith (508) 289-2444 *
* Upper Ocean Processes Group Mail Stop 29 *
* Woods Hole Oceanographic Institution *
* Woods Hole, MA 02543 *
*******************************************************
More information about the Esip-documentation
mailing list