The Dutch translation was only changed on Monday, and there hasn’t been a sync from Translatewiki since then - that usually happens once a week or so, typically at the weekend.

I’d suggest something like:

• name = Embassy of Brazil
• addr:housename = Palazzo Pamphilji

which is certainly what I’ve done before (eg osm.org/browse/way/123243789) though this is a little different as both names are actually in common use.

You did agree, but other people that edited the same objects presumably didn’t.

Given that the yahoo imagery is gone it would make more sense to delete the whole thing. That boundary never belonged in the database anyway.

Well have you ever followed the correct procedure for data sourced from in appropriate sources and (a) asked the person adding it to remote it and (b) if they fail to do so then to report it to the Data Working Group?

We're already making plans for a mapping party there in the next few weeks.

Yes and no - there is a second side to the issue here in that the "more detailed" data is harder to maintain and hence increases the maintenance overhead which may not fall on the person that contributed the more detailed data.

Personally once an area gets details (ie has buildings) I tend to delete the landuse altogether as it is very annoying to maintain, and makes maintenance of roads etc much harder, and is of very little benefit.

If it is present then I like to share it with the road so that the edges move properly as the road is refined over time.

Let me be completely clear, there are absolutely no limits on how many edits somebody can make in a given period of time.

The only limits we have are on the rate at which data can be downloaded - there are no upload limits.

If you want to close a changeset then press "C" and the next time you save it will open a new changeset and ask you for a description again.

BTW the reason pinch zoom doesn't work on Android, even with 2.11 is that the browsers don't expose the event to javascript.

What exactly is the problem that you had with osm.org?

I mean touch events don't work on the map, we know that, but that is just because OpenLayers doesn't support them yet. When OpenLayers 2.11 is release we will upgrade to it and be able to support touch events on the map.

Is there anything other than that which you had a problem with?

I'm not quite sure why you would want to do this? It seems unlikely that the location recorded by your camera will actually match the location of any real world object that you would want to add to the map - rather it would record the location where you stood to take the photo of the object.

Sounds like it was maybe a road that was planned (and the plan provided to OS by the council) but never actually built beyond the lowered curb.

No it is absolutely not OK to use Bing Maps as a source of street names.

You can use the Bing Aerial Imagery for tracing, but you cannot use the Bing maps.

Roads don't have an RGB colour. Renderings of roads do. So you will have to at least specify which rendering you are talking about...

What exactly is the suggestion you're making? That we should ignore Google's terms of use and use Streetview as a source for mapping?

Actually all the evidence is that a lot of it is human driven, not bots.

Only a tiny proportion of the spam ever appears anyway - most of it is stopped dead by our anti-spam systems without ever being seen.

The procedure is set out in the wiki:

osm.wiki/License_violations

In this case it would probably be very hard to pursue the first step of trying to contact Google directly as it would be very hard to reach anybody with any power.

I have drawn your diary post to the attention of appropriate people anyway.

Or carry on using Potlatch 1 which is still available as an option.

To explain to anybody reading this who may be wondering what on earth you are on about, this is the message you get when using the "Export" tab to try and export a map from the mapnik layer.

It's not broken as such, but those exports run on the main tile server and it's main job is rendering and serving tiles for the map so when it is busy (as it generally is during the day) it will refuse to serve expensive export requests in order to be able to keep up with rendering and serving tiles.