topic Re: Invalid or unsupported LAS files (10.1 service pack 1) in 3D Questions

Invalid or unsupported LAS files (10.1 service pack 1)

MattAyer — Fri, 09 Nov 2012 15:23:09 GMT

Prior to installing service pack one I was able to create LAS datasets with some sample LAS files that I have. These LAS datasets still work. But I can't can't create another LAS dataset with the same LAS files. Is there a known issue with service pack 1 and LAS files? I have even tried removing a LAS file from an existing dataset and adding it back in, it is no longer recognized. All I get is an error message (one or more invalid or unsupported LAS files were ignored)

Re: Invalid or unsupported LAS files (10.1 service pack 1)

CarrieDavis — Fri, 09 Nov 2012 23:53:30 GMT

Hi Matt,

Are you able to share one of these sample las files or give a link to the data if its available free from a download site? ArcGIS 10.1 Las datasets should support 1.0, 1.1, 1.2 and 1.3 version las files. Are you able to use the sample files as input to the Point File Information tool?

Point File Information (3D Analyst Conversion tool)
http://resources.arcgis.com/en/help/main/10.1/index.html#//00q900000025000000

Or view the las file in another software such as PointVue LE? http://www.geocue.com/support/utilities.html

You can remove the service pack. I would suggest to contact Esri support at support@esri.com if the service pack indeed seems to be the issue.

http://blogs.esri.com/esri/supportcenter/2011/10/07/need-to-uninstall-a-service-pack-or-patch-at-10-no-problem/

Best wishes,

Re: Invalid or unsupported LAS files (10.1 service pack 1)

MattAyer — Tue, 13 Nov 2012 10:09:11 GMT

Thanks for the information. I ended up removing the service pack and was able to use the LAS files again.

Re: Invalid or unsupported LAS files (10.1 service pack 1)

MapEnglish — Tue, 09 Apr 2013 15:23:29 GMT

Hi:

I too am experiencing the same problem. Using the CheckLAS utility here is the message:

WARNING 1: Failed to import spatial reference
Failed to read LAS linear unit geo-key.

I will uninstall SP1 and see what happens. I'm happy to share the 350MB LAS file via ftp.

Matt English
Esri Canada

Re: Invalid or unsupported LAS files (10.1 service pack 1)

AndyRitchie — Tue, 02 Jul 2013 22:46:31 GMT

I had the same problem. I have attached a sample dataset that throws the error. The dataset is viewable in PointVue LE, but generates the following error when I run CheckLAS.

WARNING 1: Failed to import spatial reference
           Failed to read LAS linear unit geo-key.

Screenshot and workaround are below. Pointcloud as a ZIP along with logfile results as attachment in case ESRI wants to fix the bug. It looks like PointVue is more forgiving of GeoKeys than ArcGIS is, and so can import the data successfully.

[ATTACH=CONFIG]25672[/ATTACH]

--EDIT--

Thanks Joel @ USGS for pointing me to a post on the lastools Google Group that led to a workaround.

I was able to strip out the offending VLRs (in my case userbytes were fine) and add correct projection information with las2las. lasinfo gave me a good look at what the offending data were.

Here's lasinfo report on the VLRs before I ran las2las:

    GeoKeyDirectoryTag version 1.1.0 number of keys 4
      key 1024 tiff_tag_location 0 count 1 value_offset 1 - GTModelTypeGeoKey: ModelTypeProjected
      key 1025 tiff_tag_location 0 count 1 value_offset 1 - GTRasterTypeGeoKey: RasterPixelIsArea
      key 3072 tiff_tag_location 0 count 1 value_offset 2285 - ProjectedCSTypeGeoKey: look-up for 2285 not implemented
      key 3073 tiff_tag_location 34737 count 32 value_offset 0 - PCSCitationGeoKey: NAD83 / Washington North (ftUS)

My las2las command line options were:

las2las -i GLI_Sparse.las -remove_extra -remove_all_vlrs -o GLI_Sparse_reproc.las -sp83 WA_N -feet -elevation_feet

and the resulting (working) keys were:

GeoKeyDirectoryTag version 1.1.0 number of keys 4
      key 1024 tiff_tag_location 0 count 1 value_offset 1 - GTModelTypeGeoKey: ModelTypeProjected
      key 3072 tiff_tag_location 0 count 1 value_offset 32148 - ProjectedCSTypeGeoKey: PCS_NAD83_Washington_North
      key 3076 tiff_tag_location 0 count 1 value_offset 9002 - ProjLinearUnitsGeoKey: Linear_Foot
      key 4099 tiff_tag_location 0 count 1 value_offset 9002 - VerticalUnitsGeoKey: Linear_Foot

Hopefully this is useful to folks.