Roadsguy's Comments
Changeset | When | Comment |
---|---|---|
100225737 | over 4 years ago | Heads up: SR 37 won't be signed along I-69 between Martinsville and Indianapolis, so it shouldn't be in the ref tag; only unsigned_ref. This is already in the note:ref tags along this section. It doubly shouldn't be in fut_ref on the closed section because it isn't "future" SR 37 at all. |
99877097 | over 4 years ago | Why do you keep reverting this? The "ramp" in question is the physical freeway mainline. I-83 bears off onto a ramp and the freeway continues, with US 322 immediately merging in. It being signed as a numbered exit doesn't make it physically a ramp. |
100146578 | over 4 years ago | Do you have a source on PA 299 still existing or being reinstated? It was cut back to just the railroad bridge in 2011, and even that is unsigned. I've reverted this change because I was unable to find anything to back it up. It's already tagged correctly with old_ref and unsigned_ref where applicable. |
99276383 | over 4 years ago | The very paragraph you quoted contradicts the edit you just made. This section of freeway (alongside the Brookshire Freeway) *are* connected to the greater freeway network. |
98828888 | over 4 years ago | Please stop demoting random roads from trunk to primary just because you don't think they're "special" enough. Significant length is not the sole deciding factor in whether a road qualifies as trunk. In the case of VA 28, it's a high-speed, limited-access road with expressway-like design (though not a freeway) and which carries significant traffic volumes. By established tagging conventions, it qualifies as trunk. |
98804351 | over 4 years ago | Please do not leave unhelpful changeset comments, and do not keep making the same edits if they are reverted. If you feel strongly enough about something, discuss it in the talk-us mailing list. |
98133184 | over 4 years ago | Do you have a source for these turn restrictions? Having driven this stretch of road, there is no signage indicating these turn restrictions, and to restrict left turns would certainly defeat the purpose of the median breaks that are already mapped. |
98041264 | over 4 years ago | Thanks for contributing! Just an FYI, objects on the ground by themselves are considered layer 0 by default, with tunnels being put on layer -1 and bridges on layer 1. Only when multiple bridges cross on different levels are higher/lower values used (e.g. layer 2, layer -2, etc.). Tagging a bridge with layer 2 and the ground-level road beneath it with layer 1 is unnecessary. |
60920488 | over 4 years ago | I believe I traced it from preliminary construction plans which were at the time available on a project website, though I can't find the website anymore, nor do I seem to have saved the image, unfortunately. A partial screenshot of those plans is in the background of this PDF that I found from a Google image search, though: https://www.roads.maryland.gov/ohd2/GA6465270_Triton_TP.pdf |
96622711 | over 4 years ago | Well movable bridges on even Interstate highways aren't unprecedented, even on relatively new bridges like the Woodrow Wilson Bridge on the Capital Beltway. Even I-278 nearby crosses the Bronx River on a drawbridge. At that point it's less "there's a gap in the freeway here" and more "substandard freeways occasionally have movable bridges on them." At minimum the bridges should be mapped as trunk roads. |