One extreme would be generating three shapefiles - one for areas, one
for linear features, one for POIs. The file for linear features
would then have database columns named type, subtype, user1,
... usern (you must specify the columns when creating the file),
and then you'd convert a secondary
Hi,
I'm currently working on a Perl re-implementation of Osmarender. It
is already almost feature complete; I've made an early announcement on
the [EMAIL PROTECTED] list:
http://lists.openstreetmap.org/pipermail/tilesathome/2008-March/001903.html
While the program generally aims to be 100%
Hi,
I think we should stick with the evenodd rule. It is not that difficult
for users when editing - colour on the right, it is neccesary for
coastlines, and there is nothing to gain by making it unneccesary. If
some renderers don't need the rule, it's going to be much harder to tell
people
Hi,
Do you think this would work? I'm a bit unsure about ignoring the tags
on the relation; ideally these should override tags on the outer way,
if specified (or no?). But since nobody supports that anyway at the
moment, I thought we can leave that for later.
Merkaartor fully supports
On Thu, Mar 13, 2008 at 6:15 PM, Frederik Ramm [EMAIL PROTECTED] wrote:
Hi,
If I understand this correctly, then for a forested island in a lake
you'd
need to have the island twice in the osm data. Once for the hole in the
lake
and once for the forest on the island.
No.
Assuming for
On Friday 14 March 2008 02:15:13 you wrote:
Hi,
If I understand this correctly, then for a forested island in a lake
you'd need to have the island twice in the osm data. Once for the hole in
the lake and once for the forest on the island.
No.
Assuming for a moment that you really
6 matches
Mail list logo
