Tobias Knerr wrote:
/ Malcolm Herring wrote:
// My other wish is that disjunct outers be dis-allowed. Where multiple
// complete areas need to be associated, then this is the proper use of
// relations.
/
+1
/ Why? How would you draw an administrative district with an exclave?
/
A relation
Hi,
if you have followed recent developments then you know that both
Mapbox and Andy Allan have moved, or are moving, away from producing
raster tiles the old fashioned way, to producing raster tiles on-the-fly
from pre-computed vector tiles.
For the time being (i.e. until we have reached a
I'd be very interested to know what formats were being considered for
the vector tiles.
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
Compared to the classic mod_tile/renderd architecture, the benefits of
vector tiles seems to be:
- easier to render different stylesheets (including retina, png+jpeg, etc)
- much less metatiles to maintain (2 or 3 levels of vector tiles coming
from the database instead of 18+)
- allows client side
Frederik Ramm frede...@remote.org wrote:
I'd be interested to hear your opinions on this.
IMO one of the big advantages of the mod_tile/tirex aproach is that it is in
not bound to use mapnik as a renderer at all. Using tirex it is currently
possible to use mapserver or any other renderer which
Hi,
in the OpenScienceMap project we actually use Tirex in our vector-tiles
stack. For this I wrote a simple Tirex backend that can render any kind of
TileStache layers[1].
I can definitely recommend Tirex for renderqueue management, though I
havent looked what is provided by the Tilelive
I just wanted to add my excitement for the growth of vector tile work with
OpenStreetMap. Most of the mapping industry is moving to vector tiles; the
big mobile maps apps like Google's and Apple's are vector based, as are
many newer browser maps like the Google Maps redesign. Offline maps also
7 matches
Mail list logo
