Incorrect EPT.JSON bounds for WI_Statewide_2016_A16?

[bkgelder]

I am experiencing failures downloading workunit_id 66791 in Wisconsin via EPT using a PDAL pipeline. It appears that at least the EPT bounds listed in the JSON are incorrect, as when I plot them it only covers a small fraction of the boundary shown in the WESM geopackage.

Here is a copy of the pipeline I am using that returns 0 points:

{
"pipeline": [
{
"bounds": "([-9912778.7488, -9897721.4119], [5694773.077100001, 5711999.096000001])",
"filename": "https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_WI_Forest_2016_LAS_2019/ept.json",
"type": "readers.ept",
"tag": "readdata"
},
{
"out_srs": "EPSG:26916",
"tag": "reprojectUTM",
"type": "filters.reprojection"
},
{
"filename": "D:/DEP_Proc/DEMProc/LAS_dem2013_3m_040302020105/ept_040302020105_66791.las",
"tag": "writerslas",
"type": "writers.las"
}]}

[keythread]

Sorry for the slow response. I was hoping for a quick fix but I've needed to create a ticket with our operations team to investigate and fix. Either the WESM boundary is incorrect or a substantial amount of data is missing from this WorkUnit. I suspect the latter.

This is what the WESM boundary shows as data coverage:

But this is what the data actually covers (including the WI_Forest_TL_2016 WorkUnit which is everything but the topmost part) :

I suspect a significant portion of data is missing from the source and may take time to recover.