[talk-au] Mapping tracks from Strava heatmap
Do people have a view on the armchair mapping of tracks from Strava heatmaps? I can see a bunch of tracks in Kanangra-Boyd NP that have been mapped by an overseas mapper off Strava heatmap. They almost certainly don't exist on the ground. They are known bushwalking routes (off track), but would be very unlikely to have a track even in good times, let along after the fires and 3 years of La Nina! Example: https://www.openstreetmap.org/way/952248376 cheers Tom Canyoning? try http://ozultimate.com/canyoning Bushwalking? try http://bushwalkingnsw.com ___ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
Re: [OSM-talk] Proposed automatic replacements of multiple surface=* and shop=* values (review welcomed!)
Feb 25, 2023, 22:00 by dieterdre...@gmail.com: > > > sent from a phone > >> On 25 Feb 2023, at 20:13, Mateusz Konieczny via talk >> wrote: >> >> 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. >> > > > forgot to say I applaud to this initiative, thank you for tackling this and > documenting the process. I agree that there are many cases that can be fixed > automatically, and your list shows good examples, but of course we must be > very careful to not iron everything flat when there might be subtle > differences. This is why it is important to have many eyes on such bot edits > and document the details. > BTW, if someone would prepare similar list for some key (replacements of value A by value B within the same key, without any additional checks/replacements/conditions, with explanations why such replacements are obviously useful), AND they confirmed that this tags are not very good at indicating places where intensive cleanup/reverts are needed AND list would be in general reasonably reviewed AND publish bot proposal on this mailing list, like this one then I can run such edit. Preparing it is time-consuming, running bot itself is easy. (lets say that offer is active for the next 30 days so noone will try this in say 6 years from now, may be revoked earlier if people will try to post really badly prepared lists) ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Test Import of forum.osm.org to community.osm.org
HI, Replies below... On Sat, 25 Feb 2023 at 18:19, Mateusz Konieczny via talk wrote: > > Old links will continue to work, right? > > Including links in posts linking other posts (that now > link to the original forum) > > Yes, all category, user and post links still work by redirecting to the imported content on community.openstreetmap.org The redirect logic is explained here: https://community.openstreetmap.org/t/migrating-content-from-old-forums/446/214 The thread also has details how you can check the logic yourself. The RSS/Atom feeds for the old forum will not be redirected, but will be pointed at a static feed asking users to update their feed links. Kind regards, Grant ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface=* and shop=* values (review welcomed!)
Am Sa., 25. Feb. 2023 um 22:07 Uhr schrieb Mateusz Konieczny via talk < talk@openstreetmap.org>: > > So shop = laundromat → shop = laundry + self_service=yes would be needed? > it could be seen as equivalent, personally I would see a case for different main tags because these are quite different features, better not intervene in an automatic way (although admittedly there is 1000 times less usage for laundromat one could also say that 40 laundromats are not worth discussing). Maybe set up a proposal for laundromat? For 25% of all laundries there is "self_service" information (and 85% of these are self service=yes which could suggest that the default is self_service=no). I'd rather go for amenity=laundromat (it has 7 uses now) ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface=* and shop=* values (review welcomed!)
On Sat, 25 Feb 2023 at 19:08, Mateusz Konieczny via talk wrote: > Please comment if any of proposed replacements are dubious in any way and > proposed migration of shop=* values: These, and the durface= values, are motsly good changes; thank you. But consider: > shop = laundromat → shop = laundry Not the same, as others have noted. > shop = Bag_shop → shop = bag Is this a shop that sells bags, or "things by the bagfull"? > shop = watch → shop = watches This could plausibly mean watch as in "monitor" - in other words "please watch for developments". -- Andy Mabbett @pigsonthewing http://pigsonthewing.org.uk ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface=* and shop=* values (review welcomed!)
sent from a phone > On 25 Feb 2023, at 20:13, Mateusz Konieczny via talk > wrote: > > 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. forgot to say I applaud to this initiative, thank you for tackling this and documenting the process. I agree that there are many cases that can be fixed automatically, and your list shows good examples, but of course we must be very careful to not iron everything flat when there might be subtle differences. This is why it is important to have many eyes on such bot edits and document the details. Cheers Martin ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface=* and shop=* values (review welcomed!)
Feb 25, 2023, 21:14 by dieterdre...@gmail.com: > > > sent from a phone > >> On 25 Feb 2023, at 20:13, Mateusz Konieczny via talk >> wrote: >> >> shop = laundromat → shop = laundry >> > > > I think the laundromat is about a diy place while shop=laundry can also be a > service where you drop off your laundry and they’ll take care of everything. > Wiki suggests adding self_service=yes for the former. > So shop = laundromat → shop = laundry + self_service=yes would be needed? ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface=* and shop=* values (review welcomed!)
Note: I want to mention for context that this was preceded with > If you reached here: I have some question about shop values that > I am NOT proposing to edit right now. Feb 25, 2023, 21:27 by dieterdre...@gmail.com: > > > sent from a phone > > >> On 25 Feb 2023, at 20:13, Mateusz Konieczny via talk >> wrote: >> 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. >> > > > maybe for these pumpkin or apple or basil shops a more generic category > (there is > https://wiki.openstreetmap.org/wiki/Tag:shop%3Dfarm> ) can make > sense, with a subtag for the kind of produce they sell, but food is very > important for all of us and we do indeed mostly tag dedicated classes for > these, like bakery, butcher, greengrocer, wine, deli, supermarket, > convenience, so if there are dedicated pierogi shops I would tag them as > this. You would not want to find them if you search for “food”, you search > for pierogi if you wanted to find them. There is shop=pasta where I think > pierogi could fit, “food” is too generic. > Shops selling pierogi are definitely not shop=pasta and I was thinking about shop=food food=pierogi or something similar for places like https://www.openstreetmap.org/node/3033173319 maybe shop=food main_food=pierogi to avoid food key ending with multiple uses? or shop=prepared_meals (almost ready for eating but requiring heating/boiling) there is shop=frozen_food not fitting shops selling food that is prepared and not frozen ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface=* and shop=* values (review welcomed!)
sent from a phone > On 25 Feb 2023, at 20:13, Mateusz Konieczny via talk > wrote: > > 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. maybe for these pumpkin or apple or basil shops a more generic category (there is https://wiki.openstreetmap.org/wiki/Tag:shop%3Dfarm ) can make sense, with a subtag for the kind of produce they sell, but food is very important for all of us and we do indeed mostly tag dedicated classes for these, like bakery, butcher, greengrocer, wine, deli, supermarket, convenience, so if there are dedicated pierogi shops I would tag them as this. You would not want to find them if you search for “food”, you search for pierogi if you wanted to find them. There is shop=pasta where I think pierogi could fit, “food” is too generic.___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Proposed automatic replacements of multiple surface=* and shop=* values (review welcomed!)
sent from a phone > On 25 Feb 2023, at 20:13, Mateusz Konieczny via talk > wrote: > > shop = laundromat → shop = laundry I think the laundromat is about a diy place while shop=laundry can also be a service where you drop off your laundry and they’ll take care of everything. Wiki suggests adding self_service=yes for the former. Cheers Martin ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Proposed automatic replacements of multiple surface=* and shop=* values (review welcomed!)
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 =
Re: [OSM-talk] Test Import of forum.osm.org to community.osm.org
Old links will continue to work, right? Including links in posts linking other posts (that now link to the original forum) Feb 21, 2023, 13:27 by openstreet...@firefishy.com: > Hi OSM Talk, > > In the near future we will be moving the old forum.osm.org content to > community.openstreetmap.org > > If you used the old forum, please login to the test import site > https://forum-import-test.openstreetmap.org/ to check your old posts. > > The imported content is at the bottom half of the test import site. > The database snapshot used for the test is from 02 Feb 2023. > > The old forum has 847000+ posts by 35000+ users in 91 categories. The > longest thread has 14700+ posts! > The old forum used fluxbb bbcode markdown, while > community.openstreetmap.org uses discourse's flavour of markdown. > The import markdown conversion can never be 100%, but it now appears > to have reached "good enough". > > We heavily extended the original fluxbb discourse importer with > additional features: > * Significantly improved fluxbb bbcode -> discourse markdown > converter, including fixes. > * Added Permalink support (To test for now use old forum url path + > parameters on forum-import-test.openstreetmap.org) > * OSM specific old forum to community account merging allowing > seamless login using osm.org account oauth flow. > * Added unit tests > > We are trying to contribute the improvements upstream where appropriate. > > There will also be a few tasks the forum governance team will be > responsible for post final import, notably: > * Manually merge duplicate categories (eg: country categories) > * Mark old abandoned categories as read-only. > * Manually merge duplicate users where the importer did not > automatically merge (very limited cases). > > Big thank you to Harry Wood, Tom Hughes and others who have helped > write code, fix bugs or assisted in other ways. > > Kind regards, > > Grant > Part of the OpenStreetMap Ops Team > > ___ > 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-ja] クリエイトSDのbrand:*を置換する自動編集
23です。 以下の変更セットで編集を実施しました。 https://www.openstreetmap.org/changeset/133014016 --- Original Message --- 2023年2月14日火曜日 1:59 に 23 が作成: > 23です。 > > クリエイトSDのbrand:wikipediaとbrand:wikidataに誤って広告代理店と曖昧さ回避ページの値が入力されているので、 > これらをクリエイトSDの値に置換する自動編集を行いたいと考えています。 > > name-suggestion-index(NSI)に誤ったデータが登録されていた事が原因ですが、NSI側はすでに修正済みです。 > > 手順など詳細についてはOSM wikiに記載のとおりです。 > https://wiki.openstreetmap.org/wiki/JA:Automated_edits/23#クリエイトのbrand:*タグを適切な値に置換 > > 1週間ほど経って問題等がなければ実施したいと思います。よろしくお願いします。___ Talk-ja mailing list Talk-ja@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ja
