Stretch Longfellow's Comments
| Changeset | When | Comment |
|---|---|---|
| 134903406 | over 2 years ago | Got it fixed, thanks! |
| 132891813 | almost 3 years ago | Yup, must have slipped when assigning route relation and hit the county boundary instead. Should be fixed. |
| 132633160 | almost 3 years ago | You can use Overpass to scan for broken relations. Wireguy is also an active member who excels at ensuring relations are working (they've caught a few of my oopsies); you could ask them for advice as well on either relations or using Overpass (I haven't used it much myself). |
| 132633160 | almost 3 years ago | Be careful when working with relations; you broke some. |
| 131893211 | almost 3 years ago | This edit seems to be made in error. US Highways do not actually pass through Yellowstone (yes, it's weird); they terminate at the gate and resume on the other side. Also, hyphens are never used in ref tags. Please revert. Thank you! |
| 127839016 | almost 3 years ago | I think I fixed it; let me know if that didn't work. There were some construction edits in that area recently so I'm not entirely sure what went wrong. |
| 131392522 | almost 3 years ago | ...Yep, I knew that. And forgot. Thanks for catching that! |
| 130563387 | almost 3 years ago | Why did you divide this? It's not divided by a median. In addition, you left some knobs of roads and broke some relations. Please be more careful in the future. |
| 130307565 | almost 3 years ago | Why did you revery these trunk roads to primary? under the new classification standards, trunks are supposed to form a complete network, avoiding spurs when possible. |
| 130485806 | almost 3 years ago | The interchange with Homestead Expwy was not correctly done. The way you have done this, the trunk designation randomly stops, as opposed to the prior configuration where it led directly into the onramp. Having the junction between the secondary road and the trunk road occur at a bridge gap furthermore complicates the situation because it causes the secondary road visually to get priority. In addition, turn lanes that are not divided from the main road (such as this case) should not be drawn separately but designated using tags. Otherwise it implies that there is a separate road. |
| 129174918 | about 3 years ago | You need to revert this edit. OSM standards do not allow 2 lane freeways to be marked as motorway. This was correctly labeled previously as a trunk road and expressway. |
| 129106991 | about 3 years ago | Just because it is in the NHS does not make it a trunk road. Please remember that OSM has its own set of standards. This results in a trunk spur, which should be avoided. I see you've been doing a lot of much needed edits in Kansas. I encourage you to start discussions on #local_kansas on Slack and maybe even start the Kansas Highway Classification page on the wiki. |
| 129348392 | about 3 years ago | See comment I just gave you on a different issue. You seem to be confusing trunk and expressway. It's a relatively recent change to the standards, but it is one that needs to be used. |
| 129348314 | about 3 years ago | See comment I just gave you on a different issue. You seem to be confusing trunk and expressway. It's a relatively recent change to the standards, but it is one that needs to be used. Trunk roads do not need to be undivided. However, if you feel that this is best left as primary, please eliminate the trunk spur further north to MO D. |
| 129378321 | about 3 years ago | See comment I just gave you on a different issue. You seem to be confusing trunk and expressway. It's a relatively recent change to the standards, but it is one that needs to be used. |
| 129378088 | about 3 years ago | According to the link you provided, there are not to be random islands of trunk roads; they are supposed to form an interconnected network. This is one of the big pushes from the 2019 and 2021 Highway Classification guides. This type of road would be primary and marked with expressway=yes, unless you see need to consider it trunk from Gray Summit to Manchester. |
| 127626257 | about 3 years ago | Please remember that OSM has its own standards not mandated by any DOT. While US 81 may not be an interstate, it meets freeway (motorway) standards as it does not have any at-grade intersections. Please revert this edit. Feel free to ask any questions and read this article. highway=motorway |
| 126674431 | about 3 years ago | Why is this a trunk highway? I 76 is right there, and BL 76 does not really serve anything beyond Sterling (I'm kind of amazed it still exists beyond a spur into Sterling). "The Trunk classification generally should not be applied to highways that are parallel to motorways, especially highways within a short distance (less than 5 miles) from the motorway." osm.wiki/United_States/2021_Highway_Classification_Guidance#Trunk |
| 126673901 | about 3 years ago | I added my points to the talk page there, but not sure where this conversation you're mentioning is taking place. All I found was one person saying it should be a trunk route to Kansas (which it doesn't enter...). If there's another conversation happening elsewhere, let me know! |
| 126673901 | about 3 years ago | Having driven this many times, I'm not sure what your justification is in upgrading this to trunk road west of Brush, and I did not see any documentation on this. Trunk roads should not be spurs of the network when possible, and should have a significant destination. How does Haigler meet that definition?
|