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

manual/maintenance: updates for redesignations/merges etc #811

Open
yakra opened this issue Jan 27, 2025 · 0 comments
Open

manual/maintenance: updates for redesignations/merges etc #811

yakra opened this issue Jan 27, 2025 · 0 comments
Labels
Low priority manual Issues related to the TM Contributor manual

Comments

@yakra
Copy link
Contributor

yakra commented Jan 27, 2025

I don't believe (without looking) this is codified in the manual, but:
When a route is deleted due to being renumbered/renamed/redesigated as, or merged into, another route,
There's a longstanding practice among some of us to, rather than leave the root field blank, use the new route's root. (Often, this new route will have the old route as an AltRouteName.)
For example,
2019-10-12;(USA) New York;I-895;ny.ny895;Renamed NY 895.

Could maybe codify this in the manual & encourage people to do it more.
Maybe make it optional? Required?
Worth some discussion in the forum before going ahead with a manual change. If nothing else, having the discussion could make more people aware the option's available.

@yakra yakra added Low priority manual Issues related to the TM Contributor manual labels Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Low priority manual Issues related to the TM Contributor manual
Projects
None yet
Development

No branches or pull requests

1 participant