[Esip-documentation] Let's get rid of spatial and temporal bounds in ACDD

Steve Hankin steven.c.hankin at noaa.gov
Mon Mar 17 16:44:03 EDT 2014


On 3/17/2014 1:35 PM, Ted Habermann wrote:
> All,
>
> This discussion is driving me bananas!
>
> I would argue (vehemently) against any recommendation that says 
> anything like "don't add bounds elements to your global attributes". 
> To encourage people to provide less metadata is just not acceptable.

Ted,

Why?

  * they are not needed for ISO metadata generation
  * a small addition to ncdump would solve the issue for desktop users

What is the compelling driver here?

     - Steve


> Much more palatable to
> 1) offer a general warning to users - all data and metadata have 
> varying quality - test before you leap and know how the data you have 
> was processed.
> 2) to start a concerted effort to encourage software developers to 
> think about the metadata in the files they create and
> 3) add a congruence check into the ACDD rubric / catalog cleaner, it 
> would be very interesting to know how many datasets in the "clean" 
> catalog suffer from inconsistencies between the data and the global 
> attributes.
>
> As I said earlier, there are much more significant problems in ACDD/CF 
> metadata land than this one. Hopefully they will generate the same 
> amount of interest as we move forward.
>
> Ted
>
>
[clipped to bypass mailer limit on email length]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-documentation/attachments/20140317/5f306f1d/attachment.html>


More information about the Esip-documentation mailing list