You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dataset, CA_ContraCostaCo_2007, is missing a lot of data when compared with what is in usgs-lidar. The attached figure shows the boundary of data from usgs-lidar AWS bucket in red, and the boundary from usgs-lidar-public AWS bucket in black outlines. I downloaded the laz files from s3://usgs-lidar/Projects/CA_ContraCostaCo_2007 to verify that there was actually data there, and that there wasn't simply an incorrect boundary. LAZ files do exist for the entire s3://usgs-lidar/Projects/CA_ContraCostaCo_2007 boundary. It could be that there are issues with these LAZ files that caused the processing workflow to throw them out, resulting in the reduced coverage seen in usgs-lidar-public for this dataset, but I just wanted to document the issue just in case.
The text was updated successfully, but these errors were encountered:
The dataset, CA_ContraCostaCo_2007, is missing a lot of data when compared with what is in usgs-lidar. The attached figure shows the boundary of data from usgs-lidar AWS bucket in red, and the boundary from usgs-lidar-public AWS bucket in black outlines. I downloaded the laz files from s3://usgs-lidar/Projects/CA_ContraCostaCo_2007 to verify that there was actually data there, and that there wasn't simply an incorrect boundary. LAZ files do exist for the entire s3://usgs-lidar/Projects/CA_ContraCostaCo_2007 boundary. It could be that there are issues with these LAZ files that caused the processing workflow to throw them out, resulting in the reduced coverage seen in usgs-lidar-public for this dataset, but I just wanted to document the issue just in case.
The text was updated successfully, but these errors were encountered: