A collection of functions to browse lidar data collections, query collections for coverage for specific locations, and retrieve data covering locations.
I pretty much ignore height units. There will be cases where the original data is in a projection that specifies height units in feet but there won't be any way to tell this from the information in the point file. It is possible to have point files that provide an EPSG code in their WKT projection information that includes vertical units but also includes a modifier to change the vertical units so they are different from the units specified by the base EPSG code. Some of these cases can be hard to figure out. The USGS project index includes vert_crs for many projects so it may be possible to check this and make some changes so we can correctly set the height units (and vertical datum).
I pretty much ignore height units. There will be cases where the original data is in a projection that specifies height units in feet but there won't be any way to tell this from the information in the point file. It is possible to have point files that provide an EPSG code in their WKT projection information that includes vertical units but also includes a modifier to change the vertical units so they are different from the units specified by the base EPSG code. Some of these cases can be hard to figure out. The USGS project index includes vert_crs for many projects so it may be possible to check this and make some changes so we can correctly set the height units (and vertical datum).