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?

Please stop adding the 'ON' to ref tags in Ontario. The people in Ontario have been tagging without them from the start. If you want them to possibly consider adding the 'ON' part officially, please make a post on [talk-ca], which is here: https://lists.openstreetmap.org/listinfo/talk-ca That way, there are no edit wars or reverts.

99.9% sure that Tiger 2014 data is wrong here with where they have 'Fontana Drive'. That is clearly a service road and a parking lot for a business, and normally wouldn't have a road name. Pretty sure that this ( way/11728956 ) is the true 'Fontana Drive'. Thus, I've turned the one you added into a 'service' highway & removed the name in changeset/32179177. changeset/32179177

The new extension of Highway 401 isn't opened yet. Marking it as 'construction' again till it officially opens.

http://blogs.windsorstar.com/news/herb-gray-parkway-only-days-away-from-opening-to-traffic

Broadhead downgraded to secondary in changeset/31983183. changeset/31983183

Reverted in changeset/31982052.
changeset/31982052