<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div dir="auto">There is noticeable (but not very high) number of surface=granite /<br></div><div dir="auto">surface=marble and other similar tagging type of stone into surface tag.<br></div><div dir="auto"><br></div><div dir="auto">-------------------------------------------------------------------------------<br></div><div dir="auto"><br></div><div dir="auto">There was some discussion on<br></div><div dir="auto"><a href="https://community.openstreetmap.org/t/type-of-stone-in-surface-surface-granite-and-similar/9424">https://community.openstreetmap.org/t/type-of-stone-in-surface-surface-granite-and-similar/9424</a><br></div><div dir="auto"><br></div><div dir="auto">-------------------------------------------------------------------------------<br></div><div dir="auto"><br></div><div dir="auto">Surface=granite blocks distinguishing between<br></div><div dir="auto"><br></div><div dir="auto">surface=paving_stones<br></div><div dir="auto">surface=sett<br></div><div dir="auto">surface=unhewn_cobblestone<br></div><div dir="auto">surface=rock<br></div><div dir="auto">etc<br></div><div dir="auto"><br></div><div dir="auto">surface=granite may be any of following:<br></div><div dir="auto"><br></div><div dir="auto">Exposed raw rock (surface=rock / surface=raw_rock)<br></div><div dir="auto"> <a href="https://wiki.openstreetmap.org/wiki/File:Half_Dome_ropes_4.jpg">https://wiki.openstreetmap.org/wiki/File:Half_Dome_ropes_4.jpg</a><br></div><div dir="auto"><br></div><div dir="auto">Natural stone machined into a flat surface (surface=paving_stones)<br></div><div dir="auto"> <a href="https://commons.wikimedia.org/wiki/File:Pretty_natural_stone_used_for_paving.jpg">https://commons.wikimedia.org/wiki/File:Pretty_natural_stone_used_for_paving.jpg</a><br></div><div dir="auto"><br></div><div dir="auto">Flattened stone, but still not entirely flat and not covering entire<br></div><div dir="auto">surface (surface=sett)<br></div><div dir="auto"><a href="https://commons.wikimedia.org/wiki/File:Granite_Setts.jpg">https://commons.wikimedia.org/wiki/File:Granite_Setts.jpg</a><br></div><div dir="auto"><br></div><div dir="auto">Raw cobblestone of natural, uncut, rounded stones.<br></div><div dir="auto">(surface=unhewn_cobblestone)<br></div><div dir="auto"><a href="https://commons.wikimedia.org/wiki/File:Ancient_road_surface.jpg">https://commons.wikimedia.org/wiki/File:Ancient_road_surface.jpg</a><br></div><div dir="auto"><br></div><div dir="auto">Stones or plates individually arranged in a row, allowing to walk on,<br></div><div dir="auto">surrounded by an unpaved medium such as grass or water<br></div><div dir="auto">(surface=stepping_stones)<br></div><div dir="auto"><a href="https://commons.wikimedia.org/wiki/File:River_Rothay_stepping_stones_120508w.jpg">https://commons.wikimedia.org/wiki/File:River_Rothay_stepping_stones_120508w.jpg</a><br></div><div dir="auto"><a href="https://wiki.openstreetmap.org/wiki/File:Stepping_stones_-_geograph.org.uk_-_832601.jpg">https://wiki.openstreetmap.org/wiki/File:Stepping_stones_-_geograph.org.uk_-_832601.jpg</a><br></div><div dir="auto"><br></div><div dir="auto">surface=gravel and surface=pebblestone and maybe some other would be<br></div><div dir="auto">valid.<br></div><div dir="auto"><br></div><div dir="auto">(note: specific photos above may be not necessarily depict granite, but<br></div><div dir="auto">`surface=granite` could also take such forms) (if you have a better<br></div><div dir="auto">photo then improving<br></div><div dir="auto"><a href="https://wiki.openstreetmap.org/wiki/Tag:surface%3Dgranite">https://wiki.openstreetmap.org/wiki/Tag:surface%3Dgranite</a> would be<br></div><div dir="auto">highly welcome)<br></div><div dir="auto"><br></div><div dir="auto">-------------------------------------------------------------------------------<br></div><div dir="auto"><br></div><div dir="auto">So instead of surface=granite using material=granite would be<br></div><div dir="auto">preferable.<br></div><div dir="auto"><br></div><div dir="auto">For example instead of:<br></div><div dir="auto">highway=pedestrian surface=granite<br></div><div dir="auto"><br></div><div dir="auto">following tagging would be better:<br></div><div dir="auto">highway=pedestrian material=granite<br></div><div dir="auto"><br></div><div dir="auto">This makes space for tagging surface=sett or surface=unhewn_cobblestone<br></div><div dir="auto">or surface=paving_stones etc<br></div><div dir="auto"><br></div><div dir="auto">I think that it would be much better to tag and such migration can be<br></div><div dir="auto">done with an automatic edits.<br></div><div dir="auto"><br></div><div dir="auto">So I am proposing following replacements:<br></div><div dir="auto"><br></div><div dir="auto">surface = granite → material = granite<br></div><div dir="auto">surface = granit → material = granite<br></div><div dir="auto">surface = marble → material = marble<br></div><div dir="auto">surface = sandstone → material = sandstone<br></div><div dir="auto">surface = laterite → material = laterite<br></div><div dir="auto">surface = limestone → material = limestone<br></div><div dir="auto">surface = limerock → material = limerock<br></div><div dir="auto">surface = chalk → material = chalk<br></div><div dir="auto">surface = basalt → material = basalt<br></div><div dir="auto"><br></div><div dir="auto">Edits will be not made where there is already material /<br></div><div dir="auto">paving_stones:material tag with a mismatching info.<br></div><div dir="auto"><br></div><div dir="auto">Edits will be made where such surface tags are present now or will<br></div><div dir="auto">appear in future.<br></div><div dir="auto"><br></div><div dir="auto">There are also surface=steel, surface=aluminium and surface=iron but<br></div><div dir="auto">these are trickier and not proposed to be edited here (I guess that<br></div><div dir="auto">leaving surface=metal would be useful and surface=iron should only be<br></div><div dir="auto">changed to surface=metal as it is really unlikely to be correct)<br></div><div dir="auto"><br></div><div dir="auto">Why it is useful? It helps newbies to avoid becoming confused. It<br></div><div dir="auto">protects against such values becoming established. Without drudgery<br></div><div dir="auto">that would be required from the manual cleanup. It also makes easier to<br></div><div dir="auto">add missing surface= values<br></div><div dir="auto"><br></div><div dir="auto">Why automatic edit? I have a massive queue (in thousands and tens of<br></div><div dir="auto">thousands) of automatically detectable issues which are not reported by<br></div><div dir="auto">mainstream validators, require fixes and fix requires review or<br></div><div dir="auto">complete manual cleanup.<br></div><div dir="auto"><br></div><div dir="auto">There is no point in manual drudgery here, with values obviously<br></div><div dir="auto">fixable.<br></div><div dir="auto"><br></div><div dir="auto">This values here do NOT require manual overview. If this cases will<br></div><div dir="auto">turn out to be an useful signal of invalid editing than I will remain<br></div><div dir="auto">reviewing nearby areas where bot edited.<br></div><div dir="auto"><br></div><div dir="auto">Yes, bot edit WILL cause objects to be edited. Nevertheless, as result<br></div><div dir="auto">map data quality will improve.<br></div><div dir="auto"><br></div> </body>
</html>