On Tue, Aug 26, 2008 at 10:51:24PM +0200, Sebastian Spaeth wrote: > I have just committed my final commit and things work fine for me now: > (r10189). I have added code to immediately request the data in stripes > if we know that the tileset is going to be complex. The API was just > failing on complex requests, this is nothing that is new in the client > and was cause by the client.
Here is an example - Handed out to a client of mine a couple minutes
ago:
[#130 0% jobinit] Doing tileset (12,54,113) (area around
84.111461,-175.209961)
[#130 0% Download] Trying smaller slices
[#130 0% Download] No data here (sliced)
[#130 0% Download] Tileset failed: No data here (sliced)
[#130 0% Download] Putting job (12,54,113) back due to 'No data here
(sliced)'
removing job dir/home/flo/tah/tilestmp3/12_54_113_VJXPy
This is actually an empty tile.
And its getting handed out to multiple clients in a row - all of them give
the tile back with NoData.
There needs to be a differentiation between "DB Fail" and "No Data"
Flo
--
Florian Lohoff [EMAIL PROTECTED] +49-171-2280134
Those who would give up a little freedom to get a little
security shall soon have neither - Benjamin Franklin
signature.asc
Description: Digital signature
_______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
