I generally go with access=private for staff entrances, car parks etc. I'm not sure that a specific tag for staff adds very much, but you could always look at subtagging. I doubt if anyone has tagged various lawns in Cambridge with access=master; access=fellow and access=scholar :-)

Operationally roundabouts determine priority at a junction: they typically need a minimum of 3 incoming & outgoing roads to be at all useful (of course there are cases with 2 roads whilst a 3rd is being built). These loops at ends of roads present no problems of this sort. I'd suggest the Maproulette challenge should add a test for numbers of input/output roads & if <3 then assume it is not a roundabout.

Turning circle is normally reserved for areas either at the end of the highway or along the highway which are enlarged enough for a car to turn: they are usually mapped with a node (the 115 which are not are likely errors https://taginfo.openstreetmap.org/tags/highway=turning_circle). This is something different it is a oneway loop at the end of the road.

Can I add that the local convention in Nottingham is definitely NOT the addition of pavements as separate ways. Adding pavements makes the data harder to maintain and may complicate routing to the point that pedestrian routing no longer works. Adding a sidewalk tag is the local convention.

Thanks,
Jerry (SK53)

Can you please stop these edits immediately you are creating bad data way/369383412/history

Can you please stop needlessly changing Bing to bing. It totally obscures other changes which you are making. You're changeset comments are not adequate to understand what you are doing. Please discuss this type of edit with the local community first.

Indeed, this is a personal judgement, based on a single use case. There are tens of use cases for the mapping of trees (including "because they are there" & no single user has any arbitrary right to override what is mapped based on a use case. As long as things can be ground truthed (for instance by the pupils) then they belong in OSM.

Can you merge tags from nodes onto your mapped ways? At the moment there area number of duplicated shops (Caffe Nero, H&M etc) and some of these have different sets of tags. I would suggest using JOSM for this rather than iD.

Straightforward actually: if in doubt don't do it.

For hill elevations there are old out-of-copyright OS maps (and possibly some OS Open Data) or elevation from a GPS with a barometer etc. For business names there may be open data such as Food Hygiene, Companies House etc. The actual problem is not what one individual does, but what the collectivity of OSM contributors do: otherwise we could each copy 1 bit of data from, say OS maps, and acquire 500k. The other side is if we want people to respect OSM's rights we should respect those of others.

I a path is a public right of way you can add designation=public_footpath or public_bridleway etc. This helps distinguish any old path from ones which can certainly be used for country walks.

I know the original creator of the path round to the W of the cottage (although not through OSM), and would trust her mapping. The path you've added is on old OS maps as a footpath. Would be interesting to know if anything has changed.

Incidentally, this area, say around Buckleberry & Yattendon, had lots of missing rights of way.

Suspect it's time that some of these Pensic War nodes etc need to be removed! (presumably from 2011 event)

Hi Dyserth,

This tool is a good place to start (I've selected only the intersecting polygon option & pointed it N Wales): http://product.itoworld.com/map/109?lon=-0.17309&lat=51.53694&zoom=13.

I wrote something about these issues a long time ago, but it might still be useful as an overview: http://sk53-osm.blogspot.co.uk/2011/02/exploration-of-bad-polygons.html.

@BCNorwich: this latter statement is incorrect. landuse=farm predates use of landuse=farmland but got used for farmyards. It was therefore decided that a clearer distinction was needed, hence farmland and farmyard. place=farm is something different and should largely be avoided in most parts of Britain.

The idea that by editing tags to some kind of common format will somehow make it easier for data consumers is a pernicious fallacy.

Any use of a speed limit with or without "mph" in the tag will require some form of parsing, error detection and data wrangling. For instance the 11th commonest value is "RO:urban". Other values which need to be deciphered include "none (autobahns in DE I presume), "signals" (M25 etc). Plus the usual tag issues of trailing spaces etc.

As @SomeoneElse says each such edit which adds little to the data and does not really help data consumers makes it harder to deal with genuinely problematic edits.

Before making such changes I would recommend checking against the code base of routers such as Graphhopper, OSRM & mkgmap to see if they have problems with such values. Even then the main place to resolve such problems is in code for consuming the data.

The second problem with changing such values is that you are not addressing issue at source. It is users creating these tags and without persuading the users who are used to tagging it this way, then such tags will continually appear in OSM. Closing the loop involves talking to users, only that will actually improve consistency of tagging in OSM. Even then with free-format tags one always has to anticipate the unexpected.

Patching tags in this way to "make it easier for data consumers" may only encourage some such consumers in unrealistic expectations of OSM data. When their programs fail because of unusual values they'll blame OSM. If they plan around the realities of OSM & program defensively (as anyone who builds DBs from multiple source needs to do) they get the benefits & no surprises.

It's a long time since I was on the Glacier des Rognons but back then the more usual way to start the Haute Route was to traverse under the seracs and the Couloir Cordelier more or less due east towards where the altiport label. This gives a less fatiguing access to the Refuge and allows to climb the Glacier de Chardonnet on the first day (basically a schuss across the flat bit of the Glacier d'Argentiere). In poor conditions it probably has many more objective dangers (serac, avalanche, crevasse).

Welcome to OpenStreetMap.

You can add the name directly to the existing area marked as a farmyard. As it stands a node with a name will not be visible or searchable. Don't worry too much about this the information is there.

Feel free to ask if you want any further advice or help.

For workflow or temporary tagging I would recommend using something like your username as a prefix thus username:munro=no. Such a scheme can also be used for something intended to be more permanent, but for which a unified tagging scheme is not present. Using a common prefix makes it much easier to find all the tags and manage them separately (e.g., removing them after the task has been completed). They also provide a hint to other users that they are not expected to be used for general consumption.

I have reverted this edit. It reused an existing node which belonged to a street in the Netherlands and therefore created a very long residential road. This alone could possibly have cause service problems by forcing many tile re-renders.

I must ask you not to use the Level0 editor for your edits. This is not designed for use by inexperienced editors.

I also must say that edits using the dwc: tags have caught our attention for a number of reasons: non-standard tags for objects which have millions of uses; data possibly with restrictions which make it not compatible with OSM; and biological observations which are not suitable for storage in OSM.

I may also ask the DWG to place a 0 hour block on your account to ensure that you read this & similar edits.

You seem to have added quite a lot of trees in St James's Square Gardens. In fact rather more than my photos show. For instance there is only one large London Plane inside the circular path. Did you just use Bing to add them?

Adding munro=no, marilyn=no etc. to anything mapped as a peak is rather pointless & just clutters up the database, and is very confusing to people not familiar with any particular class of hills. If you must also add prominence which is more generally useful (for instance for excluding the spot heights which some people insist in adding from OOC OSGB maps).