-
Notifications
You must be signed in to change notification settings - Fork 59
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
Tennessee shields #303
Comments
I think this wiki page still describes the current and historical tagging situation accurately. The My experience working on #190 has softened me to a third approach of splitting out |
I agree using |
I've been driving in Tennessee for the past few days and have seen both shields in use. There doesn't seem to be much rhyme or reason to where one or the other is used, but I guess the triangles are theoretically on less important sections. This seems like a similar situation to what we have in Vermont (described in #268) with sections of state numbered routes using a different shield where they are town maintained. The current plan (already complete?) in VT is to split off these town maintained sections into separate route relations with |
Well, ideally, the tagging would be clearly defined and they wouldn't have to rely on wildcard matching. I like the guidelines you've presented with For version 1 I guess we could go forward with rendering |
I would not be opposed to putting the burden on a future Tennessee mapping community to adding more complexity to their route network tagging in order to achieve a more nuanced rendering. |
The biggest problem currently is that the existing tagging conventions have been muddled by folks unaware of the existence of two separate networks. So any migration to a new tagging convention will require digging through feature histories across splits and merges or, more likely, taking a fresh look at street-level imagery or the same TDOT source that NE2 used. In the meantime, a binary classification that assumes primary unless known to be secondary won’t be as usable in Tennessee as it is with Vermont’s town highways, because the secondary route segments are far more numerous and lengthier than the primary route segments. |
Changeset 120,695,565 refactors one state route into child route relations along three axes:
Not all state routes will need this level of complexity. Judging from Wikipedia’s list, 86 state routes are a mix of primary and secondary segments. However, most of them are wholly or partially unsigned; many unsigned segments have been excluded from route relations. The separate relations per cardinal direction aren’t strictly necessary in a first pass. |
If someone is working on this and requires a map data update, please let me know. |
Let's find at least one Tennessee state route with signed primary and secondary portions, and map it before we go through with a data update. As a side note, I've mapped a sampling of Texas county roads and I'd love to have them show up so I can work on their shields. |
Route 62 was one I drove on recently where I'm pretty sure I saw both shield types. |
@zekefarwell is currently conducting a field survey to confirm that the variety of our highway signage is, in fact, insane. |
Changeset 120,738,589 refactors SR 394 into child relations for primary versus secondary segments (both signposted) and eastbound versus westbound. Changeset 120,734,828 refactors SR 283 into child relations for primary versus secondary segments (both signposted). |
@ZeLonewolf I think we're ready for that data update now. |
I should be able to do it this week. I need three hours when I can babysit an AWS instance :-D |
Here’s the full list of
|
Any particular reasoning for |
If I’m not mistaken, banner parts like Otherwise, the predominant practice globally uses snake_case for non-geographic, non-banner parts of I noticed |
Makes sense. Seems like we're trying to use proper case only for actual proper names. I guess my aiming for consitency was futile. May as well leave the |
Tennessee has one "network" of state highways, though signage can shift between either of two shields depending on a segment's importance in the road hierarchy. Route numbers can have up to 3 digits.
Existing relations are tagged with
network=US:TN
, conflating both shields into one network. There has been some previous discussion towards new network values that correspond to shield appearance, but none so far have produced the change in tagging guidelines necessary for renderers to support Tennessee highway shields.Primary shield:
Secondary shield:
The text was updated successfully, but these errors were encountered: