Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nebraska Secondary Highway Signage #519

Open
StretchLongfellow opened this issue Jul 28, 2022 · 3 comments
Open

Nebraska Secondary Highway Signage #519

StretchLongfellow opened this issue Jul 28, 2022 · 3 comments
Labels

Comments

@StretchLongfellow
Copy link

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

@1ec5
Copy link
Member

1ec5 commented Jul 29, 2022

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.

@StretchLongfellow
Copy link
Author

So I noticed that #141 is closed; what is the next step for this particular issue?

@1ec5
Copy link
Member

1ec5 commented Mar 8, 2023

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.

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

No branches or pull requests

3 participants