Closed gwacker closed 8 years ago
I think I figured this out. I renamed and added your gdal2tiles.py to a 64-bit version of OSGeo4W (wanted to ensure other process would not be altered in any way) and called it using OSGeo4W.bat
When I added the same file to the 32-bit version of OSGeo4W and called everything the exact same way it worked exactly as expected.
I'm attempting to move a panorama viewer from Openlayers 2 to Leaflet and tried out your modified version of gdal2tiles.
It works great on 95% of the images I give it but a handful return tiles like this link: http://dev.gregwacker.com/#/photos/panorama/clat_adams_bicentennial_park_pano_2__6_photos_.jpg
The original image I tried to tile can be found here: http://dev.gregwacker.com/photoalbums/ThePanoramas/fullsize/clat_adams_bicentennial_park_pano_2__6_photos_.jpg
The vanilla gdal2tiles output can be seen here: http://www.gregwacker.com/photos/_panoramasViewer.cfm?panoID=232
Any ideas on why the leaflet version chokes on some images like the one above? The setting are identical with the exception of the Leaflet switch.
Another alternative since I'm not worried about x,y maker coordinates is to use the TMS tiles from vanilla gdal2iles with TMS set to true in leaflet, but I can't quite figure out the math for the bounds. Would you have any interest in providing an alternate rastercoords.js for TMS tiles?
Thanks for sharing the work you've done with gdal2tiles-leaflet to date.