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
I don't know how this would be programmed, but on most print maps of Nebraska, the secondary state highways (Links, Spurs, and Recreation Roads) are designated with a letter prefix instead of a banner above the shield. For example, NE 55X Link would appear in a Nebraska shield trapezoid as L55X (some put a hyphen, as L-55X). NE 55C Spur would be S55C, and NE 55T Rec would be R55T.
This would be another case for #141 – concatenating a string based on network rather than implementing the kind of parsing that was seen as problematic in that issue.
The next step would probably be to implement a mechanism for transforming the shield’s contents as part of the shield definition – generic enough to handle some other cases that may need similar treatment, but only for presentational purposes, for idiosyncrasies on shields that don’t reflect what people consider the actual route number to be, not as an escape hatch for poorly tagged route relations. See the discussion in #676 (comment) for example.
I don't know how this would be programmed, but on most print maps of Nebraska, the secondary state highways (Links, Spurs, and Recreation Roads) are designated with a letter prefix instead of a banner above the shield. For example, NE 55X Link would appear in a Nebraska shield trapezoid as L55X (some put a hyphen, as L-55X). NE 55C Spur would be S55C, and NE 55T Rec would be R55T.
Slack discussion: https://osmus.slack.com/archives/C01V02K52UX/p1658969589352439
The text was updated successfully, but these errors were encountered: