Hi NKA. Could you please break edits like this up in smaller cs?

I think this should be reverted. Duplicate nodes are best judged individually when JOSM warns about them IMO and not through a mechanical edit.

Hej! Välkommen. Tusen tack för dina bidrag. Gerestabäckens way som du namngav har redan namn via relationen den ingår i.
Läs gärna osm.wiki/Good_practice om du inte redan gjord det.

Tack för detta! Välkommen till OSM. Vad är källan till vindskyddet här?
Om du bor i närheten får du väldigt gärna ta en bild av det med Mapillary

Hej archie. Jag undrar precis som Anders varför du raderad dessa? Jag skulle föreslå att du återställer och i stället gör en relation med labelnod med place=village och namn samt yttersträcka som outer. WDYT?

Hi, this is obviously not correct, I see you already fixed it. Thanks!

Et alternativ er at slette omkredsen og keep it simple med en node. Dette ødelægge dog fx for myosmmatic at lave fine bykort hvor området i byen ligger til grund eftersom at bygrænsen er behøvet for at vide hvilke veje som skal med i index.

Jeg forslår at vi løfter diskussionen på tagging sådan at vi kan få ryddet op i alle ca. 1 mio landområder med navn. Mit forslag er at konvertere dem til en relation med en node med rollen label og place=* og navn i tillæg til omkredsen som outer.
Dog har vi besvær med verificerbarhed når det gælder omkredsen.

Fik netop følgende svar fra thunderforest:
Thanks for getting in touch! We actually rendered place area labels for
a number of years, but stopped doing so in early 2018.

Unfortunately, the area place labels were often garbage. The main
problem is duplication, since almost every place are has a place point
too. Surprisingly often these have slightly different names, and we
ended up with a bunch of duplicate labels. The tagging between the
duplicates is often different, particularly in the US where many "city"
tags have been downgraded to e.g. "town" or "village" on points, but
linger as cities on the ways and multipolygons. And then there's a wide
variety of ideas as to what the extent of the polygons should be, and
plenty of places (especially in the US) where the place polygons follow
administrative boundaries, leading to village centroids to be many
kilometers outside the urban area. Finally, lots of non-contiguous place
multipolygons, leading to complex problems around duplicate tags.

I hoped that we could drive OSM towards supporting place areas better,
being a pioneer and showing the community what a mess it currently is
(and providing a good reason to fix the worst things, like mistagging
cities), but after a few years I had to give up. There's no real way to
handle this until after it's handled in openstreetmap-carto, since any
other renderer is going to suffer from the bad data until the mappers
notice the problems on the main layer. I just got a lot of comments
saying that the place labels were broken on my maps but fine on osm.org.
Not much I can do then!

Anyway, I hope this helps explain the situation. As for how to tag
things, or what openstreetmap-carto should do, that's something I don't
have recommendations for, beyond reminding everyone to make life easy
for mappers, not for rendering software, and so avoid relations,
multipolygons etc whenever possible.

Hej. Slangerup savner label node. Kan du fixe det?

Lynge savner label node. Dette gør at den ikke synes på vektorkort som fx https://www.thunderforest.com/maps/outdoors/

Var kommer dessa gränser ifrån?

Tack vara dessa kan vi lätt göra tex en cykelkarta över detta område, se tex https://maposmatic.osm-baustelle.de/results//101498_2020-02-02_16-59_alidhem.pdf

Hej :)
Vet du var vi har stadsdelspolygonerna ifrån?

Om du orkar framöver får du väldigt gärna ta bilder med Mapillary - det är väldigt smidigt att spela in både manuellt och automatiskt.

ingen fara. Välkommen till OSM! :)

If you have photos lying around WM Commons might be easier to upload to.

After downloading the app - press capture - change to manual - press the red record button for every image/angle you want. Upload. Done. :)

The validator is very useful but not always right/relevant. It's so good now that I very rarely ignore anything it points out (1/100 cs maybe).

Hi, sorry I did not mean to accuse you of anything really, I honestly did not look very closely on your changes. I mainly reacted to the changeset comment. My last message was meant as a tip and I regret not stating that more clearly.
Have a nice day and happy mapping.