Implementing Dapper for in-situ profile data

[Joe Sirott]

Supported file formats are described at 
http://www.epic.noaa.gov/epic/software/dapper/dapperdocs/load.html

It's probably easiest to generate profiles that follow the COARDS 
convention; in CDL something like:

dimensions:
	depth = 100;
	lat = 1;
	lon = 1;
	time = 1;
variables:
	float temp(time, depth, lat, lon);
		temp:units="degC";
	double time;
		time:units="hours since ...";
	float depth;
		depth:units="m";
	float lat;
		latitude:units="degrees_east";
...




John Caron wrote:
>
>
> Joe Sirott wrote:
>
>> By the way, I think it might actually be easier to create netCDF 
>> files from your database and load them into Dapper then it would be 
>> to write your own database layer for an OpenDap SQL based server, 
>> especially if the database is large and is not updated often (> 1 
>> hour, say). You could use any language with SQL and netCDF support 
>> (Java, Python, Ruby, Perl, etc) to generate the files and run the 
>> loader program.
>
> What format do the netcdf files have to be in?