way/427392272 Did you walk this? Was there a path? I haven't been there, but I can't see anything on orthophoto, and then there is note/2105019

Hei Kol Jørn :)
Ser du har tegnet inn masse båtruter...
Men litt usikker på hensikten med noen av dem. F.eks way/778781089 og de tre andre ved siden av. De er tagget helt likt og går samme plass. Er det noe tanke med det? Eller bare kopiert fra noen plass?

Ja, var nok annet holde styr på...
Har f.eks ikke funnet nye vegnummer på "Motorveien" mellom Madlaveien og Ullandhaugveien.
Du er selvfølgelig velkommen til å fikse :)

Did you have a particular way or relation in mind?
Perhaps you are talking about relation/7503548 ?
I (and many others) find it interesting to have data about old and removed train and tramlines in OSM.
I did not know about this particular line when I traveled through the area, but I saw many hints of it; old station buildings, embankments, alignments etc. But no tracks. Very visible to me, perhaps not so visible for you :)
It gave me great pleasure to research and discover the whole alignment and have to have all the little hints explained.
Also, many Wikipedia articles use this data to display the historic line in a map.

So I think this data is very suitable for OSM :)

All the best

Hei peet192
Ser du har slettet det midlertidige bybane-depotet. Men kan det hende at deler av gamle vossebanen også forsvant i dragsuget? Er skinnene fjernet fullstendig? De er mange som ville foretrukket å beholde litt jernbanehistorie og dermed heller byttet tagging til railway=disused/abandoned/razed.
Artiklene om nedlagte jernbaner i wikipedia bruker f.eks disse dataene.

Fixed, thanks.

You might very well be right. You are of course free to edit as you see fit.

Her har det sneket seg inn en duplikat på fergestrekningen Halhjem-Sandvikvåg.... way/625520455

way/20039839/
Somehow a name ended up in the highway tag. Perhaps you know witch name is correct?

Hi! On node/3584842493/ what does gauge=① mean? The gauge tag is usually only used for the railways themselves. Perhaps you are thinking of platform number?

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.