Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

[roads] Multiple "ref"s for a road not rendered by mapnik #667

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 8 comments
Closed

Comments

@openstreetmap-trac
Copy link

Reporter: nhoffm
[Submitted to the original trac issue database at 8.51pm, Wednesday, 6th February 2008]

Per FAQ a road with multiple refs should be tagged k="ref" v="B76;B202". Osmarender treats the value as one string (which could possibly be improved. But Mapnik doesn't render the refs at all. Perhaps the ref-numbers could be shown alternating or one above the other.

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 9.57pm, Wednesday, 6th February 2008]

Well just because the FAQ says it doesn't mean it's right ;-)

Part of the problem is the multiple refs is not a situation that arises in the UK and most of the people working on the rendering are in the UK so don't run into these things.

That said, I'm not at all sure how easy this is to fix in mapnik (the reason it isn't showing the refs is that there is a limit to how long a ref mapnik can render).

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 9.58pm, Wednesday, 6th February 2008]

Any ideas how best to handle this Steve?

@openstreetmap-trac
Copy link
Author

Author: nhoffm
[Added to the original trac issue at 5.28pm, Thursday, 7th February 2008]

Perhaps something like "alternating" (if possible) could be used for ref/int_ref too.

@openstreetmap-trac
Copy link
Author

Author: Vid the Kid
[Added to the original trac issue at 8.31am, Thursday, 30th July 2009]

I have some suggestions:

  • Replace a semicolon (or semicolon-space combination) with a newline and render multiple refs on multiple lines in the same box

  • Use information from route relations to render a separate label for each ref (like OpenCycleMap)

@openstreetmap-trac
Copy link
Author

Author: Ldp
[Added to the original trac issue at 1.51pm, Friday, 11th June 2010]

Also see #2864

@openstreetmap-trac
Copy link
Author

Author: blahedo
[Added to the original trac issue at 5.55am, Monday, 26th November 2012]

As a first approximation (that should be easy to implement), would it be possible to at least render the first label in the list? That is, treat a semicolon in a ref=* tag as a terminator? It's suboptimal, but right now there are regionally-major interstates (motorways) that have no labels at all at any zoom level, which is a problem.

For instance, in western Illinois, I-172 for its entire length (overlaps IL-110), and I-72 west of Decatur (overlaps US-36). Here are (portions of) those ways:
[http://www.openstreetmap.org/browse/way/85266056 I-172 south],
[http://www.openstreetmap.org/browse/way/146584278 I-72 west (portion)]. Both are part of relations that appear to be correctly separately tagged, but the renderer isn't using that info either. It would be nice if both "I 72" and "US 36" showed up on the rendered map, but if only "I 72" did that would catch at least 90% of the major use cases.

@openstreetmap-trac
Copy link
Author

Author: DENelson83
[Added to the original trac issue at 10.52pm, Sunday, 17th February 2013]

Why not use a tagging scheme like "ref:n=a", where 'n' is a whole number, and 'a' is a highway designation, e.g. "ref:1=I 72" and "ref:2=US 36"? This way, you can specify as many highway numbers as you want.

@openstreetmap-trac
Copy link
Author

Author: math1985
[Added to the original trac issue at 11.18pm, Monday, 21st April 2014]

This has been resolved in the meanwhile, but see also #2864.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant