OpenStreetMap

[NE2]

Say, should PA 51 from the current northern end of PA Tpk. 43 down to its interchange with US 119 still be a trunk road? Maybe not now that there's a complete expressway route along that piece, and eventually (might?) be all the way up to I-279 where it turns into a short expressway and multiplexes US 19.

It's still a high-speed road with interchanges, so why not?

[rickmastfan67]

Strange rendering bug: http://www.openstreetmap.org/?way=135724062
It's as if the nodes are missing from the rendering database. (No, it's not "redaction"-related.)

I saw something similar happen on one of the KY Parkways.  What had to be done was delete/add a node to the way to force it to re-render properly.  I'll go do that now.

[Roadsguy]

Say, should PA 51 from the current northern end of PA Tpk. 43 down to its interchange with US 119 still be a trunk road? Maybe not now that there's a complete expressway route along that piece, and eventually (might?) be all the way up to I-279 where it turns into a short expressway and multiplexes US 19.

It's still a high-speed road with interchanges, so why not?

True, true...

[Roadsguy]

Are we really supposed to be mapping turning lanes?

[NE2]

Nope, unless there's a barrier separating them.

[NE2]

Sigh. Why do people change frontage roads to secondary where they link to a primary?

[Roadsguy]

Because Google does the same thing, more or less.

[Scott5114]

Sigh. Why do people change frontage roads to secondary where they link to a primary?

Because OSM tagging is arbitrary and lacks any sort of standard?

[Roadsguy]

I noticed (and fixed) that someone marked most of the 222 part of the Trexlertown, PA Bypass as a motorway.

[NE2]

I noticed (and fixed) that someone marked most of the 222 part of the Trexlertown, PA Bypass as a motorway.

Yep, with a couple traffic lights in the middle. Sigh...
PA 145-309 should probably be reverted too.

[Roadsguy]

That's more debatable, like US 11/15 at I-81.

If I had full control, I'd have done it, but not in real life.

[vtk]

Somebody drew this new interchange a little funky:

http://www.openstreetmap.org/?lat=38.32673&lon=-87.39737&zoom=16&layers=M

This topology would be problematic for routing, making some left-turns impossible, except the mapper forgot to put oneway tags on the state route, so it sort of works out.  If someone can observe the actual topology here (or be confident that INDOT built an ordinary diamond) and could fix up this interchange, that would be great.

[Roadsguy]

Any chance we can get the renderer to make everything primary and trunk (red and green) temporarily on Christmas?

[NE2]

Any chance we can get the renderer to make everything primary and trunk (red and green) temporarily on Christmas?

Not with this War on Christmas raging in Foxland.

[Roadsguy]

US 322, west of State College, is shown as a trunk. It's marked as (and is) a short freeway after its split from I-99, but past the first intersection, westbound is a freeway, but not eastbound. How would this be marked without looking ridiculous, and appearing to ignore the intersection?

Or doesn't it count?

[NE2]

http://www.openstreetmap.org/browse/way/155807977
WTF?

http://www.flickr.com/photos/okroads/5161690779/
Yep, definitely 35-V Business.

[vtk]

While I don't think I'd have done that, I've heard each business route gets a letter suffix in Texas to make them unique, and those letter suffixes do appear on independent-mount signage.  The route relations appear to have been organized sensibly, anyway.

[lordsutch]

Yes, the business route inventory letter appears on independently-mounted business route signs, but not guide signs, in Texas.  Here are three examples:

www.aaroads.com/shields/show.php?image=TX19790351
www.aaroads.com/shields/show.php?image=TX19700351
www.aaroads.com/shields/show.php?image=TX19700831

See the Standard Highway Sign Designs for Texas for specifications (specifically signs M1-2, M1-3, and M1-4B).

[rickmastfan67]

Yes, the business route inventory letter appears on independently-mounted business route signs, but not guide signs, in Texas.

I think what NE2 was trying to get at is that the BGS say it's an "I-35W Business" route, not a "I-35 Business" route.

[lordsutch]

I think what NE2 was trying to get at is that the BGS say it's an "I-35W Business" route, not a "I-35 Business" route.

Yes, although the designation file begs to differ.  And, amazingly, so does the field signage along the route.

[rickmastfan67]

I think what NE2 was trying to get at is that the BGS say it's an "I-35W Business" route, not a "I-35 Business" route.

Yes, although the designation file begs to differ.  And, amazingly, so does the field signage along the route.

Well, the StreetView images are from 2008 (except I-35W NB only which is from 2011), and okroads's picture is from 2010.  So, who knows, something might have changed in that area with signage on the route itself.

[NE2]

Yes, the business route inventory letter appears on independently-mounted business route signs, but not guide signs, in Texas.

I think what NE2 was trying to get at is that the BGS say it's an "I-35W Business" route, not a "I-35 Business" route.

Well, I was also pointing it out as a particularly good example of the stupidity of using tiny inventory letters in the ref tag.

[rickmastfan67]

Yes, the business route inventory letter appears on independently-mounted business route signs, but not guide signs, in Texas.

I think what NE2 was trying to get at is that the BGS say it's an "I-35W Business" route, not a "I-35 Business" route.

Well, I was also pointing it out as a particularly good example of the stupidity of using tiny inventory letters in the ref tag.

I'm making a point about this in talk-us (OSM) right now too.  Also suggesting an alternative tag so that everybody can be happy and not have the renders/routers be confused up the wazzo.

[kphoger]

I think what NE2 was trying to get at is that the BGS say it's an "I-35W Business" route, not a "I-35 Business" route.

Yes, although the designation file begs to differ.  And, amazingly, so does the field signage along the route.

Well, the StreetView images are from 2008 (except I-35W NB only which is from 2011), and okroads's picture is from 2010.  So, who knows, something might have changed in that area with signage on the route itself.

Field signage was Business 35W as of June 2012.

[rickmastfan67]

I think what NE2 was trying to get at is that the BGS say it's an "I-35W Business" route, not a "I-35 Business" route.

Yes, although the designation file begs to differ.  And, amazingly, so does the field signage along the route.

Well, the StreetView images are from 2008 (except I-35W NB only which is from 2011), and okroads's picture is from 2010.  So, who knows, something might have changed in that area with signage on the route itself.

Field signage was Business 35W as of June 2012.

So the signs along the route itself are now I-35W Bus shields?  Got some pics?