-
Notifications
You must be signed in to change notification settings - Fork 66
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
Shields of Kentucky #119
Merged
Merged
Shields of Kentucky #119
Changes from 4 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
a5c492a
Delimit image name parts by newlines
1ec5 7fe0d0e
Added Kentucky state highway shield
1ec5 c0c18c7
Added AA Highway shield
1ec5 5161ae8
Added Kentucky parkway shield
1ec5 25787bd
Optimized Kentucky parkway SVG
1ec5 25ea00e
Only add name to image name for Kentucky parkways
1ec5 9e750ad
Merge branch 'main' into 1ec5-us-ky
ZeLonewolf 1958e71
Merge branch 'main' into 1ec5-us-ky
ZeLonewolf ad1ac96
Merge branch 'main' into 1ec5-us-ky
1ec5 4a9f106
Map unabbreviated names to Kentucky parkway initialisms
1ec5 f15438e
Only use refsByWayName as fallback
1ec5 2c4d7e0
Documented shield definition properties
1ec5 45a9192
Apply suggestions from code review
1ec5 212942b
Code formatting
1ec5 c3ee2fc
Fixed typo in street name
1ec5 700da78
Added FIXME about abbreviated names
1ec5 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I extracted these initialisms from KYTC’s internal alphanumeric route numbers. Some of them are pretty recognizable, but some like “JC” are more obscure. (It’s from the namesake in the official name.) For the benefit of non-locals who don’t remember the older, more usable shields, I’d be open to changing it to something more intuitive, like “P”, but such ad-hoc abbreviations definitely shouldn’t go into OSM.