I downloaded data from Noaa that is in .LAZ format. I need to convert it to .LAS format. I have the lastools toolbox and have looked through the tools and not had much luck yet. Does anyone have any ideas on how to get these files converted? Thanks
In the download there are arcgis toolboxes and in the LAStools.tbx there is a arcscript laszip that wil also unzip to las
would be wise for ESRI to consider enabling direct import of LAZ dataset into a LAS dataset. Data size is much more manageable. Extra conversion with zLAS seems like a re-invented wheel that doesnt work as well as LAZ
Data Interoperability extension can convert LAZ to LAS Dataset.
There is an Idea asking Esri to add a LAZ driver, please go vote it up:
Support LAZ format
Has anyone tried PDAL yet? (See pdal.io webside) It seems like it might be a reasonable compromise.
I want to keep lidar source data in the format in which I download it (LAZ) and I want to produce products from it (typically contours, hillshades). These days I seem to do 90% of my GIS work in Python scripts so a workflow that can do that would be ideal for me-- I would preprocess in a PDAL tool chain to produce an intermediate product (a DEM) and then do the remaining processing in ArcGIS.
The rapidlasso guy is always going on about the evils of closed source but he's producing closed source... the option he gives me is the ability to move from LAZ to LAS, requiring massive disk space then to manage LAS.
I'd be fine with using a tool chain that's all ESRI as long as it does not require converting terabytes of data from LAZ to LAS to zLAS as the first step. I already voted for the LAZ support idea.
pdal is excellent in my experience (admittedly limited to ~40 hours so far), but it can't read zLAS and there's little appetite to add that from the core team (ref). They'll accept contribution from anyone who wants to do the work though.
You are not correct in your statement about "the rapidlasso guy". He does not speak of the evils of "closed source". He speaks of the evils of "closed formats" especially when forced down the throat of a community by the mere market dominance of a company. Prior to the "LAZ clone" fiasco he was quite friendly with Esri as he is with many other closed source companies. What business model Esri uses to operate in the software business was never his beef with them. But Esri using their dominant role to push a closed LiDAR format and thereby making it impossible for other software to directly exploit this #LiDAR data, that is what he and others were critiquing. He writes both open and closed source software. As long as the formats are open both business models can live side by side in harmony.
Below an image and a quote from ESRI’s ArcNews Spring 2011 news letter about the importance of open formats, standards, and specifications. This is discussed in more detail in this blog post. “Esri continues to advocate the need for open access to geographic data and functionality through support for widely adopted and practical standards and specifications. Esri follows an open system strategy for accessing and using geographic data and functionality.” — ArcNews, Spring 2011
Agree 100%, I stand corrected.
I remember that lengthy gap when agencies started publishing file geodatabases and I had no way to read them. Then ESRI published binaries instead of specs, and only for later versions of FGDB so I still had no way to read them.
With LiDAR it's especially painful because of the time and space required to unformat LAZ -> LAS and then reformat LAS -> zLAS
It is slowing my adoption of the technology by making it easier to compromise and use lower res DEMs.
Retrieving data ...