Just so you know, the 'access=yes' and 'motor_vehicle=yes' tags are both 'unnecessary' tags here. All highways by default are 'access=yes' and 'motor_vehicle=yes' and don't need to have those tags. So, in the future with iD, just completely ignore those options unless the highway really needs a 'access=private' or something similar. Same goes with the 'motor_vehicle=*' tag.

That and please don't add the quadrant routes along routes that have primary numbers like US-322 Business in State College. That can, and does confuse drivers when the routing apps mention a highway that can't be noticed 99 out of 100 times. I was along most of US 322 Business at the beginning of the month (Aug '15), and even I was hard pressed to even 'notice' a single one of the small reference signs that PennDOT uses for quadrant routes (since I know what to look for unlike 99% of the drivers in the state) as they were very well hidden. The ONLY shields noticeable where the US-322 Business ones. And that route IS THE ONLY one that should be in the ref tag since it's the only route that has the shields posted. IF you feel you MUST add the quadrant routes (which are reference routes for PennDOT, not for routing!) along another POSTED route, please add them via the 'ref:penndot' tag instead. After discussion on [talk-us] by the community in January '15 (which I invited you to join in on several times so people could hear your side as to why you though they needed to be in the 'ref' tag), the 'ref:penndot' tag was agreed upon for use with all quadrant routes in PA, since they are, and always will be, just reference routes, and not meant for use by the public for routing because that's what the Keystone (+ US and Interstate) route shields are for (routes 1-999). Anything 1000+ should always be in the 'ref:penndot' tag since the are reference routes.

Please don't add 'historic' routes unless they are fully posted with shields and the 'Historic' banner. This is what the 'old_ref' tag is for. This is in reference to way/11836736 and a few other 'Historic' routes you've added in the State College area. PennDOT has never posted a 'Historic' bannered route that I know of anywhere in the state.

So, did you see shields for it (NY 5 Alternate), or was it a guess off of the Tiger tags that were still on the way? Let me know, and then we can proceed from there.

I was mostly wondering if you had been there recently in regards to that route you added (meaning if you had seen shields in the field for it). Since I hadn't been in that area recently, I didn't want to revert a new route (NY 5 Alternate) if it had been indeed posted by NYSDOT. That's why I was waiting for a response from you on that subject.

Just so you know, even if Potlatch 2 shows an error for the 'ref' tags, we are suppose to use the semi-colon to separate them. Thus, they aren't an error. ;) I'm working on fixing the ref tags from this changeset back to the proper standard right now.

BTW, you might want to fix the traffic light nodes. You added the 'surface=asphalt' tag to all of them it seems.

Haha, you beat me in doing this. :)

Just so you know, we don't abbreviate road names. We always put the full name in the name tag. That way, we can leave it up to the data users to abbreviate them on their own if they want to.

Alright. BTW, it looks like this 'path' would be more appropriately tagged as a 'highway=path' instead of as a footway. It's nothing like the 'sidewalk' that is parallel to Cumberland Road that is tagged as such. highway=path

I'm just curious, but is that path's name really 'Neverending'? Honestly seems like it wouldn't have any name to be honest.

The tag that this way had before was appropriate since I-99 construction eliminated any evidence of the railroad. Reverted in hangeset 33143100. Anyways, welcome to OSM!

This was an error from the Tiger data import 7 years ago, not Google.

I'm curious, but what's the basis for adding the ref tags for a PA-560 & PA-335 along some of the ways here? Both of those route numbers don't exist. PA-335 was once assigned, but in the middle of the state. As for PA-560, it was never assigned once. I've removed both of those routes ref tags from the database, but still am curious as to why you added them and would appreciate a reply to that.

Matt??

Everything looks ok to me. ;)

As you can see in this example from Google Maps, they are intentionally routing people onto the side streets to bypass the closed segment. https://goo.gl/maps/yMziB If you can convince Google not to do that, that might solve 95% of your problems, especially with the commercial drivers.

Only thing I can suggest is contacting Google. Odds are, the people are using their Android phones and the Google Maps App and just follow what the app tells them to do (or they just use that as a defense). If people want to use an app that uses the OSM data, they sometimes have to search it out on the app store.

With these kind of changesets, can you please try to limit them to one continent at a time instead of having ocean crossing changesets? It's hard to be able to keep track of changes in my local area when several 'small', yet 'worldwide' changesets, are loaded in my local areas RSS feed, especially when there are no 'local' changes in them, and the closest is ~1000 miles away. Thanks!

Any comment on this Matt?