[pdal] Request: add option for filename column

[Tom van Tilburg]

I am writing over a thousand laz files, all using the same PCID.
Does this mean that I should better create one PCID for every file that I
import?

Tom

On Mon, 5 Oct 2015 at 14:20 Paul Ramsey <pramsey at cleverelephant.ca> wrote:

> Yes, that’s how it should be done. Or, at least adding a pc_files (
> file_id, file_name ) table and a file_id column to the target pointcloud
> table.
> P
>
> On October 5, 2015 at 5:17:43 AM, Andrew Bell (andrew.bell.ia at gmail.com)
> wrote:
>
> On Mon, Oct 5, 2015 at 3:42 AM, Tom van Tilburg <tom.van.tilburg at gmail.com
> > wrote:
>
>> Considering an earlier discussion about mimicking the behaviour of GDAL
>> in PDAL (http://lists.osgeo.org/pipermail/pdal/2015-September/000744.html),
>> I had 2 ideas about improved dbase functionality:
>>
>> 1. Give the option to add filenames to the patches
>> An extra column that gives the name of the original laz file would
>> tremendously improve the administration of importing and updating your
>> pointcloud data. Imagine you receive a new lasfile with updated points (new
>> classification for instance), you would like to replace only those points
>> in your dbase, but there is no way to tell which patch originated from
>> which file.
>>
>
> Could one not store this in a separate table along with the PCID and then
> join?
>
> --
> Andrew Bell
> andrew.bell.ia at gmail.com
>
> _______________________________________________
> pdal mailing list
> pdal at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pdal
>
>
> --
> http://postgis.net
> http://cleverelephant.ca
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20151005/14181d96/attachment-0001.html>