Pauline,
I think the simplest alternative (although bulkier), is to have a string
variable with the same dimensions as your grid that contains the flag
meanings for each cell. It seems awkward to load huge flag_value and
flag_meaning attributes, but it saves lots of space, and it lends itself
to automated use. The string variable does none of those things.
Grace and peace,
Jim Biard
On 12/7/2011 5:53 AM, Weatherall, Pauline wrote:
Dear All,
I am developing a grid file that uses a flag that potentially has up
to 8000 different meanings (it references the provenance of the data
populating a given grid cell). Is there any alternative to
documenting this in flag_value and flag_meaning?'
Any advise on this would be really helpful.
Thanks in advance.
Pauline Weatherall
***********************************
Ms. Pauline Weatherall
British Oceanographic Data Centre (BODC)
6 Brownlow Street
Liverpool
L3 5DA
UK
www.bodc.ac.uk <http://www.bodc.ac.uk>
***********************************
--
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
[email protected]
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
--
Jim Biard
Government Contractor, STG Inc.
Remote Sensing and Applications Division (RSAD)
National Climatic Data Center
151 Patton Ave.
Asheville, NC 28801-5001
[email protected]
828-271-4900
_______________________________________________
CF-metadata mailing list
[email protected]
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
