compdude's Comments
| Changeset | When | Comment |
|---|---|---|
| 176079968 | Please see this wiki article: osm.wiki/United_States/2021_Highway_Classification_Guidance#Trunk It says that trunk should only be used on expressways (divided highways with at-grade intersections) in "areas with high population density" (i.e. urban areas). The only part of SR 99 that meets that definition is the stretch of Aurora Avenue between the north end of the SR 99 tunnel and where it hits the first stop light at the intersection with Winona Ave N on the north end of Green Lake. This section needs to also have the expressway=yes tag. |
|
| 176079968 | WA 99 should not be tagged as a trunk road. Please change this back to how it was before, thanks! |
|
| 175056279 | Okay, I fixed the tagging so that it would properly show up as under construction. Thanks for clarifying what is going on here! |
|
| 175056279 | Oh, I see. It's supposed to be a roundabout. I'm going to mark it as proposed since it doesn't appear to be under construction as far as I'm aware. |
|
| 175056279 | What were you intending to do with this? Not sure why you'd draw a secondary_link in a circle like this. |
|
| 175784654 | I've reverted this change in changeset/176658877. |
|
| 175784654 | Sorry, but I'm going to remove it from the ref=* tag. It's just unnecessary clutter. And while Caltrans certainly has been upgrading CA 99 to Interstate highway standards, do you have any actual evidence that Caltrans is actively working on giving CA 99 an Interstate number? If not, then this is definitely just roadgeek speculation. |
|
| 175784654 | I'd strongly encourage you to move the Future I-7/I-9 to the fut_ref=* tag. Having it in the ref=* tag just adds clutter to the map. Also, calling this Future I-7 or I-9 is pretty much just roadgeek speculation imho. |
|
| 160590655 | Why did you change the freeway ramps at I-95 exit 66 from motorway_link to trunk? It is standard practice in the US to tag all freeway exit ramps as motorway_link, even if they carry a highway route designation. |
|
| 155257209 | Thanks for your contributions! However, I noticed you mistakenly tagged long stretches of the R Line as being a bridge even though it is not on a bridge structure. I fixed it for you, but try to be more careful about this in the future. Thanks!! |
|
| 141584902 | You do realize that the highway=motorway tag is for freeways with no at-grade intersections, right? This stretch of Hwy 19 has at grade intersections and should not be a motorway. |
|
| 142590501 | Why did you tag the segment of light rail between I-5 and the Mt. Baker Tunnel as railway=rail instead of railway=light_rail? I'm assuming this was just a mistake, right? |
|
| 134597607 | I changed this back to how it was before. It is standard practice to tag a road as a bridge, even if there's a separate polygon for the bridge. |
|
| 136148182 | It seems like you made this an admin boundary by mistake. |
|
| 133808568 | Is this actually under construction, or is this yet another proposed highway that this user changed to under construction? I'm not familiar with this area to know whether or not this road is actually under construction or not. |
|
| 127817261 | Not sure if a road that closes in winter should necessarily be a trunk road. Was this agreed upon by other users in Colorado? I don't see it listed here: osm.wiki/Colorado/Highway_Classification#Trunk_Roads |
|
| 126722523 | It appears that when you removed the bicycle access, you also changed the access=* tag to no, which implies that the road is closed to the public. I'm assuming that was a mistake on your part so I am going to remove that tag from this stretch of road. |
|
| 126166211 | Interesting, I didn't know about this. I don't agree with the Forest Service's decision to do this, but whatever. Thanks for the response! |
|
| 126166211 | Why did you change FS Road 65 to FS 6500? All the signs say 65 not 6500. |
|
| 118759027 | No problem, thanks for the reply. I'll go ahead and fix this. |