Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
Le 29.03.23 à 14:21, Mateusz Konieczny via talk a écrit : Mar 29, 2023, 00:15 by marc_m...@mailo.com: Le 28.03.23 à 19:38, Mateusz Konieczny via talk a écrit : If someone speaking French would prepare pairs from-to they confirmed to be basically 100% reliable pairs I'll translate the list, it's not that the issue here is the list (thanks for the crow work via talk-fr) it might be more resilient to new cases to treat multiple values separately, case insensitive, and to replace "_et_" " et ""/" with ";" value_in_french corrected_value terre earth herbe grass cailloux gravel gazon_ras short_grass goudron asphalt sable sand bitume asphalt terre_battue clay for tennis pitch, earth for others pierre gravel bois wood macadam asphalt sable_et_terre earth;sand gazon_tres_ras grass sol earth pavés paving_stones or sett pelouse grass Terre earth resine acrylic gravier gravel gazon grass charbon coal béton_poreux concrete + smoothness=good béton_bitumineux asphalt béton concrete terre_et_sable earth;sand synthétique artificial_turf (for leisure=pitch) synthetique artificial_turf (for leisure=pitch) herbe_synthétique artificial_turf (for leisure=pitch) gazon_synthétique artificial_turf parquet wood multiple multi herb grass ciment concrete calcaire rock cailloux_et_galets pebblestone terre_goudron ground;asphalt terre_et_herbe earth;grass terre,_cailloux ground;gravel plastique plastic pierres gravel Herbe_et_cailloux grass;gravel graviers gravel gravier0 gravel carrelage tiles brique paving_stones boue mud bitumen asphalt béton_désactivé concrete banc_de_sable sand terr_et_pierre ground;gravel terre_touvenant ground terre/sable ground;sand terre_roche rock terre_pierres ground;gravel terre_naturelle,_argileuse ground terre_humide mud terre;herbe ground terre_goudrons ground;asphalt terre_et_rochers ground;rock terre_et_pierres ground;gravel terre_et_pierre ground;gravel terre_et_gravier ground;gravel terre_cailloux ground;gravel terre_boue mud terre,_boue mud terre_batue clay terre2 ground terrain_synthétique tartan terrain_en_herbe grass tere ground Sable sand rocheux/felsig rock rochers rock rocher rock polyuréthane acrylic plastique plastic planches wood pierres_sèches rock pierre_et_terre ground;gravel pelouse_naturelle grass pelouse_et_terre grass;ground neige snow Mousse moss métal metal liège cork herbe_naturel grass herbe_et_sable grass;sand gravillons,_béton concrete;gravel gravillons gravel gravillon gravel graviers_et_terre ground;gravel gourdon asphalt goudronné asphalt enrobes asphalt enrobé asphalt empierrée pebblestone diverses multi compact1ée compacted chemin_galet pebblestone chemin_en_terre ground chemin_de_terre_et_herbe ground chemin_de_terre_et_graviers ground;gravel chemin_de_terre ground "champs,_herbe" grass caoutchouc rubber cailloux_et_terre ground;gravel bois_et_goudron/plastique asphalt;plastic;wood blocs_de_roche rock béton_bois concrete;wood béton_bitumimeux asphalt ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
I am not planning to propose automatically migrating ones where situation remains unclear. Mar 27, 2023, 13:21 by dieterdre...@gmail.com: > > > Am Mo., 27. März 2023 um 10:32 Uhr schrieb David Haberthür <> > em...@davidhaberthuer.ch> >: > >> >> Ciao >> >> >>> I added >>> # translating German >>> 'holz': 'wood', >>> 'schotter': 'gravel', >>> 'Gras_Laub': 'grass', >>> to candidate list for the next one >>> >> >> I’m my (Swiss German) opinion "Schotter" is much bigger than gravel, which >> is translated to "Kies". >> Gravel might be passable by bike, Schotter is the foundation under railways >> tracks. >> I wouldn’t want to ride my bike over Schotter! >> > > > there was a discussion recently about several of these terms, including > pebbles and gravel. > The term "Kies" usually means rounded, natural pebbles as can be found in > rivers, while there is also "gebrochener Kies" which means crushed stone. > "Schotter" also means crushed stone. You correctly point out that the largest > grain size is very relevant for usability, you can't cycle on 63mm Schotter, > but you can on 16mm (still not desirable, but a huge difference to 63mm). > There are various terms, and they are sometimes colloquially used with a > different meaning than the definition used by specialists, and they may be > imprecise without adding the grain sizes, so there will probably never be an > unambiguous translation in a single word. > ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
Mar 29, 2023, 00:15 by marc_m...@mailo.com: > Le 28.03.23 à 19:38, Mateusz Konieczny via talk a écrit : > >> If someone speaking French would prepare pairs from-to they confirmed >> to be basically 100% reliable pairs (without some tricky cases where >> given word could mean both surface=asphalt and surface=gravel) >> then I could help replacing them. >> > > I'll translate the list, it's not that the issue > > what i was proposing is to use the translations already done > in the wiki instead of redoing the list in a new place. > especially since there are probably also values in German, > Dutch and any other language in the world > Well, in case of running bot edit I need to provide old value - new value pairs. So yes, if such list would be used in bot it needs to be done in a machine readable form. (for rare values it may make more sense to track down this single uses and fix them or ask authors, Overpass Turbo is useful here) ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
missed one : remplace "; " and " ;" by ";" Le 29.03.23 à 13:29, Marc_marc a écrit : suggestion for this one or for the next one : remplace / by ; _and_ by ; _et_ by ; space by _ concrete_made_paving_stones by paving_stone + material=concrete concrete_ by concrete: ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
suggestion for this one or for the next one : remplace / by ; _and_ by ; _et_ by ; space by _ concrete_made_paving_stones by paving_stone + material=concrete concrete_ by concrete: ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
Le 28.03.23 à 19:38, Mateusz Konieczny via talk a écrit : If someone speaking French would prepare pairs from-to they confirmed to be basically 100% reliable pairs (without some tricky cases where given word could mean both surface=asphalt and surface=gravel) then I could help replacing them. I'll translate the list, it's not that the issue what i was proposing is to use the translations already done in the wiki instead of redoing the list in a new place. especially since there are probably also values in German, Dutch and any other language in the world ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
If someone speaking French would prepare pairs from-to they confirmed to be basically 100% reliable pairs (without some tricky cases where given word could mean both surface=asphalt and surface=gravel) then I could help replacing them. But I do not feel comfortable to do it when I do not speak French at all and would really on dictionary. Mar 28, 2023, 02:28 by marc_m...@mailo.com: > Le 24.03.23 à 19:56, Mateusz Konieczny via talk a écrit : > >> Is any of values below has blatantly clear meaning in your language matching >> some established or missing surface value? And would be also eligible for >> such fixing? >> > > looking at https://taginfo.openstreetmap.fr/keys/surface#values > yes there are indeed 118 french words that should be converted > see below for the list > > due to the number, I wonder if it wouldn't be easier to first do this: > convert everything to lower case and underscores to space > convert "and" to ";" > see if the resulting value is the one listed as the first bold word on the > page https://wiki.openstreetmap.org/wiki/Template:FR:Map_Features:surface > and build a converting table for remain values > > (and the same for any language) > > the list of value in french found via taginfo fr > terre > herbe > cailloux > gazon_ras > goudron > sable > bitume > terre_battue > pierre > bois > macadam > sable_et_terre > gazon_tres_ras > normal > sol > pavés > pelouse > Terre > resine > gravier > gazon > charbon > béton_poreux > béton_bitumineux > béton > terre_et_sable > synthétique > plastic_grid > parquet > multiple > herb > ciment > calcaire > cailloux_et_galets > terre_goudron > terre_et_herbe > "terre,_cailloux" > synthetique > plastique > pierres > herbe_synthétique > Herbe_et_cailloux > graviers > gravier0 > gazon_synthétique > Chemin_de_terre_compactée > carrelage > brique > boue > bitumen > béton_désactivé > banquettes > banc_de_sable > terr_et_pierre > terre_touvenant > terre/sable > terre_roche > terre_pierres > "terre_naturelle,_argileuse" > terre_humide > terre;herbe > terre_goudrons > terre_et_rochers > terre_et_pierres > terre_et_pierre > terre_et_gravier > terre_cailloux > terre_boue > "terre,_boue" > terre_batue > terre2 > terrain_synthétique > terrain_en_herbe > terrace > tere > Sable > rocheux/felsig > rocher > > "revêtement_compact,_mélange_majoritaire_en_gravier_ou_pierre,_avec_des_matériaux_mous_tels_que_sable_ou_argile" > polyuréthane > plastique_glissant > planches > pierres_sèches > pierre_et_terre > pelouse_naturelle > pelouse_et_terre > Parking non goudronné > neige > Mousse > métal > liège > herbe_naturel > herbe_et_sable > "gravillons,_béton" > gravillons > gravillon > graviers_et_terre > gourdon > goudronné > enrobes > enrobé > empierrée > diverses > compact1ée > chemin_galet > chemin_en_terre > chemin_de_terre_et_herbe > chemin_de_terre_et_graviers > chemin_de_terre > "champs,_herbe" > caoutchouc > cailloux_et_terre > caillou_+_riviere_qui_coule_dedans > bois_et_goudron/plastique > blocs_de_roche > béton_bois > béton_bitumimeux > artificiel > > > > ___ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk > ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
Le 24.03.23 à 19:56, Mateusz Konieczny via talk a écrit : Is any of values below has blatantly clear meaning in your language matching some established or missing surface value? And would be also eligible for such fixing? looking at https://taginfo.openstreetmap.fr/keys/surface#values yes there are indeed 118 french words that should be converted see below for the list due to the number, I wonder if it wouldn't be easier to first do this: convert everything to lower case and underscores to space convert "and" to ";" see if the resulting value is the one listed as the first bold word on the page https://wiki.openstreetmap.org/wiki/Template:FR:Map_Features:surface and build a converting table for remain values (and the same for any language) the list of value in french found via taginfo fr terre herbe cailloux gazon_ras goudron sable bitume terre_battue pierre bois macadam sable_et_terre gazon_tres_ras normal sol pavés pelouse Terre resine gravier gazon charbon béton_poreux béton_bitumineux béton terre_et_sable synthétique plastic_grid parquet multiple herb ciment calcaire cailloux_et_galets terre_goudron terre_et_herbe "terre,_cailloux" synthetique plastique pierres herbe_synthétique Herbe_et_cailloux graviers gravier0 gazon_synthétique Chemin_de_terre_compactée carrelage brique boue bitumen béton_désactivé banquettes banc_de_sable terr_et_pierre terre_touvenant terre/sable terre_roche terre_pierres "terre_naturelle,_argileuse" terre_humide terre;herbe terre_goudrons terre_et_rochers terre_et_pierres terre_et_pierre terre_et_gravier terre_cailloux terre_boue "terre,_boue" terre_batue terre2 terrain_synthétique terrain_en_herbe terrace tere Sable rocheux/felsig rocher "revêtement_compact,_mélange_majoritaire_en_gravier_ou_pierre,_avec_des_matériaux_mous_tels_que_sable_ou_argile" polyuréthane plastique_glissant planches pierres_sèches pierre_et_terre pelouse_naturelle pelouse_et_terre Parking non goudronné neige Mousse métal liège herbe_naturel herbe_et_sable "gravillons,_béton" gravillons gravillon graviers_et_terre gourdon goudronné enrobes enrobé empierrée diverses compact1ée chemin_galet chemin_en_terre chemin_de_terre_et_herbe chemin_de_terre_et_graviers chemin_de_terre "champs,_herbe" caoutchouc cailloux_et_terre caillou_+_riviere_qui_coule_dedans bois_et_goudron/plastique blocs_de_roche béton_bois béton_bitumimeux artificiel ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
Am Mo., 27. März 2023 um 10:32 Uhr schrieb David Haberthür < em...@davidhaberthuer.ch>: > Ciao > > I added > # translating German > 'holz': 'wood', > 'schotter': 'gravel', > 'Gras_Laub': 'grass', > to candidate list for the next one > > > I’m my (Swiss German) opinion "Schotter" is much bigger than gravel, which > is translated to "Kies". > Gravel might be passable by bike, Schotter is the foundation under > railways tracks. > I wouldn’t want to ride my bike over Schotter! > there was a discussion recently about several of these terms, including pebbles and gravel. The term "Kies" usually means rounded, natural pebbles as can be found in rivers, while there is also "gebrochener Kies" which means crushed stone. "Schotter" also means crushed stone. You correctly point out that the largest grain size is very relevant for usability, you can't cycle on 63mm Schotter, but you can on 16mm (still not desirable, but a huge difference to 63mm). There are various terms, and they are sometimes colloquially used with a different meaning than the definition used by specialists, and they may be imprecise without adding the grain sizes, so there will probably never be an unambiguous translation in a single word. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
Ciao > I added > # translating German > 'holz': 'wood', > 'schotter': 'gravel', > 'Gras_Laub': 'grass', > to candidate list for the next one I’m my (Swiss German) opinion "Schotter" is much bigger than gravel, which is translated to "Kies". Gravel might be passable by bike, Schotter is the foundation under railways tracks. I wouldn’t want to ride my bike over Schotter! Greetings, habi ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
Quoting collapses ... so I ll answer directly. You asked: Would it make sense to document any of ... And yeah, I would document these and put them into "material=" for the record. If something in a foreign language is "paved" then they missed the point of OSM and its standards. Best one can do, be sceptical, keep it on record but downgrade it and hope some one encountering the wrong designation will correct it. Just my opinion on a workable solution. Yes, you are right "sett" would be more appropriate. I have barely seen actual cobblestones in Germany. On the reruns I don't really have an opinion. You will probably already correct many instances. No idea whether it makes sense to actually rerun, or just wait for the next editor to do this job. Cheers, Klaus On 25/03/2023 09:28, Mateusz Konieczny via talk wrote: Mar 24, 2023, 22:33 by facebook_140f8d4e-9d8f-4d51-a5a7-320f53afc...@vollbio.de: Hi Thanks for the comprehensive explanation. Here some answers: 1. This first part makes sense to me. Thanks! 2. Regarding your questions to document previous values, I would propose to use "material=..." as mentioned under: https://wiki.openstreetmap.org/wiki/Key:surface#See_also which "previous values" you mean? 3. "tierra" and "terra" ... the answer is obvious: "ground". 4. Also, for other languages, which are not clear, I would use the "material=..." key and just put "surface=unpaved", to be on the safe side. If unclear, I will just not touch it (especially as some unclear may describe paved surface) 5. Btw. I saw some German word: holz=>wood, schotter=>gravel, verdichtet=>paved (it means "compacted"), Gras/Laub=>grass, pflasterstein=>cobblestones Could surface=verdichtet be actually surface=compacted? Is surface=pflasterstein a surface=cobblestone (underdefined one) or can it be assumed to be in every single case surface=sett or surface=unhewn_cobblestone ? See https://wiki.openstreetmap.org/wiki/Tag:surface%3Dcobblestone I added # translating German 'holz': 'wood', 'schotter': 'gravel', 'Gras_Laub': 'grass', to candidate list for the next one (I will also review is any of them typically wrong - using aerial images - and is connected to any obvious issues not already automatically detectable) 6. Regarding regular reruns of this, I would put some quality gates into that, like: * Were previous automatic corrections reverted and why? * Does a certain type reoccur often and why? * Do new categories appear and should they become official? I inspect some sample of bot edits and before I run it I get info how many will be changed - so in case of large volume of cases (re)appearing I would investigate what is going on. I am also monitoring PMs and changeset comments on bot account - and I think that someone thinking that it made a bad edit would write. Does it seem enough for you? (I can also run this edit once and once enough new or repeated cases gather then appear here again with similar listing) ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
sent from a phone > On 24 Mar 2023, at 22:35, > facebook_140f8d4e-9d8f-4d51-a5a7-320f53afc...@vollbio.de wrote: > > Btw. I saw some German word: holz=>wood, schotter=>gravel, verdichtet=>paved > (it means "compacted"), Gras/Laub=>grass, pflasterstein=>cobblestones verdichtet is actually „unpaved“ (compacted) and pflasterstein is usually sett, sometimes paving_stones but hard ever cobblestones ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
Mar 24, 2023, 22:33 by facebook_140f8d4e-9d8f-4d51-a5a7-320f53afc...@vollbio.de: > > Hi > > > Thanks for the comprehensive explanation. Here some answers: > > This first part makes sense to me. > Thanks! > Regarding your questions to document previous values, I wouldpropose > to use "material=..." as mentioned under: > > https://wiki.openstreetmap.org/wiki/Key:surface#See_also > which "previous values" you mean? > "tierra" and "terra" ... the answer is obvious: "ground". > Also, for other languages, which are not clear, I would usethe > "material=..." key and just put "surface=unpaved", to be onthe safe > side. > If unclear, I will just not touch it (especially as some unclear may describe paved surface) > Btw. I saw some German word: holz=>wood,schotter=>gravel, > verdichtet=>paved (it means"compacted"), Gras/Laub=>grass, > pflasterstein=>cobblestones > Could surface=verdichtet be actually surface=compacted? Is surface=pflasterstein a surface=cobblestone (underdefined one) or can it be assumed to be in every single case surface=sett or surface=unhewn_cobblestone ? See https://wiki.openstreetmap.org/wiki/Tag:surface%3Dcobblestone I added # translating German 'holz': 'wood', 'schotter': 'gravel', 'Gras_Laub': 'grass', to candidate list for the next one (I will also review is any of them typically wrong - using aerial images - and is connected to any obvious issues not already automatically detectable) > Regarding regular reruns of this, I would put some qualitygates into > that, like: > Were previous automatic corrections reverted and why? > Does a certain type reoccur often and why? > Do new categories appear and should they become official? > I inspect some sample of bot edits and before I run it I get info how many will be changed - so in case of large volume of cases (re)appearing I would investigate what is going on. I am also monitoring PMs and changeset comments on bot account - and I think that someone thinking that it made a bad edit would write. Does it seem enough for you? (I can also run this edit once and once enough new or repeated cases gather then appear here again with similar listing) ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
Hi Thanks for the comprehensive explanation. Here some answers: 1. This first part makes sense to me. 2. Regarding your questions to document previous values, I would propose to use "material=..." as mentioned under: https://wiki.openstreetmap.org/wiki/Key:surface#See_also 3. "tierra" and "terra" ... the answer is obvious: "ground". 4. Also, for other languages, which are not clear, I would use the "material=..." key and just put "surface=unpaved", to be on the safe side. 5. Btw. I saw some German word: holz=>wood, schotter=>gravel, verdichtet=>paved (it means "compacted"), Gras/Laub=>grass, pflasterstein=>cobblestones 6. Regarding regular reruns of this, I would put some quality gates into that, like: * Were previous automatic corrections reverted and why? * Does a certain type reoccur often and why? * Do new categories appear and should they become official? Best, Klaus On 24/03/2023 19:56, Mateusz Konieczny via talk wrote: I proposed some time ago to replace some surface values. The initial script run was recently done,. Edit is documented at https://wiki.openstreetmap.org/wiki/Mechanical_Edits/Mateusz_Konieczny_-_bot_account/fixing_malformed_surface_tags I propose to expand this by replacing also surfaces listed below. Please comment if any of proposed replacements are dubious in any way and do not qualify for a replacement with an automated edit. Edit will affect around 2500 objects. If anyone wants I can help them to find affected objects or present listing of edits which added this tags or list people who added this values onto currently tagged osm objects. Samples of this values were tested. Tried to use them as detectors of bogus data, neither were really useful for this purpose. So I am proposing following changes surface = unpaved33 → surface = unpaved # added by TendaiNkomo - see https://www.openstreetmap.org/changeset/67017223 where I tried to contact them surface = unpaved_minor → surface = unpaved surface = unpaved_major → surface = unpaved # surface=dirt would be incorrect, "dirt road" refers also to surface=compacted surface = dirt road → surface = unpaved # https://www.openstreetmap.org/changeset/48215497 https://www.openstreetmap.org/changeset/67215079 https://www.openstreetmap.org/changeset/25703937 surface = cobbled → surface = cobblestone # apparently autocomplete accident surface = un → surface = unpaved surface = compact → surface = compacted # low use, detected via detector of values very likely to by typoed or having shiFt accident # still verified whether indicating obvious issues surface = Concrete → surface = concrete surface = GRAVEL → surface = gravel surface = Compacted → surface = compacted # surface=bamboo is not documented, this replacement is still useful surface = Bamboo → surface = bamboo # also reviewed, no special comments surface = unsealed → surface = unpaved surface = synthetic_grass → surface = artificial_turf surface = asphalt_no_1 → surface = asphalt surface = asphalt deg 3 → surface = asphalt surface = planks → surface = wood surface = cobblestone_flattened → surface = cobblestone:flattened surface = Hard_Court → surface = hard_court surface = groun → surface = ground surface = groud → surface = ground surface = groundw → surface = ground surface = ground2 → surface = ground surface = paved2 → surface = paved surface = gravel2 → surface = gravel surface = asphalt22 → surface = asphalt surface = concrete2 → surface = concrete surface = unpaved3 → surface = unpaved surface = unpaved22 → surface = unpaved surface = asphalt2 → surface = asphalt surface = compacted_gravel → surface = compacted surface = unsurfaced → surface = unpaved surface = plank → surface = wood surface = wooden_planks → surface = wood surface = wood_chip → surface = woodchips # more surface values with trailing letter/number # especially 2 and q are common - missclick of tab button? Similarly 1 and 3 # and c - missclick of ctrl+c? # and C - missclick of ctrl+c and using shift+c? surface = unpavedc → surface = unpaved surface = grounds → surface = ground surface = gravelc → surface = gravel surface = unpaveds → surface = unpaved # I have not reviewed this values specifically - but I reviewed many other single-extra-letter-cases # all values here are low use, some may be used once # I expect that reliability here will be the same as sample which I verified based on aerial images # for obvious mistake or indicators of problems surface = unpaved* → surface = unpaved surface = asphalt3 → surface = asphalt surface = asphaltd → surface = asphalt surface = asphalt; → surface = asphalt surface = asphalts → surface = asphalt surface = asphaltz → surface = asphalt surface = asphaltc → surface = asphalt surface = asphaltN → surface = asphalt surface = asphaltn → surface = asphalt surface = asphaltl → surface = asphalt surface = asphalth → surface = asphalt surface = asphaltC → surface = asphalt surface = asphaltu → surface = asphalt surface =
[OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)
I proposed some time ago to replace some surface values. The initial script run was recently done,. Edit is documented at https://wiki.openstreetmap.org/wiki/Mechanical_Edits/Mateusz_Konieczny_-_bot_account/fixing_malformed_surface_tags I propose to expand this by replacing also surfaces listed below. Please comment if any of proposed replacements are dubious in any way and do not qualify for a replacement with an automated edit. Edit will affect around 2500 objects. If anyone wants I can help them to find affected objects or present listing of edits which added this tags or list people who added this values onto currently tagged osm objects. Samples of this values were tested. Tried to use them as detectors of bogus data, neither were really useful for this purpose. So I am proposing following changes surface = unpaved33 → surface = unpaved # added by TendaiNkomo - see https://www.openstreetmap.org/changeset/67017223 where I tried to contact them surface = unpaved_minor → surface = unpaved surface = unpaved_major → surface = unpaved # surface=dirt would be incorrect, "dirt road" refers also to surface=compacted surface = dirt road → surface = unpaved # https://www.openstreetmap.org/changeset/48215497 https://www.openstreetmap.org/changeset/67215079 https://www.openstreetmap.org/changeset/25703937 surface = cobbled → surface = cobblestone # apparently autocomplete accident surface = un → surface = unpaved surface = compact → surface = compacted # low use, detected via detector of values very likely to by typoed or having shiFt accident # still verified whether indicating obvious issues surface = Concrete → surface = concrete surface = GRAVEL → surface = gravel surface = Compacted → surface = compacted # surface=bamboo is not documented, this replacement is still useful surface = Bamboo → surface = bamboo # also reviewed, no special comments surface = unsealed → surface = unpaved surface = synthetic_grass → surface = artificial_turf surface = asphalt_no_1 → surface = asphalt surface = asphalt deg 3 → surface = asphalt surface = planks → surface = wood surface = cobblestone_flattened → surface = cobblestone:flattened surface = Hard_Court → surface = hard_court surface = groun → surface = ground surface = groud → surface = ground surface = groundw → surface = ground surface = ground2 → surface = ground surface = paved2 → surface = paved surface = gravel2 → surface = gravel surface = asphalt22 → surface = asphalt surface = concrete2 → surface = concrete surface = unpaved3 → surface = unpaved surface = unpaved22 → surface = unpaved surface = asphalt2 → surface = asphalt surface = compacted_gravel → surface = compacted surface = unsurfaced → surface = unpaved surface = plank → surface = wood surface = wooden_planks → surface = wood surface = wood_chip → surface = woodchips # more surface values with trailing letter/number # especially 2 and q are common - missclick of tab button? Similarly 1 and 3 # and c - missclick of ctrl+c? # and C - missclick of ctrl+c and using shift+c? surface = unpavedc → surface = unpaved surface = grounds → surface = ground surface = gravelc → surface = gravel surface = unpaveds → surface = unpaved # I have not reviewed this values specifically - but I reviewed many other single-extra-letter-cases # all values here are low use, some may be used once # I expect that reliability here will be the same as sample which I verified based on aerial images # for obvious mistake or indicators of problems surface = unpaved* → surface = unpaved surface = asphalt3 → surface = asphalt surface = asphaltd → surface = asphalt surface = asphalt; → surface = asphalt surface = asphalts → surface = asphalt surface = asphaltz → surface = asphalt surface = asphaltc → surface = asphalt surface = asphaltN → surface = asphalt surface = asphaltn → surface = asphalt surface = asphaltl → surface = asphalt surface = asphalth → surface = asphalt surface = asphaltC → surface = asphalt surface = asphaltu → surface = asphalt surface = asphalt- → surface = asphalt surface = asphaltr → surface = asphalt surface = asphalt1 → surface = asphalt surface = concretef → surface = concrete surface = concretev → surface = concrete surface = concrete6 → surface = concrete surface = concretee → surface = concrete surface = concretew → surface = concrete surface = concretec → surface = concrete surface = concrete` → surface = concrete surface = concreteo → surface = concrete surface = concrete5 → surface = concrete surface = concretex → surface = concrete surface = concreted → surface = concrete surface = concrete3 → surface = concrete surface = concretem → surface = concrete surface = concrete- → surface = concrete surface = concreteŒ → surface = concrete surface = sand1 → surface = sand surface = sand] → surface = sand surface = sandw → surface = sand surface = sand` → surface = sand surface = sand- → surface = sand surface = sands → surface = sand surface = sand3 → surface = sand surface = sandq →
