On Fri, Nov 27, 2009 at 3:41 PM, Paul Johnson <[email protected]> wrote: > David ``Smith'' wrote: >> Given the overall network of secondary, tertiary, etcetera in the area >> and a couple of visible ref tags, I'd estimate the "highway=secondary" >> is entirely because of the original TIGER import: since a short >> section of the road is also an Oregon state highway, the whole thing >> got an Oregon state route designation in one of its name_x tags, and >> therefore the whole thing was imported as "highway=secondary" and left >> that way. > > Actually, it was promoted to secondary due to the fact that the whole > thing is a major enough road that it needed to be visually distinguished > from more minor city ways and properly reflect it's status as an > important connection between 99E, 22 and 213. > >> (I don't have local knowledge, but given the close proximity of that >> road's entire length to a parallel motorway, I wouldn't think that >> road serves as much more than a local collector.) > > It's a major commercial thoroughfare and the only easy connection > between 99E, 22 and 213 (adding I5 to the equation usually only benefits > you during the hours the anticongestion zone is in effect).
Sounds to me like drivers want to use it as a secondary road, but local authorities want it to be only a minor collector. It also sounds like I-5 needs improvements so that people will naturally use it rather than Lancaster Dr. Anyway, your explanation satisfies me. With that in mind, I would suggest promoting to secondary a little bit more of it at the ends: north to OR 99E / Portland Rd NE, and south to the southernmost trunk links to OR 22 / Santiam Expressway. (<http://osm.org/go/TdXV2vRe> <http://osm.org/go/TdXUoDMr>) That would make things a bit neater looking. -- David "Smith" a.k.a. Vid the Kid a.k.a. Bír'd'in Does this font make me look fat? _______________________________________________ newbies mailing list [email protected] http://lists.openstreetmap.org/listinfo/newbies
