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!

Not all of the bike shops available in the bike hub app are in openstreetmap yet - check out

http://shaunmcdonald.dev.openstreetmap.org/bike-shop-locator

... and help track down the ones we don't have yet!

Glad to see someone treading carefully - and more importantly realising when it's not worth it! Sometimes I think when people have such high expectations of an import they aren't willing / able to back down when they realise it's not of the quality we aspire to.

Interesting to hear your thoughts on NHD, and I think it would really help to promote your methods of using the data, through documentation and blog posts like this.

Unless you're putting demonstratably false data into OSM and seeing it on Google, it's hard to be conclusive. If you're just adding the correct name - regardless of it not being in some other datasets you mention - it's hard to prove that someone else hasn't also independently corrected it in Google. After all, they have their Map Maker project where someone else just like you could be fixing things for them.

A deliberately incorrect tell-tale - like the famous Lye Close - would be more convincing.

osm.wiki/Copyright_Easter_Eggs#Printed_Maps_that_.22Lye.22

Your quote from the Contributor Terms is a false quote, since you've chosen to remove some words from the start of the first sentence that you are quoting. Funnily enough, these extra words are there for good reason. By removing important words from the CTs you can make them say all kinds of different things, you know.

As for the memorandum of association stuff, that's a different issue. Given that they are a) boilerplate and b) currently under review anyway, I don't see why it's such a big deal to stop you from contributing to OpenStreetMap. Instead it would be nice if you joined in with the OSMF working group that's looking into the MoA and lend a hand, how about it?

Try the osmosis plugin TagTransform - osm.wiki/Osmosis/TagTransform

Your basic premise of the whole discussion is false - you can certainly have overlapping polygons in OSM, and I've no idea why you would think otherwise.

As for the grass on a building thing, that's fine, just use the layer tag to describe how objects are related vertically.

Please rename your project - we already have osm2pgsql and so this new project will lead to huge amounts of confusion.

Good stuff - It's great to see the level of detail that you're adding.

Great to see your enthusiasm - I hope you manage to recruit more cycling mappers!