⇐ ⇒

[CF-metadata] code that does semantic checking of CF headers

From: Dave Allured <dave.allured>
Date: Thu, 19 Apr 2012 14:11:42 -0600

Sean,

I run into this frequently, especially with files that do not come
from carefully crafted official archives. I regard all flavors of
range attributes as frequently unreliable. I think best practice is
to extract ranges directly from the coordinate values when plotting
data on the fly, and pay no attention to incorrect secondary metadata.
 This should be simple to code and have no performance penalty.

--Dave

On Thu, Apr 19, 2012 at 9:13 AM, Gaffney, Sean P. <sgaf at bodc.ac.uk> wrote:
> Hi all,
>
> My name is Sean Gaffney, from the British Oceanographic Data Centre, and I'm working on a project dealing with numerical model data that are in CF compliant NetCDF, so I thought I'd sign up to the community.
>
> The project I am working on aims to develop a web-based delivery system for oceanographic numerical model data and has a module which allows visualisation of the data. We've been using test CF data to fine-tune some of the technical aspects of this visualisation.
>
> I have a particular issue at the moment which I hope someone out there might be able to assist me with.
>
> My problem started when I found that the test CF data were passing the BADC CF compliance checker, but not visualising properly. A check with the people who developed the visualisation module led to the discovery that, while the CF metadata were formatted correctly, the actual values within the metadata were incorrect e.g. the valid_min and valid_max attributes for both the latitude and longitude and dimensional variables had values which did not reflect the actual range of data in the file. The visualisation was setting itself up based on the values stored in the attributes and was therefore not displaying any data.
>
> Has anyone in the CF community come across this sort of issue before and if so, what solutions would you recommend? My initial thoughts were that I'd have to develop some sort of code which interrogates the data file and compares the entries in the CF metadata header against the actual data values in the file, but I'd be interested to see what people think. Please bear in mind that I won't actually be generating model runs myself, but will be receiving data from people that have done so and need to know that I'm being given valid data and metadata.
>
> Sorry for making my first message to the CF community so long.
>
> Looking forward to your responses
>
> Yours
>
> Sean Gaffney
> BODC
>
>
> --------------------------------------------------------------------------------
> Sean Gaffney
> Data Scientist
> British Oceanographic Data Centre
> Joseph Proudman Building
> 6 Brownlow Street
> Liverpool
> L3 5DA
> UK
> +44 (0)151 795 4950
>
>
> --
> This message (and any attachments) is for the recipient only. NERC
> is subject to the Freedom of Information Act 2000 and the contents
> of this email and any reply you make may be disclosed by NERC unless
> it is exempt from release under the Act. Any material supplied to
> NERC may be stored in an electronic records management system.
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
Received on Thu Apr 19 2012 - 14:11:42 BST

This archive was generated by hypermail 2.3.0 : Tue Sep 13 2022 - 23:02:41 BST

⇐ ⇒