Search changeset comments
Source:R/osmapi_changeset_discussion.R
osm_search_comment_changeset_discussion.RdReturns changeset comments that match the specified query. If no query is provided, the most recent changeset comments are returned.
Usage
osm_search_comment_changeset_discussion(
user,
from,
to,
format = c("R", "xml", "json"),
tags_in_columns = FALSE
)Arguments
- user
Search for changeset comments created by the user with the given user id (numeric) or display name (character).
- from
Beginning date range. See details for the valid formats.
- to
End date range. Only works when
fromis supplied. See details for the valid formats.- format
Format of the output. Can be
"R"(default),"xml", or"json".If
FALSE(default), the tags of the changesets are saved in a single list columntagscontaining adata.framefor each changeset with the keys and values. IfTRUE, add a column for each key. Ignored ifformat != "R".
Value
If format = "R", returns a data frame with one comment per If format = "xml", returns a
xml2::xml_document. If format = "json", returns a list with the json structure.
Details
The valid formats for from and to parameters are POSIXt values or characters preferably in
ISO 8601 format.
See also
Other changeset discussion's functions:
osm_comment_changeset_discussion(),
osm_hide_comment_changeset_discussion(),
osm_subscribe_changeset_discussion()
Examples
# See the latest changeset comments globally:
osm_search_comment_changeset_discussion()
#> id date visible uid user
#> 1 1619360 2026-07-01 08:26:22 TRUE 23056305 Ozon OSM16
#> 2 1619359 2026-07-01 08:25:49 TRUE 23056305 Ozon OSM16
#> 3 1619358 2026-07-01 08:23:42 TRUE 23056305 Ozon OSM16
#> 4 1619357 2026-07-01 08:23:25 TRUE 23056305 Ozon OSM16
#> 5 1619356 2026-07-01 08:16:10 TRUE 4451328 Arflha
#> 6 1619355 2026-07-01 08:13:15 TRUE 69628 vsandre
#> 7 1619354 2026-07-01 08:12:45 TRUE 289775 trial
#> 8 1619353 2026-07-01 08:12:38 TRUE 830106 literan
#> 9 1619352 2026-07-01 08:11:52 TRUE 24268372 Jona18345
#> 10 1619351 2026-07-01 08:07:56 TRUE 3249777 opendcc
#> 11 1619350 2026-07-01 08:06:07 TRUE 67832 joost schouppe
#> 12 1619349 2026-07-01 08:03:06 TRUE 34927 flohoff
#> 13 1619348 2026-07-01 08:01:07 TRUE 334075 eggie
#> 14 1619347 2026-07-01 07:59:19 TRUE 334075 eggie
#> 15 1619346 2026-07-01 07:56:10 TRUE 334075 eggie
#> 16 1619345 2026-07-01 07:55:54 TRUE 21888737 Sébastien Pi
#> 17 1619344 2026-07-01 07:53:19 TRUE 24265561 Morgsman
#> 18 1619343 2026-07-01 07:53:11 TRUE 334075 eggie
#> 19 1619342 2026-07-01 07:50:09 TRUE 334075 eggie
#> 20 1619341 2026-07-01 07:47:57 TRUE 17978826 LexB22
#> 21 1619340 2026-07-01 07:47:41 TRUE 13762529 no details provided here
#> 22 1619339 2026-07-01 07:46:06 TRUE 14014476 Eslam_Elsayed
#> 23 1619338 2026-07-01 07:39:16 TRUE 1813986 AndyB_66
#> 24 1619337 2026-07-01 07:38:25 TRUE 1293194 nevw
#> 25 1619336 2026-07-01 07:36:26 TRUE 24236201 Gavek
#> 26 1619335 2026-07-01 07:34:13 TRUE 21982638 pwbriggs
#> 27 1619334 2026-07-01 07:28:24 TRUE 23056305 Ozon OSM16
#> 28 1619333 2026-07-01 07:27:54 TRUE 23056305 Ozon OSM16
#> 29 1619332 2026-07-01 07:26:22 TRUE 23056305 Ozon OSM16
#> 30 1619331 2026-07-01 07:25:44 TRUE 718054 Piskvor
#> 31 1619330 2026-07-01 07:25:10 TRUE 23056305 Ozon OSM16
#> 32 1619329 2026-07-01 07:23:40 TRUE 23056305 Ozon OSM16
#> 33 1619328 2026-07-01 07:23:24 TRUE 3735696 DwarfNebula_
#> 34 1619327 2026-07-01 07:23:00 TRUE 23070430 Bloomenwease
#> 35 1619326 2026-07-01 07:21:38 TRUE 23056305 Ozon OSM16
#> 36 1619325 2026-07-01 07:18:59 TRUE 22440403 Ozon OSM4
#> 37 1619324 2026-07-01 07:09:54 TRUE 21587137 bernward1
#> 38 1619323 2026-07-01 07:09:14 TRUE 20051395 ajmat
#> 39 1619322 2026-07-01 07:08:23 TRUE 19194886 橘ヒカリ
#> 40 1619321 2026-07-01 07:07:39 TRUE 21587137 bernward1
#> 41 1619320 2026-07-01 07:07:13 TRUE 5426135 Carto'Cité
#> 42 1619319 2026-07-01 06:59:11 TRUE 197244 JeroenHoek
#> 43 1619318 2026-07-01 06:58:27 TRUE 20051396 rajdhani
#> 44 1619317 2026-07-01 06:54:21 TRUE 197244 JeroenHoek
#> 45 1619316 2026-07-01 06:52:44 TRUE 3172019 nurdafur
#> 46 1619315 2026-07-01 06:47:57 TRUE 24239154 Preben Vangberg
#> 47 1619314 2026-07-01 06:47:54 TRUE 9366685 Taunusklub | Stubenkaterin
#> 48 1619313 2026-07-01 06:44:39 TRUE 23813808 Gaung Tebono
#> 49 1619312 2026-07-01 06:43:32 TRUE 20051395 ajmat
#> 50 1619311 2026-07-01 06:41:51 TRUE 23813808 Gaung Tebono
#> 51 1619310 2026-07-01 06:41:05 TRUE 23813808 Gaung Tebono
#> 52 1619309 2026-07-01 06:39:12 TRUE 24265483 Robert Widmann
#> 53 1619308 2026-07-01 06:30:45 TRUE 22994073 RahilPasha
#> 54 1619307 2026-07-01 06:30:34 TRUE 564585 wegavision
#> 55 1619306 2026-07-01 06:25:24 TRUE 553736 A67-A67
#> 56 1619305 2026-07-01 06:21:19 TRUE 23941607 Hnsptrs
#> 57 1619304 2026-07-01 06:20:51 TRUE 52626 pitscheplatsch
#> 58 1619303 2026-07-01 06:18:56 TRUE 9526415 UT93
#> 59 1619302 2026-07-01 06:15:09 TRUE 52626 pitscheplatsch
#> 60 1619301 2026-07-01 06:10:20 TRUE 6794624 Comino
#> 61 1619300 2026-07-01 06:10:13 TRUE 567792 Natfoot
#> 62 1619299 2026-07-01 06:09:16 TRUE 322785 BCNorwich
#> 63 1619298 2026-07-01 06:07:34 TRUE 322785 BCNorwich
#> 64 1619297 2026-07-01 05:59:00 TRUE 2649988 FajrAl
#> 65 1619296 2026-07-01 05:58:49 TRUE 2649988 FajrAl
#> 66 1619295 2026-07-01 05:58:20 TRUE 365601 Luzandro
#> 67 1619294 2026-07-01 05:55:51 TRUE 353766 PeeWee32
#> 68 1619293 2026-07-01 05:55:41 TRUE 274857 Supaplex
#> 69 1619292 2026-07-01 05:46:43 TRUE 365601 Luzandro
#> 70 1619291 2026-07-01 05:41:31 TRUE 322785 BCNorwich
#> 71 1619290 2026-07-01 05:32:35 TRUE 20051396 rajdhani
#> 72 1619289 2026-07-01 05:31:07 TRUE 348712 lukasbrunner
#> 73 1619288 2026-07-01 05:30:29 TRUE 22419583 Amirali Asghari
#> 74 1619287 2026-07-01 05:29:30 TRUE 22419583 Amirali Asghari
#> 75 1619286 2026-07-01 05:28:46 TRUE 3085 mat
#> 76 1619285 2026-07-01 05:27:32 TRUE 22419583 Amirali Asghari
#> 77 1619284 2026-07-01 05:21:51 TRUE 34927 flohoff
#> 78 1619283 2026-07-01 05:16:28 TRUE 7130304 gc27
#> 79 1619282 2026-07-01 05:08:34 TRUE 7130304 gc27
#> 80 1619281 2026-07-01 04:56:58 TRUE 20144444 MappingMore
#> 81 1619280 2026-07-01 04:54:31 TRUE 7130304 gc27
#> 82 1619279 2026-07-01 04:52:57 TRUE 16979815 citrula
#> 83 1619278 2026-07-01 04:51:22 TRUE 21943149 alokchauhan_Lyft
#> 84 1619277 2026-07-01 04:42:19 TRUE 22495932 Ozon OSM10
#> 85 1619276 2026-07-01 04:41:04 TRUE 353766 PeeWee32
#> 86 1619275 2026-07-01 04:30:37 TRUE 2649988 FajrAl
#> 87 1619274 2026-07-01 04:26:20 TRUE 2649988 FajrAl
#> 88 1619273 2026-07-01 04:23:48 TRUE 9473778 jmarchon
#> 89 1619272 2026-07-01 04:21:21 TRUE 4997045 Tomas_J
#> 90 1619271 2026-07-01 04:10:30 TRUE 18783691 sbedwal_Lyft
#> 91 1619270 2026-07-01 04:03:56 TRUE 10163840 okadatsuneo
#> 92 1619269 2026-07-01 04:02:20 TRUE 1403313 supervalters
#> 93 1619268 2026-07-01 03:35:22 TRUE 542403 SD Mapman
#> 94 1619267 2026-07-01 03:06:05 TRUE 16275544 nileshbarawkar
#> 95 1619266 2026-07-01 03:05:26 TRUE 16275544 nileshbarawkar
#> 96 1619265 2026-07-01 02:57:32 TRUE 1676637 Kilkenni
#> 97 1619264 2026-07-01 02:46:55 TRUE 5706452 Bienson
#> 98 1619263 2026-07-01 02:15:00 TRUE 18308607 LeticiaB
#> 99 1619262 2026-07-01 02:13:36 TRUE 2008037 VictorIE
#> 100 1619261 2026-07-01 02:04:21 TRUE 9104166 pantufla
#> comment_text
#> 1 Здравствуйте, все исправлено
#> 2 Здравствуйте, все исправлено
#> 3 Здравствуйте, все исправлено
#> 4 Здравствуйте, все исправлено
#> 5 https://www.openstreetmap.org/changeset/184390244
#> 6 Hallo Jeti,\nich fand auf Seiten der Stadt Marienberg nur die Schreibweise mit ß. Gab es hier offiziell eine Anpassung des Namens?\n\nhttps://www.google.com/search?q=schlossbergstra%C3%9Fe+site%3Ahttps%3A%2F%2Fwww.marienberg.de
#> 7 Oui, une remarque 15 ans après !\nN'est-ce pas plutôt Le Tinduff (et non Tinduff tout court). On parle du Port du Tinduff, pas du Port de Tinduff par exemple.
#> 8 теги группы name предназначены для common name (общеупотребительных названий). Для официальных названий есть тег official_name (и даже official_name:en и т.п.)\n\nНазвания, используемые в официальной навигации, вполне применимы в ОСМе, просто не в тегах name:en. Я уже написал выше, что теги name:en и прочие предназначены не для локализации на латинице, не для транскрипций и транслитераций (их вообще нельзя вносить в ОСМ, т.к. они легко получаются автоматом), а для названий на английском языке. Очевидно, что "Moskva" это не название на английском языке.
#> 9 Die 30 sind neu die wurden vor ungefähr 2 Wochen aufgestellt
#> 10 Hallo, ein paar Hinweise:\na) bitte einen kurzen Kommentar angeben, was Du gemacht hast (hier z.B. Saugstelle ergänzt)\nb) Bitte benutze die richtigen Tags - also z.B. emergency=suction_point. Siehe auch https://wiki.openstreetmap.org/wiki/DE:Key:emergency\nc) Vermeide name-tagging. Name ist nur der Eigenname, keine Beschreibung.\nViele Grüße
#> 11 De "traverser" is duidelijk geen "rails for full sized passenger or freight trains in the typical gauge of the country or state" en het lijkt me ook geen "railway track in private use that serve only freight transport to/from ports, industrial complexes or mining areas, and for connecting these to the public network"\nIk zou hier minstens voor usage iets "unieker" gebruiken, ik kwam bijvoorbeeld al usage=freight_crane tegen. Misschien kan je gewoon een nieuwe waarde uitvinden.
#> 12 Moin,\nist das 30 neu z.b. auf der Preußenstraße? Das hir hat zu einer routingänderung geführt und ich habe mal schnell Bilder auf Mapillary von 2023 gesehen und da steht da nix von 30.\n\nSind die neu?\n
#> 13 reverted by changeset #184899467\n\nJe eigen edits https://overpass-api.de/achavi/?changeset=184898648\n\n De huidige situatie deze week..\nhttps://viewer.satellietdataportaal.nl/@52.00041,4.488811,19/?datastrip=20260628_SVNEO-01&sensorname=SuperView-NEO
#> 14 Op 28 juni waren deze straten gewoon aanwezog. Ik draai je edits even terug. Ik denk niet dat dit je bedoeling was.\n\nMVG\neggie
#> 15 Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.\nFeedback Jouw betere aanpassing bestaat uit het verwijderen van een woonstraat en een fietspad waardoor hier niets meer routeert? \nMVG,\nEggie\nNamens de OSM Community\n\n
#> 16 Bonjour Charles,\n\nMerci pour avoir fait le gros du parc. Vous n’aviez pas vu ma note ?\n\nSinon, j’ai remarqué un trou au nord : https://www.openstreetmap.org/note/5369456. Il y a une sorte de structure (un abri ?) qui n’est pas cartographié. Est-ce que vous savez ce que c’est ? Je ne suis pas repassé depuis 10/15 j, de l’extérieur, je ne savais pas trop ce que c’était.\n\nMerci
#> 17 Ok thanks. The track at the back of my property is a gated (locked) fire track not accessible to the public. I’ll see if I can work out how to map my driveway.
#> 18 Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.\nMVG,\nEggie\nNamens de OSM Community\n\n
#> 19 👍
#> 20 Hi Eggie,\n\nDank voor de reactie en tip.\nHeb het daar ook gemeld.\n\nGroet, Lex.
#> 21 Thanks for doing this and making some valuable changes. Good work. But I can see some semi detached houses near me which have now been tagged as terraced. Can I help with anything in 'my' patch?
#> 22 Hello Equalizer379,\n\nThank you for reaching out.\n\nI edited the petrol station paths based on more recent imagery for this area (Vantor satellite imagery via Vantor Hub, dated 2026-06-08.\n\nCould you please provide us with the source you used?\nRegards,\nEslam_Elsayed
#> 23 OSM to nie prywatny notatnik.
#> 24 Thanks for tidying that up. There is a chance that some navigation apps may try to use the 4wd track at the back of your property instead of Parkside Court to get to your place. If that happens, you could put your address on a node and shift it to be closest to Parkside Court or map your driveway.
#> 25 Witaj, zostawiłem sobie nazwe Tartak, bo miałem na celu doprecyzowanie tej nazwy po wizycie w terenie.
#> 26 Confirming that "West Main Plaza" is official and/or signed, and not a descriptive name?\n\nThanks
#> 27 Здравствуйте, все исправила
#> 28 Здравствуйте, все исправила
#> 29 Здравствуйте, хорошо
#> 30 Ahoj, teď jsem jel kolem, a asi je to z hlediska mapy jedno - ale ta nástupiště už tam nejsou, fyzicky rozebrali zastřešení, a teď bourají samotná nástupiště. Nové koleje budou v nové poloze, a k nim (někdy) budou nová nástupiště. Pokládal jsem za vhodnější nemást cestující veřejnost, když reálně existuje už jen nástupiště 4/5 - proto jsem 2/3 a 1 označil jako removed:*\n\nNicméně nebudu se o to přetahovat, vzhledem k tomu, že tu stavbu aktualizuješ šířeji a přesněji - za což děkuji.\n\nMapování zdar, \nPiškvor
#> 31 Здравствуйте, спасибо, буду внимательнее
#> 32 Здравствуйте, все исправила
#> 33 Nr 6 heb ik overgenomen van https://www.openstreetmap.org/way/1328889979/history/1. Hier stonden twee ways over elkaar heen getekend. Deze heb ik samengevoegd tot 1.
#> 34 Besten Dank, wieder was gelernt. Ist korrigiert!
#> 35 Здравствуйте, все исправлено
#> 36 не заметила тег. Спасибо
#> 37 Ich hab mich vertan, Buttermarkt ist richtig, aber - Im Broel - ist falsch.
#> 38 Reverted in https://www.openstreetmap.org/changeset/184897694
#> 39 良乡站内卫星图未更新，副中心线关系待更新后重新组织。
#> 40 Diese Änderung stimmt nicht.\nDie Busse von Kellberg fahren nicht über Buttermark. Dort werden nur einige Kurzstreckenbusse eingesetzt
#> 41 Bonjour.\nC'est une erreur de ma part, je n'ai pas fait attention au tag oneway lorsque j'ai fusionné les 2 chaussées, suite à la modification de la voirie (la BDOrtho n'est plus à jour).\nJe viens de corriger, merci pour la notification !\nAntoine.
#> 42 https://www.openstreetmap.org/way/1328548408\n\nDeze brug kreeg hier in de bouwfase emergency=no mee. Wat betekent dit? Zit er nu deze brug af is nog een beperking op voor hulpdiensten?\n\nHet probleem van emergency=no is dat niemand weet wat het betekent, en waarom die er staat. We weten nu alleen dat iemand van de veiligheidsregio heeft geconstateerd dat er geen hulpdiensten kunnen komen (alle?), maar niet of er een specifieke beperking is. Mappers durven emergency=no ook niet weg te halen uit angst iets open te zetten wat problemen oplevert bij gebruikers van LiveNav.\n\nIn plaats van emergency=no is de specifieke beperking (gewicht, breedte) handiger. Weet je nog wat hier speelde?\n\nZie ook:\n\nhttps://community.openstreetmap.org/t/emergency-yes-op-wegen/125607/106
#> 43 Partially reverted in changeset id: https://www.openstreetmap.org/changeset/184897400
#> 44 Dank je, dat illustreert het probleem er mee wel een beetje.
#> 45 Das darfst du gerne mit dem Menschen besprechen, der den Tunnel angelegt hat. Ich hab es einfach so belassen, wie es war.
#> 46 Thank you for the clarification, I just wanted to be sure. Having searched around for a while, it seems to me that as long as it came from OS Open data (https://wiki.openstreetmap.org/wiki/Ordnance_Survey_OpenData) it is fine, while if it came from Geoplace (i.e. NSG) then it probably isn't since their licence is more strict.
#> 47 Hallo Herwescheluc, Warum hast Du den Weg umgelegt? Wie sehen die Wegezeichen vor Ort aus? Sind diese auch umgelegt oder verweisen sie noch auf die alte Führung? Danke für Deine Antwort Stubenkaterin
#> 48 Sorry, Open Street Maps (OSM) has different terminology than the basic government regulations regarding road status. If the status written on the OSM Wiki is still the same as government regulations, the explanation should be changed as much as possible so as not to cause confusion for contributors who want to edit.
#> 49 Reverted in https://www.openstreetmap.org/changeset/184896810
#> 50 In OSM, it's not mandatory to follow government regulations regarding road classification, as road classification status in OSM is dynamic, not static. It could be that the road classification in OSM has increased in level because the traffic level is quite high, so it requires a more appropriate classification for high traffic.
#> 51 In OSM, it's not mandatory to follow government regulations regarding road classification, as road classification status in OSM is dynamic, not static. It could be that the road classification in OSM has increased in level because the traffic level is quite high, so it requires a more appropriate classification for high traffic.
#> 52 Hallo Marv,\n\nes sind zwei getrennte Grundstücke.\nProblem ist das Paketdienste hier durchfahren da sie meinen es ist eine Öffentliche Durchfahrt.\n\nDieser sogenannte Weg sollte kompett raus aus der Karte (den gibt es eigentlich nicht (siehe bei Google oder anderen Maps)\n\nBesten Dank und viele Grüße\n\nRobert
#> 53 Hi gurglypipe,.\nThanks for the correction and for fixing it. I will be more careful with tagging and checking existing history next time\nRegards\nRahil Pasha\n
#> 54 Man kann ja schauen, was vorher war, es ist aber wirklich spitzer Splitt, wie er für den Unterbau von Straßen genutzt wird. Also nur was für sehr breite Reifen.
#> 55 Deze tags zijn ooit toegevoegd door iemand van de veiligheidsregio in deze wijziging https://www.openstreetmap.org/changeset/137556695\n\nHet is inderdaad een onduidelijke tag waaruit niet blijkt of de brug niet voor hulpdiensten beschikbaar is, of dat dit alleen gold tijdens de bouwfase. Dat weet ik dus ook niet. Ik probeer zo veel mogelijk van dat soort tags af te blijven.\n\n
#> 56 beter...\n\nbedankt
#> 57 Thanks for adding this information. I just want to make sure the tagging is correct: are values like YY11, YY07, RIP 1 and RIP 2 official/public track names, or are they internal track references from the source data?\n\nIf they are track references, they may be better mapped with ref=* or railway:track_ref=* instead of name=*\n
#> 58 Für mich erscheint es auch als Novum, dass man Tunnelumrisse separat erfasst. Dass es sich um einen Tunnel handelt, ist doch eigentlich schon in den Attributen vom Weg https://www.openstreetmap.org/way/83518319 niedergeschrieben...
#> 59 Thanks for confirming. I asked because the name is strongly worded and I wanted to verify that it is indeed the established/intentional route name rather than vandalism or an accidental edit.
#> 60 Thanks for adding the address details. I made some changes based on the Japanese wiki I wrote. Please have a look at: \n\nhttps://gitea.btcmap.org/teambtcmap/btcmap-general/wiki/Tagging-Merchants-in-Japan\n
#> 61 yeah sorry about the G used it for the multipolygon. please point me at the documentation for land coverings. about multipolygon use. \nThanks\n
#> 62 The route relation was also removed; it would not have been needed for a single road.
#> 63 Way: 1533918293 is removed as it duplicates existing highways and thus could dusrupt routing. It also caused the warning above that you ought to have heeded.\n\nRegards Bernard.
#> 64 #MapCupAPAC2026 #WOMAN #tt_event
#> 65 #MapCupAPAC2026 #WOMAN #tt_event
#> 66 Danke, wollte es auch gerade endlich wiederherstellen, nachdem hlfan nicht auf meinen Kommentar reagiert hat
#> 67 Ik zie dat er veel nog een tourism = viewpoint hebben toegevoegd. Dat rendert wel
#> 68 Block given by Data Working Group: https://www.openstreetmap.org/user_blocks/20893\n\nPeople are trying to contact you about your border edits. Please respond to these comments, and please refrain from making any further border edits unless you have some sort of consensus about them.\n\nIf you have anything to say, you can email us at data@osmfoundation.org with the subject containing “Ticket #2026061810000406”\n\nBest regards, Dennis Raylin Chen On behalf of the OSMF Data Working Group OpenStreetMap Foundation [Ticket #2026061810000406]\n\nDennis Raylin Chen, Data Working Group, OpenStreetMap Foundation\n ---\n #REVIEWED_BAD #OSMCHA\n Published using OSMCha: https://osmcha.org/changesets/182192067\n
#> 69 Hallo,\n\nich habe die Änderung auf highway=busway wieder rückgängig gemacht. Eine Zufahrt zu einer Haltestelle ist grundsätzlich schon einmal kein "Bus Rapid Transport System"\n\nhttps://wiki.openstreetmap.org/wiki/Tag:highway%3Dbusway#What_is_not_a_busway\n\nIm konkreten Fall können die Straße außerdem auch noch andere Berechtigte zur Zufahrt für https://www.openstreetmap.org/way/235770799 verwenden, was durch die Änderung genauso abgeschnitten war, wie die Zufahrt zum Radweg (wobei letzteres sowieso nicht ganz korrekt war, weil der eigentlich schon ein paar Meter vor der Einfahrt anfängt)
#> 70 Hi, The terraced buildings you are adding are often self-intersecting and have many unjoined nodes at party walls. I've corrected a lot of these and also squared up the buildings.\n\nIt's quite easy with JOSM to terrace a building, and doing so alleviates all the mentioned problems. It will make your mapping much better and neater.\n\nNeed any help? Please just ask.\n\nRegards Bernard.
#> 71 Reverted in changeset id: https://www.openstreetmap.org/changeset/184894648
#> 72 Grazie della pronta risposta.\nHo giusto fatto un sopralluogo ieri, non ho visto divieti specifici, e ho visto parecchi velocipedi circolare. Procederò quindi a reintrodurre il tag.\nGrazie ancora e buona giornata!
#> 73 کدگذاری معابر حذف شدنی نیستند و معبر تگ فرعی، تگ اصلی نمیگیرد.\nنقض یک سند شهرداری تهران میباشد.\nوقتی تابلو، کدگذاری دارد، اینجا کدگذاری نداشته باشد؟\nقطع دسترسی بی پایان لیاقت شماست.\nمن که نمی توانم تو را مسدود نمایم. یکی مسدودش کند. حداقل ۱۰ سال. حداکثر بینهایت و بیپایان.\nخرابکار معابر تهران تویی.\nاوپن استریت مپ برای امثال شما طراحی نشده.\nپس، گوگل مپ هست که بعضی معابر را قبول می کند ولی بعضی را قبول نمیکند.\nبجای ویرایش نقشه، غاز بچرانید.\nوالا که در ایستگاه های جدید مترو تهران میبینم، نقشههای اوپناستریت مپ هست. تو رو خدا خرابکاری نکنید و نقشه ویرایش کن نیستید.\nاگر الان تو ویکیپدیا بودی، الان داشتی توی قطع دسترسی بیپایان به سر میبردی. و الان داشتی گوسفند چرا میکردی نه ویرایش.
#> 74 کدگذاری معابر حذف شدنی نیستند و معبر تگ فرعی، تگ اصلی نمیگیرد.\nنقض یک سند شهرداری تهران میباشد.\nوقتی تابلو، کدگذاری دارد، اینجا کدگذاری نداشته باشد؟\nقطع دسترسی بی پایان لیاقت شماست.\nمن که نمی توانم تو را مسدود نمایم. یکی مسدودش کند. حداقل ۱۰ سال. حداکثر بینهایت و بیپایان.\nخرابکار معابر تهران تویی.\nاوپن استریت مپ برای امثال شما طراحی نشده.\nپس، گوگل مپ هست که بعضی معابر را قبول می کند ولی بعضی را قبول نمیکند.\nبجای ویرایش نقشه، غاز بچرانید.\nوالا که در ایستگاه های جدید مترو تهران میبینم، نقشههای اوپناستریت مپ هست. تو رو خدا خرابکاری نکنید و نقشه ویرایش کن نیستید.\nاگر الان تو ویکیپدیا بودی، الان داشتی توی قطع دسترسی بیپایان به سر میبردی. و الان داشتی گوسفند چرا میکردی نه ویرایش.
#> 75 Bonjour, vous avez passé une partie de l'avenue jean-jaures, en dessous du Auchan, en sens unique, mais le reste de la rue est à double sens. Ça semble étrange de juste avoir une section de genre 50 mètres en sens unique, est-ce une erreur, ou y-a-t-il une autre raison ?
#> 76 کدگذاری معابر حذف شدنی نیستند و معبر تگ فرعی، تگ اصلی نمیگیرد.\nنقض یک سند شهرداری تهران میباشد.\nوقتی تابلو، کدگذاری دارد، اینجا کدگذاری نداشته باشد؟\nقطع دسترسی بی پایان لیاقت شماست.\nمن که نمی توانم تو را مسدود نمایم. یکی مسدودش کند. حداقل ۱۰ سال. حداکثر بینهایت و بیپایان.\nخرابکار معابر تهران تویی.\nاوپن استریت مپ برای امثال شما طراحی نشده.\nپس، گوگل مپ هست که بعضی معابر را قبول می کند ولی بعضی را قبول نمیکند.\nبجای ویرایش نقشه، غاز بچرانید.\nوالا که در ایستگاه های جدید مترو تهران میبینم، نقشههای اوپناستریت مپ هست. تو رو خدا خرابکاری نکنید و نقشه ویرایش کن نیستید.\nاگر تو ویکیپدیا بودی، الان توی قطع دسترسی بیپایان بودی. و الان داشتی گوسفند چرا میکردی نه ویرایش.
#> 77 Wie unterscheidest du am weg das sie angeordnet sind Z240ff. (Also nicht an der Straße sondern an dem eigentlichen weg?)\n\nUnd dann guck mal in dem Wiki Artikel ob es dazu mal eine Abstimmung und einen Konsens gab. \n\nUnd dann Frag mal im Forum - Dann bekommst du 20 Antworten. \n\nDas Radverkehrsanlagen mit "designated" getagged werden auch ohne Piktogram oder Z240ff ist kein Konsens (Und ich halte es für informationsverlust es zu tun)\n\nFlo
#> 78 https://wiki.openstreetmap.org/wiki/JA:Automated_edits 機械的編集についてOSMコミュニティの方針を確認してください
#> 79 https://wiki.openstreetmap.org/wiki/JA:Automated_edits 機械的編集についてOSMコミュニティの方針を確認してください
#> 80 Partially Revert of https://www.openstreetmap.org/changeset/184816297
#> 81 https://wiki.openstreetmap.org/wiki/JA:Automated_edits OSMの指針を確認してください
#> 82 hello, and welcome back to OSM! You seem to be changing a lot of cycleways from `cycleway:*=separate` to `cycleway:*=track`. Could you explain what you are trying to accomplish with these edits?\n\nWhen cycleways are tagged as a separate way, we use =separate on the road to indicate that.\n\nhttps://wiki.openstreetmap.org/wiki/Tag:cycleway%3Dseparate\n\n
#> 83 Hi cubbe8,\nThank you for reviewing this edit and correcting the mistake. My name is Alok, and I am a mapper on Lyft's OSM team.\nRegarding my edits: the no left turn restriction was added based on a bit outdated ground truth imagery (https://drive.google.com/file/d/1q3ocbAQKH8rPVkkjscsK32P2DrB5_6F6/view?usp=sharing), from 9th of June. Upon reviewing your feedback and verifying the location with Lyft-owned street-level imagery (https://drive.google.com/file/d/1hp5o_a6Y3uUDG2PLl0jqbDUDUGriU_ve/view?usp=sharing) dated June 27, I agree that no restriction sign is present & the lane markings have also been updated.\nPlease accept my sincere apologies for this oversight. I appreciate your careful review and will ensure greater attention to detail in future changesets.\nAlok\n
#> 84 Здравствуйте, все исправила, извините за вневнимательность.
#> 85 Ik zie dat je alleen 6 hebt toegevoegd en dat de andere al bestonden. Mijn fout. https://wcww.openstreetmap.org/way/1334532172/history/2 Het is wel consequent . Het is ook lastig hoe een locale ref aangegeven moet worden. Misschien was Toilet 6 wat duidelijker. Ik zie dat het bij spoornummer op een station ook soms zoiets gedaan wordt. Al lijkt daar https://wiki.openstreetmap.org/wiki/Key:railway:track_ref ook gebruikt te worden Helaas zie ik nergens in OSM een toilets_ref. Ik laat het maar zitten. Groet Peter https://www.openstreetmap.org/way/423874816
#> 86 ketika salurannya melewati jalan (contoh: https://www.openstreetmap.org/way/800604062), bisa klik salurannya dan pilih bar kuning "make as culvert / buat gorong-gorong" secara otomatis. Atau jika jalannya berupa jembatan, jalannya yg diklik, nanti ada tulisan "make as bridge / buat jembatan" secara otomatis.
#> 87 Ubah pengaturan ke bahasa Indonesia, itu akan lebih memudahkan saat pencarian jenis objeknya.
#> 88 Looks good to me. Welcome to OSM!
#> 89 Tak plz. vymaž alebo zmeň na description. Dik.
#> 90 Hi ChaireMobiliteKaligrafy ,\nMy name is Santosh & I am the mapper on the OSM team at Lyft.Apologies for the mistake, and thanks for pointing this out. I’ll review the wiki guidance on placement=transition and the correct usage of width:lanes:start/end to better understand the expected approach.I’ll also share this learning with the team to help ensure we follow the correct approach in similar cases going forward. Appreciate you reverting the change and providing the clarification. \n\nThank you for your contribution to OSM!\n\n\nRegards,\nSantosh\n
#> 91 勝手な値 "building:levels=2" を入れないで下さいと別のコメントで書きましたが、まだ同様の編集をされるのでしょうか？\n
#> 92 north side. almost at the end of the road. a new path emerged east side at the end of the road.
#> 93 So after discussion in the local-nebraska channel on Slack, it looks like the intent was to keep it motorway until 96th, which also follows the state-specific classification schematic (https://wiki.openstreetmap.org/wiki/User:Stretch_Longfellow/Nebraska_Highway_Classification). I have made the changes to match the 2021 classification page: https://www.openstreetmap.org/changeset/184891161
#> 94 Hi,\n\nCould you please let us know the basis on which you changed the highway classification from trunk to residential? This road is NH 227 and as per OSM highway classification guidelines, National Highways should be mapped as trunk roads.\n\nKindly refer to the OSM highway classification guidelines before making such edits to ensure consistency and accuracy.\n\nThank you.
#> 95 Hi,\n\nCould you please let us know the basis on which you changed the highway classification from trunk to unclassified? This road is NH 227 and as per OSM highway classification guidelines, National Highways should be mapped as trunk roads.\n\nKindly refer to the OSM highway classification guidelines before making such edits to ensure consistency and accuracy.\n\nThank you.
#> 96 Заливати проміжки між будинками "парком" - некоректно. Це газони, а не парки, так робити не треба. leisure=park використовується тільки для справжніх парків та скверів (зазвичай цей статус їм наданий містом, і вони знаходяться на балансі місцевого Зеленбуду)
#> 97 surface=paving_stones beschreibt nur ein zusammenhängendes Pflaster aus Steinen. Das hier wäre surface=stepping_stones.\n\nSiehe https://wiki.openstreetmap.org/wiki/DE:Key:surface
#> 98 Hola Felipe\nDale, gracias. Tomaré cuidado para los proximos
#> 99 Hi,\n\nhttps://www.openstreetmap.org/way/1301808776\n\nTypo: 87 x "addr:city=Battystown" in Cois na Mara estate.
#> 100 Hello, there is an important mistake here, since according to wiki, when adding damage event, the building=* \nshould NOT bet removed. This is important for map data consumers, especially in critical moments, like rescuers using updated map data, to be able to find these buildings. \n\nThis is critical.\n\nPlease help me correct all the data.
# Search for changeset comments by a specific user:
osm_search_comment_changeset_discussion(user = "Steve", format = "json")
#> $version
#> [1] "0.6"
#>
#> $generator
#> [1] "OpenStreetMap server"
#>
#> $copyright
#> [1] "OpenStreetMap and contributors"
#>
#> $attribution
#> [1] "http://www.openstreetmap.org/copyright"
#>
#> $license
#> [1] "http://opendatacommons.org/licenses/odbl/1-0/"
#>
#> $comments
#> $comments[[1]]
#> $comments[[1]]$id
#> [1] 664366
#>
#> $comments[[1]]$visible
#> [1] TRUE
#>
#> $comments[[1]]$date
#> [1] "2021-02-25T19:31:46Z"
#>
#> $comments[[1]]$uid
#> [1] 1
#>
#> $comments[[1]]$user
#> [1] "Steve"
#>
#> $comments[[1]]$text
#> [1] "woo!"
#>
#>
#>
# Search for changeset comments between January 1st and January 2nd, 2015:
osm_search_comment_changeset_discussion(from = "2015-01-01", to = "2015-01-02", format = "xml")
#> {xml_document}
#> <osm version="0.6" generator="OpenStreetMap server" copyright="OpenStreetMap and contributors" attribution="http://www.openstreetmap.org/copyright" license="http://opendatacommons.org/licenses/odbl/1-0/">
#> [1] <comment id="3597" date="2015-01-01T23:41:30Z" visible="true" uid="10915 ...
#> [2] <comment id="3596" date="2015-01-01T23:36:36Z" visible="true" uid="88164 ...
#> [3] <comment id="3595" date="2015-01-01T23:29:40Z" visible="true" uid="88164 ...
#> [4] <comment id="3594" date="2015-01-01T23:24:27Z" visible="true" uid="61942 ...
#> [5] <comment id="3593" date="2015-01-01T23:19:58Z" visible="true" uid="88164 ...
#> [6] <comment id="3592" date="2015-01-01T23:15:54Z" visible="true" uid="23858 ...
#> [7] <comment id="3591" date="2015-01-01T23:15:38Z" visible="true" uid="39688 ...
#> [8] <comment id="3590" date="2015-01-01T23:12:25Z" visible="true" uid="61942 ...
#> [9] <comment id="3589" date="2015-01-01T22:23:35Z" visible="true" uid="61942 ...
#> [10] <comment id="3588" date="2015-01-01T22:14:08Z" visible="true" uid="61942 ...
#> [11] <comment id="3587" date="2015-01-01T21:53:43Z" visible="true" uid="18850 ...
#> [12] <comment id="3586" date="2015-01-01T21:53:40Z" visible="true" uid="61942 ...
#> [13] <comment id="3585" date="2015-01-01T21:29:38Z" visible="true" uid="33121 ...
#> [14] <comment id="3584" date="2015-01-01T20:30:27Z" visible="true" uid="25485 ...
#> [15] <comment id="3583" date="2015-01-01T19:49:08Z" visible="true" uid="23858 ...
#> [16] <comment id="3582" date="2015-01-01T19:40:03Z" visible="true" uid="12992 ...
#> [17] <comment id="3581" date="2015-01-01T19:39:16Z" visible="true" uid="12992 ...
#> [18] <comment id="3580" date="2015-01-01T17:53:47Z" visible="true" uid="13112 ...
#> [19] <comment id="3579" date="2015-01-01T16:35:02Z" visible="true" uid="10915 ...
#> [20] <comment id="3578" date="2015-01-01T16:23:43Z" visible="true" uid="61942 ...
#> ...