The particular accelerator itself is fairly stationary of course, so surely the tag should be particle:maxspeed=1079252850?

You could try sending a polite message to those other mappers pointing out why you think what they have done is not fully correct. That would be better than just adjusting tags, as otherwise they will continue in the same way.

Surprisingly this isn’t spam.

Except that has the downside of omitting posts by non-English users who wrote their post in English, e.g. Rolf Schinkel

As an aside, OSM’s OS OpenData StreetView tiles are currently years out of date. They could be freely updated if someone has access and knows how to do so.

Spam de Spam spam.

Chaos99: While it is fine to map what is shown as per the street sign, it is less useful for databases search engines to automatically expand/guess abbreviations to match search terms with a canonical form. It is better for the full form to be provided by the mapper somewhere. While the signs are sometimes abbreviated due to physical space limitations, the OSM database has no such issue. With full street name information, renderers can selectively abbreviate via an abbreviation lookup table where necessary.

F*ck = osm.wiki/Public_Domain_Map

F*cking
osm.wiki/Proposed_features/Highway_key_voting_importance

Sh*t
osm.wiki/State_Of_The_Map_2010/Concert_Contest/Mapper_Explorer
osm.wiki/Quotes
osm.wiki/Potlatch_1/Development_overview/FAQs
osm.wiki/Proposed_features/Highway_key_voting_importance
osm.wiki/NL:Potlatch/Development_overview/FAQs

B*stard
osm.wiki/Cycle_routes/cyclability

I would suggest barrier=gate; access=private, presuming the gate is occasionally unlocked by the land owner. The routing agents need to realise that it is not ideal for pedestrian access, so access=no or access=private should do it.

In English, a farm is a general term for everything on a farm site - the buildings, yard and fields. So farmland and farmyard are just more specific terms. I am fine with landuse=farm for a general definition of the purpose of the land. See http://en.wikipedia.org/wiki/Farm for European definitions.

Is there any point recording noexit at all? The data in OSM as used by routing algorithms will determine itself that there's no exit, and they may need to route inside a noexit section too. Other mappers just want to know if somewhere needs more attention, so perhaps use FIXME="Incomplete way" instead on the final node?

That wasn’t there earlier.

Not an attribution for OSM in sight.

Personally I prefer to align the Bing aerial to the OS_OpenData_StreetView tiles based on buildings and junction central points, on the basis that the OS tiles after conversion to WGS84 are still likely the highest precision available in terms of allowable use.

There are already default maximum speed limits on a per-country basis by highway type:
osm.wiki/OSM_tags_for_routing/Maxspeed

So I typically add any exceptional speed limits that couldn't be implicitly derived.

Though the last time I checked Skobbler didn't use any of the implicit defaults, hence a lot of missing speed limit reports on the MapDust site.

Perhaps the first trace was someone using a smart phone in a light aircraft.

Probably because Microsoft could withdraw it (or start charging) at any point, no derivative versions from it could be easily made, requests for feature improvements could be ignored, etc.

I too would like to see addr:housename rendered in preference to addr:housenumber, but for now I'll continue adding an additional name tag to ensure that house names are displayed.

Postcodes are codes associated with addressable properties, not the road itself. Roads can be considered to fall wholly/partially within postcode areas by the outline shape that is made from the properties. In OSM, there is the "postal_code" tag for rough use on a way. Better would be drawing the outlines from the now-legal Bing aerial imagery and then assigning the addr:* fields, including addr:postcode, from local knowledge.

(except where lit=no on them)