You tagged one of the sidings here with electrified=no and gauge=electrified
What did you mean by that?
I suspect it should be gauge=1435 ?

... Men NVDB er ikke helt konsistent ennå, så det kan hende at strekket fra Solbakk via Jørpeland til Oanes nå har blitt Fv523

Also proposed new road to ENGK airport. Should have been two changesets :/

Som nevnt; forberedelser.
Har ikke fått gjort meg ferdig her.
Bakgrunnen var å bli kvitt "hvite" linjer langs grensene. Det er også en mengde vann og våtområder som var kuttet direkte på grensen. Skoger slutter ikke på kommunegrenser... Skogsgrensene som fulgte kommunegrensene gjorde det også bare delvis.Dette changesettet var for å "løsrive" skogen fra grensen. Neste trinn er å forenkle skog-mp-en langs grensen og slå den sammen med nabo-skogen.

Ja, nå ser det mye bedre ut :)

Hei Kristoffer
Velkommen til OSM :)
Litt feedback til dette og liknende endringssett.
Det ser ut til at du har forvekslet "residential" og "driveway".
highway=residential brukes om det som vi på norsk gjerne kaller gater og veier (oftest kommunale).
Det som vi gjerne på norsk gjerne kaller for oppkjørsler (oftest private) blir helst tagget med highway=service service=driveway.
Hvis du ser i kartet nå, er oppkjørslene "dine" blitt fete og tydelige, mens en del av veiene er blitt tynne og pinglete :D
Selvsagt best om du ordner dette selv. men jeg kan godt hjelpe til hvis du vil.

You need to relax a bit.
Having some duplicates is not a big problem. A bigger problem is that you keep deleting true information. Last time you did this to one of my contributions, the multipolygon got deleted by someone else "because it was empty", making investigation even harder.
If you really want to avoid duplicates, don't jut delete the multipolygon. Rather add the aerodrome node to the multipolygon as the ARP.
Also, if you have concerns about how orher people map, write a changeset comment and don't just delete stuff. Otherwise we have no way, as a community, to improve.
As this is the second time you do this to data I have contributed, I am tempted to report you to the Data Working Group as I am sure you have done the same with multiple other aerodromes.

nikoo
How are you planning to revert? We are talking 11000 objects. I looked into using the reverter plugin, but that still left 8-900 objects with conflicts. The more manual work done to fix it, the harder it will get to do a full revert of the two changesets. So I strongly recommend we cooperate on this task.

(Also JOSM already, by default, warns about moving many objects. There should be no need for a plugin for this purpose)

And changeset/71615846 is probably the tail end of this changeset after it failed at 10000 objects.

Fixing misalignment, you say. Yet at least some nodes have moved about 10 m out of place in this changeset: One example: node/2411503427
There is an upper limit for the size of changesets. It's currently set to 10,000 objects per changeset. This changeset contains 10 thousand objects. I suspect you had many nodes selected and then you accidentally moved all of them at the same time.

I suggest we should revert this changeset.

It was _not_ an old scool multipolygon...

Then why didn't you do as you suggested yourself? Now there is no rendering of the outer perimeter of the aerodrome...

Sensible? I disagree.

There were two aerodrome objects:
* A multipolygon with several correct tags and outline of the aerodrome.
* A node with fewer tags than the MP.

They both represent the same object but are not exact duplicates. The MP had significantly more information in it.
Then someone delete _all_ of the tags on the multipolygon? I don't call that sensible.

With that edit, the rendering of the aerodrome outline disappeared, f.ex.

Also: The edit you refer to was done by a editor with only a handful of edits at the time.

Also: Your changeset comment is misleading. Deleting an untagged MP is not the same as "fixing old-style multipolygons"

I see. It was that edit was in the wrong. Don't know if you looked into this before you deleted the relation? Reverted.

reverted

The nightmare is certainly you deleting information from the more complete relation. If only you had copied the tags from the aerodrome node...
Sometimes duplicate information is accepted. The world is not black and white. :/

What was wrong this multipolygon? Did it warrant outright deleting it?

Hei. Ser at en rundkjøring (way/645963847/history) ble tagget som oneway=yes i heller enn junction=roundabout. Kanskje dette var noe som kom fra nvdb via et script el.l?

Also added some flares to roundabouts.

ADDRESS var brukt 88 ganger før dette og 125 ganger i dette changesettet.