The Rio de Janeiro favelas should be good candidates for a resident-led slum mapping, like happened in Kibera. I wonder if there are big OSM contributors living in Rio who could mentor this.

The most common way to convert pixel values to a shape (the term ‘contour lines’ is usually associated with relief) is to use a “lakewalker” algorithm (surely not the proper COMP-SCI term, I’m just using the name of a JOSM plugin here). You can use other tools, but that one should work relatively well.

Go ahead and try it actually: install the scanaerial JOSM plugin and use it on one of the dataset’s imagery. You’ll get a feel of how well it works. Don’t upload your work unless you have checked that the license is OK. Now think about doing this automatically at a larger scale, and about conflating this new natural=wood with any existing osm data.

My guess is that doing this automatically (as an import) will look much less appealing to you after this experiment. But using the dataset as a source to manually run scanaerial on might still be a time-saver. Sometimes, you’re better off doing it manually than algorithmicaly. Your call.

Concerning the Bing vs Landsat argument, consider the fact that Mapbox updates its landsat source (wherever no highres imagery is available) automatically, and is going to be much better than a 2010 non-averaged snapshot used by that dataset.

In my experience, import of landcover data is near-impossible to get right.

For example the Corine data was imported in France, and the amount of post-import work to disentangle the result and conflate with pre-existing data is still ongoing. It would probably have been faster to do everything ourselves via satellite imagery. In Ireland we did all the pre-import work, evaluated it, and concluded that it would do more harm than good.

This dataset doesn’t look much more appealing: it’s guaranteed to have both false-positive and false-negatives, it is based on images much older than what’s currently available, you’ll have to use a lakewalking algorithm to vectorize it (which pretty much always require manual touches afterwards), and only then can you start dealing with the conflation problem (which is a biggie).

IMHO It’s a great dataset to use at low zooms, but not for the OSM usecase. Time would be better spent tracing by hand.

I have seen a lot of roundabouts constructed “preemptively” when there isn’t yet a 3rd road connected to it. The plan is probably always to have more roads connected to it, but that might be many years away if it happens at all.

It’s not clear what you’re asking for.

• If you want to get the OSM data there are many sources, for example geofabrik extracts or the osm.org export tool.
• If you want to improve the map you can just open an editor in an area you know, or check the beginner’s guide first.
• If you want government data that isn’t already open, you’ll need to talk to the government. But first check the wiki’s Nigeria page and in particular its existing imports.

Neither option solves the fundamental problem (improving our anti-vandalism processes and tools). They only ease the pain somewhat for this particular instance of the problem.

But both options fix the wrongness that a hugely successful commercial game is indirectly harming a Free data/software community without any attempt to soften the issue, and maybe even profiting from it without respecting its license.

Note that I’ve been playing PoGo since August, and mapping on OSM since 2010.

Sigh… If abuse from PoGo player is continuing to waste OSM contributor time like this, we should really push for some official response from Niantic to the OSM Foundation.

Either PoGo doesn’t use OSM at all (in that case Niantic should say so clearly) or it does (in that case Niantic must respect the license by crediting OSM, and should acknowledge the maintenance burden they are causing and help somehow).

In the first case, the abuse will hopefully slow down, and in the second case OSM will get some PR, the respect of not violating its license, and hopefully some resources to deal with the abuse.

Osmose and OSMI both also catch self-intersecting ways and multipolys. Don’t think it would catch that particular problem, but they catch many others. Those QA tools will keep you busy. http://wiki.openstreetmap.org/wiki/Quality_assurance

While OSM has that data (quite complete in my experience), getting OSM-based routing apps to issue a warning is going to take a fair bit of outreach effort (given how many apps would need to add the feature).

Insert jokes about americans clinging to demonstrably-flawed election systems here (sorry for the smugness, Eurrope isn’t free from election problems either but the USA’s is quite high-profile).

For what it’s worth (I’m not going to be an OSM-US member anytime soon), switching to STV would IMHO be a great thing to do.

http://mc.bbbike.org/mc/ est une autre installation du même outil, avec notament le fond de carte osmfr.

Or even compare against all the users (in other locations probably) which you didn’t welcome to see if, for example, the retention ratio is better ?

https://tyrasd.github.io/osm-qa-feeds/ is a handy tool to grab more monitoring links. It’d be great to keep it updated with other tools.

Most OSM contributors have areas they specially care about, but don’t get too hung up about people editing “your” data specifically. The OSM data is constantly in flux, with some occasional setbacks in quality but generally moving in the right direction. It’s better to worry/care about a specific region/topic than about the particular set of objects you edited.

Pour supprimer un compte Il faut envoyer un mail à support@openstreetmap.org

https://wiki.openstreetmap.org/wiki/OpenStreetMap_account#Deletion

Cela dit, supprimer un compte qui n’a eu aucune activité ne sert pas à grand-chose. Vous trouverez peut-être plus interessant d’aller sur http://www.openstreetmap.org/user/chap’s/account pour changer l’email et/ou le nom affiché pour votre compte.

Pretty much all OSM surveyer have to deal with that. I find that giving lots of info when locals get curious/suspicious works best.

Be cheerful and use it as an opportunity to evangelize about OSM. Print some small flyers to hand out. Show osm on your smartphone. Show the photos you’ve taken. Be ready to answer the usual “it’s a private road” (It’s actually public, no trespassing needed), “what company do you works for” (it’s a worldwide community of volunteers), “we’ve had burglaries here recently” (I can understand why you were worried when you initally saw me). Compare with Google Map/StreetView (more pervasive privacy issues, harder to fix, lower quality data…). Etc

Un peu vague comme question. Quel critère définis la personne recherchée ?

Getting back on the subject of using the right OSM medium for the right purpose, may I suggest http://help.osm.org/ for questions like this ? It’s made for that, it uses your osm.org login, you’ll get (in my experience) better feedback than on a diary post, and the questions and answers feed a searchable knowledge base.

Regarding the original question, it seems that “unadopted” is purely an ownership/maintainership distinction, and is orthogonal to all the other tags we frequently use (highway=residential/service/track, access=private, surface=*, etc).

So I’d say tag all those first, since they cover all the attributes that OSMers usually care about. Then go ahead and add unadopted=yes, if you know this fact for sure. Just don’t make it imply any physical attribute of the road.

There are currently 89 unadopted=yes in the db. It’d be great if you had the time to write a wiki page explaining what it is, as it’s unlikely to be understood outside of the UK.

What’s an “unadopted road” ?

Also, remember that noexit=yes is only useful as an aid to mappers in unclear cases, and doesn’t actually need to be added to cul de sacs. A bit like oneway=no. Noname=yes is different, because that information can’t be infered from the rest of the data.

Checking the wiki spam page history, the last batch of spam cleanup was in march. Not great indeed, I thought it was more frequent than this.

It may be effective, but I don’t think that diaries are the right medium for spam warnings : people reading them are looking for news about OSM, not routine admin stuff.

Hopefully https://github.com/openstreetmap/openstreetmap-website/issues/841 and its associated PR will be solved/merged soon, so that we finally have a decent reporting system.