I proposed some time ago to replace some surface values.

The initial script run was recently done, after waiting for a potential 
feedback.
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 surface and shop tags listed below.
Shop edit would get own wiki documentation page, surface replacements would
be added to existing page and it would link to both discussions.

Please comment if any of proposed replacements are dubious in any way and 
do not qualify for a replacement with an automated edit.
List previously was really short, this one is longer - let me know if either 
format is preferred.
Either way, I will not make any bot edits before 11 III in my time zone.
(I wait for about two weeks after proposing bot edits, as usual).

overpass query listing where surface would be edited: 
https://overpass-turbo.eu/s/1rKh - 2084 objects right now



surface replacements:

surface = artificial_grass → surface = artificial_turf
See 
https://community.openstreetmap.org/t/surface-artificial-grass-vs-surface-artificial-turf/6295

surface = barkchips → surface = woodchips
surface = bark_wood → surface = woodchips
opened notes for some of them and some turned out to not be even made
of actual bark when checked by local mappers...

something went wrong with autocomplete:
surface = as → surface = asphalt
surface = asp → surface = asphalt
surface = grav → surface = gravel
surface = pebb → surface = pebblestone

seems like name in a different language, but with a clear meaning
surface = asfalto → surface = asphalt

in several languages "beton" is word for concrete, so far I was opening notes
for a long time and asking in changesets and in every single case it was a 
clearly correct replacement
surface = beton → surface = concrete

translating from Polish
surface = ziemna → surface = earth

we do not have unpaved_dirt either
surface = unpaved_gravel → surface = gravel

clear typos
surface = ashpalt → surface = asphalt
surface = Asphalt → surface = asphalt
surface = ashalt → surface = asphalt
surface = aspahlt → surface = asphalt
surface = ashphalt → surface = asphalt
surface = paving_stone → surface = paving_stones
surface = Paving Stone → surface = paving_stones
surface = paving_stoness → surface = paving_stones
surface = wood_chips → surface = woodchips
surface = woodchip → surface = woodchips
surface = wood chips → surface = woodchips
surface = wood_chippings → surface = woodchips
surface = peeblestone → surface = pebblestone
surface = pebbles → surface = pebblestone
surface = pebblestones → surface = pebblestone
surface = pebbelstone → surface = pebblestone
surface = pepplestone → surface = pebblestone
surface = pebble → surface = pebblestone
surface = pavedq → surface = paved
surface = pavedc → surface = paved
surface = pavedw → surface = paved
surface = unapved → surface = unpaved
surface = groundц → surface = ground
surface = groundmm → surface = ground
surface = grround → surface = ground
surface = groundc → surface = ground
surface = gorund → surface = ground
surface = grounD → surface = ground
surface = concreate → surface = concrete
surface = concrete\ → surface = concrete
surface = gravelw → surface = gravel
surface = Gravel → surface = gravel
surface = fine gravel → surface = fine_gravel
surface = fine_gravelC → surface = fine_gravel
surface = Boardwalk → surface = boardwalk
surface = Metal → surface = metal
surface = gras → surface = grass
surface = grasss → surface = grass
surface = concrete:plate → surface = concrete:plates
surface = Cobblestone:flattened → surface = cobblestone:flattened
surface = cobbelstone:flattened → surface = cobblestone:flattened
surface = cobblestone:flatten → surface = cobblestone:flattened
surface = cobblestone:flattended → surface = cobblestone:flattened
surface = cobblestone:flattend → surface = cobblestone:flattened
surface = cobblestone:flatened → surface = cobblestone:flattened





------------------------------





proposed migration of shop=* values:
https://overpass-turbo.eu/s/1rLI for current listing of objects - 1117 right now

various ways of saying that we lack info about shop type
shop = user defined → shop = yes
shop = user_defined → shop = yes
shop = lack_of_info → shop = yes
shop = other → shop = yes
shop = unknown → shop = yes
shop = * → shop = yes
shop = Shop → shop = yes
shop = shop → shop = yes
shop = stuff → shop = yes
shop = store → shop = yes

shop=* and shop = user defined are used literally - and not catchalls.
see https://taginfo.openstreetmap.org//search?q=shop%3Duser+defined

synonyms or synonyms in this context
sometimes product tagged as a shop type
shop = pawnshop → shop = pawnbroker
shop = bread → shop = bakery
shop = laundromat → shop = laundry
shop = flowers → shop = florist
shop = meat → shop = butcher
shop = glasses → shop = optician
shop = hgv → shop = truck
shop = liquor → shop = alcohol
shop = Bag_shop → shop = bag
shop = empty → shop = vacant
shop = travel_agent → shop = travel_agency

https://wiki.openstreetmap.org/wiki/Proposed_features/shop%3Dmarijuana
shop = marijuana → shop = cannabis

singular vs plural
shop = toy → shop = toys
shop = watch → shop = watches

translation from Polish
shop = opał → shop = fuel






If you reached here: I have some question about shop values that I am NOT
proposing to edit right now.

shop=eggs -> shop=food food=eggs
maybe such migration would be a good idea?
having top value for every single shop type specializing in a given food
seems hopeless - we would need shop=pumpkin, shop=apples, shop=basil,
shop=pierogi...
That is nighmarish for data consumers.
If not shop=food - what would be a good shop value for myriad shops
selling some specific food, that are clearly neither restaurant nor fast foods?
Not all foods are as commonly sold in dedicated shop to get shop=rice or 
shop=cheese

shop=snacks -> shop=snack
or maybe it would be better to change in opposite direction?
it is not too late as it is a rarely used tag

shop=map -> shop=maps
or maybe it would be better to change in opposite direction?
it is not too late as it is a rarely used tag

shop=religious -> shop=religion
or is it not a safe replacement

shop=fireworks -> shop=pyrotechnics pyrotechnics=fireworks
maybe it would be clearly superior?




Following is the same reasoning and plan as previously:

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%20bot%20account

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 surface= and shop= values

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.
_______________________________________________
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Reply via email to