Incorrect EPT.JSON bounds for SD_Southwest_B2_2018?

[bkgelder]

I am experiencing failures downloading workunit_id 79125 in South Dakota 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": "([-11386571.4549, -11370238.3078], [5310909.450199999, 5314697.409899998])",
"filename": "https://s3-us-west-2.amazonaws.com/usgs-lidar-public/SD_Southwest_B2_2018/ept.json",
"type": "readers.ept",
"tag": "readdata"
},
{
"out_srs": "EPSG:26913",
"tag": "reprojectUTM",
"type": "filters.reprojection"
},
{
"filename": "D:/DEP_Proc/DEMProc/LAS_dem2013_3m_101402030101/ept_101402030101_79125.las",
"tag": "writerslas",
"type": "writers.las"
}]}

[keythread]

I'm in the process of transferring an update to the original project that should now match the WESM boundaries. The original dataset was missing a large chunk of data within the Pine Ridge Indian Reservation. I'll update this issue when the transfer is complete (should be in the next 24-48 hours).

[keythread]

Data updates have been transferred. Please test again. The data coverage now reflects the entirety of the WESM boundaries now: