This is incorrect fix, please revert. There's only one swing with opposing seats (which both have _at least_ the capacity you've set there).

Kannattaisikohan noi vanhat osoitteet kuitenkin säilyttää nodeissa tuolla talopolyjen sisällä ja laittaa notet niille vaan että ovat vanhoja osoitteita? IMHO, osoitteiden deprekointi ei oikeasti toimi oikeassa elämässä eli vanhat osoitteet ovat hyödyllistä dataa vielä jälkipolville saakka.

Please don't remove oneway=yes just like that or did you visit the place and checked that it really is a dead-end? You're very likely wrong even if you might have tried to interpret imagery. My guess (non-verified on ground) is that one can drive around that building below the upper loading/parking lot bridges.

Also, traffic_sign=FI:331 (forbidden driving direction sign) is there and even mapped to OSM to help mappers to not make mistakes like this but you didn't seem to understand enough local context to be able "fix" it correctly!!

Unfortunately, using "error" tasking tools like the one you're using easily introduce errors to maps rather than fix them if you not extremely careful (and willing to admit that occassionally some "errors" are not fixable without somebody surveying what's on the ground and that they should not be "fixed" improperly in that case).

Onko tuolle Hermannin rantatielle tapahtunut mitään muuta kuin että se on suljettu ja aidattu? Ei kai sitä nyt varsinaisesti REDIn takia raksata uusiksi vai miksi nuo tiet on nyt =construction?
Vai onko se kaivettu ihan aukikin sitten viimeisen visiittini (jolloin =construction olisi ihan paikallaan)?

Tässä poistit yhden kerätyn liikennemerkin (osm.org/node/3514422229/history)... onko kyseessä vahinko vai tarkoitus?

Thanks for adding the Swedish streetnames, however, you should retain name=* so that it matches the Finnish streetname and also name:fi must not be removed like you did. Only add Swedish name to name:sv. This applies to most names in Finland but in case you add Swedish streetnames into "kunta" that has Swedish speaking majority, then put also the Swedish streetname into name too.
That is, name=* is selected using similar language majority rule as the top entry in streetname signs. Thank you.

Hei,

Kysyisin sellaista pientä detailia, että ovatko nuo rapunovet todella aivan "nurkassa" (esim. 45 asteen kulmassa) vai ovatko ne oikeasti jommalla kummalla seinällä kulman vieressä (kuten yleisempi tapaus on)? Josset tiedä suoralta kädeltä, niin ei haittaa paljoa jos jäävän noi kuin ovat, mutta pääsääntöisesti kannattaisi koittaa laittaa ne oikealle seinälle pikemminkin kuin siihen kulmanodeen. Tarvittaessa zoomaa tarpeeksi lähelle editorissa, että saat tehtyä uuden noden siihen kulman viereen sopivalle etäisyydelle (ainakin JOSM-editorissa, jota itse käytän, auto-snappi vanhoihin nodeihin estää nodejen lisäyksen kovin lähelle kulmia ellei zoomaa lähelle, iD:tä en ole tarpeeksi käyttänyt että tietäisin miten se toimii :-)).

Didn't you even read what I said?
...Given what you say now here, why you didn't then "replace" it with "english, well known and defined tag" yourself like you actually PROMISED in your changeset comment?!? Although I highly doubt there's some global tag you can find but I'm not entirely dismissing possibility that some subsidy related tag might exists deeply buried into the wiki.
In addition, the meaning of "Arava" is so obvious to locals (that name actually comes from Finnish law I think) that there's absolutely no point in adding notes about it for some non-locals who should randomly delete stuff that make no sense to them. It's alarming BTW, that also "further destroy of data" is to be expected?!? If you'd only delete data whose meaning you fully understand (or if applicable, you'd really "replace" the tags with ones that apply more globally like you claimed to do, even better obviously), we'd not be talking here.

Ok, thanks.
It's indeed unfortunately how difficult it's to change the default rendering currently but I suspect this might even be fixable if somebody would submit a patch which adds a check for the highway type that crosses the waterway as both should be in the DB already so no technical blockers for such fix (like there are for many other useful mapnik improvements; if one needs more data columns = tags than the DB currently has, it would require reimporting the DB which is rarely done).

This is entirely mapnik issue. It should not render car image there and that's it.
Please see
osm.wiki/Key:ford It mentions even ford=stepping_stones which definately does not apply to vehicles but foot so it's entirely valid to tag these as fords!

I think this change should simply be reverted or actually replaced with ford=* rather than deprecated highway=ford.

Mapnik issue shouldn't be solved by removing correct tags!

Hmm, this is the correct copy paste link I meant:

osm.org/way/135744885/history

Why you LIE in your changeset comments? Or how exactly did you "replace local tags" here: osm.org/changeset/30803284

Please please please, you're not even the first one to trying to destroy this data, why we need to continuously complain about same tags getting deleted by some random, non-local guy?

hups, söit tässä liikennemerkin vahingossa keskelle katua...

...Koitanpi korjailla itse revertillä tuon.

Sure, the current way of tagging it is definately not the most optimal. I'd say it's more of a "reminder" type of a tag that can/should be changed to a proper tag once one discovers what that would be. I bet there are others similar ones in Finland for features that either didn't have a tag when inputted to OSM or for some reason the tag was not found from the wiki even if it existed (for non-natives it's often a challenge to figure out the magic words to locate something from the wiki).

Of course it would be even better to have some proper English key for this kind of devices (I'm assuming they might have similar ones in other countries?). There seems to flashing_lights=yes/no in wiki BTW which would be at least close, however, does it mean traffic lights type of flashing or is it more generic, it doesn't seem to have that much documentation either... ;-) However, I don't know if "välkky" itself generalizes as there seem to be many types of them and alv seems to be interested in keeping the different types too for now (it would be better in value than in a key though, at minimum).

While I understand why having wiki page on every tag would be useful for others (mainly for non-locals though), it's also rather heavy-weight for those who tend to map a lot and for example in case like this it also feels the benefits are not that high due to sparsity of the välkky devices to begin with and since it's unlikely to be the final key for these kind of devices for obvious reasons it would also likely duplicate some effort. Certainly if we know the canonical tag for something we use it and slowly convert the previously used ones to that format but mapping on large are obviously means that it would take lots of time to notice everything :-).

So, was it "mistake or redundant information", I don't believe you can say honestly you thought it would be either? That it only appears once doesn't mean it's a "mistake" and certainly you cannot decide if it's redundant information either as you don't even know what it means. Locals certainly might know what it is (I do and many mappers interested in city planning aspects likely do also) and even Google was clever enough when I pushed it slightly (it's not easy though if you don't have any clue what to look for). I suspect the other spots with "välkky" have used other tag or haven't just been tagged so far. ...So, what I said earlier still applies: find a better tag for it, or revert and let locals change it to a better tag at a later time (if there's some available, I don't know immediately nor have time to browse wiki to see if there would be some relevant tag).

See now, we end up spending again extra time on this pointless arguing. Your change was simply not good, I hope you could just accept it. In addition you probably have to accept that you might need too much local context to really fix these the way you're currently working (and perhaps some similar cases in the future you're likely to encounter if you keep doing these cleanups). I know there's lots of useful edits from this cleanup process you're participating in, also from you (I found at least one while checking your track record in Finland :-)). However, it would make it much less painful for all if you could please avoid touching keys which make absolutely no sense to you and seem like no obvious typos or such. And when you still end up occassionally making mistakes (who wouldn't), you would simply accept that a revert is the easiest way forward (less time wasted and more productive work done). No need to explain like you did as the local likely knows already enough as he/she gave you feedback which you hopefully value (if this kind of error repeats itself, I simply recommend that you say to the next mapper giving feedback that you'll leave it to the locals to fix when they come across it, they also care for the data like you do)!

And btw, I'm quite sure that alv still remembers and would have told you if you would have asked! And even better, we'd have avoided this whole episode if you would have asked _first_ and acted only after that when you know what it means :-).

I wrote to some previous guy who just removed stuff something along these line: Because of these random removals, those people doing the hard work of surveying need nowadays fear for their tags (especially if there are not yet that many of the particular tag). I hope you understand this mapper/surveyer perspective also when removing anything :-) (which is much more than what I could achieved by simply telling you what "välkky" is). Thanks.

Spoiler: "välkky" is a device that blinks or otherwise highlights the crossing traffic sign poles when it detects nearby pedestrians (or bicycles). Usually installed close to schools or some such "sensitive" places. There are at least dozens of them installed in Helsinki region alone.

And my apologies for writing so long reply, I just cannot keep replies neat and short like some other people.

Please please, you're modifying something in Finland and don't have clue what languages we use around here? Perhaps you should not modify in Finland at all then since you're clearly not used to our tagging environment.
The use of name:fr* is obviously some auto-completion error of an editor program, not an error of the mapper who was trying to type name:fi. The error should have been CORRECTED not REMOVED like you did. If you REMOVE rather than FIX errors, nobody else has the opportunity to do the RIGHT FIX since the error would be only available in the history now and no QA tool nor a mapper is going to catch it from there (luckily I caught you from the history since you also did other incorrect edits in Finland so I had to check your track record to see if there are other bogus fixes too). ...And it's not redundant information like you're trying to imply which also shows that you don't even seem to understand how bilingual naming does work in OSM which is a serious issue if you touch any names in bilingual country such as Finland.

This fix was counter-productive. Please find the real name:* postfix or just revert!

Why did you remove välkky and provided absolutely no replacement for it (nor did you tell honestly what you did in your changeset comment)? Please revert or find a better tag, if you don't know what it is, please simply revert without asking me to spend extra time on explaining what it is (I'm beginning to get very tired of constantly complaining to about these "fixes" that randomly remove tags without any sensible process to prevent data loss). Also, don't leave it as is and force me to poll and revert (as if I would remember), which is what I've had to do with the previous removers changes, unfortunately.
I suppose this edit was is due to taginfo cleanup process which should definately fall under Mechanical Edits Policy and its review clauses but each and every mapper removing data so far have claimed that it magically doesn't. I don't believe you or them did randomly end up seeing this particular node in your editor but rather you used computer assisted search to get the nodes you edit (the search runs on Taginfo computer or on overpass) that should definately make them subject to MEP.

Thank you.

Olisi varmaan parempi tehdä tuo Mustikkamaan liikuntapuisto leisure=sport_centre:nä koko tuolle alueelle kattaen kaikki kentät ja huoltorakennuksenkin ja jättää se pois tuolta itse kentältä.