piebro/osm-data huggingface dataset:
berms (2019-02-25 23:15:50+00:00): Hi Hjart,

Thanks for the recommendation on the changeset comments.

I think we could simplify this junction while still maintaining functionality. What if I edit the members/roles in relation 9292138 (https://www.openstreetmap.org/relation/9292138) as such: from (https://www.openstreetmap.org/way/117459151), via (https://www.openstreetmap.org/way/496188128), to (https://www.openstreetmap.org/way/668141663). This would allow us to remove relation 9291740 (https://www.openstreetmap.org/relation/9291740) and way 668141664 (https://www.openstreetmap.org/way/668141664).

I also propose we remove relation 9292142 (https://www.openstreetmap.org/relation/9292142), because according to Mapillary https://www.mapillary.com/app/?lat=55.374774&lng=10.36890500000004&z=17&pKey=iRV92h0yVvqkQkcisvROFA&focus=photo, left turns appear to be legal. What are your thoughts?

Thanks,

Berms
FrankXF (2019-02-04 21:33:53+00:00): Hallo  timfelgentreff, das Hotel gibt es doch schon hier.
eggie (2019-02-03 22:48:57+00:00): Oke.., maar wat ik bedoel is dat je alle weggebruikers niet op een reguliere weg hoeft te taggen met access tags. 
Fout is het niet, maar wel heel erg overbodig. 
https://overpass-api.de/achavi/?changeset=66887969
Eggie
takazu (2019-03-22 00:51:07+00:00): Dear jdd3,

there are several issues with your changeset. Please take a look at diff view at https://overpass-api.de/achavi/?changeset=66887990

Why have you
* deleted the platform ways at Deerfield?
* created this artifact https://www.openstreetmap.org/way/668153669 ?
* cut the railway lines beneath this bridge https://www.openstreetmap.org/way/668155605 ?

Please explain your actions and be more careful!
geozeisig (2019-02-05 07:39:43+00:00): Du hast auf der Schönhauser Allee embedded_rails=tram hinzugefügt. Hier hat die Tram aber einen eigenen Gleiskörper und ist nicht auf der Fahrbahn. Auf der Kastanienallee paßt diese Eigenschaft.
28MzXP5-_uXH (2019-02-05 09:45:00+00:00): Aber dort ist der Gleisbereich doch auch Fahrbahn für Autos, siehe https://www.mapillary.com/app/?pKey=2h3WSXSr2b9-btunW4Z7Pg&focus=photo&lat=52.54839738545656&lng=13.413435232653551&z=17
Oder wird das anders gewertet, weil es schon eine "eigene" Fahrbahn ist?
geozeisig (2019-02-05 17:19:47+00:00): Du hast recht. Ich hatte eine falsche Vorstellung von dem Ort in meinem Kopf.
embedded_rails=tram ist noch so neu das ich mal Beispiele dafür gesucht habe. Las es also so.
28MzXP5-_uXH (2019-02-06 22:15:43+00:00): Alles klar, aber danke für's Checken :)
viloan (2019-02-03 22:53:55+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
Carnildo (2019-02-05 10:38:43+00:00): The "apartment complex" tag is meant to go around the entire area - buildings, parking, garages, lawn, and all.  There's also an "apartment building" tag for the actual building.
Evilscaught (2019-02-05 18:45:16+00:00): Thank you for informing me and fixing that mistake, I'll keep that in mind for future edits!

Best,
Scott.
Hjart (2019-02-03 23:29:35+00:00): Bemærk at det generelt er bedst at holde arealer adskilt fra vejnettet.
Poul G (2019-02-03 23:33:57+00:00): Øh ... tænker du på, at indkørslen skal stoppe ved gårdspladsen? For der går da masser at veje og stier hen over skoven.
Hjart (2019-02-03 23:44:26+00:00): Jeg mener "haven". Det er bedst at undgå at tegne kanten af arealer oveni veje. Det er fint at veje går gennem skove mm.
Hjart (2019-02-03 23:55:36+00:00): Årsagen opdager man desværre først hvis man senere skal ændre vejnettets geometri. Så kan det vise sig at være en voldsomt besværlig operation og for en del mindre erfarne næsten umuligt uden at ødelægge begge dele.
BCNorwich (2019-02-04 07:48:45+00:00): Hello and Welcome to OpenStreetMap.

You've made a good job of adding the cycleway but I just wanted to point out a few things regarding this. 

In the middle the cycleway crosses over a footway leading to Olive Road, the two ways should be joined here with a node.

If this is a formal signed shared use (foot and cycle), cycleway, then a better set of tags would be :- bicycle=designated
foot=designated
highway=path
segregated=no
and because the highway=path then there's no need for the tag access=no.
I doubt if the cycleway is formally named Princes Road.

At the west end approaching Heath Lane surely the cyclyway does not end, I would have thought it carrys on over Heath Road. Thus the existing footway ought be made a cycleway. Perhaps even the crossing over Princes Road here should be a cycleway.

Regards Bernard.
DoDoMR (2019-02-05 18:13:21+00:00): Hallo,
ich habe Deinen Änderungssatz reverted, da Du - sicherlich unbewusst - durch Deine Änderung die Schnellstraße "Auf den Lahnbergen" zerstört hast.
Auch die Änderung der Fahrbahnoberfläche auf "gravel" dürfte m.E. nicht korrekt sein. Gem. Erläuterung im Wiki (https://wiki.openstreetmap.org/wiki/DE:Key:surface) ist gravel als "Loser Schotter: Scharfkantig gebrochener Naturstein." definiert. Korrekter dürfte m:E. entweder "compacted" oder "fine_gravel" sein. Ich werde mir den Weg in den nächsten Tagen mal persönlich anschauen und dann die erforderlichen Korrekturen vornehmen.

Wenn Du Fragen hast - einfach kontaktieren.

Viele Grüße,
Thorsten
Andrea Musuruane (2019-02-04 14:37:37+00:00): Ciao, addr:street un un nodo che non sia un numero civico non ha senso. Inoltre, fuel:metano=yes non è corretto. Il tag corretto è fuel:cng=yes Vedi: https://wiki.openstreetmap.org/wiki/Key:fuel Ciao, Andrea
Bytemark (2019-02-04 00:16:28+00:00): Hi Kremator,

it's not OK just to fill in "…" to please iD.

https://wiki.openstreetmap.org/wiki/Good_changeset_comments are not a shame!
🇨🇿 Roman Horník (2019-02-04 09:42:19+00:00): Hi Bytemark,
if you create tens of diametrally different edits within one changeset, it's hard to compose accurate comment for all of these modifications. I'm NOT a writer!
Sure, I can write "Just a few edits", but it will be the same like "…".
OSM doesn't live by comments, OSM lives by editting.
Bytemark (2019-02-09 21:26:39+00:00): Hi Kremator,

surly there are many bad editing behaviours by me, but I've just asked you to improve a certain behaviour.

"OSM doesn't live by comments, OSM lives by editting" is somehow nonsense. Changeset comments don't improve the map, but the are crucial for traceability.

Good luck!
nevw (2019-02-04 09:29:27+00:00): Hi Luen
I noticed the change of name for the southern section of Clemant State Forest to Mount Cataract State Forest.
If you search for Clemant State Forest on the Qld Globe it seems it is still called Clemant State Forest 
http://qtopo.dnrm.qld.gov.au/mobile/
We don't have permission to use the Qld Topo on the OSM but the Department of Environment and Science Protected Areas of Queensland are fine to use
http://qldspatial.information.qld.gov.au/catalogue/custom/detail.page?fid={6C180042-2B50-4018-8B29-E245818B1B8A}
and is still Mount Clemant on that database too.
Maybe you could use Mount Cataract State Forest as an alt_name or local_name   
https://wiki.openstreetmap.org/wiki/Key:name
unless you have more up to date info than I have suggested that this section has indeed changed to Mount Cataract State Forest.
Luen Warneke (2019-02-04 23:39:10+00:00): Hi nevw, 

You know best when it comes to mapping so I have changed the name back to "Clemant State Forest" and added in the alt_name "Mount Cataract State Forest"  - see changeset 66917820 / 66917847. 
There are references to this area being called "Mount Cataract State Forest" & "Mount Cataract Forest Reserve" online, including my website (https://wanderstories.space/mt-cataract/) and Google (https://goo.gl/maps/tzpA6Js4VeA2). 
However, I would think that QSpatial (QTopo/Qld Globe) to be the most trusted. 

Thanks for your message and correction.
nevw (2019-02-05 07:48:19+00:00): Thanks Luen
I sent an email to the Qld Department of Environment and Science asking if both co-exist or some other situation.
Luen Warneke (2019-02-05 23:12:13+00:00): Thank you
nevw (2019-02-06 05:25:17+00:00): Hi Luen
I got a reply back already and they said...
Mount Cataract Forest Reserve was amalgamated into Clemant State Forest in 2014.
So tagging can stay as is I guess.
Luen Warneke (2019-02-06 05:42:02+00:00): Thanks for the update. Cheers
DoctorSpeck (2019-02-04 05:16:01+00:00): Hi, I noticed you edited the admin boundary for newport news/James City County, I'm curious as to what the problem was with the pulled node mentioned in  the changeset comment.
DoctorSpeck (2019-02-04 06:41:47+00:00): It looks like the node you referenced was https://www.openstreetmap.org/node/3667985601.

I've since fixed the boundary to where it was joined(my previous error).

Please review the changeset: https://www.openstreetmap.org/changeset/66894159 

or in OSMCha
https://osmcha.mapbox.com/changesets/66894159

to see if it addresses your concern. If this was in error please let me know and I'll work with you to make sure it's fixed.
freebeer (2019-02-04 10:56:23+00:00): hallo,
glad to see you noticed my changeset, and apologies i did not contact you a week ago when i analysed the OSM inspector area and decided a simple node revert with my tools to restore the dam and river boundaries, was not trivial.

the problem was that somehow, a node on the southeast side of the dam, joining the dam, river, and landuse got pulled out of position and joined/merged to your adjustments of the admin boundary, resulting in the original dam node being deleted/recycled and your admin boundary node serving two purposes.

the OSMI errors visualised by the rendering were that half the dam disappeared and the landuse did not render due to the overlapping ways, which drew my attention to this area.

viewing my own changesets in achavi, i can see the version revert did not work at all as intended in this changeset, when the intent was to restore your last boundary edit version, with the joined node replaced.

i have seen this too often when potlatch restores a pulled node to its correct position in the display, yet finds nothing to update and upload.

anyway, i believe my grave error was to save the boundary to a previous state before your corrections (in order to restore the pulled node back to the dam), and this changeset which attempted to undo that action, turned out to be a no-op.

i am satisfied with your changes, and my apologies for my focus on the pulled node while attempting to understand how best to remedy such changes with unintended errors, like across canada where the original mapper has disappeared.

in retrospect, i should have aborted the multiple changesets, as i abandoned my efforts a week earlier, rather than trying to slog along and achieve some sort of result, correct or not.  i lay the blame at michigan state university where i restored a mangled circular intersection to a reasonable state after multiple passes with different tools for each affected segment.

i hope you will forgive me for my blind, pig-headed blundering in this area in a futile attempt at learning, and again, apologies for the additional work it imposed on you.

cheers
DoctorSpeck (2019-02-06 10:33:12+00:00): lol, no worries, that's how we learn indeed. Early on in that string of reverts, I didn't know how to use the recursive features of overpass so I wasn't pulling the connected ways/nodes into JOSM when downloading the admin boundaries, hence how I messed up that edit. I learned like an engineer's son... mess with things until they break, then try to fix them. PS looked through your commit history, some truly great changeset comments rofl.
eggie (2019-02-04 08:30:55+00:00): Hi annarassa... Alle Gebäude sind importiert fom Holländische Kadaster und genau eingemessen.
Sie haben Gebäude gelöscht und ein neues konstruiert. 
daneben haben Sie nog Adresse kombiniert. weshalb?

... Und weiter bitte nicht schieben mit der karte im editmodus. 

Deine edits werden revetiert.

Grüss,
Eggie
 

http://overpass-api.de/achavi/?changeset=66890067
eggie (2019-02-04 08:37:19+00:00): Reverted by changeset #66896257
aaronsta (2019-02-04 16:11:37+00:00): Hi christopherlam,

This road is infact not yet open, and should have been split, also same comment as per previous changeset, please ensure you are familiar with OSM mapping practice.

Cheers,
aaronsta


Hi christopherlam,

Thanks for your edits :)

Please be more careful when making edits.
Regarding these roads they all had the following tags:

fixme=REMOVE REDUNDANT TAGS WHEN YOU EDIT THIS WAY
construction=motorway_link
highway=construction.

The correct procedure would have been to tag ALL the roads with their construction=* value which was motorway_link, then check over ALL the keys, and remove the redundant ones (i.e fixme=* and construction=* in this case) You removed some values, and not others and tagged the road incorrectly.

I suggest you review the wiki pages and guides for tagging, as the Perth mapping community is small and problem edits can take months if not years to be corrected.

Cheers,
aaronsta
andrewwiseman (2019-07-24 15:46:48+00:00): Hi, this road doesn't match imagery here, can you take a look? https://www.openstreetmap.org/way/372792034
farmal (2019-07-25 08:15:30+00:00): 
Hi Andrew, 
Thanks for flagging this. While I was reviewing the way in Feb, part of the way was covered with dense clouds and hence I could not completely align the stretch. Looks like Imagery is now updated, I made the alignment changes accordingly. 

Thanks,
farmal.
andrewwiseman (2019-07-25 13:46:40+00:00): Thank you!
aaronsta (2019-02-04 16:09:04+00:00): Hi  christopherlam,

Thanks for your edits :)

Please be more careful when making edits.
Regarding these roads they all had the following tags:

fixme=REMOVE REDUNDANT TAGS WHEN YOU EDIT THIS WAY
construction=motorway_link
highway=construction.

The correct procedure would have been to tag ALL the roads with their construction=* value which was motorway_link, then check over ALL the keys, and remove the redundant ones (i.e fixme=* and construction=* in this case) You removed some values, and not others and tagged the road incorrectly.

I suggest you review the wiki pages and guides for tagging, as the Perth mapping community is small and problem edits can take months if not years to be corrected.

Cheers,
aaronsta
seattlefyi (2019-02-04 07:32:58+00:00): Hi, and welcome to OSM! Thanks for updating the building. Do you happen to know the address of the new building you added? The building you removed had been tagged as 1220 East Spring, that address was also removed at the same time. Thanks again!
5m4u9 (2019-02-14 06:51:07+00:00): arreglé el area de la escuela que registraste
geoaria (2019-02-04 14:12:12+00:00): مسیر های داخلی ادرات و دانشگاه ها با تگ service مشخص می شوند
GOwin (2019-02-07 06:50:17+00:00): Kindly do not add `junction=yes` to all intersections. These are unnecessary, unless they are named junctions.
GOwin (2019-02-07 06:51:49+00:00): Kindly do not add `junction=yes` to all intersections. These are unnecessary, unless they are named, or has other properties.
deepthi1 (2019-02-08 07:42:48+00:00): Hi Gowin,

Thanks for the feedback.

Junction=yes tag is not given by me. Its was tagged by user: DearPaulPH. We didn't remove the tag as we were not sure if they were tagged basis local knowledge
Please refer to screenshot for more details
https://lh3.googleusercontent.com/-4jAsd_Cm8qc/XF0yJ8gIxSI/AAAAAAAACz8/N0jVtIVk7yEHvJR_hAP0bw8iboN5IaC4QCL0BGAYYCw/h932/2019-02-07.png

Thanks,
deepthi
GOwin (2019-02-08 07:47:10+00:00): Noted. Thanks.
Gazer75 (2019-03-01 18:15:43+00:00): Please do not change things without local knowledge, or contacting previous mapper. There is a new swimming hall built here now. I have reverted your edit already btw.
hannaklimovich (2019-03-02 05:23:43+00:00): Hey Gazer75 👋
In this case it looks like overlapping. It's possible to face outdated imagery from time to time. And if you have the opportunity to share a fresh aerial photo of this area then upload it to https://openaerialmap.org/
Thank you for fixing this issue.
Gazer75 (2019-03-02 12:40:49+00:00): Even so, there was a start date on the building that should be a clue. It was set as 2017. Also make sure you use Norwegian Orthophoto as background imagery in Norway. Unless the imagery_used value bugged the changeset is showing Bing.
hannaklimovich (2019-03-03 05:56:36+00:00): Ok thank you, I will pay attention on it
mavl (2019-02-28 17:16:24+00:00): This changeset was redacted.
mueschel (2019-02-04 12:18:05+00:00): Hi,
please don't add dozens of route_ref_43 tags. You can add all refs of routes that serve a given bus stop in a single tag, separated by ';':
route_ref=1;2;3;4

Cheers, Jan
Frans S (2019-02-25 19:00:04+00:00): Hi. Thanks for mapping here/
Just a small remark. When you map highways, try to connect them where logical and possible. f.i where several highways comes to a hemlet, connect them
Thanks
ftcat (2019-02-25 19:57:13+00:00): I was not the original mapper here just corrected where highway types were wrong as most are tracks or paths if I see that highways are not connected I connect them but otherwise just change the types. I find a lot of the remote mappers make many assumptions and errors as they have no idea as to what they are mapping. As this area has been my home for over 50 years I think I have a little knowledge.
ma-rt-in (2019-02-04 10:40:55+00:00): Hallo,
wozu der Namen?
Willkomm1 (2019-02-04 10:43:35+00:00): wollte Schornsteinfegerbetrieb markieren
ma-rt-in (2019-02-04 10:56:26+00:00): dann musst du aber auch ein entsprechendes Handwerker-Key setzten. Das wäre in dem Fall craft=chimney_sweeper
vg
Willkomm1 (2019-02-04 11:07:19+00:00): wo kann ich das Eintragen?
ma-rt-in (2019-02-04 11:09:20+00:00): DU hast 41 Bearbeitungen gemacht und weißt nich wie du das eintragen sollst? Bitte lies dir mal das hier durch: https://wiki.openstreetmap.org/wiki/Willkommen_bei_OpenStreetMap
Cascafico (2019-02-04 09:51:26+00:00): "Airport - Railway station" è il nome segnalato in loco?
Presumo highway=footway sia più adatto di path.
chnav (2019-02-04 14:16:54+00:00): Пожалуйста не меняйте тег на здании !!! Bing устарел в этом месте. Я уже исправляю за вами второй раз.

Please note the Bing imagery is outaged and is not correct in this place. This is second time you ignore fresh imagery.

Your changeset has been reverted.
hannaklimovich (2019-02-05 12:49:13+00:00): Hi thank you I'll pay attention
henke54 (2019-02-04 09:58:18+00:00): Mussenberg is just a HAG (Herbevestigde Agrarische Gebieden) and a 'relictzone' ->
http://onroerenderfgoed.github.io/la2001/relictzones/R20022.html

https://www.milieuinfo.be/dms/d/d/workspace/SpacesStore/57692f2e-c2fe-4e65-b87d-69bca10f43b8/Finaal%20MER-PR2194_MetBijlageFluxys.pdf

https://mer.lne.be/merdatabank/uploads/merntech4185.pdf

https://www.vlaamsbrabant.be/binaries/afbakening-halle-2016-prup-cluster-binnenstad-toelichtingsnota_tcm5-110961.pdf

so , ... simply said ; a agricultural area on a hill  ... or in Dutch ; een akkerzone op een heuvelplateau ... ;)
dieterdreist (2021-11-27 01:18:56+00:00): any reason why you did not consider these as work of public art? I believe the tags that have been removed were valid tags...
GBAB (2021-11-27 16:09:46+00:00): According to OSM wiki, the difference between a tourism=artwork and a historic=memorial + memorial statue is whether they represent a named figure or not.

For example if there is a statue of a bird or ship or even of an unnamed girl on a street, that is a tourism=artwork. If there is a statue of e.g. Giordano Bruno, then it is an historic=memorial.

Also according to OSM wiki, monuments are a very rare species: they should be very big ('monumental') and commemorate of a very big event. Even if something is mentioned as "monumento" in everyday language, it does not entail that it should be mapped as an historic=monument on OSM.
dieterdreist (2021-11-28 12:22:35+00:00): Hallo Gàbor,
ich antworte auch hier auf deutsch wie in unserer parallelen Diskussion zum Arco di Giano besprochen (zu historic=monument siehe dort, https://www.openstreetmap.org/changeset/75592071 )
Hinsichtlich tourism=artwork in Abgrenzung zu historic=memorial war mir nicht klar, dass es hierzu Festlegungen gibt, ich gehe bisher davon aus, dass ein Objekt durchaus beide tags tragen kann, sofern sie zutreffen (nicht jedes memorial ist ein Kunstwerk, manchmal ist es z.B. auch nur eine Hinweistafel, in anderen Fällen sind es (teilweise berühmte) Skulpturen).

Im Wiki zu artwork steht nichts von einer Abgrenzung:
https://wiki.openstreetmap.org/wiki/Tag:tourism%3Dartwork

Im Wiki zu historic=memorial steht auch nichts von einer Abgrenzung zu tourism=artwork:
https://wiki.openstreetmap.org/wiki/Tag:historic%3Dmemorial

Wo hast Du das gefunden? Evtl. muss man das Wiki dort ändern? 

Gruß,
Martin
GBAB (2021-11-30 10:34:56+00:00): Hallo Martin,

ich habe die Abgrenzung an den deutschen Wiki-Seiten gefunden:

https://wiki.openstreetmap.org/wiki/DE:Tag:artwork_type%3Dstatue
„Für eine Statue, die eine historische Person darstellt und gedenkt, benutze historic=memorial + memorial=statue.”

Und https://wiki.openstreetmap.org/wiki/DE:Tag:memorial%3Dstatue
„tourism=artwork + artwork_type=statue - Kunstwerk ohne Namensbezug”

Gruß,
Gábor
dieterdreist (2021-11-30 11:51:08+00:00): Danke für die Rückmeldung, habe jetzt gesehen dass es im englischen auch so steht (beides von Geozeisig in 2018 eingebracht). Ich habe dazu jetzt mal im deutschen Forum einen Thread aufgemacht: https://forum.openstreetmap.org/viewtopic.php?pid=848263
Gruß,
Martin
WoodWoseWulf (2019-02-04 11:02:06+00:00): A lake isn't a park, what are you trying to do here?
WoodWoseWulf (2019-02-04 11:01:31+00:00): Why have you mapped the entrance to the cemetery as a park? Is this an error?
Abyssminded (2019-02-04 13:20:34+00:00): yes.....the cemetry has a park inside,but now is closed for general public
WoodWoseWulf (2019-02-05 00:10:33+00:00): Hi, you may need to revise your tagging if that is the case. "Entrance to cemetery" is a descriptive name, something we try to avoid on osm: https://wiki.openstreetmap.org/wiki/Names

If there is a park in the Cemetery (are you sure it's not a garden?) then you should map that area specifically.

The tagging also doesn't match up which what you've called it, why is it called "Entrance to cemetery" if it's a park?
Warin61 (2019-02-11 07:21:23+00:00): Hi
Way 546709282 does not connect to way 546708622
biancah_telenav (2019-02-11 07:26:56+00:00): Thank you. I corrected it
Владимир К (2019-03-17 10:32:36+00:00): пожалуйста, используйте highway=living_street только для именованных улиц, отмечаенных знаком "Жилая зона"
eggie (2019-02-04 08:59:46+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
eggie (2019-02-04 09:03:19+00:00): 
Dag IAAY, Je hebt de functie en naam gewijzigd. Dat is oke. 
Normaliter taggen we bij op de bestaande BAG adresnode. Die ligt er net onder. Nu komt het adresnummer 2x voor. 
De info kan dus beter naar de adresnode.
MVG,
Eggie
SomeoneElse_Revert (2019-02-26 21:35:42+00:00): This changeset has been reverted fully or in part by changesets 67597451, 67594431 where the changeset comment is: Reverting some problem changes in Africa following complaint to DWG (a revert was thought to be the least-worst option).  See https://www.openstreetmap.org/user_blocks/2533 and http://resultmaps.neis-one.org/osm-discussion-comments?uid=2762871.