[pdal] Proposal: Remove SQLite reader/writer for PDAL 2.0

[Norman Barker]

>
> >More seriously, I think things are a little better than they used to be,
> but there were definitely dragons here in the past. This internal and
> external lack of interchange is why efforts like >Arrow are gaining
> traction, but there has been bumps along that road too.  I'd be curious to
> hear what Norman has to say on this topic as it is a space they are
> charging after quite intently.
>
> Round tripping between PDAL and other tools using TileDB is something we
have done. I will be creating a couple of example python notebooks
demonstrating some of this in the next few weeks. We have done a fair
amount of testing of creating TileDB arrays with PDAL and then accessing /
modifying the arrays outside of PDAL with other tools and then back to PDAL
which I think is the use case you are describing. It works well.


> > """
> > It is untested whether problems may occur if the versions of Python
> > used in writing the file and for reading the file don’t match.
> > """
> >
> > Is this referring to issues such as:
> >
> >
> https://stackoverflow.com/questions/24105148/load-python-2-npy-file-in-python-3
> >
> > or something else?
>
> Yeah.
>
> _______________________________________________
> pdal mailing list
> pdal at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pdal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20190801/84d0dff1/attachment.html>