[Thread Prev][Thread Next][Index]

[las_users] addXML and "coordinates" attribute



I'm using addXML 1.7 to feed LAS with my netcdf data.
I get errors when addXML processes variabiles having 2dims coordinates.

I'm used to indicate the existence of such variables by means of their 
"coordinates" attribute, as stated in the CF Metadata Convention.

I wonder wether I must program a modified version of addXML (almost impossible 
for me!) or not. May be I'm lucky and such a program already exists. 

Am I lucky?
Thank you very much form Italy,
Emanuele Lombardi


Here it follows an example of a netcdf file I'm having troubles with.

netcdf lele {
dimensions:
        im = 306 ;
        jm = 53 ;
        km = 25 ;
        time = UNLIMITED ; // (21 currently)
variables:
       float sigma(km) ;
                sigma:long_name = "sigma_level" ;
                sigma:standard_name = "ocean_sigma_coordinate" ;
                sigma:formula_terms = "sigma: sigma eta: ELEV depth: TOPO";
    double time(time) ;
                time:units = "days since 1979-01-01 00:00:00" ;
                time:long_name = "time" ;
                time:standard_name = "time" ;
        float lon(jm, im) ;
                lon:long_name = "longitude" ;
                lon:standard_name = "lon" ;
                lon:units = "degrees_east";
                lon:_FillValue = 9.96921e+36f ;
       float lat(jm, im) ;
                lat:long_name = "latitude" ;
                lat:standard_name = "lat" ;
                lat:units = "degrees_north" ;
                lat:_FillValue = 9.96921e+36f ;
       float TEMP(time, km, jm, im) ;
                TEMP:long_name = "potential temperature" ;
                TEMP:standard_name = "temp" ;
                TEMP:units = "C" ;
                TEMP:_FillValue = 9.96921e+36f ;
                TEMP:coordinates = "lon lat sigma time" ;
// global attributes:
                :Conventions = "CF-1.0";
}




[Thread Prev][Thread Next][Index]


Contact Us
Dept of Commerce / NOAA / OAR / PMEL / TMAP

Privacy Policy | Disclaimer | Accessibility Statement