1) Merge maptiler's gdal2tiles enhancements into GDAL version, and make
maptiler just a GUI over it
2) Merge maptiler's gdal2tiles enhancements into GDAL version, and
also import
the GUI (I think it is lightweight) if there's no too strong build
complications involved for GDAL. Would have to be checked
3) Remove gdal2tiles from GDAL so that the reborne maptiler is the
reference.
But there are perhaps fixes in GDAL gdal2tiles that should be merged
into
maptiler one (Python3 compatibility comes to mind)
Any option would need someone to champion it of course...
IMO, the third option should not be considered at all, since
gdal2tiles is very important tool in gdal and many people (including
me) prefer the script from any GUI out there. I have also seen an
improved version of this script dealing with multiple threads.
My preference would be option 1.
Just my 2c :)
Totally agree: cmd-line faaar more useful than GUI, for production jobs.
Regards,
Zoltan
--
===========================================
Zoltan Szecsei PrGISc [PGP0031]
Geograph (Pty) Ltd.
GIS and Photogrammetric Services
P.O. Box 7, Muizenberg 7950, South Africa.
Mobile: +27-83-6004028
Fax: +27-86-6115323 www.geograph.co.za
===========================================
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
