OMG, I just came across this for the first time (via the OSMUS-Slack), Soooo accurate!

Thanks for writing this up! I nocticed that there’s a small typo in step 16: mapillaary vs mapillary

@stevea Thanks! That means a lot to me.

@b-jazz Thanks for the feedback. I edited the post to add some intermediate steps that make it more obvious what’s going on. You don’t use the “search” function, but add the filter in the filter pane (which may or may not be activated for you). Please let me know if the new version of the description makes more sense.

I don’t have an answer for your side streets or ToDo plugin questions unfortunately, but maybe this is less of an issue when you have the filtering set up properly.

Are we all done with the challenges or is maproulette broken at the moment? I can’t get it to load any further tasks.

@Katie U: I’ve encountered lots of those in MA where they seem to come from an import. I usually simplify those ways (NOT using JOSM’s default setting, as its way too coarse) and then manually confirm that things look good. Usually I have to add in a few nodes again.

Another observation: Some of the ways I came across had 5 or more changes in the last few days, presumably all related to the roulette. How many times does a task get assigned before it is marked as fixed?

Nice challenge. I noticed that there are a lot of false-positives with highway off- and on-ramps. Maybe it would make sense to filter those out for the remaining 90000?

Thanks for organizing, it was a lot of fun!