Hey Jeremy, I would say I don't know anything about GeoPackage or tile grids profile. What I can say: - the new version only brings parallelism to the script - because of the rewrite, I would hope anything to be slightly easier.
Cheers --- Gregory Bataille On Fri, Sep 29, 2017 at 9:24 PM, Jeremy Palmer <[email protected]> wrote: > Thank you for these great improvements Grégory. > > I'm wondering does gdal2tiles now support output to GeoPackage to save > storage of tiles on disk? Also how hard would it be to support tile grids > profiles with custom origins and resolutions in the new architecture? > > Cheers > Jeremy > > On Sat, Sep 30, 2017 at 4:50 AM, Grégory Bataille < > [email protected]> wrote: > >> Hi all, >> >> I just wanted to announce that after a few months of work (took long, I >> got lazy), *gdal2tiles has gained parallel computing abilities* >> >> It is now *on trunk*. >> >> *A few things to know:* >> - I took upon me to rewrite the script almost entirely to make it more >> modular, testable, ... >> - Because the rewrite + the pararellization are a big and risky work >> (since there were no tests really), there is a new gdal2tiles_old.py script >> on trunk to provide an easy "back-out" for people who would get into >> trouble in their production >> - The script continues to work in a single thread/process mode by default >> - Actually, if you chose the default (or explicitely ask for 1 single >> process), the script will not use any python multiprocessing library (which >> have been known to be flaky). That should ensure that default behavior is >> not disturbed. >> - To activate parallel processing, you need to pass a new flag >> *--processes=n* >> >> >
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
