OpenStreetMap

Heads up TriMet

Posted by Paul Johnson on 13 June 2011 in English (English)

I know there's a few folks at TriMet working on geometry and access issues, however I do have a couple friendly requests:

Don't squash "name=" without double-checking it first. Most glaring example: The Robert Baldock Freeway is not "I5 Freeway (North|South)bound." Nor is the Boone Bridge.

Don't squash "highway=" without looking. At least make an honest attempt at figuring out why something is tagged the way it is before arbitrarily changing paths to footways, cycleways to paths, etc, especially if they're already part of an lcn relation.

Don't squash "cycleway=*" without looking or ground knowledge. I've noticed several instances of opposite_lane being cleared or set lane when the lane is only on one side.

Comment from Wynndale on 13 June 2011 at 12:21

Is there ever any point in putting the road number in the name= field? We always leave name= blank on motorways that haven’t got proper names in Britain.

Hide this comment

Comment from Sundance on 13 June 2011 at 14:28

In the case of Interstates, US and state highways there is a list of official names, don't remove them, if a freeway is more commonly known like above I would do...
name=Robert Baldock Freeway
alt_name=Boone Bridge (I'm going to assume this is the name of the bridge)
nat_name=Interstate 5
ref=I 5

The list of official names is here;
http://en.wikipedia.org/wiki/Numbered_highways_in_the_United_States#State_highways_and_other_similar_systems

Hide this comment

Comment from Paul Johnson on 13 June 2011 at 17:46

@Wynndale: Not that I'm aware of. People seem to fill it in to satisfy renderers.

Hide this comment

Comment from Paul Johnson on 13 June 2011 at 18:23

@Sundance: I'm not even sure filling in nat_name when all it does is reiterate the ref= is useful in the slightest (especially in I5's case, the nat_name would more likely be Pacific Highway, and the ref and nat_name would more properly belong in a relation)

Hide this comment

Leave a comment

Parsed with Markdown

  • Headings

    # Heading
    ## Subheading

  • Unordered list

    * First item
    * Second item

  • Ordered list

    1. First item
    2. Second item

  • Link

    [Text](URL)
  • Image

    ![Alt text](URL)

Login to leave a comment