Re: [OSM-dev] Planet change tile expiry list service

2016-09-01 Thread Martin Koppenhoefer 


sent from a phone

> Il giorno 01 set 2016, alle ore 11:25, Andy Allan  ha 
> scritto:
> 
> It's not really something that should be relied on, since there's no
> "one true list" of expired tiles.


it also depends on the features you are showing in your rendering and at which 
zoom levels.


cheers,
Martin 
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Planet change tile expiry list service

2016-09-01 Thread Yves 
>> which list would you like? 
Oh me myself I need for opensnowmap all ski pistes,  ways and relations down to 
nodes,  plus aerialway,  including tiles w/o nodes but between two distant 
nodes of a lift. 
But that specialized expiry I'll probably keep it to myself. 
The OpenStreetMap. org output of one of the two methods you suggest would be a 
good starting point that could be supplemented with specialized expiry as 
needed. 
Yves

Le 1 septembre 2016 11:25:27 GMT+02:00, Andy Allan  a 
écrit :
>On 1 September 2016 at 09:25, Yves  wrote:
>> Along with minutely diffs, I wonder if expired tiles lists would be
>> something to be shared: this is something each tile server is doing
>by
>> itself by now, and seems a waste in ressources.
>
>It's not really something that should be relied on, since there's no
>"one true list" of expired tiles. For example, the osm.org tileservers
>ignore relation expiry entirely. Other servers might expire relations
>only when certain tags are changed (little point in expiring all of
>germany when an unrendered tag on an admin boundary changes). Some
>tileservers use the osm2pgsql output. With large polygons, only the
>exterior is expired, but  different operators will have different
>ideas as to how large a "large" polygon is, or they may want to expire
>the interior too.
>
>Or to put it a different way - which list would you like? The one
>generated by osm2pgsql, or the one generated by
>https://github.com/openstreetmap/chef/blob/6db231309db4c58f4264beab8a72fd46fdd0d01d/cookbooks/tile/files/default/ruby/expire.rb
>? Which is "right"?
>
>Thanks,
>Andy

-- 
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Planet change tile expiry list service

2016-09-01 Thread Andy Allan 
On 1 September 2016 at 09:25, Yves  wrote:
> Along with minutely diffs, I wonder if expired tiles lists would be
> something to be shared: this is something each tile server is doing by
> itself by now, and seems a waste in ressources.

It's not really something that should be relied on, since there's no
"one true list" of expired tiles. For example, the osm.org tileservers
ignore relation expiry entirely. Other servers might expire relations
only when certain tags are changed (little point in expiring all of
germany when an unrendered tag on an admin boundary changes). Some
tileservers use the osm2pgsql output. With large polygons, only the
exterior is expired, but  different operators will have different
ideas as to how large a "large" polygon is, or they may want to expire
the interior too.

Or to put it a different way - which list would you like? The one
generated by osm2pgsql, or the one generated by
https://github.com/openstreetmap/chef/blob/6db231309db4c58f4264beab8a72fd46fdd0d01d/cookbooks/tile/files/default/ruby/expire.rb
? Which is "right"?

Thanks,
Andy

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Planet change tile expiry list service

2016-09-01 Thread Yves 
Along with minutely diffs, I wonder if  expired tiles lists would be something 
to be shared: this is something each tile server is doing by itself by now,  
and seems a waste in ressources. 
Or is there already such a service somewhere? 
Yves 
-- 
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev