[pdal] [EXTERNAL] Unable to create hexer stage, PDAL_DRIVER_PATH

Richard Greenwood richard.greenwood at gmail.com
Tue Apr 5 20:38:17 PDT 2016


FWIW - I built hexer and rebuilt pdal w/ hexer and now I'm getting the same
error that I get when using * --fast_boundary*
    PDAL: GDAL failure (1)
"/gis/Wyoming/22_Teton/DEM/NAVD88/Lidar2015/Alta/LAS_1.3/Alta_0101.las" not
recognised as an available field
"Alta_0101.las" is the first file in the directory. I tried on two other
directories with data from different sources and got the same error
referring to the first file in the directory.

The results from
   $*pdal info Alta_0101.las*
Look pretty reasonable, not that I know anything about Lidar data, but the
values shown are all within ranges that I expect for my coordinate system.

Thanks for the advise so far.

Rich




On Tue, Apr 5, 2016 at 2:19 PM, Richard Greenwood <
richard.greenwood at gmail.com> wrote:

> Again, Thanks so much for the replies. Trying with a new (not an existing)
> shapefile I get the same error:
>     $*pdal tindex --tindex newindex.shp *.las --fast_boundary*
>     PDAL: GDAL failure (1)
> "/gis/Wyoming/22_Teton/DEM/NAVD88/Lidar2015/Alta/LAS_1.3/Alta_0101.las" not
> recognised as an available field.
>
> "/gis/Wyoming/22_Teton/DEM/NAVD88/Lidar2015/Alta/LAS_1.3/Alta_0101.las" is
> the first file in the directory so it's weird that it's complaining about
> it being a "field".
>
> A new shapefile is created with four fields and but no rows:
> $*ogrinfo newindex.shp newindex -so*
> INFO: Open of `newindex.shp'
>       using driver `ESRI Shapefile' successful.
> Layer name: newindex
> Metadata:
>   DBF_DATE_LAST_UPDATE=2016-04-05
> Geometry: Polygon
> Feature Count: 0
> Extent: (0.000000, 0.000000) - (0.000000, 0.000000)
> Layer SRS WKT:
> GEOGCS["GCS_WGS_1984",
>     DATUM["WGS_1984",
>         SPHEROID["WGS_84",6378137,298.257223563]],
>     PRIMEM["Greenwich",0],
>     UNIT["Degree",0.017453292519943295]]
> location: String (254.0)
> srs: String (254.0)
> modified: Date (10.0)
> created: Date (10.0)
>
> Thanks,
> Rich
>
>
>
> On Tue, Apr 5, 2016 at 1:56 PM, Andrew Bell <andrew.bell.ia at gmail.com>
> wrote:
>
>> On Tue, Apr 5, 2016 at 2:35 PM, Andrew Bell <andrew.bell.ia at gmail.com>
>> wrote:
>>
>>> On Tue, Apr 5, 2016 at 1:57 PM, Richard Greenwood <
>>> richard.greenwood at gmail.com> wrote:
>>>
>>>> All -
>>>>
>>>> Thanks for the swift replies.
>>>>
>>>> Just the getting the bounding box is all I need so I tried using
>>>> --fast_boundary:
>>>>     $*pdal tindex --fast_boundary --tindex tindex.shp *.las*
>>>>     PDAL: GDAL failure (1)
>>>> "/gis/Wyoming/22_Teton/DEM/NAVD88/Lidar2015/Alta/LAS_1.3/Alta_0101.las" not
>>>> recognised as an available field.
>>>>
>>>> tindex.shp is an exiting, empty shapefile:
>>>>     $*ogrinfo index.shp index -so*
>>>>     INFO: Open of `index.shp'
>>>>           using driver `ESRI Shapefile' successful.
>>>>     . . .
>>>>
>>>
>> If PDAL can open the output index file, it tries to use it and assumes
>> that it has all the necessary fields to accommodate the output.  If you had
>> an existing, empty shapefile, this isn't going to be the case.  It happens
>> to error when it tries to write the filename to a field that we normally
>> create.  I'll try to get some better error checking/info for this.
>>
>> --
>> Andrew Bell
>> andrew.bell.ia at gmail.com
>>
>
>
>
> --
> Richard W. Greenwood, PLS
> www.greenwoodmap.com
>



-- 
Richard W. Greenwood, PLS
www.greenwoodmap.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20160405/53de0e5b/attachment-0001.html>


More information about the pdal mailing list