https://openstreetmap.org/copyright | https://openstreetmap.org |
Copyright OpenStreetMap and contributors, under an open license |
https://openstreetmap.org/copyright | https://openstreetmap.org |
Copyright OpenStreetMap and contributors, under an open license |
Yes, though that would be what it would referred to as locally for navigation. I have used lower case.
That doesn't make it a name though. We could use that logic to add 'names' such as 'pond', 'gate', 'group of trees' etc. The name tag is for the actual name (proper nouns with a capital letter). Features can be described by tagging with specific tags or using the description=* tag
So in this case instead of
name=limestone pavement
it should be
description=limestone pavement
material=limestone
I plan on retagging this objects to move description from name tag to description tag.
I do second that. While there are cases where descriptions work as names and are referred to locally, this is clearly not the case here. The "name" tag is not a tool for adding arbitrary text to map elements for mere description.
I prefer the tag "bare_rock=limestone_pavement" given here over a mere "material=limestone" since a limestone _pavement_ is a particular form of limestone rock, so this tag allows a limestone pavement to be distinguished from other limestone forms. Just remove the wrongful name tag, and everything’s fine for me.
Fixed in https://www.openstreetmap.org/changeset/57685310