OpenStreetMap generally has the concept of "default" values, to save everyone time and effort. One example would be that if there's no oneway tag on a road, it's assumed to be two-way.

You can take the same approach to frequencies on powerlines. Perhaps life is too short to worry about tagging every powerline in Europe with the frequency - simply tag the (presumably very few) examples where this is not the case. As Sanderd17 said, when people use the data they can set sensible interpretations for when the frequency tag is missing.

I'm with Chaos on this one.

Great to hear about the progress on this - would love it if you can keep everyone up to date with how you all get on.

maxolasersquad: see osm.wiki/Community_Code_of_Conduct_%28Draft%29

The google maps charges are per map view as counted by loading their javascript library - so if you keep loading their library, that counts as a chargeable page view regardless of the tiles.

I think Google (quite rightly) see loading their api, which contains tiles, hooks for geocoding, streetview etc as the main thing to be concerned about.

If it's not there, then feel free to delete it. We're not trying to record the former positions of everything that ever has been!

If people keep re-adding it, either manually or via imports, then take them to task about it. Nobody should be adding stuff to OSM unless they know that their data is correct.

You move it!

http://www.wired.co.uk/news/archive/2011-08/19/mappers-targeted-by-police?page=all

From a bit of googling, the northern one appears to be a private airstrip

See osm.wiki/Stratford-upon-Avon/Imagery and osm.wiki/Vertical_Aerial_Photographs#Kites for two ideas

It's not important whether it "messes up" routing or rendering, those can be fixed later. If the track exists, you should map it.

that "forcing" the update makes very little difference, you know. The tiles that need updating (which are figured out when the database is updated) are already marked as needing updating on disk, so just viewing them has the same effect as forcing a refresh like that. Neither method makes my server run any faster though!

Appearing where?

It's perfectly possible, but nobody has got around to it yet. We're all volunteers and all have our own todo lists and priorities, and it'll only happen when it (eventually) becomes the number 1 priority for one of the developers.

If you don't have the development abilities yourself, then you could either learn how to do it, or try to make it someone else's #1 priority! Maybe find some developers, buy them a pizza or find something that they would like done in return.

Great stuff!

Great to hear about more mapping in Cornwall, and I hope your proselytizing has encouraged your friend to help too!

The touch limitations of our version of OpenLayers are well known. The latest version has just been released and should work better, but we're always looking for more developers to help with tasks like this.

It would be great to see more mapping parties being held!

Yeah, I'm really sorry about the recent delays to the updating. The root cause is the one server trying to do too many things at the same time - updating the database, rendering all the new tiles, and serving the tens of thousands of people hammering away at the server.

I've spent the last two days configuring another caching proxy in front of the tileserver - the first one has lightened the load, but it needs another. Most importantly the new one has got throttling to help deal automatically with people who are mass-downloading tiles. I've also got a few minor updates to the rendering side of things to help it go faster too.

I'll keep working on it (of course) and hopefully things will go better. It's all a question of time spent doing this, and when I need to spend days working on it then real work gets in the way!

I'm with Pink Duck on this one - there's no point in tagging no_exit, the software figures out whether it's a dead end or not. It's a cargo cult tag.

I'll second Richard on this one - the potlatch2 developers have a strong and impassioned sense of editorialism with the tagging presets, and certainly aren't swayed just on raw usage numbers - otherwise we'd be at the mercy of tag-changing bots!