⇐ ⇒

[CF-metadata] standard way to store lookuptables

From: andrea antonello <andrea.antonello>
Date: Tue, 19 Jan 2010 09:25:47 +0100

Dear Jonathan,
I finally came to that section and went after your advice.

I am trying to implement the timeseries as explained in 5.4, but I run
into what I feel gives memory overload, so I think I might be doing
something wrong.

Assuming that I have different stations that serve temperature, I would:
Dimensions:
- create a dimension for the stations
- create the time dimension
Variables:
- create the lat, lon, time variables
- create the temperature variable

When the moment comes to fill in the temperature, I create an
ArrayDouble.D2 depending on timeDim and stationDim.
At that point I am asked to insert the size of this array, which is
timeSIze and... here I would like to insert only the number of
stations that serve temperature, instead I have to insert the number
of all the stations that I have (else indexes will fail).
In that case assuming that I have 100 stations and only two serve
temperature, I will create anyways an array of timeSize*100 instead of
timeSize*2.
I hope I have been able to explain this properly.

Any help would be very apreciated.

Best regards,
Andrea





On Fri, Oct 2, 2009 at 5:17 PM, Jonathan Gregory
<j.m.gregory at reading.ac.uk> wrote:
> Dear Andrea
>
> I think some of your conversation has been off the list, so I'm not sure
> exactly what has been said. Anyway, here are some remarks.
>
>> >? If so these would be easily encoded using netCDF
>> > variables that all depend upon a dimension "numberOfSoilTypes".? Having said
>> > this I'd add that while this is a natural encoding in netCDF there is no
>> > explicit convention for it.
>
> It would be fine in CF to have a data variable e.g. of hydraulic conductivity
> with a dimension for soiltypes. This data variable could have a string-valued
> auxiliary coordinate variable to identify the soil types by name. This idea
> is described in CF 6.1.
>
> In your lat-lon field which gives the geographical
> distribution of soil types, you can use some encoding e.g. as integers,
> and attach flag_values and flag_meanings attributes to give the translation
> of these integers into soil type names. This is in CF 3.5.
>
> There is an example of precipitation timeseries from stations in CF 5.4.
> Again, they could be given names, like in CF 6.1.
>
> Cheers
>
> Jonathan
> _______________________________________________
> CF-metadata mailing list
> CF-metadata at cgd.ucar.edu
> http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
>
Received on Tue Jan 19 2010 - 01:25:47 GMT

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

⇐ ⇒