Re: [OSM-talk-fr] Relations intermédiaires pour les routes de bus ?
Bonjour à tous, On a déjà un élément partagé qui est à l'origine d'une part très importante des ruptures de continuité des tracés : le rond-point. C'est un élément très local et on corrige assez simplement : on segmente de plus en plus. Manipuler des segments va demander des évolutions importantes dans les outils, j'attends d'abord celle pour les ronds-points. Marc ___ Talk-fr mailing list Talk-fr@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-fr
Re: [OSM-talk] Proposed bot edit: fixing bunch of typos in tags
On 06/03/2024 18:15, Mateusz Konieczny via talk wrote: state before a mechanical edit (example for a tunnel value): highway=footway tunnel=building_passage2 layer=-1 In favour of this one specifically; It is an error I often make myself using iD by not writing a node edit before selecting another node. It does not apply only to "building_passage". -- Cheers, Jeremy ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk-fr] State Of The Map 2024, c'est parti !
Désolé pour les liens, mon courrieleur a bugué... 6 mars 2024 22:47:52 Cédric Frayssinet : > Bonsoir à toutes et tous, > > Les contributeurs lyonnais se sont lancés dans la grande aventure de > l'organisation du 10ème SOTM, il se tiendra donc à Lyon le 28, 29 et 30 juin ! > > Les 2 premiers jours auront lieu sur le site de la Manufacture des Tabacs à > l'Université Lyon 3. > > N'hésitez pas à rejoindre l'organisation, cela se passe sur le forum : > https://forum.openstreetmap.fr/tag/sotmfr2024 > > Si vous êtes sur Mastodon, le compte à suivre : https://fr.osm.social/@sotmfr > > Et dernière information importante : la vente des billets TGV démarre demain ! > > Bonne soirée et n'hésitez pas si vous avez des questions, > > Cédric > > ___ > Talk-fr mailing list > Talk-fr@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-fr ___ Talk-fr mailing list Talk-fr@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-fr
[OSM-talk-fr] State Of The Map 2024, c'est parti !
Bonsoir à toutes et tous, Les contributeurs lyonnais se sont lancés dans la grande aventure de l'organisation du 10ème SOTM, il se tiendra donc à Lyon le 28, 29 et 30 juin ! Les 2 premiers jours auront lieu sur le site de la Manufacture des Tabacs à l'Université Lyon 3. N'hésitez pas à rejoindre l'organisation, cela se passe sur le forum : https[https://forum.openstreetmap.fr/tag/sotmfr2024]://[https://forum.openstreetmap.fr/tag/sotmfr2024]forum.openstreetmap.fr[https://forum.openstreetmap.fr/tag/sotmfr2024]/tag/[https://forum.openstreetmap.fr/tag/sotmfr2024]sotmfr2024[https://forum.openstreetmap.fr/tag/sotmfr2024] Si vous êtes sur Mastodon, le compte à suivre : https[https://fr.osm.social/@sotmfr]://[https://fr.osm.social/@sotmfr]fr.osm.social[https://fr.osm.social/@sotmfr]/[https://fr.osm.social/@sotmfr]@sotmfr[https://fr.osm.social/@sotmfr] Et dernière information importante : la vente des billets TGV démarre demain ! Bonne soirée et n'hésitez pas si vous avez des questions, Cédric ___ Talk-fr mailing list Talk-fr@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-fr
Re: [OSM-talk] Proposed bot edit: fixing bunch of typos in tags
Mar 6, 2024, 20:00 by a...@pigsonthewing.org.uk: >> On Wed, 6 Mar 2024, 18:15 Mateusz Konieczny via talk, >> wrote: >> >> I propose to fix some obvious typos in tag values. >> >> Full list of values is at >> https://wiki.openstreetmap.org/wiki/Mechanical_Edits/Mateusz_Konieczny_-_bot_account/fix_many_obvious_typos#What >> >> material=woodc -> material=wood >> > > This could plausibly be a typo for "wooocrete": > https://en.wiktionary.org/wiki/woodcrete > >> material=metal+ -> material=metal >> removed from lisr > This could mean "metal and something else" > >> healthcare=occupational_therapist >> > > -> healthcare=occupational_therapist > > No change? > there is newline there :) Clarified it a bit. > > No other issues; thank you for doing this tedious cleanup work. > > -- > Andy Mabbett > @pigsonthewing > https://pigsonthewing.org.uk > > ___ > 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 bot edit: fixing bunch of typos in tags
> On Wed, 6 Mar 2024, 18:15 Mateusz Konieczny via talk, > wrote: > I propose to fix some obvious typos in tag values. > > Full list of values is at > https://wiki.openstreetmap.org/wiki/Mechanical_Edits/Mateusz_Konieczny_-_bot_account/fix_many_obvious_typos#What > material=woodc -> material=wood This could plausibly be a typo for "wooocrete": https://en.wiktionary.org/wiki/woodcrete > material=metal+ -> material=metal This could mean "metal and something else" > healthcare=occupational_therapist -> healthcare=occupational_therapist No change? No other issues; thank you for doing this tedious cleanup work. -- Andy Mabbett @pigsonthewing https://pigsonthewing.org.uk ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Proposed bot edit: fixing bunch of typos in tags
I propose to fix some obvious typos in tag values. Cases were found automatically and manually reviewed with sampling across values (in process some were entirely retagged). Content here is a mirror of https://community.openstreetmap.org/t/proposed-bot-edit-fixing-bunch-of-typos-in-tags/110039 as required by automated edits code of conduct - if you have seen then it is likely not worth rereading it here Typical example would be something like state before a mechanical edit (example for a tunnel value): highway=footway tunnel=building_passage2 layer=-1 state after an edit: highway=footway tunnel=building_passage layer=-1 Full list of values is at https://wiki.openstreetmap.org/wiki/Mechanical_Edits/Mateusz_Konieczny_-_bot_account/fix_many_obvious_typos#What (in case of finding more cases like this - can I just add them to bot edit? Or should I make a new thread here and on talk mailing list) 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= values and makes easier to use OpenStreetMap data, including support in editors which explain/translate meaning of surface 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 obviously fixable. 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. I already skipped edits to primary tags except few blatant cases where mistake is easy to miss (flowerbed until recently was not rendered). Typos in primary tags that cause them to be outright missing from typical map rendering is often coupled with other serious problems. Probably because it indicates mapping by newbies who are likely to be confused also by other complexities. The same goes for access tags that I will keep fixing manually. Though typos in for example shop values are safe to fix automatically, probably because effects are less noticeable. Also, more obvious typos in rare, typically not rendered amenity tags are often safe to fix. Yes, bot edit WILL cause objects to be edited. Nevertheless, as result map data quality will improve. This values were found automatically based on taginfo and iD presets, also accessed via taginfo. Taginfo values statistics list values in OSM database, while iD presets list which values are known for given keys. Multiple heuristics were applies to find various typos, for example “cuisine=bubble tea” was found to match “cuisine=bubble_tea” from iD presets after space was replaced by underscore. “cuisine=Thai” to “cuisine=thai” after lowercasing value. “cuising=regional1” to “cuisine=regional” after skipping ending. All values were looked at then manually to drop any dubious replacement (for example healthcare=nursery to heatlhcare=nurse was skipped). Samples was also looked at in OSM, with many values just edited. Note that not each replacement was sampled: as many, many have just few cases, so sampling and verifying ends with just editing all of them manually. If you see any values where edit would be dubious, not safe or in any way problematic: let me know. (BTW, one typo in iD presets was found while looking for typos, see https://github.com/openstreetmap/id-tagging-schema/pull/1063 ) Some conversion were found manually in addition to iD presets, currently it is only cycleway:both and shop=gun. I also contacted community already in some cases (like sport values with ; and in some cases of extra trailing characters) - via changeset comments and notes. Response confirmed that this changes are a good idea - and that just editing will be better than asking more people. This edit will be rerun in future as many of such typos are expected to reappear. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk-fr] Relations intermédiaires pour les routes de bus ?
Il y a le cas assez courant des lignes partagées partiellement entre plusieurs opérateurs. Aussi bien our les bus que les trains. Certaines "sections" sont communes et accessibles aux porteurs de titres des différents réseaux, les autres nécessitent un complément de billet de transport ou un autre abonnement. A Paris aussi il y a les zones de carte Orange. Ailleurs les réseaux d'agglomération peuvent partager des bus avec les transports départementaux ou régionaux, là encore avec des sections communes. Chaque section peut avoir une série de variante de trajets (tant que les sections se raboutent avec un point d'extrémité commun ou y font un terminus, aucun problème; cependant dans certains cas, le raboutement des sections peut se faire sur des nœuds différents: il faut alors autant de variantes pour chaque section à rabouter à la suivante, chaque section ayant plusieurs "pseudo-terminus"). Bref ce qui manque dans le schéma des routes c'est une relation de type "section", une ligne pouvant avoir plusieurs sections, et les sections pouvant être partagées (membres) par plusieurs lignes différentes (du même opérateur ou d'un autre opérateur). Cela résoudrait le tout, en permettant effectivement de mettre en commun des sections de plusieurs lignes, chaque section pouvant partager les mêmes conditions tarifaires ou pas, et être accessible dans plusieurs réseaux de transport partiellement superposés pour des lignes en co-exploitation. Le jeu. 15 févr. 2024 à 18:25, Eric SIBERT a écrit : > Des fois, je me dis que ça ne serait pas mal qu'il y ai un peu de > factorisation sur certaines lignes de bus hors agglomération. > > Sur un tronçon de la D1075 en Isère, il y a : > - 2 relations Bus 55 (aller et retour) (bus Zou opéré par Transdev > Dauphiné!!!) > - 2 relations bus T73 (interurbain Isère) > - 8 relations bus T75 (idem): différentes combinaisons de départ/arrivée > - 2 relations TA2A (pour aller au ski) > - 2 relations TAAH (idem) > - 2 relations TAVR (idem) > (- l'ancien train qui roulait sur la chaussée) > > Eric > > ___ > Talk-fr mailing list > Talk-fr@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-fr > ___ Talk-fr mailing list Talk-fr@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-fr
Re: [talk-au] Question about using NSW Speed Zone Data in OSM
They responded a few days ago but, as we're travelling atm, I didn't have a chance to do anything about it. Their response: "We sincerely appreciate your efforts in bringing to our attention the organised edits rules and guidelines, of which we were previously unaware. We acknowledge the necessity to adhere to these guidelines and commit to creating a wiki page for our organised edits accordingly. However, we kindly request some time to complete this task. Regarding our compliance with other editing rules, we are confident that we are fully adhering to them. It's important to note that our system utilises tools that rely on OpenStreetMap data. Upon discovering numerous discrepancies in the NSW speed zone data within OpenStreetMap, we initiated edits to rectify these inconsistencies. Our editing process follows a detailed verification procedure, outlined as follows: 1. A driver reports a speed discrepancy on a specific road. 2. The driver report undergoes thorough verification and is escalated for further examination. 3. We utilise NSW Speed Data ( https://opendata.transport.nsw.gov.au/dataset/speed-zones) to verify the reported speed limit. 4. If the claimed speed limit aligns with the NSW Speed Data, we proceed to update it in OpenStreetMap. 5. Conversely, if the reported speed limit does not match the NSW Speed Data, we reject the claim. However, if multiple drivers report the same speed limit discrepancy over time, we request evidence from the drivers, often resulting in the provision of images depicting posted speed limit signs. Based on this evidence, we update the speed limits in OpenStreetMap accordingly. We are eager to address any discrepancies that other mappers may have reported concerning the edits we have made. Could they kindly provide us with evidence to facilitate a detailed investigation? This will enable us to reassess and update our map editing processes as necessary. Our primary objective in making these edits is to enhance the experience of our drivers and community. Therefore, we welcome any suggestions or further discussion that would contribute to ensuring the accuracy of our edits." Don't know if that answers the questions you have? I've suggested that they set up an account here to talk about what they are doing. Thanks Graeme On Tue, 27 Feb 2024 at 11:36, Graeme Fitzpatrick wrote: > Message sent to User pointing out the OE Guidelines & also asking for > their sources. > > To f/up next week. > > Thanks > > Graeme > > > On Wed, 21 Feb 2024 at 22:10, Andy Townsend wrote: > >> On 21/02/2024 11:45, Mark Pulley wrote: >> >> I’ve got some further info on how this user has been editing (see comment >> on changeset https://www.openstreetmap.org/changeset/117791362 ) >> >> In short, Harsimranjit works for an un-named company. Unspecified people >> can report an incorrect speed limit on a road segment, it is verified >> (?how?) by someone else in the company, then goes to Harsimranjit who >> checks the claimed speed limit change with NSW Speed Zone Data, then if the >> NSW Speed Zone Data matches the proposed change, the edit is made. This >> process has obviously not worked in at least a few of these changesets (the >> ones I found had been changed incorrectly). >> >> >> Separate to any other issues, at the very least, that company should be >> following the organised editing guidelines. If you drop an email to >> d...@openstreetmap.org, we can try and persuade them to do so. I don't >> think we've had a ticket or report about this particular one so far. >> >> Best Regards, >> >> Andy (from the DWG) >> >> >> >> ___ >> Talk-au mailing list >> Talk-au@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/talk-au >> > ___ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
