[Liblas-devel] GPS time and intensity?

[Jason.Woolard at noaa.gov]

Thanks Mateusz. Most of the LAS files I've seen have more precision than to the nearest second. I guess whether it's needed or not depends on what you are doing.

I just checked one of the sample LAS files and it has GPS time data out to 6 decimal places. 

Just wanted to check on that since my input gps time wasn't matching my gps output time. 

----- Original Message -----
From: Mateusz Łoskot <mateusz at loskot.net>
Date: Sunday, October 12, 2008 7:09 am
Subject: Re: [Liblas-devel] GPS time and intensity?
To: Jason Woolard <Jason.Woolard at noaa.gov>
Cc: liblas-devel at mail.hobu.net


> Jason Woolard pisze:
> > Two more quick questions. I can't seem to pull the intensity from a 
> LAS 
> > file. The documentation shows intensity in the LASPoint class. Has 
> that 
> > been implemented? I'm getting a Traceback error in Python 2.5 with 
> > intensity while x,y,z return_number and classification are all 
> coming 
> > across fine.
> 
> Jason,
> 
> I'm not an expert of the bindings for Python but as I see, intensity 
> getter/setter is missing:
> 
> 
> 
> Let's wait for Howard to confirm.
> 
> > Also, the GPS time seems to be rounding to the nearest second . My 
> input 
> > file has data to 3 decimal places. Is there any way to carry that 
> > precision over?
> 
> As I can tell from what I see in the code, get_time method returns 8 
> elements of struct_time (range [0:7]). All these elements are integers
> and number of seconds is represented as integer. By the nature of 
> functions like localtime, gmtime, etc. fractions of second is lost.
> 
> 
> 
> Aren't LiDAR observations (pulses) measured in seconds with fractions 
> 
> ignored?
> 
> Best regards,
> -- 
> Mateusz Loskot, 
> Charter Member of OSGeo,