OpenStreetMap

Mistakes & Regrets I've Made Editing OpenStreetMap

Posted by Johnny Mapperseed on 19 August 2017 in English. Last updated on 8 August 2018.

Edit: This list is pretty out of date, and I have a different perspective of things now. I’ll update this later.

  1. Armchair Mapping Mistakes
  • Thinking that going to a place and coming back to your home to actually make the change in OpenStreetMap instead of doing it on the spot is “Armchair Mapping” and not a survey.

  • When actually armchair mapping, assuming that just because something was there in my childhood, that it still would be there and unchanged.

  • Trusting satellite imagery more then my own eyes. Ground truth matters. If you think satellite imagery is going to be out of date for a long time in an area and it doesn’t reflect ground truth, it’s best to leave a note as a separate node or area explaining such so you dont forget and “Correct” you factual edits. Be sure to leave a date in your note for easy reference.

  • Not correcting misaligned satellite imagery with GPS traces whenever it is appropriate.

  1. Surveying Mistakes
  • Using OpenStreetCam on a footpath is a semi mistake. Ultimately the data is correct, but the render can misrepresent it, making it hard to find areas that haven’t been covered yet, but should be. Of course you should not simply map for the renderer.

  • Not uploading high quality 360 degree photos to Mapillary when possible and instead focusing on frequent low quality 2D images taken with a wonky satnav.

  • Not using Mapillary or OpenStreetCam at all when there was no coverage in my area.

  • Surveying areas that are hard to get to without a full charge on devices. This should be a no brainier, but if you won’t be back for a while, be extra sure to charge your devices to do more photomapping..

  • Using a standard lens instead of a wide angle one when it’s avalible. If you have a wide angle lens available when doing traditional photomapping it can often be better because it’s basically a time saving panoramic picture. Of course quality and distortions can be an issue outside the center of the shot.

  1. Community Mistakes
  • Not taking advantage of my surveys to also improve Wikipedia, Wikidata, and Wikivoyage. Some OpenStreetMap applications pull in data from them to help fluff their user interface.

  • Trying to do things alone doesn’t work. Have local mapping parties. Edit the wiki for your local area to help others. Go to SOTM if you can. Get involved.

Location: Downtown, Bowling Green, Wood County, Ohio, 43402, United States

Discussion

Comment from kucai on 20 August 2017 at 02:20

…Trusting a wonky smartphone satnav and compass when using Mapillary. Openstreetcam handles the wonky satnav part really well, but it’s even worse with the compass since you can’t currently correct it manually after uploading…

Unless your are talking about Openstreetcam only, compass heading can be corrected in Mapillary, but you have to use the web interface which I found to be slow. About time for an app/plugin that can edit those details before uploading to the Mapillary server. Regards.

Comment from Johnny Mapperseed on 20 August 2017 at 02:23

Howdy! I didn’t word it really clearly but I did mean OpenStreetCam only. Sorry for the confusion! I’ll edit it to make it clearer. Thanks for pointing this out though! :D

Comment from escada on 20 August 2017 at 06:16

What’s wrong with using OpenStreetCam on a footpath ?

Comment from Alexander-II on 23 August 2017 at 00:08

Thank you for sharing mistakes you made. It looks so familiar to me.

Comment from Johnny Mapperseed on 15 December 2017 at 20:32

Hi!

Sorry it took me a while to get back to this! I honestly didn’t expect any comments or for anyone to read this. :O

I’ve gone back and did some proofreading and justified by points more instead of simply stating them.

Thank you for your feedback! :D

Log in to leave a comment