[pdal] EPT:// prefix issue with PDAL 2.2

[Matt Beckley]

Hello,

It seems like when reading the ept data from the AWS 3DEP entwine bucket
the reader will not work unless I add the prefix, "ept://" to the URL (see
examples below).  This applies only to PDAL v2.2, and it is not clear if
this is a dataset-specific issue.  PDAL 2.1 will run with or without the
ept:// prefix, but it has the odd result that the filesizes will differ
slightly if using ept:// in the prefix or not.  Point counts are the same
whether or not you use ept:// with PDAL 2.1, but the "filesource_id"
parameter differs, so the filesize differences are probably due to slight
header differences.  In regards to the PDAL2.2 EPT issue, so far this seems
to happen on the following AWS 3DEP Entwine datasets:

USGS LPC CA Central Valley 2017 LAS 2019
CO_Southwest_NRCS_B2_2018
TX WestTexas B1 2018
NM SouthCentral B8 2018

*My question:*  For PDAL v2.2, should I always use the EPT:// prefix when
using readers.ept?  (seems related to:
https://github.com/PDAL/PDAL/pull/3174).  Also, as an aside, is streaming
available for readers.ept?  Documentation doesn't indicate it is, but this
issue: https://github.com/PDAL/PDAL/issues/2439 makes it seem that maybe it
is?  I'm uncertain how to test this.

Any info you could provide would be most appreciated.

Test1:  PDAL 2.2 WITHOUT EPT:// Prefix (PDAL installed via isolated conda
environment):

{


    "pipeline": [{


        "type": "readers.ept",


        "filename": "
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_CA_Central_Valley_2017_LAS_2019",

        "bounds": "([-13484500, -13484200], [4653000,4654200])"


    },


       "points_CA_noept.laz"]}

pdal pipeline pipeline.json gives error:

PDAL: readers.ept: Could not read from
s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_CA_Central_Valley_2017_LAS_2019

Test2:  PDAL 2.2 WITH EPT:// Prefix (PDAL installed via isolated conda
environment):
{


    "pipeline": [{


        "type": "readers.ept",


        "filename": "ept://
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_CA_Central_Valley_2017_LAS_2019",

        "bounds": "([-13484500, -13484200], [4653000,4654200])"


    },


       "points_CA_wept.laz"]}

pdal pipeline pipeline.json runs successfully


Test3:  PDAL 2.1 WITHOUT EPT:// Prefix (PDAL installed via isolated conda
environment):
{
    "pipeline": [{
        "type": "readers.ept",
        "filename": "ept://
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_CA_Central_Valley_2017_LAS_2019
",
        "bounds": "([-13484500, -13484200], [4653000,4654200])"
    },
       "points_CA_wept_v21.laz"]}

pdal pipeline pipeline.json runs successfully, filesize is: 3453289 bytes.
 "count": 956938


Test4:  PDAL 2.1 WITH EPT:// Prefix (PDAL installed via isolated conda
environment):
{


    "pipeline": [{


        "type": "readers.ept",


        "filename": "
https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_CA_Central_Valley_2017_LAS_2019",

        "bounds": "([-13484500, -13484200], [4653000,4654200])"


    },


       "points_CA_NOept_v21.laz"]}

pdal pipeline pipeline.json runs successfully, but filesize is different:
 3479637 bytes. "count": 956938


Point counts for results from PDAL 2.1 run match.  Only difference is
"filesource_id".  Version without EPT:// prefix has filesource_id=0, while
with EPT:// prefix "filesource_id": 26982.
---------------------------
Matthew Beckley
Data Engineer
UNAVCO/OpenTopography
beckley at unavco.org
cell: 301-982-9819
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20201215/bc9ff3b2/attachment.html>