[OSM-talk] Mapnik tileset coherency issues
Patrick Weber
p.weber at ucl.ac.uk
Thu Oct 18 09:59:25 BST 2007
I think all I meant is that is *the map* that greets you when you go to
www.openstreetmap.org. For any user who just heard of OSM and goes to
the webpage, that's what they see first by default. I dont want to
belittle any other tilesets by that comment.
80n wrote:
> On 10/18/07, *Patrick Weber* <p.weber at ucl.ac.uk
> <mailto:p.weber at ucl.ac.uk>> wrote:
>
>
> As I see it, Mapnik is the "production" tileset, the official face of
> OSM, versus OsmaRender T at H is for map editors who want to check their
> updates and people wanting the latest data. My point is then, that
> Mapnik should be an attempt to present a coherent view of the OSM
> data.
> Thats where I think the updating artefacts become an issue.
>
> I don't think there is really such a notion as the production or
> official OSM map, although these are the only two rendered tilesets
> that are hosted by OSMs servers.
>
> tiles at home is a full function slippy map - it is not aimed at map
> editors - and is no more or less official than Mapnik. You might be
> confusing it with the maplint layer which is for map editors and is
> produced as a by product of the tiles at home process.
>
> The API is the definitive dataset. Everything else is a derivative,
> and all derivatives have different characteristics of completeness,
> consistency and currency. Even planet.osm can be inconsistent - ways
> added while it is being generated may reference non-existent nodes.
>
> The Mapnik based and tiles at home slippy maps are both fairly complete
> and comprehensive, but neither shows *all* the data. Other specialist
> maps are starting to show up - like Gravitystorm's cycle map
> http://www.gravitystorm.co.uk/osm/ - which accentuates cycle routes.
>
> 80n
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: p.weber.vcf
Type: text/x-vcard
Size: 282 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20071018/da1d4682/attachment.vcf>
More information about the talk
mailing list