Just happened to come across this changeset, and noticed that it completely incorrect. The 'destination' tags were put on the completely WRONG ways. The tags you put on the I-376 ways were meant for the US-422 ways. Look @ way/19322510, the 'destination' info on that was meant for way/55455970 instead, as that's US-422's way, and the 'exit' here. As for the info on way/413903594, I'd just completely remove it, unless there's a picture in Mapillary showing the signage, as I'm 2000% sure this ramp isn't for 'US-422 East', as US-422 joins up with I-376 to head up towards New Castle.

Cool beans. :)

This changeset has been reverted in 'Changeset 44867867', as the data it added was completely fictional.
changeset/44867867

Well, I would have agreed with you on this if PA-8 had been built like US-22 is between I-76/I-376 & the freeway section before I-99. But since the only divided segments seem to be around only major intersections, and the only interchanges it has are with PA-28, I-76, the partial one @ Bakerstown Rd, & the road to Alcoa in Butler, I personally honestly don't see it being worthy of the 'trunk' tag. I've personally traveled along PA-8 & US-22 in both of the mentioned areas and can see major differences between the two that can justify the 'trunk' for US-22, but not for PA-8 IMO.

Pretty sure PA-8 shouldn't be classified as 'trunk' north of PA-28. Should stay as 'primary' IMO (except for the freeway section right around the PA-28 interchange of course).

Pretty sure PA-8 shouldn't be classified as 'trunk' north of PA-28. Should stay as 'primary' IMO (except for the freeway section right around the PA-28 interchange of course).

Hey Chris, I think you got caught up in this changeset with that false 'I-295' shield they showed in PRs about the new section of highway opening. It's all posted as NC-295 for now. So, I'd recommend fixing that. http://www.aaroads.com/forum/index.php?topic=8390.msg2168222#msg2168222

I would recommend you fix your sources for your changesets before you make any more changes. This is clearly not part of Los Angeles, and you've been using the same 'false' source for the last several changesets you've made.

I would recommend you fix your sources for your changesets before you make any more changes. This is clearly not part of Los Angeles, and you've been using the same 'false' source for the last several changesets you've made.

Just so you know, in this changeset, you added a few incorrect lane counts. For instance, on the two "Market Street" ways, you said they were 2 lanes, but they are only 1 way in each direction. Also, with way/369274384, you said it was only 1 lane, but it's clearly 2, and not oneway.

Just thought I'd mention this stuff so you were aware in case these mistakes were done in error. ;) I've already fixed them, so you don't have to worry about it. ;)

This changeset has been reverted in "changeset/43826763" ( changeset/43826763 ) because this is an offramp, not mainline I-79, and this ramp wouldn't be posted @ 55mph.

This changeset has been reverted in changeset/43376932 ( changeset/43376932 ). Also, here's some more proof that this section isn't posted @ 70mph: https://www.paturnpike.com/press/2016/20160502143015.htm Search and find the phrase "the eastern slope of the Allegheny Mountain", where it clearly says it stayed @ 55mph.

This changeset should be reverted. As I mentioned back in changeset/42684737 ( changeset/42684737 ), this part of the PA Turnpike wasn't eligible for the upgrade to 70mph (clearly shown here: http://www.post-gazette.com/.media/2/2016/05/06/fb84f985-c064-4edd-9fbb-a4e9352851d2.jpg, as this area isn't in green ). None of your drivers are not telling you the truth here about this. Unless they have picture proof of 70mph signs in this section, you should ignore any future reports from them saying it's 70mph here and refuse to change the data. If they have governors on their trucks or are being GPS tracked for speed, this is why they are falsely saying this section is 70mph so they can go 5-15 over the limit. Incorrect data has no purpose here in OSM, as normal people also use items that use this data too, not just truckers.

Please make sure you update your changeset comment when you change to doing other things. I don't think Butler, Pennsylvania is part of the Caribbean.

I've gone ahead and already fixed that part.

Thank you for changing those back. However, you missed the part at the Allegheny Tunnel that you changed. That curvy section also remained at 55 mph. This image ( http://www.post-gazette.com/.media/2/2016/05/06/fb84f985-c064-4edd-9fbb-a4e9352851d2.jpg ) that shows where the speed limits were upgraded clearly shows that it stayed as-is. Especially since that section in the future should be bypassed when a new tunnel or highway cut is added there and they don't plan on trying to upgrade it's allowed speed limit.

Same goes for ways 47625568 ( way/47625568 ) & 47625569 ( way/47625569 ). There is NO way the speed limit jumps to 70 mph between the Blue Mountain Tunnel & Kittatinny Mountain Tunnel which are both posted @ 55 mph.

I would recommend this changeset to be reverted.

I'm sorry, but I'm 99.9% sure that the speed limits drop to 55mph before getting to any of the tunnels on the PA Turnpike, and not right at the portal. Same with leaving them, they don't instantly jump up to 70mph. For instance, with 'Way 4968249', (while I was last there before the Turnpike got the speed boost to the West of Exit 201), the first '65 mph' sign (now 70 mph) was posted well after the bridge ( way/4968249#map=17/40.09143/-77.85749 ) at the end of that way. Thus, way/4968249 is still officially 55 mph, even though you've left the tunnel.

Changeset has been reverted in 'Changeset 42301159' (changeset/42301159), as this node was taken from a USA road and moved all the way to France creating a false road link over the Atlantic Ocean.