[Thread Prev][Thread Next][Index]

[las_users] Questions about adding data to LAS



Greetings LAS users,

I'm having some problems in adding data to our LAS:

First of all, I'm trying to add altimetry data (CF-1.0 convention). While doing “make” I get the following error:

Argument "\x{30}\x{2c}..." isn't numeric in numeric ne (!=) at ../xml/perl/LAS.pm line 1310.
Axis latitude-y-id-5cf22bee2f: axis step (currently '0,05') must be != 0 at ../xml/perl/LAS.pm line 1521

I've found that /usr/local/las/bin/./addXML.sh is creating a wrong XML. At the "latitude" tag, addXML creates the “step” attribute with value “0,05”:

<latitude-y-id-5cf22bee2f type="y" units="degrees_north">
<arange start="32" size="321" step="0,05" />
</latitude-y-id-5cf22bee2f>

I've changed by hand step=”0,05" to step="0.05" and “make” worked perfectly. So, is addXML.sh working properly or I'm doing something wrong?


The second question is about how to add time series to LAS. Specifically, I want to add the satellite data received by our HRPT station (one NetCDF for each pass). I've tried to add directly this data but LAS doesn't recognize “TIME” variable although I think it's well defined:

double TIME(TIME) ;
TIME:units = "days since 1970-01-01 00:00:00" ;
TIME:time_origin = "01-JAN-1970 00:00:00" ;
TIME:axis = "T" ;

I've found this link (LAS documentation website)

http://ferret.pmel.noaa.gov/Ferret/LAS/FAQ/descriptor_files.htm

but I'm not sure that's what I want. Any idea?


Finally, I want to improve the resolution of the coastal lines (by using etopo05). At

http://ferret.pmel.noaa.gov/Ferret/LAS/Mail_Archives/fu_2003/msg00264.html

I've found a short "howto" but I think it's obsolete (dataset.xml doesn't exist at LAS 6.5.2.1). Do you know any other “howto”?

Any help would be appreciated.

Roger
--

Roger Olivella Pujol
Institute of Marine Sciences (CMIMA-CSIC)
Barcelona, Catalonia (Spain)
(+34) 932 309 500 voice
http://saidin.cmima.csic.es



[Thread Prev][Thread Next][Index]

Dept of Commerce / NOAA / OAR / PMEL / TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement