[Tilesathome] real NoData tiles Was: either nodata or Forked render failure

Łukasz Jernaś deejay1 at srem.org
Wed Aug 27 09:20:14 BST 2008


On Wed, Aug 27, 2008 at 9:52 AM, spaetz <osm at sspaeth.de> wrote:
> On Wed, Aug 27, 2008 at 09:28:25AM +0200, Florian Lohoff wrote:
>> Here is an example - Handed out to a client of mine a couple minutes
>> ago:
>
>> [#130   0% Download] Putting job (12,54,113) back due to 'No data here (sliced)'
>> This is actually an empty tile.
>
> Yes, No Data here really means the API did not respond at all, or it threw an error while responding. So its unfortunate, but the client is acting absolutely correct here.

IMHO this could be useful. BTW is the API server differentiating
between clients that download data? My request from the client always
end up with an error 500, but when I copy the URL to Firefox it opens
correctly every time..

-- 
DeeJay1




More information about the Tilesathome mailing list