You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
On the plus side, I don't see any error rounded rectangles for Interstates or U.S. Routes, but this may be a consequence of my recent post-"redaction" once-over that removed most spaces after semicolons. Keep up the good work; showing overlaps is important. And four-character routes are now displayed (not for county roads though?).
I'm starting to think perhaps a prefix that has nothing to do with the actual abbreviation (state or route type) may be best, but that's not what trac is for.
Reporter: NE2
[Submitted to the original trac issue database at 10.47pm, Monday, 10th September 2012]
I see that you're experimenting with two-route overlaps as higher zooms. But there are some issues with the second route being in a circle rather than the correct shield. For example:
http://www.openstreetmap.org/?lat=33.166&lon=-81.147&zoom=9&layers=Q 301 and 601 are U.S. Routes
http://www.openstreetmap.org/?lat=41.752&lon=-85.094&zoom=9&layers=Q 90 is an Interstate
The issue may be related to refs having a space after the semicolon.
Other issues with shields:
SR * (State Route/Road) is now being rendered with a county rectangle rather than the correct state circle: http://www.openstreetmap.org/?lat=40.238&lon=-82.361&zoom=9&layers=Q
Louisiana has parishes rather than counties. So PR * should be treated like CR *. (But Puerto Rico should be cut out of this rule, I suppose.)
"Historic" is not being recognized as a banner: http://www.openstreetmap.org/?lat=33.41594&lon=-117.14475&zoom=16&layers=Q The US 395 shields are on what is tagged ref=US 395 HISTORIC.
The text was updated successfully, but these errors were encountered: