lidar-with-pdallisted
Install: claude install-skill wiatrek-kevin-s/columbus
# Lidar with PDAL
PDAL (Point Data Abstraction Library) reads, filters and writes point clouds through
**pipelines**: a JSON list of stages run in order. Readers bring points in, filters change
or select them, writers send them out (to LAS/LAZ, COPC or a raster).
## General practice (with or without Columbus)
### 1. Look before you process
```bash
pdal info --summary tile.laz # point count, bounds, CRS, dimensions
pdal info --metadata tile.laz # header: LAS version, point format, scale/offset, SRS, VLRs
pdal info --boundary tile.laz # real footprint (hexbin) and average point density
```
Answer these first:
- **LAS version and point format**: LAS 1.4 with point formats 6 to 10 is current; it
stores the CRS as OGC WKT. LAS 1.2/1.3 (formats 0 to 5) store it as GeoTIFF keys and allow
only classes 0 to 31.
- **Horizontal CRS and units**: metres or US survey feet. Texas data is often state plane in
feet (EPSG:2277 NAD83 / Texas Central ftUS, or EPSG:6578 for NAD83(2011)).
- **Vertical datum and units**: usually NAVD88 (with a geoid model such as GEOID18) for US
public lidar, as a compound CRS (EPSG:6343+5703 is NAD83(2011) / UTM 14N + NAVD88 height).
If the header has no vertical CRS, find it in the project report. Do not guess; ellipsoid
and NAVD88 heights differ by tens of metres in the US.
- **Classification counts**: has it been classified, and with which codes?
```json
[
"tile.laz",
{ "type": "filters.stats", "dimensions": "Z", "count