That is 'Truck US-20' on the 'Howard Street' route. That way linked above has always been US-20 as long as I've visited that area.

Is there really now a posted NY-5 Alternate in Silver Creak, NY? I'll admit, I haven't been up there for awhile, but there was never one posted there in the past. The only 'bannered' route was the 'Truck US-20'. way/44732385

Also, you damaged routing in this area by not updating the lane counts when you twinned it. You left it as '4' in both directions, when it should have been changed to 2.

If you look close up at way/352696638, you can clearly see an access road into the cemetery there where you have it going under Curry Hollow Road instead.

You added a false bridge in this changeset. This isn't a bridge: way/352696637 & way/352696638

Please update your changeset comment in JOSM. You're saying 'Changeset 31829188 was reverted.' across the entire country.

Thanks.

So, in closing, most of these segments have a striking similarity to McKnight Road (US 19 Truck) in the North Hills of Pittsburgh. On it's Northern-most segment, it has a high speed limit (50mph) and an interchange, but you don't see me upgrading it to a motorway in that area (like you did for that Economy and Baden segment). Also, by your reasoning for the upgrades here in this changeset, PA-68 between Evans City and Butler should be a motorway. It has a high speed limit (55mph) and no traffic lights, but it's only 2 lanes. [sarcasm] But hey, your reasoning means it should be a motorway! [/sarcasm]

Thus, you really have to think stuff like this thru before just upgrading a road to a higher level. We don't want to screw up the routing engines that rely on us mappers not screwing up the highway classifications or any of the other tags (like # of lanes, the speed limit, & the oneway tags). Especially since some routers have options to 'avoid motorways', and they might give somebody a messed up route because of false upgrades to that classification when the route should have never been upgraded in the first place. Also, compare the road to other known (for sure) motorways in the area before upgrading. Also make sure the segments are fully limited-access too before upgrading. Doing that can solve a lot of headaches for all the mappers in the area.

Anyways, I recommend a full revert of this changeset to put those segments of PA-65 back to 'trunk' (and the ramps as trunk_link of course).

As for the 'Freedom' segment, some of that segment has a sidewalk right beside the highway (Northbound PA-65 side to the South of Freedom) which is visible in Bing. I've never seen a motorway with one of those right smack beside the highway, without at least a guard rail, jersey barrier, or something similar helping protect the pedestrians from 'idiots' or wrecks. If the segment between the 2 ramps had been connected to the motorway segment in Rochester without any gaps, then yes, I could see the segment being considered as a motorway. However, because of that sidewalk, the big gap with at-grade intersections in it between Freedom and Rochester, it honestly should have stayed as a 'trunk' highway, just like the other two segments you 'upgraded' in this changeset.

As for the area of PA-65 around I-79. IMO, that should have stayed as trunk too. They allow bicycles in that area. Tagging it as a motorway breaks that type of routing instantly once those services update their data from OSM. Also, you missed that there IS an at-grade intersection in that area @ Toms Run Road ( osm.org/go/ZWtBfaR2m?m= ), right in the middle of the segment you turned into a motorway. Motorways don't have those (except out West in Western Texas, where they are needed to access private ranches because the old US Highways out there were upgraded in place to Interstates, like I-10. But, then again, most of them are already marked as 'trunk' in those small areas). Also, we don't upgrade small segments of highway like this to motorway just because they have 'one' interchange. Otherwise, trunk highways like US-19 in WV between I-79 and I-77 ( osm.org/go/ZTyUEY?m= ) would have several small motorway segments for it's few interchanges outside of the Oak Hill Bypass (which is a motorway). That's just not how it works here. Not even Google does it this way.

Wow, I'm sorry, but some of these areas are no way 'motorways'. For instance, the segment that you made motorway between Economy and Baden. There is absolutely no way it can be motorway. This segment isn't limited-access at all. There are a few access points to places like these 2 along it: http://binged.it/1Hh73Lu & http://binged.it/1Hh7c1E Just those alone disqualify it from being a 'motorway'. That segment should have stayed as a trunk highway, hands down.

I'm sorry, but there is no way Broadhead is a 'primary' highway. A 'secondary' highway, yeah, just not primary. First of all, it's between I-376 (motorway) and PA-51 (primary). 2nd, It's not a 'primary' state highway (meaning it doesn't have a 2-digit or 3-digit route number). Those two other routes have more lanes, capacity, and higher speeds (at least for sure with I-376) then this route. 3rd, is it honestly a 'higher' priority highway than PA-51 in terms of design? I honestly don't think so.

Thus, I would recommend downgrading it to secondary, which is still higher than the territory it was classified as before.

You have to think stuff like this thru before just upgrading a road to a higher level. We don't want to screw up the routing engines that rely on us mappers not screwing up the highway classifications or any of the other tags (like # of lanes and the speed limit).

Just so you know, we do not add the quadrant route numbers to ref tags. Those routes do not get shields like the 'normal' state routes. They should be tagged as: ' ref:penndot=SR 3016 ', not ' ref=SR 3016 '. Please see: osm.wiki/Pennsylvania/State_Route_Relations#Four_digit_routes

I noticed you merged several of the I-476 offramps in this changeset together, which damaged the 'lanes' tags. The person before you happened to split the ramps where the # of lanes changed and added where each lane went. When you merged them together, it damaged this work. Thus, I've partially reverted this changeset in changeset/31624102 (I left the houses you added in tact).

Are there any signs posted restricting these movements? If not, then it's a flaw in the router you were using and should be reported to them.

Just so you know, the Tiger data isn't always correct and you shouldn't just blindly trust it to add roads from it. While yes, there's a 'path' there, it's a person's driveway, not a residential road. I've been past this location over 500 times in my life. If this had been a residential road, I would have added it myself a long time ago. I've changed it to a service road/driveway.

That's a 'Kings Family Restaurant', correct? Or is it the 'Kings Hometown Grille' location I read about on the Wikipedia entry for Kings? Either way, it should have the 'full name' (depending on which it is), not just tagged as 'Kings'. Also might want to add their website link at the same time (especially if it's the 'Hometown Grille' location so people know it's one of their locations.

Just so you know, you don't have to put 'source=bing' on stuff like turning circles if you put it in the changeset comment. ;) Especially since you can see them in Bing and the 'imagery_used=Bing' tag is already on your changeset comment (added by iD automatically). ;) Just a way to keep down on tags when they aren't needed in some cases. :)

np man! (BTW, the only exception to the oneway=no rule is for motorway's & motorway_link's. They are always assumed as oneway=yes unless they are truly oneway=no or oneway=reversible. I-279's HOV lanes/ramps are the latter since you can only go in one direction at any one time.)

Just so you know, we don't need to add the 'oneway=no' tag in areas like this unless there are a mass amount of oneway roads there and the two-way are very occasional. Also, are you sure way/54459358 is one way for that bridge? way/54459358

And welcome to OSM!