I just installed OSM Composer, which seems to be a cool tool to generate Garmin hiking maps directly from OSM. I generated a map for a very small area successfully.
However, I am now trying to generate a map for a slightly larger area (maybe 100km x 50km) and after downloading some tiles, I get messages like this
in the log, and after a while the program stalls. Entering the same URL in the browser leads to the same error message, so it is probably not a problem of OSM Composer directly.
Anybody have a clue what is going on here? Does the OSM api count the number of requests from my IP and block after, say, 20 requests in a day? I never had this problem when mapping, though. And, since I was mapping in large areas, I had to reload OSM data into Merkaartor quite a bit and never had this problem.
Thanks for the tip with xapi. Fortunately it supports the same read requests, so I could just change Composer’s api address setting. Now it doesn’t stall anymore. However, now I get 501-Errors for most of the requests:
Ok, just checked, this is a “Not Implemented” error. Which is funny, because the first (of the same type) reads seem to go through. But maybe Composer was reading them from cache and not actually accessing the server? It says XAPI-URL on Composer’s setting page though.