Hi,
As a 'user' as opposed to a developer, this would get my vote & would
save me firing up the calculator!
'
I've just found the "Tile usage policy" of OSM. They request
downloaders use HTTP Expiry Header or 1 week age per default. We have
to change the value in Viking's code.
http://wi
I've just found the "Tile usage policy" of OSM. They request
downloaders use HTTP Expiry Header or 1 week age per default. We have
to change the value in Viking's code.
http://wiki.openstreetmap.org/wiki/Tile_usage_policy
OK, so in order to be good OSM citizens
change the units to day
2011/5/11 Greg Troxel :
>
> The default for tile age seems to be 30s. This seems way too short.
> While someone actively mapping in OSM might want to reload, it seems
> like map tiles are relatively static over that kind of timescale. I
> have set the tile age to 604800s (1 week). It seems rud
2011/5/13 Robert Norris :
>
>
>>The default for tile age seems to be 30s. This seems way too short.
>>While someone actively mapping in OSM might want to reload, it seems
>>like map tiles are relatively static over that kind of timescale. I
>>have set the tile age to 604800s (1 week). It seems
>The default for tile age seems to be 30s. This seems way too short.
>While someone actively mapping in OSM might want to reload, it seems
>like map tiles are relatively static over that kind of timescale. I
>have set the tile age to 604800s (1 week).It seems rude to OSM to
>recheck tiles m
The default for tile age seems to be 30s. This seems way too short.
While someone actively mapping in OSM might want to reload, it seems
like map tiles are relatively static over that kind of timescale. I
have set the tile age to 604800s (1 week).It seems rude to OSM to
recheck tiles more of
