[OSM-talk] Osmarender based slippy map
David Earl
david at frankieandshadow.com
Thu Nov 23 23:32:23 GMT 2006
> -----Original Message-----
> From: talk-bounces at openstreetmap.org
> [mailto:talk-bounces at openstreetmap.org]On Behalf Of Nick Whitelegg
> Sent: 23 November 2006 17:40
> To: talk at openstreetmap.org
> Subject: Re: [OSM-talk] Osmarender based slippy map
>
>
> >The renderer can be blamed for that. At no point has it been specified
> >that the segments must be in a specific order. If the renderer is making
> >assumptions about the data format that are so blatantly incorrect then
> >there is something wrong with it.
>
> Surely though it is better to specify that the segments *do* have
> to be in
> a specific order, to avoid undue complexity in making sense of them?
> That's arguably another argument for superways: branched streets can be
> dealt with using one way for each branch, then a superway to group the
> whole lot together as a street entity.
>
> A simpler solution still would be to remove segments altogether and have
> nodes, ways and super-ways.
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
I think this is unnecessary. The renderer could make sense of these things,
and it's *much* easier for it to be done in an atomated fashion than to have
the human inputter worry about them. Of course if JOSM (etc.) automatically
split up branched, disordered, commonly-named-but-separate, looped etc ways
into superways that would be fine, but automation of this is necessary
somewhere along the line. Making the map creation absolutely as simple as
possible with as few assumptions as possible is crucial if it is going to
work with a wider group of participants to whom these "rules" just look
arbitrary.
So whether it is done at the input, database upload, or renderer stage, I
think it absolutely has to be an automatic thing.
David
More information about the talk
mailing list