This object is in archive!
Custom tile server: Problem with downloading tiles
Not a Problem
I am hosting my own tile server (mapproxy glued from various sources). Everything seems to be working correctly in the online map view, but I have problems downloading the tiles - the process stops after some time with message:
"""Problem with downloading tiles. Check internet connections and space on SDCard and try again! Error: 2"""
My guess is that Locus stops whenever HTTP 500 response is received, or when the server responds too slowly... Can I make Locus to ignore just a single tile in these cases and continue to download all the other tiles?
Or, perhaps, I should modify my server to respond with a different HTTP code?
The same problem 
Hello Wojciech,
timeout on downloading of tiles should be set to quite common 30 seconds. Which should be enough. Anyway if Locus receive response as 500, then it logically stops as it means some problem on tile server. So main question from my side is : why you server returns error 500?
Hello Wojciech,
timeout on downloading of tiles should be set to quite common 30 seconds. Which should be enough. Anyway if Locus receive response as 500, then it logically stops as it means some problem on tile server. So main question from my side is : why you server returns error 500?
Once in a thausand tiles it returns HTTP 500 - probably because of a bug somewhere in the code. However, it is not my own code, I am only using it to serve the map (it's a mapping proxy, written in Python). Of course, I could try to find and fix the bug, but that would be a hard task... Instead of fixing the bug itself, it would be much easier for me, for example, to include a special header for Locus to process, or alter the status code itself. For example, would returning HTTP 404 instead of HTTP 500 fix the issue?
Once in a thausand tiles it returns HTTP 500 - probably because of a bug somewhere in the code. However, it is not my own code, I am only using it to serve the map (it's a mapping proxy, written in Python). Of course, I could try to find and fix the bug, but that would be a hard task... Instead of fixing the bug itself, it would be much easier for me, for example, to include a special header for Locus to process, or alter the status code itself. For example, would returning HTTP 404 instead of HTTP 500 fix the issue?
Understand, hmm if you really wants to fix it in this way, probably only solution is to return 204 (no content) or 404 (not found - as you suggested). Then Locus should use empty tile and continue in download.
Understand, hmm if you really wants to fix it in this way, probably only solution is to return 204 (no content) or 404 (not found - as you suggested). Then Locus should use empty tile and continue in download.
Thank you. :)
PS. It would be nice to include this information in a short chapter for server implementors in your custom maps docs. http://docs.locusmap.eu/doku.php?id=manual:advanced:customization:online_maps
Thank you. :)
PS. It would be nice to include this information in a short chapter for server implementors in your custom maps docs. http://docs.locusmap.eu/doku.php?id=manual:advanced:customization:online_maps
You are welcome.
PS: I believe it is not necessary. Quite common is that server do not return error messages without reason ;).
You are welcome.
PS: I believe it is not necessary. Quite common is that server do not return error messages without reason ;).
Replies have been locked on this page!