lastile error: WARNING: on-the-fly merged LAS 1.2 files contain too many points (8441563175)

642 views
Skip to first unread message

Andy Ritchie

unread,
Feb 22, 2016, 6:13:20 PM2/22/16
to LAStools - efficient tools for LiDAR processing
I'm getting a lastile error when I try to tile some lidar data. The data converted into .laz just fine, and I was able to render some test dems using blast2dem, although the coordinate system is "unknown" when I open the resulting DEM in GIS.

I first converted las to laz then indexed using lasindex:

>lasindex -i *.laz

I am running lastile as:

>lastile -i *.laz -files_are_flightlines -buffer 25 -o ..\tiles\olympex.laz

I also tried -tile_size 500.

The largest .laz file only has ~170 million points and there are two scanners per flightline (2 files/line) with flightlines sidelapping about 50%.

Here are the first few errors when I try to tile:

WARNING: on-the-fly merged LAS 1.2 files contain too many points (8441563175) for single LAS 1.2 file.
WARNING: written 98320 points but expected 0 points
WARNING: on-the-fly merged LAS 1.2 files contain too many points (8441563175) for single LAS 1.2 file.
WARNING: written 72557 points but expected 0 points
WARNING: on-the-fly merged LAS 1.2 files contain too many points (8441563175) for single LAS 1.2 file.
WARNING: written 118057 points but expected 0 points
WARNING: on-the-fly merged LAS 1.2 files contain too many points (8441563175) for single LAS 1.2 file.
WARNING: written 105559 points but expected 0 points
WARNING: on-the-fly merged LAS 1.2 files contain too many points (8441563175) for single LAS 1.2 file.
WARNING: written 138444 points but expected 0 points
...

filenames are as follows

USWAOL20140904f1a1 - Scanner 1 - 140904_145250_1 - originalpoints_dem_filter.laz
USWAOL20140904f1a1 - Scanner 2 - 140904_145250_2 - originalpoints_dem_filter.laz
USWAOL20140904f1a1 - Scanner 1 - 140904_151114_1 - originalpoints_dem_filter.laz
...

in the target directory I am getting small (<1mb) and zero-byte tile files. when I ran single-core I got over 100mb of them in a few tens of seconds.

lasinfo for the largest file is below (note that I ran the reports on the original .las files and rescaled to 0.01 0.01 0.01 when I compressed to .laz)

reporting all LAS header entries:
  file signature:             'LASF'
  file source ID:             0
  global_encoding:            0
  project ID GUID data 1-4:   00000000-0000-0000-2020-202020202020
  version major.minor:        1.2
  system identifier:          'EXTRACTION                      '
  generating software:        '                                '
  file creation day/year:     274/2015
  header size:                227
  offset to point data:       714
  number var. length records: 3
  point data format:          1
  point data record length:   28
  number of point records:    171838760
  number of points by return: 86588632 53455528 23997314 6573379 1100164
  scale factor x y z:         0.001 0.001 0.001
  offset x y z:               455217 5317224 52
  min x y z:                  452785.026 5310223.030 -102.966
  max x y z:                  459228.630 5331567.813 1220.983
variable length header record 1 of 3:
  reserved             43707
  user ID              'LASF_Projection'
  record ID            34735
  length after header  208
  description          'GeoKeyDirectoryTag (mandatory)'
    GeoKeyDirectoryTag version 1.1.0 number of keys 25
      key 1024 tiff_tag_location 0 count 1 value_offset 1 - GTModelTypeGeoKey: ModelTypeProjected
      key 1025 tiff_tag_location 0 count 1 value_offset 2 - GTRasterTypeGeoKey: RasterPixelIsPoint
      key 1026 tiff_tag_location 34737 count 27 value_offset 0 - GTCitationGeoKey: WGS84, WGS84, UTM zone 10N
      key 2048 tiff_tag_location 0 count 1 value_offset 32767 - GeographicTypeGeoKey: user-defined
      key 2049 tiff_tag_location 34737 count 13 value_offset 40 - GeogCitationGeoKey: WGS84, WGS84
      key 2050 tiff_tag_location 0 count 1 value_offset 32767 - GeogGeodeticDatumGeoKey: user-defined
      key 2051 tiff_tag_location 0 count 1 value_offset 32767 - GeogPrimeMeridianGeoKey: look-up for 32767 not implemented
      key 2052 tiff_tag_location 0 count 1 value_offset 9001 - GeogLinearUnitsGeoKey: Linear_Meter
      key 2054 tiff_tag_location 0 count 1 value_offset 9102 - GeogAngularUnitsGeoKey: Angular_Degree
      key 2056 tiff_tag_location 0 count 1 value_offset 32767 - GeogEllipsoidGeoKey: look-up for 32767 not implemented
      key 2057 tiff_tag_location 34736 count 1 value_offset 6 - GeogSemiMajorAxisGeoKey: 6378137
      key 2059 tiff_tag_location 34736 count 1 value_offset 7 - GeogInvFlatteningGeoKey: 298.2572236
      key 2060 tiff_tag_location 0 count 1 value_offset 9102 - GeogAzimuthUnitsGeoKey: Angular_Degree
      key 2061 tiff_tag_location 34736 count 1 value_offset 5 - GeogPrimeMeridianLongGeoKey: 0
      key 3072 tiff_tag_location 0 count 1 value_offset 32767 - ProjectedCSTypeGeoKey: user-defined
      key 3073 tiff_tag_location 34737 count 13 value_offset 27 - PCSCitationGeoKey: UTM zone 10N
      key 3074 tiff_tag_location 0 count 1 value_offset 32767 - ProjectionGeoKey: user-defined
      key 3075 tiff_tag_location 0 count 1 value_offset 1 - ProjCoordTransGeoKey: CT_TransverseMercator
      key 3076 tiff_tag_location 0 count 1 value_offset 9001 - ProjLinearUnitsGeoKey: Linear_Meter
      key 3080 tiff_tag_location 34736 count 1 value_offset 1 - ProjNatOriginLongGeoKey: -123
      key 3081 tiff_tag_location 34736 count 1 value_offset 0 - ProjNatOriginLatGeoKey: 0
      key 3082 tiff_tag_location 34736 count 1 value_offset 2 - ProjFalseEastingGeoKey: 500000
      key 3083 tiff_tag_location 34736 count 1 value_offset 3 - ProjFalseNorthingGeoKey: 0
      key 3092 tiff_tag_location 34736 count 1 value_offset 4 - ProjScaleAtNatOriginGeoKey: 0.9996
      key 4099 tiff_tag_location 0 count 1 value_offset 9001 - VerticalUnitsGeoKey: Linear_Meter
variable length header record 2 of 3:
  reserved             43707
  user ID              'LASF_Projection'
  record ID            34736
  length after header  64
  description          'GeoDoubleParamsTag (optional)'
    GeoDoubleParamsTag (number of doubles 8)
      0 -123 500000 0 0.9996 0 6.37814e+006 298.257 
variable length header record 3 of 3:
  reserved             43707
  user ID              'LASF_Projection'
  record ID            34737
  length after header  53
  description          'GeoASCIIParamsTag (optional)'
    GeoAsciiParamsTag (number of characters 53)
      WGS84, WGS84, UTM zone 10N|UTM zone 10N|WGS84, WGS84|
reporting minimum and maximum for all LAS point record entries ...
  X            -2431974    4011630
  Y            -7000970   14343813
  Z             -154966    1168983
  intensity         163      65535
  return_number       1          7
  number_of_returns   1          7
  edge_of_flight_line 0          1
  scan_direction_flag 0          0
  classification      2          4
  scan_angle_rank   -35         33
  user_data           0          0
  point_source_ID     0          0
  gps_time 593238.884927 593582.912432
number of first returns:        86588635
number of intermediate returns: 31794551
number of last returns:         86588440
number of single returns:       33132866
WARNING: for return 1 real number of points by return (86588635) is different from header entry (86588632).
WARNING: there are 115619 points with return number 6
WARNING: there are 8121 points with return number 7
overview over number of returns of given pulse: 33132866 58916291 52271895 21893062 4922805 647238 54603
histogram of classification of points:
         9874058  ground (2)
       161964702  medium vegetation (4)

Kirk Waters - NOAA Federal

unread,
Feb 23, 2016, 10:17:30 AM2/23/16
to LAStools - efficient command line tools for LIDAR processing
Andy,
I'm not sure if the projection issue is related to the problems lastile is having, though it is possible. What strikes me as odd in your projection info is that WGS84 UTM 10N is a very standard projected coordinate system with a well defined EPSG code, however, your file is listing it as user defined (all those 32767 entries). It looks like all the info is there (and some extra stuff too), but the GIS software is going to look at how it's coded and assume it is something unusual and "unknown".

Kirk Waters, PhD                     | NOAA Office for Coastal Management
Applied Sciences Program      | 2234 South Hobson Ave
843-740-1227                          | Charleston, SC 29405    

--
Download LAStools at
http://lastools.org
http://rapidlasso.com
Be social with LAStools at
http://facebook.com/LAStools
http://twitter.com/LAStools
http://linkedin.com/groups/LAStools-4408378
Manage your settings at
http://groups.google.com/group/lastools/subscribe

Martin Isenburg

unread,
Mar 14, 2016, 4:09:34 PM3/14/16
to LAStools - efficient command line tools for LIDAR processing

Hi Andy,

Sorry for the late reply. Looks like you are running lastile with the '-cores n' option as you are getting so many "on-the-fly" WARNINGs. Good that you run lasindex first because otherwise multi-core lastile degenerates to be very slow.

http://rapidlasso.com/lastile
http://lastools.org/download/lastile_README.txt

Note these are all just WARNINGs and not ERRORs. Make sure you use a newer LAStools version as there was some issue with exzessive temp files of size zero in an earlier version.

I suggest to make one run of lasvalidate over your input files just to make sure that no corruptions in the input files mess up your computations:

lasvalidate -i *.laz -o report.xml

Regards,

Martin @rapidlasso

Reply all
Reply to author
Forward
0 new messages