A better data format for
rendering would contain only point of interest nodes, with ways
represented as polylines of points, with no need for the client to look up
the coordinates of the way's constituent nodes by ID.
What you're talking for is a xml/json frontend for a postgis-db. The
On Mon, 26 Oct 2009 13:05:07 +0100, Peter Körner osm-li...@mazdermind.de
wrote:
A better data format for
rendering would contain only point of interest nodes, with ways
represented as polylines of points, with no need for the client to look
up
the coordinates of the way's constituent nodes
Looks interesting but only for high zoom-levels.
What queries can be supported to e.g. render a map of the world?
That would at least require all coastlines but not in full resolution.
This is only true for the coastlines, as mapnik is doing the same
(coastlines from shapefile, everything
This is directly possible within DBSlayer.
Stefan
Op 26 okt 2009 om 13:05 heeft Peter Körner osm-li...@mazdermind.de
het volgende geschreven:\
A better data format for
rendering would contain only point of interest nodes, with ways
represented as polylines of points, with no need for the
A better data format for
rendering would contain only point of interest nodes, with ways
represented as polylines of points, with no need for the client to
look
up
the coordinates of the way's constituent nodes by ID.
What you're talking for is a xml/json frontend for a postgis-db. The
On Mon, Oct 26, 2009 at 1:24 PM, Peter Körner osm-li...@mazdermind.de wrote:
Looks interesting but only for high zoom-levels.
What queries can be supported to e.g. render a map of the world?
That would at least require all coastlines but not in full resolution.
This is only true for the
On Tuesday 27 October 2009 06:01:05 Marcus Wolschon wrote:
I wasn´t aware that mapnik did not actually render the coastlines
we have in the database.
It does render the OSM coastlines. It's just that the coastline data goes
through a different preprocessor.
--
m.v.g.,
Cartinus
7 matches
Mail list logo
