As explained earlier, OSM does add 'Railway Station' to names of those stations. Please revert.

As per my direct message, could you please refrain from make inaccurate edits.

Are you sure? - osm.org/way/89379029

Thanks

Hi Alan
Could you clarify what you've amended in this Changeset please?

OK I've updated to make it slightly more accurate. I made the building an office & added a separate node to indicate the shop. Needs a subtag to indicate what it does/doesn't sell..

Hmm... I thought the Sustrans building was their HQ. Can you bike bikes there?

Hi Welcome to OSM.
This node looks a little out of place so close the the highway. You'll notice similattags, such as the Airport Tavern, are set back from the road close to the centre of the area they're representing, If you know where the car rental is located could you move the node to that position?

Yes, but I think Tagging is the more appropriate forum.

-----
I need to clarify I reverted the edit, not due to 'tagging choices', but that there were three different George Pubs. All Mar Mar's additional tags have been added to the existing way. Between us we've made the OSM database more accurate & detailed.

Good question, & one I've thought about but come to no concrete conclusions. I believe there should be some kind of tag, be it amenity=place_of_worship or some other tag, to define the extent of a place of worship's property which could encompass things such as the building, graveyards, church halls, car parks etc. I'm in two minds whether building=church/synagogue etc. automatically defines where the actual act of worship takes place so frees up amenity=place_of_worship to be used on the boundary.

@SK53
The reason Mar Mar added amenity=pub (well, restaurant actually), not only to the building but as a node, was his failure to notice the boundary & the icon in both the render & the editor, not due to tagging choice .
'Retail' isn't a substitute for defining a boundary of individual premises.
@Ed
The wiki appears to be out dated & doesn't take into account detailed mapping. Wiki pages should be amended to suit tagging practices, not the other way around.

Thanks for the replies

Please don't tag incorrectly to suit a failing of just one renderer. Remember this is a database & their are many different renderings taken from it.

Similar to schools, the amenity=* tag should be a closed polygon encompassing the full area of usage by the organisation with individual entities mapped within. This removes the need for explicit tagging (the car park's name could be removed) or relations, which shouldn't really be used just to collect entities together.

Any failure to notice the icon might be overcome if those in charge of mapnik carto might be persuaded to render the polygon. So far, they appear extremely reluctant to do so.

The George is already there.

Could you contact the app's creators please & let them know that trunk roads are assumed accessible by foot.

Do you know why it's only a few disjointed sections?

Which app was failing to interpret OSM data correctly?

Hi Miko

FYI I've started a discussion on the Tagging forum regarding using relations to tag bridges.

No problem, Marcus. Details like this are what make OSM better than other online maps. Keep mapping.

Hi Readie
Welcome to OSM.
I've amended your bike parking slightly duplicating both node & polygon would have made the total parking spaces = 40.

If you draw rectangular boxes there's an option to 'square them up' in the toolbar

Cheers
Dave F.

You appear to be misunderstanding. It's not the linear ways (waterway=river) that's the problem, but the polygon denoting the riverbanks.(waterway=riverbank).

It's disappointing you can't see the clear benefit of not tagging canal banks as river banks.

Hi Malcolm
Being in the majority doesn't automatically make it correct nor a reason not to change. If a better way to tag is conceived, making it easier for the data to be used, then it should be adopted. As in previous occurrences this is a gradual process often brought about by messages like mine.

Changing a valid tag for a non preferred one does not improve the database.

I originally tagged waterway=riverbank. A couple of months later the newer way was point out to me. I was mildly irritated as I'd spent a lot of time tagging them, but I saw it was an improvement, so put in the extra time to amend them.