[OSM-talk] Various POI extracts from the web ... What to do?
Hi there I am sometimes faced with websites that have collected a lot of GPS POIs that are of interest to me but not available in OSM, e.g.: https://mundraub.org/map (a website for free fruits) https://drive.google.com/open?id=1gFCcfcdvdQr4e0dKmyNnsn-4q7ATlCix=sharing (rest places in Japan) https://www.titsa.com/index.php/atencion-al-cliente/puntos-de-venta-y-recarga (a website with a map of recharge points of bus money cards in Tenerife ... currently not working) I often will run a script to scrap/extract the GPS and other information and then put it into a GPX, which I can use in OsmAnd. Now, I wouldn't put all these points into OSM, both due to licencing questions and accuracy of POIs. However, I was wondering how these GPS POIs could be made available to other users that might find these POIs relevant? I wouldn't want to create OsmAnd tiles, but I was looking for something like OSM Traces, just for POIs. Does anyone have an idea hoer to spread such information? Many thanks Klaus ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Automated Edit - Bus stops status link & Bus lines timetable link (Tenerife)
Will do however this operation is geographically limited, so the author must ask the local community for their agreement, and not a global one ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Automated Edit - Bus stops status link & Bus lines timetable link (Tenerife)
Sorry about that. I was just mentioning this another source of the information. But I am actuall proposing the regular QR code links, not these Ajax ones. On 26/03/2023 18:41, Sören Reinecke wrote: I speak about e.g. https[https://titsa.com/ajax/xGetInfoParada.php?id_parada=4004]://titsa.com/ajax/xGetInfoParada.php?id_[https://titsa.com/ajax/xGetInfoParada.php?id_parada=4004]parada[https://titsa.com/ajax/xGetInfoParada.php?id_parada=4004]=4004[https://titsa.com/ajax/xGetInfoParada.php?id_parada=4004] (the ajax interface) Mar 26, 2023 19:39:13 Marc_marc : Le 26.03.23 à 18:39, Sören Reinecke a écrit : the resources behind these urls are in a machine readable format did you click on the link or are you talking theory? I don't see how a link intended for the general public could be "machine-only readable" content in any case when I click on it, I understand perfectly the content of https://movil.titsa.com/infoparada.php?IdParada=4004 ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk ___ 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!)
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] Automated Edit - Bus stops status link & Bus lines timetable link (Tenerife)
See below ... On 24/03/2023 21:33, Mateusz Konieczny via talk wrote: Mar 24, 2023, 20:40 by valin...@gmx.net: What do you think about this idea? What would be the best way to achieve this in an automated way? If these urls are following a fixed scheme like you mentioned then I see no need to add the urls. There is no need to store them if you can create them from a combination of the hard coded Well, as template for links is not present then it is not a good reason against it. I would be more concerned whether links will be stable or change format soon. I also don't quite understand the reasoning against such a generic web link. The only way to obtain that link would be through the QR code at the bus stop, which is an obstacle. Not even the website actually has this information on a separate page, but only through a popup clicking onto the station. And I think it would greatly improve the usefulness of the bus stop nodes in the map. Same is true for the bus line links. Why search through the Titsa website to gain this information when it can readily be associated with the node. If I click onto a restaurant or hotel and get their website, that's not different, is it? I wouldn't go though Google to find such information. It requires knowledge how databases work in general, why normalization & abstraction is important and at last you need to be developer. OSM map database is not normalized (at least as far as tags are concerned) is actually a good thing as it an obstacle to not make it too easy for "children" (in double quotes for reasons) and protects us from edit spaming. this really could be phrased better without making it insulting and it does not really protect as strongly, though maybe it could be worse This is the reason why I currently abstain from writing a python3 script to make it easier to write editing bots. This scripts exist already, and were written multiple times already one more would not change much @Mateusz: Any help regarding the script would be greatly appreciated. I have worked with databases before (PostgreSQL, MySQL, SAS) and am aware of the pitfalls. Best, Klaus ___ 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] Automated Edit - Bus stops status link & Bus lines timetable link (Tenerife)
Hi there I would like to update all bus stops on the island of Tenerife with a link to the status website of upcoming connections to this bus stop: * An example of bus stop: https://www.openstreetmap.org/node/1147359056 * Each such bus stop inhibits a reference: ref=4004 * This reference can be used to obtain that bus stops upcoming connections: http://movil.titsa.com/infoparada.php?IdParada=4004 * Actually, in reality each bus stop has a QR code to check this status, which leads to the latter website. * Hence, all these QR codes are spread across the island, I assume the link will seldomly change. * There is also an Ajax link: https://titsa.com/ajax/xGetInfoParada.php?id_parada=4004 (But thats directly from the website and probably not that stable as the former one). I think, this link would be good to have with each bus stop for Tenerife on OSM, so one can easily derive the upcoming departure times, even when not being nearby the bus stop. Furthermore each bus line on the island has a timetable available online, that I would like to link for each bus line: * An example bus line: https://www.openstreetmap.org/relation/7165110 * Each such bis line inhibits a reference code: ref=419 * This reference can be used to obtain that bus lines timestable and overview website: https://titsa.com/index.php/tus-guaguas/lineas-y-horarios/linea-419 * An alternative link is this: https://movil.titsa.com/infolinea.php?IdLinea=021 (But I guess, it is less useful and does not immediately display the general times.) Also these links would be good to have with each bus line. What do you think about this idea? What would be the best way to achieve this in an automated way? I know the Overpass API and I could probably readily identify all the relevant bus stop nodes and bus line relations. However, I have never updated such things in an automated way. Many thanks Klaus ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
