[roads] Multiple "ref"s for a road not rendered by mapnik #667
Comments
Author: tom[at]compton.nu 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). |
Author: tom[at]compton.nu Any ideas how best to handle this Steve? |
Author: nhoffm Perhaps something like "alternating" (if possible) could be used for ref/int_ref too. |
Author: Vid the Kid I have some suggestions:
|
Author: Ldp Also see #2864 |
Author: 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: |
Author: 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. |
Author: math1985 This has been resolved in the meanwhile, but see also #2864. |
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.
The text was updated successfully, but these errors were encountered: