I have a few suggestions too:
 
verdichtet => compacted
straatstenenc => paving_stones
bestraat => paving_stones
niet-bestraat => unpaved
niet-bestraat2 => unpaved
niet-bestraat33 => unpaved
щебеночное_покрытие => gravel
no_paved => unpaved
concreteas => concrete
Pflastersteine => sett
pflastersteine => sett
Bosbodem => dirt
klinkers => sett
sans_revêtement => unpaved
schotter => gravel
Turf => turf
holz => wood
грунт => dirt
terre_battue => gravel
плитка => paving_stones
pavingstones => paving_stones
não_pavimentado => unpaved
Waldboden => ground (literally forest soil)
permukaan tanah dan Beton means ground and concrete
 
And I want to point attention to surface=앿
https://www.openstreetmap.org/way/1185643877
Seems someone is adding this in Taiwan a lot. I think it means unpaved.
 

> Op 01-11-2023 23:42 CET schreef Mateusz Konieczny via talk 
> <talk@openstreetmap.org>:
>  
>  
> I proposed some time ago to fix some surface values.
>  
> 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 fixing also values 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.
>  
> Please also comment if you checked values proposed to be edited and they seem 
> fine!
>  
> Edit will affect around 2200 objects.
>  
> It is preferable to use standard tag values where possible,
> and in many cases unusual values can be migrated without any data loss.
> The list below is supposed to contain only such cases.
>  
> 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. I also asked for review at 
> https://forum.openstreetmap.fr/t/review-requested-before-proposing-bot-edit-for-automated-fixing-of-surface-values/18419
>  
> Tried to use them as detectors of bogus data, neither were really useful for 
> this purpose.
> We have many better ways to find OSM data requiring human review.
>  
> So I am proposing following changes
>  
> tags with highest use, among ones that will be retagged
> surface = astroturf with 297 uses
> surface = timber with 122 uses
> surface = paving with 179 uses
> surface = U with 82 uses
> surface = enrobé with 276 uses
> surface = terre with 383 uses
>  
>  
> surface = astroturf → surface = artificial_turf
> surface = timber → surface = wood (see 
> https://www.openstreetmap.org/changeset/66866027 
> https://www.openstreetmap.org/changeset/126078123 
> https://www.openstreetmap.org/changeset/126078123 
> https://www.openstreetmap.org/changeset/68461319 
> https://www.openstreetmap.org/changeset/69445813 
> https://www.openstreetmap.org/changeset/57280475 
> https://www.openstreetmap.org/changeset/126800407 )
> surface = DIRT → surface = dirt
> surface = paving → surface = paved
> surface = U → surface = unpaved
>  
> French from 
> https://lists.openstreetmap.org/pipermail/talk/2023-April/088164.html
> review at 
> https://forum.openstreetmap.fr/t/review-requested-before-proposing-bot-edit-for-automated-fixing-of-surface-values/18419
>  
> surface = enrobé → surface = asphalt
> surface = béton_bitumineux → surface = asphalt
> surface = béton_bitumimeux → surface = asphalt
> surface = bitumen → surface = asphalt
> surface = enrobes → surface = asphalt
> surface = bitume → surface = asphalt
> surface = goudronné → surface = asphalt
> surface = gourdon → surface = asphalt
> surface = plastique → surface = plastic
> surface = banc_de_sable → surface = sand
> surface = terre → surface = earth
> surface = Terre → surface = earth
> surface = terre_boue → surface = mud
> surface = terre_humide → surface = mud
> surface = terre,_boue → surface = mud
> surface = graviers → surface = gravel
> surface = tere → surface = earth
> surface = terre2 → surface = earth
> surface = caoutchouc → surface = rubber
> surface = bois → surface = wood
> surface = béton_désactivé → surface = concrete
> surface = terre_batue → surface = clay
> surface = pavés → surface = paved
> surface = carrelage → surface = tiles
> surface = pelouse_et_terre → surface = grass;ground
> surface = terre_touvenant → surface = ground
> surface = terre;herbe → surface = ground;grass
> surface = terre_naturelle,_argileuse → surface = ground
> surface = gravier → surface = gravel
> surface = gazon_synthétique → surface = artificial_turf
> surface = béton → surface = concrete
> surface = ciment → surface = concrete
> surface = herbe → surface = grass
> surface = gazon → surface = grass
> surface = herb → surface = grass
> surface = herbe_naturel → surface = grass
> surface = pelouse → surface = grass
> surface = pelouse_naturelle → surface = grass
> surface = terre_et_rochers → surface = ground;rock
> surface = béton_bois → surface = concrete;wood
> surface = terre,_cailloux → surface = ground;gravel
> surface = terre_et_herbe → surface = earth;grass
> surface = herbe_et_sable → surface = grass;sand
> surface = sable_et_terre → surface = sand;earth
> surface = terre_et_sable → surface = earth;sand
> surface = terre_cailloux → surface = ground;gravel
> surface = terre_goudrons → surface = ground;asphalt
> surface = terre_goudron → surface = ground;asphalt
> surface = terre_pierres → surface = ground;gravel
> surface = terre_et_pierre → surface = ground;gravel
> surface = terr_et_pierre → surface = ground;gravel
> surface = terre/sable → surface = ground;sand
> surface = terre_et_pierres → surface = ground;gravel
> surface = Herbe_et_cailloux → surface = grass;gravel
> surface = terre_et_gravier → surface = ground;gravel
> surface = gravillons,_béton → surface = gravel;concrete
> surface = graviers_et_terre → surface = gravel;ground
> surface = sable → surface = sand
> surface = Sable → surface = sand
> surface = cailloux → surface = gravel
> surface = pierre → surface = gravel
> surface = gravier0 → surface = gravel
>  
> surface = asphalt_on_concrete_sub-base → surface = asphalt 
> https://www.openstreetmap.org/changeset/30055680 - asked on 2023-03-20 
> (mapper is inactive, commented that they are fine with this change)
>  
> surface = Sand → surface = sand
> surface = unhewn_cobblestones → surface = unhewn_cobblestone
> surface = holz → surface = wood
> surface = асфальт → surface = asphalt
> surface = concrete1 → surface = concrete
> surface = compactedc → surface = compacted
> surface = concreteq → surface = concrete
> surface = paving_stones2 → surface = paving_stones
> surface = asphaltq3 → surface = asphalt
> surface = asphaltcc → surface = asphalt
> surface = asphaltqq → surface = asphalt
> surface = unpaved-- → surface = unpaved
> surface = unpavedMN → surface = unpaved
> surface = a → surface = asphalt
> surface = asphalt:chipseal → surface = chipseal
> surface = pavement → surface = paved
> surface = ground_dirt → surface = dirt
> surface = tiled → surface = paved
> surface = astro_turf → surface = artificial_turf
> surface = wood_planks → surface = wood
> surface = AS → surface = asphalt
> surface = flooring_tiles → surface = tiles
> surface = lawn → surface = grass
> surface = Brick → surface = brick
> surface = Artificial Turf → surface = artificial_turf
> surface = ea → surface = earth
> surface = dit → surface = dirt
> surface = wooden deck → surface = wood
> surface = paved_minor → surface = paved
> surface = s-and → surface = sand
> surface = cobble → surface = cobblestone
>  
> surface = unpaved2 → surface = unpaved
> surface = paving_stones4= → surface = paving_stones
> surface = concretefl → surface = concrete
> surface = asphaltww → surface = asphalt
> surface = grassq → surface = grass
> surface = unpaved∂ → surface = unpaved
> surface = unhewn-cobblestone → surface = unhewn_cobblestone
> surface = unpavedŒ → surface = unpaved
> surface = paving_stonesv → surface = paving_stones
> surface = unpavedNo → surface = unpaved
> surface = gravel3 → surface = gravel
> surface = sett9 → surface = sett
> surface = concreteas → surface = concrete
> surface = paved3 → surface = paved
> surface = asphaltŒ → surface = asphalt
> surface = asphalt_ → surface = asphalt
> surface = asphaltw → surface = asphalt
> surface = asphaltq → surface = asphalt
> surface = grass2 → surface = grass
> surface = paved22 → surface = paved
> surface = dirtц → surface = dirt
> surface = unpaved1 → surface = unpaved
>  
>  
> there are also many low-use values with one or two or three extra bogus 
> characters, for example
> surface = artificial_turf22 → surface = artificial_turf
>  
> would be also OK to migrate them without listing them
> for review here and just add them to replace list later?
> And other similar obvious typos appearing or found in future?
>  
> Only low use obvious mistakes would be changed. 
> If anyone at all will protest and I will not do this and post
> for review, like list here, once sufficiently many values are found.
>  
> Proposed edit would be automatic, rerun from time to time, split into small
> changeset by geographic areas and run by
> https://www.openstreetmap.org/user/Mateusz%20Konieczny%20-%20bot%20account/history
>  bot account
>  
> Following is the same reasoning and plan as previously:
>  
> Why it is useful? It helps newbies to avoid becoming confused. It
> protects against such values becoming established. Without drudgery
> that would be required from the manual cleanup. It also makes easier to
> add missing values where needed.
>  
> It also cuts down on help/research to answer cases "why this feature
> is not showing up properly" (because it has a typo in a tag).
>  
> Why automatic edit? I have a massive queue (in thousands and tens of
> thousands) of automatically detectable issues which are not reported by
> mainstream validators, require fixes and fix requires review or
> complete manual cleanup.
>  
> There is no point in manual drudgery here, with values clearly
> replaceable by better matches.
>  
> This values here do NOT require manual overview. If this cases will
> turn out to be an useful signal of invalid editing than I will remain
> reviewing nearby areas where bot edited.
>  
> And I fixed some manually and they were not a great sign of a problematic 
> data.
>  
> Yes, bot edit WILL cause objects to be edited. Nevertheless, as result
> map data quality will improve.
>  
> note: there is a matching announcement at community forum, but 
> talk mailing list confirmation is intended to be as a final one.
> ( 
> https://community.openstreetmap.org/t/proposed-bot-edit-automatic-replacement-of-surface-values-where-it-is-safe/105361
>  )
> _______________________________________________
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
> 
_______________________________________________
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Reply via email to