Las2Las - Embedding Projection and going 1.2 to 1.4

153 views
Skip to first unread message

Maros Hana

unread,
Nov 13, 2019, 4:11:28 PM11/13/19
to LAStools - efficient tools for LiDAR processing
Hi 
since Terrascan strips the projection info from our files I need to embed projection into new 1.4 files created from 1.2

goal: go from 1.2 to 1.4 & embedding UTM10, navd88, feet
I tried: 


las2las -i *.las  -set_version 1.4 -set_point_type 6 -epsg 6339 -vertical_navd88 -set_ogc_wkt 

when I load the files in Global mapper they are out of range

any ideas am i going right about this? thanks.


our original files have: the following info 

NAD_1983_UTM_Zone_10N_Feet
NAD_1983_UTM_Zone_10N_Feet|projection: Transverse Mercator
NAVD88 - Geoid12B (Feet)

-------------------------from lasinfo 1.2 before terrascan----------------------------------
variable length header record 1 of 5:
  reserved             0
  user ID              'LASF_Projection'
  record ID            34735
  length after header  216
  description          'GeoTiff Projection Keys'
    GeoKeyDirectoryTag version 1.1.0 number of keys 26
      key 1024 tiff_tag_location 0 count 1 value_offset 1 - GTModelTypeGeoKey: ModelTypeProjected
      key 1026 tiff_tag_location 34737 count 38 value_offset 59 - GTCitationGeoKey: PCS Name = NAD_1983_UTM_Zone_10N_Feet
      key 2048 tiff_tag_location 0 count 1 value_offset 4269 - GeographicTypeGeoKey: GCS_NAD83
      key 2049 tiff_tag_location 34737 count 103 value_offset 122 - GeogCitationGeoKey: GCS Name = GCS_North_American_1983|Datum = North_American_1983|Ellipsoid = GRS_1980|Primem = Greenwich
      key 2050 tiff_tag_location 0 count 1 value_offset 6269 - GeogGeodeticDatumGeoKey: Datum_North_American_Datum_1983
      key 2051 tiff_tag_location 0 count 1 value_offset 8901 - GeogPrimeMeridianGeoKey: PM_Greenwich
      key 2054 tiff_tag_location 0 count 1 value_offset 9102 - GeogAngularUnitsGeoKey: Angular_Degree
      key 2055 tiff_tag_location 34736 count 1 value_offset 9 - GeogAngularUnitSizeGeoKey: 0.01745329252
      key 2056 tiff_tag_location 0 count 1 value_offset 7019 - GeogEllipsoidGeoKey: Ellipse_GRS_1980
      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.2572221
      key 2061 tiff_tag_location 34736 count 1 value_offset 8 - GeogPrimeMeridianLongGeoKey: 0
      key 3059 tiff_tag_location 0 count 1 value_offset 1 - key ID 3059 not implemented
      key 3072 tiff_tag_location 0 count 1 value_offset 32767 - ProjectedCSTypeGeoKey: user-defined
      key 3073 tiff_tag_location 34737 count 59 value_offset 0 - PCSCitationGeoKey: NAD_1983_UTM_Zone_10N_Feet|projection: Transverse Mercator
      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 9003 - ProjLinearUnitsGeoKey: Linear_Foot_US_Survey
      key 3077 tiff_tag_location 34736 count 1 value_offset 5 - ProjLinearUnitSizeGeoKey: 0.3048006096
      key 3081 tiff_tag_location 34736 count 1 value_offset 0 - ProjNatOriginLatGeoKey: 0
      key 3082 tiff_tag_location 34736 count 1 value_offset 1 - ProjFalseEastingGeoKey: 1640416.667
      key 3083 tiff_tag_location 34736 count 1 value_offset 2 - ProjFalseNorthingGeoKey: 0
      key 3088 tiff_tag_location 34736 count 1 value_offset 3 - ProjCenterLongGeoKey: -123
      key 3092 tiff_tag_location 34736 count 1 value_offset 4 - ProjScaleAtNatOriginGeoKey: 0.9996
      key 4097 tiff_tag_location 34737 count 25 value_offset 97 - VerticalCitationGeoKey: NAVD88 - Geoid12B (Feet)
      key 4099 tiff_tag_location 0 count 1 value_offset 9003 - VerticalUnitsGeoKey: Linear_Foot_US_Survey
variable length header record 2 of 5:
  reserved             0
  user ID              'LASF_Projection'
  record ID            34736
  length after header  80
  description          'GeoTiff double parameters'
    GeoDoubleParamsTag (number of doubles 10)
      0 1.64042e+006 0 -123 0.9996 0.304801 6.37814e+006 298.257 0 0.0174533 
variable length header record 3 of 5:
  reserved             0
  user ID              'LASF_Projection'
  record ID            34737
  length after header  226
  description          'GeoTiff ASCII parameters'
    GeoAsciiParamsTag (number of characters 226)
      NAD_1983_UTM_Zone_10N_Feet|projection: Transverse Mercator|PCS Name = NAD_1983_UTM_Zone_10N_Feet|NAVD88 - Geoid12B (Feet)|GCS Name = GCS_North_American_1983|Datum = North_American_1983|Ellipsoid = GRS_1980|Primem = Greenwich| 
variable length header record 4 of 5:
  reserved             0
  user ID              'NIIRS10'
  record ID            4
  length after header  10
  description          'NIIRS10 Timestamp'
variable length header record 5 of 5:
  reserved             0
  user ID              'NIIRS10'
  record ID            1
  length after header  26
  description          'NIIRS10 Tile Index'
the header is followed by 2 user-defined bytes
reporting minimum and maximum for all LAS point record entries ...
  X           437507190  438103430
  Y          -580533669 -579528789
  Z              374420     827600
  intensity           0      65535
  return_number       1          4
  number_of_returns   1          4
  edge_of_flight_line 0          1
  scan_direction_flag 1          1
  classification      1          7
  scan_angle_rank   -29         35
  user_data           0          0
  point_source_ID    73         73
  gps_time 244478445.026995 244478455.923836
WARNING: range violates GPS week time specified by global encoding bit 0
WARNING: there is coordinate resolution fluff (x10) in XYZ
number of first returns:        888444
number of intermediate returns: 280
number of last returns:         888444
number of single returns:       841479
covered area in square survey feet: 325728
point density: all returns 2.87 last only 2.73 (per square survey foot)
      spacing: all returns 0.59 last only 0.61 (in survey feet)
overview over number of returns of given pulse: 841479 93374 828 8 0 0 0
histogram of classification of points:
          330353  unclassified (1)
          186862  ground (2)
          197432  low vegetation (3)
          220152  high vegetation (5)
             890  noise (7)

Martin Isenburg

unread,
Nov 13, 2019, 4:30:44 PM11/13/19
to LAStools - efficient command line tools for LIDAR processing
Hello,

I see two other issues in your file:

WARNING: range violates GPS week time specified by global encoding bit 0
WARNING: there is coordinate resolution fluff (x10) in XYZ

I would fix this in two steps with las2las:

:: rescale from fake millifeet to actual centifeet resolution

las2las -i bad\*.laz ^
             -rescale 0.01 0.01 0.01 ^
             -auto_reoffset ^
             -remove_all_vlrs ^
             -set_global_encoding_gps_bit 1 ^
             -odir better -olaz ^
             -cores 8

:: now go to LAS 1.4 and specify the lost projection.

  las2las -i bad\*.laz ^  
              -set_point_type 6 ^
              -epsg 6339 ^
              -vertical_navd88_geoid12b ^
              -elevation_survey_feet ^
              -set_ogc_wkt ^
              -odir fixed -olaz ^
              -cores 8

Here is the error. You are using 6339 which is in horizontal meters but the original files were in horizontal feet. 

https://epsg.io/6339  

You need to add back in the exact same projection.

Regards.

Martin @rapidlasso

--
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
---
You received this message because you are subscribed to the Google Groups "LAStools - efficient tools for LiDAR processing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lastools+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lastools/fc6d81af-3c71-4a6f-81a0-10810f199909%40googlegroups.com.

Maros Hana

unread,
Nov 15, 2019, 11:58:50 AM11/15/19
to LAStools - efficient tools for LiDAR processing
Cool thanks!  that worked
 - 
question though about best & proper way embedding custom UTM 10 US survey feet for horizontal and vertical

this was info from our .prj ....


PROJCS["NAD_1983_UTM_Zone_10N",
GEOGCS["GCS_North_American_1983",
DATUM["D_NORTH_AMERICAN_1983",
SPHEROID["GRS_1980",6378137,298.257222101]],
PRIMEM["Greenwich",0],
UNIT["Degree",0.017453292519943295]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",-123],
PARAMETER["scale_factor",0.9996],
PARAMETER["false_easting",1640416.666666667],
PARAMETER["false_northing",0],
UNIT["Foot_US",0.30480060960121924]]

Maros Hana

unread,
Nov 15, 2019, 11:58:57 AM11/15/19
to LAStools - efficient tools for LiDAR processing
Hi - Looks like espg 4110 will work

Scope: US survey foot form of UTM zone 10N.


http://pacificprojections.spc.int/4110


Reply all
Reply to author
Forward
0 new messages