Issues with making my own TMS for JOSM

Help and support
1

I’ve made a simple server that receives TMS queries from JOSM and responds with PNG tiles.

I add the layer to JOSM, and it seesms to work – the tiles are loaded and displayed correctly, matching the terrain. But in the background JOSM seems to bombard my server with lower-level tiles requests. I opened at level ~13, but I see queries for deeper tiles, and the server is overloaded, responding like more than a minute after I turned the tiles on (I hadn’t patience to wait.)

GET 14/6608/8555
GET 14/6609/8556
GET 14/6609/8562
GET 13/3304/4280
GET 13/3304/4278
GET 13/3304/4279
GET 14/6609/8555
GET 12/1652/2139
GET 11/826/1069
GET 12/1652/2140
GET 10/413/535
GET 11/826/1070
GET 10/413/534
GET 14/6608/8558
GET 14/6608/8557
GET 14/6608/8560

The layer in JOSM has 2 settings: Autoload tiles, and Autozoom. When I turn one of these off, the flood stops, but JOSM stops to show the proper tiles at current zoom.

Any suggestion, how to stop the requests flood?

2

sounds like something worth reporting as a bug to JOSM developers, if not reported already?

1 Like
3

Oh, I found there page with tickets, no idea how to search it.

For check, I configured the tile service in QGIS, and it works correctly, dowloading only the required layer.

Double-checking, I saw JOSM dowload some tiles more than once. Definitely a bug.

4

for example with site: prefix in regular web search - see cycleway site:josm.openstreetmap.de/ticket at DuckDuckGo

1 Like
5

News from me: I updated JOSM, it had the same issue, I switched to QGIS, improved the server code, and tested again on JOSM. It turned out JOSM duplicates the queries only if it got code 500 or 404 (which my server sends if there’s no data). I think the reason was the server was sending 500s very often, and JOSM re-queried them, causing hickups.

1 Like