According to what I see I can guess that your LAS file is a LAS 1.4 file with a CRS stored as WKT string instead of an EPSG code. The string stored in the LAS file is:
PROJCS["NAD_1983_NSRS2007_StatePlane_Florida_East_FIPS_0901",GEOGCS["GCS_NAD_1983_NSRS2007",DATUM["D_NAD_1983_NSRS2007",SPHEROID["GRS_1980",6378137.0,298.257222101,AUTHORITY["EPSG",7019]],AUTHORITY["EPSG",6759]],PRIMEM["Greenwich",0.0,AUTHORITY["EPSG",8901]],UNIT["Degree",0.0174532925199433,AUTHORITY["EPSG",9102]],AUTHORITY["EPSG",4759]],PROJECTION["Transverse_Mercator",AUTHORITY["Esri",43006]],PARAMETER["False_Easting",200000.0,AUTHORITY["Esri",100001]],PARAMETER["False_Northing",0.0,AUTHORITY["Esri",100002]],PARAMETER["Central_Meridian",-81.0,AUTHORITY["Esri",100010]],PARAMETER["Scale_Factor",0.9999411764705882,AUTHORITY["Esri",100003]],PARAMETER["Latitude_Of_Origin",24.33333333333333,AUTHORITY["Esri",100021]],UNIT["Meter",1.0,AUTHORITY["EPSG",9001]],AUTHORITY["EPSG",3511]],VERTCS["NAVD_1988",VDATUM["North_American_Vertical_Datum_1988",AUTHORITY["EPSG",5103]],PARAMETER["Vertical_Shift",0.0,AUTHORITY["Esri",100006]],PARAMETER["Direction",1.0,AUTHORITY["Esri",100007]],UNIT["Meter",1.0,AUTHORITY["EPSG",9001]],AUTHORITY["EPSG",5703]]
that is interpreted by sf
using st_crs()
. This is the content you copy/pasted above. This CRS is a compound CRS with XY
being NAD83(NSRS2007) / Florida East and Z
being NAVD88 height.
Your vector file on another hand only contains XY data with a simple CRS which is NAD83(NSRS2007) / Florida East.
The two CRS are indeed different. sf
performs string comparisons and strings mismatch even if they are equivalent for XY. This is not something I, as the lidR developer, can improve. This is something that must come from sf
.
The simplest workaround is to assign the CRS of the vector to the point cloud
st_crs(FL_20180602_B1_e1586n0472) = st_crs(clip_sf)
Best Answer
What you are reporting is simply a little bug. When plotting with
chunk = TRUE
lidR tries to build the filenames but in this context it cannot. I opened an issue with a reproducible example here.However clipping works as expected:
Created on 2022-02-22 by the reprex package (v2.0.1)