MapRoulette is a fun way to spend a few minutes (or hours…) improving OpenStreetMap. MapRoulette will present you with a random, easy to solve issue in OSM. MapRoulette is organized in ‘Challenges’, groups of tasks that are of the same nature. For example, there is a challenge to add missing crosswalks in various areas in Switzerland, based on analysis of aerial images.
How do you find a challenge you would like to work on? The MapRoulette home page provides a map of all the challenges, but this has some shortcomings. The challenge ‘centers’ are no
t always representative of where the tasks actually are located. It is also hard to search by topic. MapRoulette also has a search bar that you can use to find a challenge by keyword.
I want to work on making it much easier to find
interesting MapRoulette challenges, and I would like to hear from you how you think that should work. Please add a comment below with your ideas!
Because the number of old TIGER ways is huge, this challenge covers only a tiny part of the U.S. as you can see here:
Once this part is done, we can reload the challenge with more old TIGER ways.
If you look at the screenshot above, you can also see what the query is that goes into Overpass to create the challenge in the first place. You can easily adapt it to make your own local challenge if you want to start fixing up old TIGER ways with your local mapping friends! (Why not organize a TIGER fixing party? OSM US will pay for pizza!)
If you’re interested in the Overpass details and some ideas for improving it, keep reading. Otherwise, just start fixing!
Query Overpass for old TIGER
Here is my extremely simplified way to query Overpass for old TIGER ways:
way[highway]["tiger:tlid"](40, -113, 41, -111);
out body geom qt;
It takes the bounding box (40, -113, 41, -111) and searches for ways that have the highway tag as well as the tiger:tlid tag. This query should be a pretty good approximation of a real old TIGER way query, because the tiger:tlid tag is removed automatically when you edit such a way in iD or JOSM. So any way that still has this tag must not have been edited since the import.
This query falls short of a real old TIGER ways query, because the nodes that make up the way may very well have been edited. I am also not 100% sure under which circumstances the editors remove the tiger:tlid and other unnecessary TIGER import tags. It may be safer to look for last edited date or version number. If you have suggestions for improvement, please let me know in the comments.
ImproveOSM has been updated with many new roads. We processed recent GPS data from a number of data partners with some great results. A total of 30,000 new missing road tiles were added, over 17000 in Indonesia alone.
Aside from the missing roads, we added 67000 potential missing one-way roads that we detected with high confidence. Internal testing revealed only 6% false positives.
We are happy to continue providing OSM mappers with high quality data about missing things in OSM based on billions of GPS traces. Because ImproveOSM is based on actual drives from people using navigation or mapping software in their vehicles, and we apply a pretty high threshold for number of trips and quality of the GPS data, you can be pretty confident that every ImproveOSM feature will lead you to something you can add to OSM. Even if the aerial imagery is poor.
You should see the new data in your ImproveOSM plugin or on the ImproveOSM web site very shortly. Happy mapping and let us know what you mapped using ImproveOSM!
Late last week, we released new versions of the OpenStreetCam apps and the web site. While we continue to make the platform faster and more reliable, we also like to keep adding interesting and fun features from time to time! This new release introduces points and levels. Every time you drive, you earn points. Earn enough points and you level up.
We went back in and calculated points for all your existing trips, so why not head to the newly designed leaderboard and see how you stack up against your fellow cammers? You can also see the leaderboard in the app:
We also enabled leaderboards by country on top of the daily, weekly and monthly rankings.
Your profile screen in the app and on the site will show you exactly how many points you have, how many you earned per trip, and what your current level is.
More points for unexplored roads
So as you are driving around, you will automatically earn points for every picture recorded. But not all pictures earn you equal points! The less explored a road is, the more points you get — up to 10x the points for roads that have no coverage at all yet!
(This made it possible for me to gain 11k points on a 50 minute drive last week: most of the roads had no coverage yet, so I was getting 10x points for most of the way. )
You can see which roads are less covered, or not covered at all yet, in the app. Just look for the roads with lighter or no purple OSC overlay:
We calculate the quality of coverage by the number of trips that cover the way as well as the age of the existing trips. This way we encourage each other to always have the most recent imagery available for OpenStreetMap.
We hope you enjoy the new features! Please let us know what you think by writing us at firstname.lastname@example.org.
OSMTime is a monthly OSM mapping event organized by Telenav colleague Beata Jancso. Telenav hosts the events in the Cluj-Napoca office and sponsors with pizza. Usually Bea chooses a theme and sometimes there will also be a speaker with an interesting OSM related topic.
While visiting the Telenav Romania office in Cluj last week, I was lucky to also catch an OSMTime event. The theme of the evening was ‘Mapping Roundabouts using MapRoulette’. Being the person behind MapRoulette, Bea asked me to do a quick introduction. Colleague Bogdan Gliga also presented the metodology he used to detect missing roundabouts from massive amounts of probe data. (He wrote about that topic here as well.)
After the presentations and pizza, the 25 or so mappers logged on to MapRoulette to start with the new Missing Roundabouts challenge. Most people had not used MapRoulette before, so I was glad that everyone was getting the hang of it quickly. Most of the problems and questions were not about MapRoulette but about what is a roundabout exactly, and what is the difference between a roundabout and a mini_roundabout and a traffic_circle. (The OSM wiki helps out a little here.)
At the end of the evening, the mappers in the room already made a good dent in the challenge, which has more than 4500 tasks total.
I had a great time, thanks to Bea for organizing the OSMTime events every month and spreading the word. If you are in the Cluj-Napoca area, you may want to subscribe to the OSMTime meetup so you know when the next one takes place. Or look for an OpenStreetMap meetup in your area and meet local mappers!
We added more than 800 thousand new road tiles to ImproveOSM all over the world. The anonymous GPS traces are sourced from INRIX, a company that provides traffic and connected car services. We are extremely excited to have such a huge boost to ImproveOSM and to OSM itself!
If you haven’t tried ImproveOSM recently, why not head over to improve-osm.org right now and explore the millions of missing roads, one-way streets and turn restrictions detected from big data analysis on anonymous GPS traces from drivers all over the world?
This summer, we launched OpenStreetView and received great response both from the OpenStreetMap community and the press.
After only 4 months, you have already contributed almost 12 million images covering 322 thousand kilometers. We have released open source apps, upload and OpenStreetMap editing tools, and are working on many improvements aimed at improving OSM faster than is possible now.
As part of our fast growing public profile, we have also attracted the attention of Google Inc, who holds the ‘Street view’ trademark. They are really interested in OpenStreetView but also expressed concerns about the name creating confusion. Obviously to us this confusion does not exist, but after considering the pros and cons carefully, we decided to change the name.
From now on, OpenStreetView will be known as OpenStreetCam.
Aside from the name, nothing changes. In fact, we will be launching some pretty cool new features and improvements very soon, so please stay tuned for that. If you have not tried OpenStreetCam yet, why not download the free and open apps for Android or iOS, explore the coverage or start editing with OSC in OpenStreetMap?
With the help of ImproveOSM, Telenav’s project to analyze billions of GPS points to detect missing roads, one-ways, and turn restrictions, you have already looked at 60,000 missing road tiles, 15,000 one-way suggestions, and 2,000 turn restriction suggestions since the project launched in September 2015.
Today, the Telenav OSM team has released a completely new version of the ImproveOSM web site. ImproveOSM.org is now entirely based upon the OpenStreetMap iD editor. The new ImproveOSM combines the benefits of the familiar, user-friendly iD editing environment with the power of ImproveOSM detections.
The new ImproveOSM web site showing missing roads.
Since the new web site is based on iD, it should look very familiar and you should have little trouble getting started with it. The main difference you will see is that the ImproveOSM version of iD has a special panel, which shows ImproveOSM specific options, actions and information. If you have used ImproveOSM before, these will be familiar to you. You can mark items as solved or invalid and apply filters to determine which detections you see.
I do not want to go into too much detail in this post, but I do have a quick power tip: following up on many requests from you, you can now select multiple missing road tiles more easily by pressing shift and selecting one tile. This will automatically select all adjoining tiles within the current view.
Our goal is to integrate the ImproveOSM functionality into the main iD editor over time. To make that happen, your feedback is really important, so please do not hesitate to report bugs and ideas on the project GitHub page, where the source code will also become available soon.
We hope you enjoy the new ImproveOSM web site and look forward to your feedback! Happy mapping!
The team has been working on some nice updates to the ImproveOSM JOSM plugin. I have been taking the new version for a spin and wanted to report back.
In case you need a refresher: ImproveOSM is a suite of tools (currently a web site and a JOSM plugin) that takes the results of a massive data analysis comparing billions of GPS data points with existing OSM data and displays them in a way that makes it easy for any mapper to improve OSM with missing roads, turn restrictions, and one-way tags.
The improvements are fairly small but gave me a noticeably nicer workflow, so I thought it would be worth sharing.
The first improvement is that you can now right-click on any of the ImproveOSM layers in the layer panel to access the data filtering options for that layer.
The data filters let you see part of the data for that layer based on various criteria, such as number of trips, confidence level, status and others. The criteria available vary by layer. Here is the filter window for Missing Roads, for example:
The filters themselves are not new, but you needed to go to the ImproveOSM panel to access them before. I think this is way quicker.
Another thing I really like is the improved visualization for the turn restrictions. The team made it much easier to see the from-via-to flow of the suggested restriction. The from-segment is now green and the to-segment is red. When selected, the info panel will also display more useful information than before:
The detailed info panel was improved for the other categories (missing roads and one-ways) as well.
Finally, when you are done mapping an ImproveOSM thing, you can now quickly mark the thing as invalid or solved, without having to enter a comment. We realized that this was not a very efficient workflow. You can still add a comment upon closing the issue, but now it’s easy to do it without, by right-clicking on the ‘solve’ or ‘invalidate’ buttons and selecting the appropriate action.
These small but meaningful improvements made my work with ImproveOSM in JOSM much more efficient. We are always looking for more ways to make ImproveOSM better. If you have used ImproveOSM and you have a few minutes to spare, I would appreciate it if you filled out this survey. Thanks a lot!
In a new data release today, we added about 500 tiles worth of missing roads in and around Guatemala!
We are excited to be adding more and more Missing Roads data to ImproveOSM using GPS data from our own users as well as from data partners, like we did in Brazil and in this case.
You will notice that the tiles look a little different from the ones you are used to if you have used ImproveOSM before: they don’t show the individual points. This is because this particular data was processed a little differently. If you use JOSM, you will also see an update to the ImproveOSM plugin to accommodate this change.
While you are looking at the new Missing Roads, perhaps you will also notice some other recent improvements to the ImproveOSM web site. We re-ran all tiles based on new map data from mid-April, and we improved our turn restriction detection so we won’t show a missing turn restriction when OSM already has a ‘only straight on’ restriction.