OpenStreetMap
Baloo Uriza's Comments
| Changeset | When | Comment |
|---|---|---|
| 55397514 | almost 8 years ago | It's also intentionally flexible to deal with localisms, like calling this loop as "Creek Turnpike" even when it's officially not known as that, but frequently colloquially known as that to a very high degree. Or to internationalize, like Mission Street being renderable as Yugheea Yusten in Sapulpa if your data consumer is localized with a Mvskoke language preference if you wanted to navigate in Mvskoke, for example. |
| 55397514 | almost 8 years ago | The data is intentionally flexible to be able to deal with situations exactly as messy as this. |
| 55397514 | almost 8 years ago | Just like, using the above example, you were supposed to get off at Elm, without being aware of destination tagging, you'd get "In 250 meters, turn slightly right." With destination tagging, if it's tagged with destionation:street=Elm Place, then you'd get "In 250 meters, turn slightly right, towards Elm Place." |
| 55397514 | almost 8 years ago | As for the guide sign for "Creek Turnpike" as a destination, that would be a good value for "destinaton:street=*" on the ramp it's referring to, as these are often the last signs to be updated. That way a data consumer aware of these tags could say something like "In 250 meters, turn right onto OK 364 West towards Creek Turnpike" and then once it's up on 364, "Continue on OK 364, Liberty Parkway, for 7 kilometers". |
| 55397514 | almost 8 years ago | The confirmation signs say Liberty Parkway. The approach signs list destinations, which IIRC, are tagged at the major ramps, though not the minor ones, since the intervening ramps are inconsistently signed. There is no name signage at any ramp in Broken Arrow, just generically "Turnpike East/Westbound" between Olive and County Line Roads, and "Turnpike North/Southbound" between New Orleans and Omaha Streets, on an east-west route, signed as east-west once you're on it, for example. I don't think anybody's really arguing that the street name sign in that case is what's accurate at all. Only other signage on that section are either OTA shields or OK 364 shields, and shields are indicative of routes, which are mapped as relations. Both of these are mapped to OSM convention as relations already. All of the information is there, at this point, which the data consumer uses is up to the data consumer, not the map data. |
| 55394832 | almost 8 years ago | Hello!
|
| 55390868 | almost 8 years ago | Hello!
|
| 55390528 | almost 8 years ago | Hello!
|
| 55397514 | almost 8 years ago | reg_name would work, too. Creek Turnpike isn't a name anyone other than locals and road geeks are going to recognize for this strip based on available signage. However, keep in mind that people are looking for reassurance after an interchange. Entering from a midpoint, yeah, nobody really expects a street name for an onramp unless you are used to driving in LA, and not always even then. The first signs you see from the only two major junctions after entering are for OK 364, Liberty Parkway, or both, not Creek Turnpike at this point. People not from the area are going to go for the posted name or the route number, and might not necessarily be aware of another name even if you know, and I know, when someone says Creek Turnpike, they mean the whole route, whether we're talking the original Creek Turnpike between Riverside and 169, the Western Extension between 44 and Riverside, or the Liberty Parkway through BA or the Eastern Extension from the Muskogee Turnpike to the Rogers Turnpike. Even when it was Liberty Parkway with a Creek Turnpike shield, unless you're used to spotting the Flyspeck 3pt font used on the shields, if you're new to the area (as I was the first time I drove it), you see Liberty Parkway and an OTA shield with something (what did it say?) on it, you're immediately thinking, "I screwed up" not "Oh, good, I am on the right road." |
| 55390366 | almost 8 years ago | Hello!
|
| 55390251 | almost 8 years ago | Hello!
|
| 55397370 | almost 8 years ago | This changeset has been reverted fully or in part by changeset/55397820 where the changeset comment is: Hold off on editing this for a minute, let's keep it consistent while it's discussed in changeset/55397514 |
| 55397370 | almost 8 years ago | Hello!
|
| 55397514 | almost 8 years ago | I think an accurate characterization of the situation is that highways and routes get renamed regularly by legislative and executive fiat, and OklaDOT tends to ignore the naming in favor of the local nicknames. I think you have a strong argument for changing alt_name to loc_name as Creek Turnpike, however, since loc_name is for the informal name that locals call it. How about loc_name=Creek Turnpike and name=Liberty Parkway? I think this reflects the local custom and the ground truth more accurately than the previous agreement based on the legislation that named it. |
| 55367616 | almost 8 years ago | There is signage westbound. It's at node/4884335483 and at node/4884339565 , plus the cited doc in the source notes also supports this. |
| 55390192 | almost 8 years ago | Hello!
|
| 55397514 | almost 8 years ago | There is signage westbound. It's at node/4884335483 I'll agree that Liberty Parkway is the name of this section of road, and Creek Turnpike is the name of the route, but ignoring the Liberty Parkway name and calling it just Creek Turnpike is factually incorrect as it is on the ground. |
| 55369254 | almost 8 years ago | Hello!
|
| 55369238 | almost 8 years ago | Hello!
|
| 55369225 | almost 8 years ago | Hello!
|