[Liblas-devel] Dealing with "bad" data

Mike Grant mggr at pml.ac.uk
Thu Nov 4 14:25:49 EDT 2010


On 04/11/10 16:07, Howard Butler wrote:
> This email asks what should be our default stance should be in the
> face of bad data.  Some things, like an invalid point count, are
> partially recoverable, but attempts to reconcile many other will
> often result in proliferating bad data.  Should we be hard asses and
> always throw an error?  Do our best to recover on a case-by-case
> basis?

I'd just throw an exception when a LAS file isn't standards compliant
(+1 hard ass).  A separate tool can be written that catches these and
tries to fix up files.  This keeps things clean and gives direct
feedback on naughty LAS files.

If you want to include additional code to handle bad data, it would be
definitely be nice to be have a flag that enables or disables this
behaviour (the strict/loose interpretation Mateusz suggests).

Cheers,

Mike.

--------------------------------------------------------------------------------
Plymouth Marine Laboratory
 
Registered Office:
Prospect Place 
The Hoe
Plymouth  PL1 3DH
 
Website: www.pml.ac.uk
Registered Charity No. 1091222
PML is a company limited by guarantee
registered in England & Wales
company number 4178503

--------------------------------------------------------------------------------
This e-mail, its content and any file attachments are confidential.

If you have received this e-mail in error please do not copy, disclose it to any third party or use the contents or attachments in any way. Please notify the sender by replying to this e-mail or e-mail forinfo at pml.ac.uk and then delete the email without making any copies or using it in any other way.

The content of this message may contain personal views which are not the views of Plymouth Marine Laboratory unless specifically stated.

You are reminded that e-mail communications are not secure and may contain viruses. Plymouth Marine Laboratory accepts no liability for any loss or damage which may be caused by viruses.
--------------------------------------------------------------------------------


More information about the Liblas-devel mailing list