[Liblas-devel] liblas throwing an error upon wrong day of the year on "corrupt" LAS file

[Martin Isenburg]

> Anyhow the problem was easily solved by changing the code in header.cpp
> Ciao
> Francesco

But it should be fixed in the main release. I see a Y10K bug looming ... (-;

337	void Header::SetCreationYear(uint16_t v)
338	{
339	    // mloskot: I've taken these values arbitrarily
340	    if (v > 9999)
341	        throw std::out_of_range("year out of range");
342	
343	    m_createYear = v;
344	}

in many data sets from http://liblas.org/samples  the creation day /
year is not set anyways

lasinfo -i autzen-colorized-1.2-3.laz -no_check -stdout | grep creation
  file creation day/year:    0/0
lasinfo -i TO_core_last.laz -no_check -stdout | grep creation
  file creation day/year:    0/0
lasinfo -i SerpentMoundModelLASData.laz -no_check -stdout | grep creation
  file creation day/year:    0/0
lasinfo -i TO_core_last.laz -no_check -stdout | grep creation
  file creation day/year:    0/0
lasinfo -i TO_core_last.laz -no_check -stdout | grep creation
  file creation day/year:    0/0
lasinfo -i IowaDNR-CloudPeakSoft-1.0-UTM15N.laz -no_check -stdout |
grep creation
  file creation day/year:    0/0

On Mon, Apr 4, 2011 at 5:05 AM, francesco <francesco.pirotti at unipd.it> wrote:
> Thanks for all answers.
> @David - my version is 1.5.5 should be quite recent.
> Anyhow the problem was easily solved by changing the code in header.cpp
> Ciao
> Francesco
>
> Il 03/04/2011 16:48, Finnegan, David ERDC-CRREL-NH ha scritto:
>
> Francesco,
>
> What version of Riscan Pro are you using? The latest should be OK
> David C Finnegan
> Research Physical Scientist
> CRREL
> ---------
> Message sent via my BlackBerry Wireless Device
>
> ________________________________
> From: liblas-devel-bounces at lists.osgeo.org
> <liblas-devel-bounces at lists.osgeo.org>
> To: liblas-devel at lists.osgeo.org <liblas-devel at lists.osgeo.org>
> Sent: Sun Apr 03 09:46:26 2011
> Subject: [Liblas-devel] liblas throwing an error upon wrong day of the year
> on "corrupt" LAS file
>
> Hello, just thought I'd drop by a note regarding reading a not-well-formed
> LAS file.
> I am reading a file exported from RiScanPRO into LAS format, with a bad day
> of the year tag on the header.
> When reading with ReaderFactory -> CreateWithStream, Liblas throws an error
> and exits upon reading the bad date.
> So I hacked the liblas to send a message but not throw an error, so my code
> keeps going. Am I an ignoramous coder and there are ways of ignoring a
> thrown error somewhat, or isn't it better to keep from throwing an error
> upon such non-fatal problem as a wrong date format?
> (I hope I expressed myself correctly).
> Cheers and thanks for your time,
> Francesco
> --
> **************************************************
> Francesco Pirotti
> Dep. TESAF
> CIRGEO – Interdepartmental Research Center on Cartography Photogrammetry
> Remote Sensing and G.I.S.
> University of Padova
> Web: http://www.cirgeo.unipd.it/cirgeo/francescopirotti.htm
> Email: francesco.pirotti at unipd.it
> Phone: +39 049 827 2710
> Phone: +39 349 55 39 261
> **************************************************
>
> --
> **************************************************
> Francesco Pirotti
> Dep. TESAF
> CIRGEO – Interdepartmental Research Center on Cartography Photogrammetry
> Remote Sensing and G.I.S.
> University of Padova
> Web: http://www.cirgeo.unipd.it/cirgeo/francescopirotti.htm
> Email: francesco.pirotti at unipd.it
> Phone: +39 049 827 2710
> Phone: +39 349 55 39 261
> **************************************************
> _______________________________________________
> Liblas-devel mailing list
> Liblas-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/liblas-devel
>
>