10th Anniversary Name Fix Challenge

Posted by KristenK on 9 August 2014 in English (English)


Today I would like to share some words about the latest challenge to hit MapRoulette—the 10th Anniversary Name Fix Challenge ( ; active on 8/9/2014).

OSM data is not only used for cartographic purposes, but also for route navigation and guidance (audio/text). Spelling and punctuation errors in the raw OSM data affect navigation end-user experience. At Telenav, we've queried the raw data and identified various types of name spelling/punctuation errors that results in less-than-ideal text-to-speech pronunciation and display. Here's a sampling of the errors we've identified and pushed to MapRoulette--and suggestions on how to fix them. I've also included in a link below, sound bytes of the OSM names pronounced by our text-to-speech service.

Way ID = 12980620; "South8th Street"

Way ID = 110323605, "Treetop La\ne"

Way ID = 13090901, "40 Th Street"

Way ID = 19459430, "2 Nd Street"

Way ID = 12061780, "Cementary Hill Road"

Way ID = 9002952, "Altman Cemetary Road"

Way ID = 205289167, Street Joseph Street

Way ID = 17454543, "South Sweeetbriar Circle"

Way ID = 7797877, Oakwooods Drive"

Way ID = 12677584, My Happpiness Lane"

Way ID = 13451423, "Hedda St; La Jara Street"

My Dropbox folder that contains audio listed above:

If you've got any questions or can think of other types of spelling errors in the data, give me a shout via or at



Location: Fusion Sunnyvale, Sunnyvale, Santa Clara County, California, 94086, United States of America

Comment from EdLoach on 9 August 2014 at 07:51

A quick note in case it helps anyone else - the Street Joseph Street example suggests checking the way history, but the linked way is v1. That is because it was split from this way where the railway line splits the road in two, and the bot damage was before the way was split.

Hide this comment

Comment from KristenK on 9 August 2014 at 08:29


Yeah I caught that after I posted, but wanted to carry on with my evening (Guardians of the Galaxy). So the example didn't get updated.

In any case, here's the OSM Way that the above Street James Street example was probably derived from:


Hide this comment

Comment from KristenK on 9 August 2014 at 17:32

Another thing I would like to add is that there are also OCR errors. So when someone's scanning in names. Check out this changeset:

  • "Corrected "B0Bbys Circle" to 'Bobbys Circle"
Hide this comment

Comment from skorasaurus on 9 August 2014 at 18:38

There's a few questions that we have in cleveland for this challenge: a several of the ways we've seen are "Highway 17 (Trans-Canada)'," for example. fo's the tagging for this? is there a relation for the trans-canada?

  • should county route 44 be tagged as ref=CR 44 ?
Hide this comment

Comment from KristenK on 9 August 2014 at 19:28

I've noticed these cases too. If you edit with JOSM, the application has a feature to see if the Way is part of a relation.

I would put the Highway 17 ways into a relation, and have the name for the edges, "Trans-Canada". But I am not familiar with Canadian roads at all (some got selected because of my bounding box.)

My advice to you is message someone local to Canada, such as Paul Norman, who I believe is based out of Vancouver. I chatted with him earlier in the week and I understand that he's traveling to Seattle for the Mapathon. Message him.

I'm about to head out for lunch, so I hope the above helps. I may not be able to answer other questions today. Maybe via mobile.


Hide this comment

Comment from DaCor on 10 August 2014 at 06:33

Found something I havent seen before. the following tags applied to roads

source=Eric Jarvies. All rights reserved. ©2010 ( or added_by=Eric Jarvies(

Hide this comment

Comment from KristenK on 29 August 2014 at 22:19

I have come across instances where a bridge has a name that is traversed by a roadway.

Per the Key:bridge OSM wiki page, if the bridge has a name add the name to the value of the bridge:name tag. The name of the roadway should be in the name tag.



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

  • Image

    ![Alt text](URL)

Login to leave a comment