piebro/osm-data huggingface dataset:
puchaczowsky (2019-05-19 09:37:56+00:00): 1) Skoro Google Maps nie jest w stanie poprawnie przekopiować czegoś co w mapach Waze jest naniesione poprawnie (a przecież Waze należy do Google), to wtedy trzeba się wspomóc OSM (ale czasami nawet i to nie pomaga). A co zniechęcenia to jakoś nie chcę się przenosić na OsmAnd itd.

2) Rondo wraz z ulicami było zbyt kanciaste (czyt. korekty geometrii), dodałem też dwa brakujące elementy. Jak już jesteśmy przy opisywaniu to wiele osób również używa stwierdzenia "poprawki/drobne poprawki" więc nie wiem w czym problem.
maraf24 (2019-05-19 22:58:32+00:00): >wiele osób również używa stwierdzenia "poprawki/drobne poprawki" więc nie wiem w czym problem."

I one również nie zamieszczają prawidłowych komentarzy.
kreuzschnabel (2020-03-24 07:59:25+00:00): Info: Ich habe https://www.openstreetmap.org/relation/9583149/history gelöscht. Damit verbietest du nämlich das Linksabbiegen von Horperath nach Berenbach :/ Bitte äußerste Sorgfalt beim Setzen von TRs, mit so was zwingst du viele Nutzer zu sinnlosen Umwegen.
viloan (2019-05-12 18:36:28+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!
Frans S (2019-07-21 09:37:16+00:00): Hello Kkatarina. Thanks for mapping here.
a request. Please square the rectangular buildings with the Q key. You overlooked quite a lot of them
Please map a building as a round building as the shadow has also a round for,
Best regards and keep mapping
DemoLogin (2019-05-12 19:03:43+00:00): source: survey
bbmiller (2022-01-03 20:07:47+00:00): Should "Le Ferre Lake" really be named "LeFevre Lake"? That's the name on the USGS topo layer, and the Internet doesn't seem to know anything about a "Le Ferre" Lake in Kalamazoo County.
wolfgang8741 (2022-01-04 02:43:21+00:00): Its quite possible that "Le Ferre Lake" "Le Fevre Lake" are name variants or misreading of the lake name.  USGS GNIS states the spelling as "Le Ferre", and I was using GNIS as a second pass while linking to Wikidata. USGS national map layer shows the "Le Ferre" spelling captured in GNIS as of April 13, 1980 (though I've found errors in GNIS's import from maps and written records at times and reported for verification and correction.) No name variant is currently shown, but I'm not sure if the name variants are in the national map entry. I would guess LeFevre Lake, Le Ferre Lake, and Le Fevre are name variants from different times or maps. See current entry for the national map with "Le Ferre Lake": https://edits.nationalmap.gov/apps/gaz-domestic/public/summary/630236 and Michigan DNR uses the "Le Fevre Lake" spelling - https://www.michigan.gov/dnr/0,4570,7-350-79119_79146_81198_85509_105929-67578--,00.html
I do confirm that the USGS Topo Layer displays "LeFevre Lake". Not sure what on the ground signs say at this time. The on the ground sign would be the best source, but these others are not without merit.

As for other "Le Ferre Lake" in Kalamazoo County references online, I found many, but I suspect they are derived from the GNIS entry for 630236 and are not reliable sources for a check as I've seen propagation of GNIS fixes sometimes appear in similar contexts.(https://usa.fishermap.org/depth-map/le-ferre-lake-mi/ - http://www.michiganlakes.com/counties/michigan-lakes-by-county/kalamazoo/le-fevre-lake.html - https://lakeplace.com/lakefinder/mi/kalamazoo/le-ferre/39-232)
wolfgang8741 (2022-01-04 02:45:54+00:00): In summary - It probably should updated to "Le Fevre Lake" to be more consistent with Michigan DNR and closer to USGS topo.
bbmiller (2022-01-04 13:52:55+00:00): Just to muddy the waters, Climax Township has a map calling it "LaFevers Lake." https://399da70a-bd9d-4c4a-8bc4-efff71abaeb7.filesusr.com/ugd/c714ae_53df38dc6e704b179f16d8a2943bd510.pdf?index=true

There doesn't seem to be a good, authoritative source for this. I'll add an alt_name, but now I'm hesitant to change the name without a better source.
PT-53 (2019-05-13 09:01:00+00:00): Hallo geo-ranger,
Du hast diese Hofzufahrt https://www.openstreetmap.org/way/689517748#map=18/47.95390/9.21534 als Feldweg eingezeichnet.
Die Zufahrt  zu einem Aussiedlerhof - auf öffentlichen Wegen  ab der Kreisstraße - sollte als service klassifiziert werden. Die Hofzufahrt auf dem Aussiedlerhof selbst mit service + service=driveway.
Schau Dir dazu mal das Wiki zu service an:
https://wiki.openstreetmap.org/wiki/DE:Tag:highway%3Dservice
Grüße
Leo Slager (2019-05-12 23:27:09+00:00): Hi ursus kirk,
Please do not add adresses that are already on the map to the buildings.
PT-53 (2019-06-07 04:59:00+00:00): Hallo Matthias,
Du hast an dieser Haltestelle https://www.openstreetmap.org/node/4586787602/history wohl versehentlich shelter=no in h=no abgeändert.
Schaust Du Dir das nochmal an?

Fragende Grüße
Matthias Frank (2019-06-08 22:07:49+00:00): Hallo Peter, ich habe das jetzt wieder korrigiert. Bitte um Entschuldigung für die erneute Schlamperei. Danke Dir für den Hinweis. Grüße von Matthias
abakus_uploader (2019-05-12 22:30:24+00:00): (Wiadomość automatyczna)
Cześć!
Otrzymujesz ten komentarz, ponieważ dodałeś lub zmodyfikowałeś adres, który jest niepełny lub błędny.
Adres powinien zawierać minimum trzy znaczniki: addr:city=[nazwa_miejscowosci] + addr:street=[nazwa_ulicy] + addr:housenumber=[numer_porządkowy].
Wyjątkiem są miejscowości bez nazwanych ulic - wtedy stosujemy znaczniki: addr:place=[nazwa_miejscowosci] + addr:housenumber=[numer_porządkowy].
Bez poprawnego oznaczenia adresów, nie będą one brane pod uwagę przez wyszukiwarki, dlatego warto je dostosować do ww. schematu (w zależności od sytuacji).
Więcej informacji na forum: https://forum.openstreetmap.org/viewtopic.php?id=5632 - a pytania najlepiej zadawać tu: https://forum.openstreetmap.org/viewtopic.php?pid=681873
Pozdrawiamy!
SomeoneElse_Revert (2019-05-12 20:59:54+00:00): This changeset has been reverted fully or in part by changeset 70171026 where the changeset comment is: Reverting a persistent sockpuppet in Rochester.  See block 2548 et al
pio2_122 (2019-06-06 21:44:23+00:00): Idiotyczne zmiany...
1) Już pisałem, że nazwy rozwijamy, a ty je usilnie skracasz...
2) Dublujesz adresy w POI, które są już na budynkach...
Leo Slager (2019-05-12 23:05:26+00:00): This is not a park according to the definition in the wiki.
I suggest you change it in landuse=grass.
Leo Slager (2019-05-12 23:23:37+00:00): Hi ursus kirk,
The restaurant was already on the map.
The tags should be on the adress-node and not on the building.
I moved the tahs to the adress-node
Carto'Cité (2019-05-16 17:45:13+00:00): Bonjour.
J'ai restauré les traversées piétonnes que tu as supprimées (par exemple https://www.osm.org/way/690529984), en améliorant les tags conformément au Wiki https://wiki.osm.org/wiki/FR:Tag:footway%3Dcrossing.
Il est important de conserver ces jonctions entre les pistes cyclables et les chaussées afin de permettre aux calculateurs d'itinéraires de passer de l'un à l'autre.
Cordialement,
Antoine de Carto’Cité, projet #CartoVeloIDF
dunnno (2019-05-16 20:31:35+00:00): Bonsoir, au temps pour moi, je pensais que c'était des erreurs ;)
goedegazelle (2019-05-12 22:24:11+00:00): De beek loopt hier door een verhoogde goot en zou daarom niet onder de paden door kunnen stromen. Ik ga binnenkort even kijken en dan teken ik de trappen naar de bruggen erbij.
WoodWoseWulf (2019-05-12 23:54:41+00:00): Hi yellowboi and welcome to OSM :)

Are you able to clarify what Blandin is? Looking at the available satellite imagery, I'm not sure if it would be a park by OSM definitions:
https://wiki.openstreetmap.org/wiki/Tag:leisure%3Dpark
Leo Slager (2019-05-12 23:16:41+00:00): name and adress were already on the map.
Buildings are an import from the Netherland Government's Kadaster-
With the building comes an adresnode.
So in the Netherlands there are no adresses on the buildings.
Leo Slager (2019-05-12 23:32:02+00:00): This is not the correct way to do this.
Look in the wiki for opening_hours=*
and access:conditional=*
PT-53 (2019-05-13 08:20:22+00:00): Hallo  Jo89195,
Du hast in diesem Änderungssatz u.a.an diesem Straßenstück https://www.openstreetmap.org/way/599957533/history#map=16/48.2079/9.6608&layers=N maxspeed=50 ergänzt.
Bist Du Dir sicher, daß 50 kmh auf dem ganzen Straßenstück gilt? Wo steht denn das Ortsschild?
Fragende Grüße
PT-53 (2019-05-19 06:13:45+00:00): Hallo Jo89195, 
es wäre schön, wenn Du noch antworten würdest.
Grüße
Jo89195 (2019-05-19 19:43:21+00:00): Ich weiß nicht wo das Ortschild steht, bzw. ab wo 50 beginnt.
PT-53 (2019-05-20 05:58:30+00:00): Hallo Jo89195, 
dann wäre es besser, den maxspeed-Eintrag an dieser Straße wieder zu löschen. So ist das ja auf jeden Fall falsch.
Machst Du das oder soll ich das machen?
Fragende Grüße
PT-53 (2019-05-26 05:53:13+00:00): Hallo Jo89195, 
es wäre schön, wenn Du antworten würdest-
Grüße
Jo89195 (2019-05-26 20:25:00+00:00): Habe es rückgängig gemacht
EinKonstanzer (2021-09-06 18:36:39+00:00): Es gibt Zweifel ob es den Namen "Jägerhofallee" wirklich gibt. Bist du dir da sicher?
f0x86 (2021-09-06 19:13:46+00:00): Man findet jedenfalls Quellen, die das bestätigen. Ich meine auch auf dem Parkplan vor Ort ist sie so benannt.
https://www.lokalbuero.com/wp-content/uploads/2020/03/Krankmeldung.jpg
f0x86 (2021-09-06 19:14:12+00:00): Wo kommen die Zweifel her? Gibt es da auch eine Quelle?
f0x86 (2021-09-06 19:15:39+00:00): https://www.express.de/nrw/duesseldorf/lichtbaenke-kehren-zurueck-duesseldorfer-hofgarten-geht-ein-licht-auf-71564
f0x86 (2021-09-06 21:34:45+00:00): Hier ein Bild vom Plan an den Schaukästen vor Ort:
https://commons.m.wikimedia.org/wiki/File:Düsseldorf_-_Hofgarten_01_ies_(cropped).jpg
EinKonstanzer (2021-09-06 21:50:43+00:00): Danke für deine prompte Reaktion. Zum Hintergrund: Im Kataster ist der Name nicht zu finden und es wurde der tag "de:strassenschluessel_exists=no" gesetzt, der gesetzt wird wenn der Name dem Amt nicht bekannt ist. Die offizielle Karte der Stadt Düsseldorf benutzt Straßen und Wege aus OSM.

Inzwischen bedienen sich viel der Daten von OSM. Vielleicht auch der "Express". Die Presse ist da nicht zwingend eine gute Quelle.

Die beste Quelle ist immer noch ein Straßenschild Vorort!
mgpx (2019-05-15 20:40:28+00:00): Ez így többszörösen hibás jelölés.
Egyrészt, azonos településrészt csak egyetlen suburb elementtel jelölünk.

Másrészt, az OSM-en megelégszünk a valóság feltérképezésével. fikciókat nem jelölünk, 

Kérlek töröld.
Frans S (2019-08-15 14:35:35+00:00): Hello. Thank you for mapping. A request.
Try to map individual buildings as 1 building .You tend to map clusters of buildings including ground level as 1 building.
This need special attention and correcting work.
Best regards and keep mapping
eggie (2021-02-15 16:08:22+00:00): deleted nonsense
user_5359 (2019-10-18 16:43:05+00:00): Hallo! Kannst Du bitte die vier Häuser mit Hausnummer 6 nochmal prüfen, ob die Hausnummer wirklich bei alle korrekt ist?
papamat15 (2019-10-20 20:49:18+00:00): Es handelt sich hier um Ferienhäuser ohne Hausnummern am Gebäude.
Siehe: https://odis.homeaway.com/odis/listing/b88b36b0-e849-4976-a450-d7800f39e7c9.f10.jpg
Die Nummer wurde uns für die Anreise zu den Häuser vom Vermieter so angegeben.
PT-53 (2019-12-31 10:52:11+00:00): Hallo Marius,
Du hast in diesem Änderungssatz Straßen und Wege eingezeichnet und diese mit den Merkmalen (z.B.)
highway=residential + construction=yes
versehen. Im OSM-Inspector werden dort nun Hinweise "nonop_confusion_on_ways" angezeigt:
http://tools.geofabrik.de/osmi/?view=tagging&lon=11.30747&lat=48.10038&zoom=18&opacity=0.34&overlays=nonop_confusion_on_nodes,nonop_confusion_on_ways

Straßen und Wege im Bau sollten gem. Wiki mit den Merkmalen
highway=construction + construction= z.B residential
markiert werden.
Wiki:
https://wiki.openstreetmap.org/wiki/DE:Lifecycle_prefix
https://wiki.openstreetmap.org/wiki/DE:Key:construction

Schaust Du Dir das nochmal an?
Grüße und einen guten Rutsch ins neue Jahr
PT-53 (2020-01-13 11:32:15+00:00): Hallo Marius,
Schaust Du Dir das nochmal an? 
Fragende Grüße
PT-53 (2020-01-26 08:28:38+00:00): Hallo Marius,
Schaust Du Dir das nochmal an?
Fragende Grüße
PT-53 (2020-02-16 12:41:31+00:00): Siehe
https://www.openstreetmap.org/changeset/80816715
abakus_uploader (2019-05-12 22:30:25+00:00): (Wiadomość automatyczna)
Cześć!
Otrzymujesz ten komentarz, ponieważ dodałeś lub zmodyfikowałeś adres, który jest niepełny lub błędny.
Adres powinien zawierać minimum trzy znaczniki: addr:city=[nazwa_miejscowosci] + addr:street=[nazwa_ulicy] + addr:housenumber=[numer_porządkowy].
Wyjątkiem są miejscowości bez nazwanych ulic - wtedy stosujemy znaczniki: addr:place=[nazwa_miejscowosci] + addr:housenumber=[numer_porządkowy].
Bez poprawnego oznaczenia adresów, nie będą one brane pod uwagę przez wyszukiwarki, dlatego warto je dostosować do ww. schematu (w zależności od sytuacji).
Więcej informacji na forum: https://forum.openstreetmap.org/viewtopic.php?id=5632 - a pytania najlepiej zadawać tu: https://forum.openstreetmap.org/viewtopic.php?pid=681873
Pozdrawiamy!
stevea (2019-05-12 21:43:09+00:00): NeverFollow:  Welcome to OSM and your first edit!

Rather than mapping the entire landuse=commercial polygon (the shopping center area) as both the name of the shopping center (that's not correct) and the name of a yet-to-exist Tesla Supercharger station, I have some suggestions.  You were helpful with your description=* text, so thanks for that.

First, take the "Tesla Supercharger" name tag off the shopping center polygon.  I've been to this place many times (Target, Del Taco...) but I don't know if the shopping center has a name (the entrance sign simply lists the names of the stores).  It might, but if we don't know the name of something in OSM, we simply omit the name=* tag.  That's OK.

Second, use a node (sometimes called a "point") to map the charging station, rather than the whole polygon of the shopping center.  For the node's location, the rather precise lat-long coordinates you gave seem to indicate it will be in the far eastern lobe of parking, in the area just to the south of the building south of Del Taco.  What to put on its tags?  I suggest:

amenity=charging_station
name=Tesla Supercharger
state=proposed
start_date=2019
capacity=14
charging_station:output=72 kW

That's a good start.  I also recommend reading our wiki at https://wiki.osm.org/wiki/Tag:amenity%3Dcharging_station to see if there are other subtags there that might be applicable.

Map well, have fun in OSM!

Steve in Santa Cruz
NeverFollow (2019-05-13 03:19:31+00:00): Thank you for your comments, but I believe that I selected a "Point" with coordinates 36°54'56.2"N 121°46'24.1"W which is at the center of the 14 new stalls. The area is just at the north east corner of the main building.
Note: I wonder if it would be possible to show a status for a supercharger, like Permit Found, Construction Started, Available, Temporary Closed, Permanently Removed.
stevea (2019-05-13 18:18:27+00:00): Ah, yes, thank you for pointing out that you DID enter a node where you say.  (It is node 6468638563, which you can use a browser to see with http://www.osm.org/node/6468638563).

OK, so you're almost done.  1)  Please remove the name=Tesla Supercharger tag from the "surrounding polygon" (the one tagged landuse=commercial), as that isn't correct, it isn't the name of the whole shopping center.  (Again, I don't know if it has one, but it's OK omit a name=* tag from OSM if we don't know the name of something).

2)  The node you entered isn't really correct (yet), even though it has decent address tags (and a start_date).  But in order for OSM to really "know" this node as a charging_station, you'll need to add those tags I suggested above to the node.  The amenity=charging_station is the most critical one to add, the others are more minor "window dressing."

As I read our charging_station wiki (and you would benefit by doing so, too, especially as you might add more of these charging stations), I don't see any subtags that logically apply to the other "status" things you want to enter, like Permit Found.  However, the "state=proposed" tag does a good job of describing that it is "on the way soon."  Also, I suggest you look up "construction" at wiki.osm.org to see how we show that things are under construction, should that be the case.  (It really is important to NOT use construction tags unless construction REALLY has begun).  For things like "permits, etc." those aren't really relevant to OSM, but if you like (as you discovered before, and it was helpful to me), you can use either a note=* tag or a description=* tag to tag things like that.

Good luck, have fun!

Steve
NeverFollow (2019-05-13 19:22:21+00:00): Thank you for your help. Let me review your suggestions and I will try fixing the issues. The Watsonville is completed, so it seems to be now the issue to get the inspection permit and the green light from PG&E. I wonder if it possible to include some pictures showing the site, which could help user in the future. For some location, the charger are inside an underground parking, so some pictures could be helpful. There is in fact a project of Supercharger in Big Sur, but I don't have yet too much detail. This Watsonville update is certainly a good experience for  contributing to the OpenStreetMap project.
stevea (2019-05-13 19:43:00+00:00): You are quite welcome, it is my pleasure to help new users.

If you are interested in "pictures," I encourage you to learn about Mapillary and OpenStreetCam.  (You probably already know that using Google Maps and its "street cam" images are not to be used in OSM, as that would violate OSM's ODbL / open database license).

I'm glad you are adding local (to me, anyway) charging_stations to OSM, especially as 1) electric cars are the FUTURE! and 2) these are in my area, and I have an electric bicycle (I charge it with solar) and one of my cars is part-electric.  (Another car of mine got 53 MPG when I bought it new in 1988!)  Plus, Big Sur is an smart and awesome place to put a charging station:  it's quite rural, gas is expensive (at Gorda, further south, gas is often over $7 a gallon) and it's a great place to have a burger, stock up on supplies, shop the nice gift shops or take a nice hike while you wait for your batteries to charge.

If you need any help "fixing the issues," simply ask and I'll be glad to offer help.

Enjoy your future mapping!

Steve
NeverFollow (2019-05-14 15:23:07+00:00):  Hi Steve, thank you so much for your help. You really nail it at providing me all the information about Superchargers. I would apology for the little mess that I might created, so I let you check if there is a need to do some more clean up: The Watsonville Tesla Supercharger should be under the Node 6468638563. However the Nodes  70170520 and 6468638563 could be removed, or at least not show up by just clicking on the map? Please tell me what you think. - Regarding the future Tesla Superchargers, there is a plan for Santa Cruz, Cambria, and I imagine also the Hearst Castle parking in San Simeon area.  You can also review the SuperCharger map using https://www.tesla.com/findus  - About EV in general, there is a Web tool called  ABRP (A Better Route Planner)  https://abetterrouteplanner.com/ based on OSM. But I imagine that they use their own Superchargers database, since I only noticed few SuperChargers on OSM. The ABRP is quite powerful, as it used results from reported real consumption from other drivers to determine the Superchargers required stops. It support various EV vehicles based on battery, driving speed, elevation, and so on. - Tahnk you again for your help. -- Paul
stevea (2019-05-14 16:09:55+00:00): Hi Paul:  Node 70170520 is in Georgia, so I don't know about that.  And 6468638563 is indeed the Tesla Supercharger and it looks like you tagged it properly (as I suggested, but I'm not the ultimate authority on tagging, usually our wiki is).

Somehow it looks like you deleted the shopping center polygon (landuse=commercial) but that's OK, I added it back in.

So, it all looks OK now, thanks for your addition to the map!

Steve
stevea (2019-05-14 17:50:17+00:00): Continuing a trend around here, I've changed the shopping center's landuse tag from commercial to retail, as that is a more precise tag.  (Commercial might be "office parks" or similar, but shopping centers like this one fit exactly the definition of "retail" in our wiki).

"Done for now" around here!
dgitto (2019-05-13 07:27:59+00:00): hello. there is a typo in the key "abandonned"
SomeoneElse_Revert (2019-05-12 20:59:54+00:00): This changeset reverts some or all edits made in changeset 70169238.
Leo Slager (2019-05-12 22:37:12+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
Na 8 jaar weer een wijziging aangebracht dus vandaar alsnog het welkomst bericht.
Leo Slager (2019-05-12 22:40:19+00:00): review:
De editor iD is helaas niet geschikt om routerelaties te bewerken.
iD zet alles wat je toevoegt achter aan de relatie, waardoor de volgorde van de elementen dus niet meer correct is.
ik kijk even of ik wat kan herstellen.
Viajero Perdido (2019-07-04 02:37:55+00:00): Hi badenk.

Somehow we have a residential road crossing mountains and glaciers.  Could you check? Thanks.
badenk (2019-07-04 03:47:11+00:00): Hola Sr. VP:

Yes, I had temporarily changed the park boundary to a road to enable it to be visible on other maps, specifically OpenTopoMap and Sentinel2.

I will need to review the boundary section that I re-drew to correlate deviations with the other maps.

Thanks for reminding me,
Baden
Viajero Perdido (2019-07-13 04:16:49+00:00): Yoho Park doesn't render, possibly because the polygon isn't closed at the northern end; there are two instances of Mt. Rhondda very close to each other with no boundary connection there.
badenk (2019-07-14 04:03:45+00:00): Thanks for the tip.

There are two issues here:

1) The legal (watershed) boundary for Yoho Park is incorrectly described in the Parks Act to terminate on the Alberta-B.C border at Mount Rhondda.  However, the actual watershed joins the continental divide north of Mount Rhondda.  I moved the Yoho border north to be hydrologically more accurate, and removed the redundant north Mount Rhondda.

2) I am not sure why "Yoho Park doesn't render".  If you view "https://www.openstreetmap.org/relation/9368703", the entire Yoho Park boundary is depicted.  The parameters are the same as adjacent parks.  If I zoom in (14), the boundary is visible.

ciao,
Baden
Viajero Perdido (2019-07-14 15:22:47+00:00): Thanks for fixing this.  Un-twinning Mt. Rhondda and closing the gap has indeed made it render as a park again.

Happy mapping,
VP
patrick noll (2019-05-12 23:22:23+00:00): will be reverted, nodes should not have height tag
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/70171201
patrick noll (2019-05-12 23:22:11+00:00): will be reverted, nodes should not have height tag
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/70171309