[Thread Prev][Thread Next][Index]

RE: Creating a netCDF file



Ben,

You may also look at our data sets at http://dods.mbari.org/lasOASIS
which are structured similar to what you describe.

Use the 'i' information icon links for full details on the data sets. 

-Mike

> -----Original Message-----
> From: Ansley Manke [mailto:ansley.b.manke@noaa.gov]
> Sent: Thursday, September 30, 2004 10:20 AM
> To: Ben Burford
> Cc: ferret_users@noaa.gov
> Subject: Re: Creating a netCDF file
> 
> 
> Hi Ben,
> How about using Ferret to write yourself an example file?  Pick
> a single location from any file that depends on time, and 
> write it out:
> 
>   yes? use fnoc_winds
>   yes? save/file=example.nc  uwnd[x=180,y=0] , vwnd[x=180,y=0]
> 
> Pretending uwnd is air temperature and vwnd is the flag.
> 
> Ansley Manke
> 
> Ben Burford wrote:
> 
> >Hello All,
> >
> >I'm writing software to create a netCDF file and write data 
> and metadata int
> >o the file.  The data is internal to my program so I can't 
> use routines to c
> >onvert from another format to netCDF, I have to create the file.
> >
> >My data is time series station data (e.g. Air_Temperature) 
> at a lat/lon poin
> >t.  I also have a second variable that is a quality flag 
> (single ascii chara
> >cter) for each Air_Temperature value.  I want to set up the 
> metadata (lat/lo
> >n location and time series info) so that Ferret reads the 
> file and sees the 
> >data as a time series and can create a (normal) time series 
> plot of the data
> >  I'm having some trouble with the axis information, 
> especially the time se
> >ries part.
> >
> >Can someone please send me (or give me a URL to) an example 
> of a similar tim
> >e series netCDF station data file (ideally that is COARDS 
> compliant) that I 
> >can look at with ncdump and see the contents?  A single 
> example is worth a s
> >tack of documents.
> >
> >Thank you,
> >
> >Ben
> >
> >  
> >
> 


[Thread Prev][Thread Next][Index]

Dept of Commerce / NOAA / OAR / PMEL / TMAP

Contact Us | Privacy Policy | Disclaimer | Accessibility Statement