Opened 12 years ago

Closed 6 years ago

#667 closed enhancement (fixed)

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

Reported by: nhoffm Owned by: mapnik-team@…
Priority: minor Milestone:
Component: mapnik Version:
Keywords: Cc:


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.

Change History (11)

comment:1 Changed 12 years ago by Tom Hughes

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).

comment:2 Changed 12 years ago by Tom Hughes

Owner: changed from Tom Hughes to steve8@…

Any ideas how best to handle this Steve?

comment:3 Changed 12 years ago by nhoffm

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

comment:4 Changed 11 years ago by Vid the Kid

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?)

comment:5 Changed 11 years ago by Ldp

Owner: changed from steve8@… to mapnik-team@…

comment:6 Changed 10 years ago by Ldp

Also see #2864

comment:7 Changed 8 years ago by blahedo

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: I-172 south, 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.

comment:8 Changed 7 years ago by DENelson83

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.

comment:9 Changed 6 years ago by math1985

Summary: Multiple "ref"s for a road not rendered by mapnik[Roads] Multiple "ref"s for a road not rendered by mapnik

comment:10 Changed 6 years ago by math1985

Summary: [Roads] Multiple "ref"s for a road not rendered by mapnik[roads] Multiple "ref"s for a road not rendered by mapnik

comment:11 Changed 6 years ago by math1985

Resolution: fixed
Status: newclosed

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

Note: See TracTickets for help on using tickets.