Closed jrjdavidson closed 3 years ago
Pls, could you grep the log for tile:2-3-1
? There is too little info about what is done with this tile at the end of the log as it runs in parallel.
Do logs get saved anywhere? I’ve already deleted the dataset to try another method..
On Sat, 4 Sep 2021 at 19:33, Václav Blažek @.***> wrote:
Pls, could you grep the log for tile:2-3-1? There is too little info about what is done with this tile at the end of the log as it runs in parallel.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/melowntech/vts-backend/issues/27#issuecomment-912927264, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALFBMNYRF5TP6NT6XZGTZ3TUAHDU3ANCNFSM5DMM2X5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
No, you need to explicitely specify the log file via --log.file PATH
.
I'm affraid I can't investigate what went wrong without log and/or data.
Goes beyond 180? https://www.dropbox.com/s/xhxjq7gfjfc8zcy/log.txt?dl=0
It's strange, the error message from GDAL is empty (quoted by <>
).
How large is the dataset? Would it be possible to share it?
Also, Ubuntu/Focal?
its a 800 Mb file, I'll upload it somewhere to share - it's the de ferranti 15 arc s world DEM all merged into one tif it's strange because i had already created a resource from that exact file before on our local server (ubuntu 18). Now I'm working on ubuntu 20 on azure.
Thank you.
We've found some problems in our internal SW on focal
with stock GDAL (3.0.4) so we had to switch to newer GDAL (3.2.1) from ubuntugis
repo. Maybe this might be some related problem. I'll try it to run it against both versions once I have the data.
Sent to your @melowntech address
Assuming this is solved by #28
Got this error while running mapproxy-setup-resource on a world DEM dataset. It's strange because I had already processed this specific dataset, had just copied the raw data over and tried to process it again. ( i thought it would be faster than trying to copy gigs of data).