On Wed, Sep 23, 2020 at 6:22 PM Andy Townsend <ajt1...@gmail.com> wrote:
> On 24/09/2020 00:00, Paul Johnson wrote: > > > > On Wed, Sep 23, 2020 at 5:56 PM Andy Townsend <ajt1...@gmail.com> wrote: > >> >> On 23/09/2020 23:01, Paul Johnson wrote: >> >> >> >> On Wed, Sep 23, 2020 at 4:37 PM stevea <stevea...@softworkers.com> wrote: >> >>> Paul Johnson <ba...@ursamundi.org> wrote: >>> >> > 2. Tagging route information on ways. It's about a decade too long at >>> this point for ref=* on a way to be completely disconnected from the entity >>> the tag applies to: That's why route relations exist. Biggest problem >>> child on this at the moment: OSM's own tilesets. Let's drop rendering for >>> ref=* on ways and just render the route relations already, this and >>> multipolygons are why relations came to exist in the first place. >>> >>> Yes, 100% agreement. I think this is simply pure inertia (the kind that >>> says "broken process") on the part of renderers. >>> >>> Can anybody (renderer authors included, maybe even especially) are >>> welcome to offer reasons why "the old machinery" remains in place? Are >>> there legacy use cases that remain unclear to the wider community? Please >>> tell us here, if so. >>> >> The US is unusual in that it doesn't have a single ref per section of >> road. Most places in OSM map what they see on the ground, and the current >> OSM Carto rendering works just fine for them >> > Right up until there's more than one kind of route on the way. > > No-one's disputing that this is a major problem for mappers in the US - > I'm just saying that it's really not a major problem in most other places. > That doesn't make it any less of a problem in the US but does help to > explain why people elsewhere seem not to see it as a problem. > I don't mean just route=road, literally any other route.
_______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
