Missing data from WY_YellowstoneNP_2RF_2020

[mattbeckley]

The dataset, WY YellowstoneNP 2RF 2020, seems to be missing a lot of data. Attached image shows coverage of data relative to dataset bounds

[keythread]

There are only two lidar tiles in this WorkUnit (WY_Yellowstone_2RF_2020) and they are geographically separate (I don't yet know the purpose of this WorkUnit - I will check into this.) The footprints of the tiles look like this:

Additionally, the PDAL generated boundaries do look odd based on the source. Not exactly sure what's going on.

[connormanning]

The PDAL generated boundaries are computed from a coarse hexagonal grid (using filters.hexbin) and I am not surprised that they'd look like this from only these small chips of underlying data. I forget the exact hexagon grid size we use, but they are massive compared to these chips since their purpose is for broad national-scale coverage context like the map here, and not intended to be useful or close-fitting for individual tiles like this.

When the only available data all fits within one or a couple of hexagons you'll get weird shapes like this as the hexagons get sliced up based on the data contained within it. Of course this is not an issue when the data is the size of several hundred hexagons which is more typically the case for this dataset.

[keythread]

FYI - the 'RF' in the WorkUnit name stands for 'reflight' - something was wrong with the data initially and the contractor delivered the original WorkUnit (WY_YellowstoneNP_2_2020) with holes and submitted a new WorkUnit with the corrected 2 tiles when it became available.