Pieren: You have discovered a bug. bridge=viaduct was not processed and will appear as false positives. We are working on a fix! This is less than 1% of bridges in the US, most are just bridge=yes. We discovered another bug where we did not recognize _link ways that are also tagged as bridge (or tunnel). This is also being fixed.

Thanks for reporting!

Thanks @Alan, fixing…

jumbanho - those are excluded for now, but it’s a good idea for a followup challenge.

Thanks for this write-up - Osmium and the tools that use it can be a little tough to get into, and articles like these help.

I have used osmjs, the Javascript v8 interface to Osmium, for a few projects that may be of interest to you - see this diary entry for a discussion.

Sorry for the intermittent problems, folks! I hope everything works well again now.

We actually added a new feature, more about that in a new diary entry soon. It’s already live on MapRoulette.org - can you find it? :)

Fantastic job, Werner. Thank you for taking on this big effort of closing out all these ‘forgotten’ OSB’s.

Katie: there’s no strict rules! As many as you think makes it look decent. Be sure however that you are zoomed in far enough to really see the road well on the aerial image. (You should be able to see the markings on the road, and cars, if there are any.) I would also suggest that that it’s not necessary to put any additional nodes on straight parts of the way, as those do not add any useful information.

Chris: That is a very good point, and I should (and will!) include a note of caution to MapRoulette users. I am sorry I messed up data in your area, and thanks for watching over it.

robbieonsea: These are Telenav traces only - so yes, these are driving traces, not walking or cycling.

The confidence level is a simple ratio of traces going in one direction versus traces going in the other, and for the results that are in this particular MapRoulette challenge, we set the threshold at 95%, meaning that for a way to be flagged we will see at least 95 out of 100 traces going in one direction for that segment. There is also a minimum threshold for the number of traces we want to see, but I cannot recall what that threshold is.

Incidentally, what you see right now is the first batch of 5000 tasks out of a total of over a hundred thousand, and I will load them sorted by the number of traces. So the tasks you are seeing in MapRoulette today are the ones that have the most traces attached to them.

Ideally, as Mappo also mentioned, this challenge would be fed to tools that allow for on site verification. Osmose is a good candidate, especially now that Frederic is doing a ton of work to make that tool mobile-friendly. I have been working with Frederic over the SOTM US weekend to build a bridge between Osmose and MapRoulette, so we will see an exchange of tasks / challenges between these two QA tools in the near future.

Thanks everyone for the feedback!

Welcome to OpenStreetMap! If you want some help with your first steps, LearnOSM can be helpful - unfortunately not in Chinese (yet). http://learnosm.org/en/beginner/

Or just ask here, or on the live chat at irc.osm.org - happy mapping!

hobbesvboyle: The tasks need only one person to say it’s fixed (or not an error) for them not to appear again. The reason you are seeing what seems to be the same task twice is that the logic that detects these sharp angles sometimes operates on parts of ways, so one way that has multiple sharp angles may appear twice. Also, folks often choose to load a bigger area once they fixed the error, as it’s often obvious that there’s more things to be fixed. In the process, they may be fixing what are separate tasks in MapRoulette :)

Stalfur: I am writing up a challenge creation guide. I will post a diary entry when that is done.

They are almost never ending….I only loaded the first ~6000 of them, around 90000 more to go after that…

Ben - Thanks again for taking part and for the great summary, and congratulations :) !! We (speaking as a Telenav employee) knew this was going to be a challenge not only for the participants but also for us. We learned some things along the way, and the new iteration of the contest (started yesterday) channels participants to MapRoulette so we can be more certain that we get quality edits. Let me know if we can do more to improve on the contest idea. I do believe a contest can be a good tool to help improve OSM faster, and I am eager to get it right.

And as for MapRoulette - it’s an open source project and while I initially came up with the idea, the current version is as much Serge’s work as it is mine. So credit where credit is due. Also, anyone with a good idea for a challenge and some server resources and scripting skillz can submit challenges to MapRoulette. I will be writing up a how-to some time soon. Let me know if you are interested!

we’re live at maproulette.org!

Yes, there is functionality for getting ‘local’ challenges although it is not fully leveraged in the UI yet. MapRoulette remains more suited for bugs that do not require local knowledge, however.

Mobile is not planned for the immediate future, but MapRoulette does have an API now that could potentially be opened up for third party apps.

Sorry - there was a server hiccup…

Good one - I had something similar, but more specifically geared towards the Pushover notification platform for Android / iOS phones: https://ifttt.com/myrecipes/personal/1634033

Good one - I had something similar, but more specifically geared towards the Pushover notification platform for Android / iOS phones: https://ifttt.com/myrecipes/personal/1634033

Good one - I had something similar, but more specifically geared towards the Pushover notification platform for Android / iOS phones: https://ifttt.com/myrecipes/personal/1634033

I think I understand where your skepticism comes from, but I don’t subscribe to your arguments. What happens right now is that folks seek out alternative group contexts for their OpenStreetMap social needs. Meetup is one. Facebook is another. The Forums are also divided up into topical and geographical entities you could see as groups. You see this as a reason not to build our own, but I feel strongly that this is one of the most important reasons why we should. We should make a strong effort to reel that social energy into our own web site, and to add our specific flavor to it in the form of local groups defined by geographical boundaries, benefiting from the OSM internals such as OSM user’s set home location, changeset feeds, diary feeds etc.

You state that most conversations don’t require groups. I would like to propose that most conversations don’t even happen because there is no obvious context for them. As a new mapper just signing up and setting my home location, wouldn’t it be great if I were made aware of a local OSM discussion happening right here on osm.org? Right now, this user gets dropped on osm.org and with some luck, he or she finds the forums (hit or miss, no obvious connection or integration with osm.org other than single sign on), the mailing lists (don’t even get me started) or perhaps even a local Facebook or Meetup group. This all feels very disconnected, and chances are that this new user will not engage in any discussion at all, overwhelmed an not sure where to start.

I see it as our responsibility to provide new (and existing!) users with our own native platform to gather around topics or places of interest, to take away the confusion about the social dimension of OpenStreetMap. You say it’s hard to get it right, an argument I don’t get at all. If we keep it lightweight and flexible and start out modestly, I think it’s not hard at all.

The part of your argument I have the most trouble digesting is that you suggest yet another third party platform (Discourse) to route our users to. How does that not just add to the confusion? Discourse is shaping up to be a great discussion platform, but it doesn’t offer the tight integration with OSM data that our own groups will be able to benefit from. To my mind, this is one of the big benefits of rolling our own groups - we can connect local mappers to each other and to the data.

Some of your suggestions for improving current functionality make sense, but they don’t add up to anything nearly as powerful as a group context.

Agreed, a great conference excellently captured. Looking forward to working together more and keeping the momentum.