You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When boundary=marker is shown, text from operator= is shown. I've seen this for boundary posts in Dartmoor marking the boundaries of the military training area. It arguably clutters the map.
In the UK, boundary=marker & operator=* is rare. Overpass shows it's mainly the markers on Dartmoor, and several in the East of England. https://overpass-turbo.eu/s/1ReI
Looking at other markers it appears the text shown is the operator, and the name or description
I feel this arguably clutters the map, and would suggest dropping the operator tag.
But I can see merit in the display of data, and it can be argued this issue is simply the large number of nearby markers. An issue that could happen with any object that occurs in large numbers in small areas.
The text was updated successfully, but these errors were encountered:
Yes, that doesn't look ideal. What would make more sense would be to either (a) make it red instead of brown (as already happens for military signs and some other military stuff) and/or (b) exclude boundary markers from "operator" tagging (some items are already excluded).
When boundary=marker is shown, text from operator= is shown. I've seen this for boundary posts in Dartmoor marking the boundaries of the military training area. It arguably clutters the map.
https://www.openstreetmap.org/node/1312872895
https://map.atownsend.org.uk/maps/map/map.html#18/50.63167/-3.95238
In the UK, boundary=marker & operator=* is rare. Overpass shows it's mainly the markers on Dartmoor, and several in the East of England.
https://overpass-turbo.eu/s/1ReI
Looking at other markers it appears the text shown is the operator, and the name or description
https://www.openstreetmap.org/node/11960798203#map=19/52.378548/1.027859
https://map.atownsend.org.uk/maps/map/map.html#18/52.37855/1.02724
I feel this arguably clutters the map, and would suggest dropping the operator tag.
But I can see merit in the display of data, and it can be argued this issue is simply the large number of nearby markers. An issue that could happen with any object that occurs in large numbers in small areas.
The text was updated successfully, but these errors were encountered: