the entire edit was not reverted, only the way.

i have doubts about node/6944588985 named `Craft beer fest' as the name implies an event, not an object, and would be typical for the sort of maps.me personal bookmarks that somehow get uploaded to the osm map itself inappropriately and do not reflect reality.

this is a completely unhelpful comment. mapper Cebderby has given a detailed and clear explanation of the problems and issues with your mapping, which should be respected and not simply dismissed in the way you have by trying to deny reality, closing your eyes, and hoping it is all a bad dream and those nasty mappers out there should leave you alone.

> Jeg mener at dette endringssettet bør bli reversert.

i see that some days later, this has not happened, and checking a few ways below, they remain deleted or unchanged.

https://nrenner.github.io/achavi/?changeset=76562562 shows me compared with aerials that the simplification (supposedly to save nodes) does more to degrade the map than to improve it, and the idea to save nodes is misled, once they are created, they exist in the database.

i agree this changeset should be reverted.

ad_maps, thanks for your correction to the private car park, as described above.

also, it looks as if you are running a custom script or utility, as the changeset tag
created_by David Nicholson
appears to refer to your own name, i'm guessing, rather than to identify the particular trackable source-code of the data (like Acme Fix-o-bot v.003644).

this changeset (that i missed at the time, due to Having A Real Life™, whatever that is) is being discussed elsewhere, and what caught my eye is:

node/108172/history

this shows an old node, long since deleted, and improperly brought back from the dead with this changeset.

i've also seen this behaviour with an improbable number of changesets in iran that recycle deleted nodes, adding rubbish tags such as gamification. i have not kept track of all these, but my recent memory is they appear to be from a legit version of josm, whether faked or from a malware plugin. i seem to remember analysing earlier gamification instances claiming to be from the bogus josm 1.6, but my dementia appears to be growing exponentially every day i awaken.

i just thought i'd mention this. no real reason. carry on.

i am not [name revealed elsewhere], but i believe he is passionate about stadiums/stadia and their sports, and while he is related to a website that may or may not use osm data, his work on osm is not sponsored as such.

he may receive payment outside osm. at this point i should probably let stadiaarcadia speak for himself, rather than trying to defend him.

i see a problem in this changeset, subject of earlier comments that have fallen off my week-only radar history due to actually having a real life by day leaving less time to swat spammers. and that is the use of ALL-CAPS for Weserstadion, in addition to the locals' reservation of using a sponsor name in the regular name field rather than in the official name. osm does not blindly mimic the advert-wishes of corporations, but tries to treat them all alike. if wohninvest wishes to be written so rather than Wohninvest, then fine, just like i find dm (Drogerie Markt) totally in line when DM means to me Deutsche Mark, a currency.

however, to write WESERSTADION in all caps goes against the osm policy that names should be written out without advert enhancements, and only acronyms like MAN (vehicles) or TITSUP (total incompetence to sling uppercase prattle) should get the uppercase treatment, lest the map be spammed by firms TRYING TO OUTSHOUT EACH OTHER.

there is an ici paris xxl or something i've wanted to apply this to, as i understand, without knowing french, ici to be a word, same with paris. at best the XXL can remain all caps like with austrian XXXXXXXL Lutz or whatever they are now. if you cannot provide the words forming the acronym WESERSTADION, then don't write it that way. I'll try to come up with a backronym i feel is suitably disrespectful, and probably should not make it into osm:
Wan*ers E*ting S*it
oh this is too stupid and off-topic. Weserstadion is one word, not an acronym, and should be written so, not screamed.

sorry for going off-topic here. anyway, i believe stadiaarcadia is independent but with personal interests, like most of us volunteers.

would love to be proven wrong. again.

grazie.

mojn citysuite,
thanks for your changeset changeset/76667142 , `Links entfernt.'. good work.

this came after changeset changeset/76667012 , `Werbelinks entfernt' by DD1GJ, and in the first example i look at, node/6949393708/history , i can see no difference between the latest version and the earlier one from Joachim, eyeballing things. not sure why that is, but no matter.

in any case, i am glad you made a changeset to take responsibility for cleaning up after your bad tagging. herzlichen dank.

for reference, the deleted way (within this year, after this changeset) can be sorta seen in way/39568965/history or history inspections.

no idea why it was deleted or anything.

based on the visualisation offered by https://nrenner.github.io/achavi/?changeset=76230264 (zoom in to the area of activity as this covers the whole pipeline segment), this looks not dissimilar to another golf mapper who repeatedly distorted and shoved to the side various features in the vicinity of a different golf course(s), as well as deleting nearby features outright.

it should be made clear that osm is a map of the real world, and not a playground that can be manipulated for the self-interest needs of some golf course game or pokémon go or whatever, and if these other uses cannot ignore the reality that appears to corrupt the pristine golf courses, they need to be fixed to adhere to osm standards, rather than falsifying osm data.

moin moin, georg,

i' verstehe dein antwort nid, weil...

This tag is used to describe the computer program (editor or script) which made the changes' - similar to a user agent - and is automatically added by editors to a saved changeset.

[i quote from the wiki 05.aug.2019 edit, including the spurious single-quote after the plural `changes']

weiter:

Guidance to software developers
[...]
* You should record a created_by tag on a changeset when saving
changes

i would recommend that the internet RFC language be used, even though this is the editable-by-anyone wiki and may not reflect the ideas held by the various *WG members, and the SHOULD should be replaced with MUST.

because (for a different reason, but applicable here)...

This helps people track down problems if a version of your editor/script has a bug in it.

or here, where the present version (also not provided by maps.me to aid in identifying categories of misbehaviour) of this unknown app/script/editor/program is submitting bogus data based on the supplied changeset comment.

we are seeing a bug here. we have no way to identify what is causing this bug. i am also seeing a bug/abuse in iran - where there is also serious notes abuse, probably unrelated - where earlier a bogus created_by line was supplied by the user agent responsible for the gamification spam / unwanted node recycling, and now of late the probably current josm version is being supplied for this unusual and irresponsible behaviour, with no way for an outsider to identify whether this header is faked, or the result of a malware-alike plugin for a real josm instance.

i saw recently that the tileserver CDN got updates to identify rogue clients masquerading as legitimate apps in order to attempt to conceal their abuse.

unfortunately the fingerprints of this changeset are unavailable to end-users such as myself concerned with identifying and resolving problems, so a strongly-enforced created_by policy seems needed, and the wiki language to me suggests an idealistic policy like the early days of the internet, failing to foresee the abuse that became commonplace there, and can be observed in varied stages of infancy in osm, from anonymous spam to outright abuse.

verzeihung, weil mein englisch ist nicht so leicht zu verstehen oder übersetzen.

schöne grüße
ciao

further, without actually analysing any of the changesets you've made recently, i can only say you have been ignoring my and other mappers' requests to use relevant and meaningful changeset comments. which include:

Edits (repeated)
[an off-topic sensible description]
jw
dtj
hc
getkhuf
dtuk
dhtxxxxxx
yeetus defeatus
glu
7e
yeet
8846
356
iyrxr
tvfts7c frefear jaku103 rd alt 6667
get out of my car N O W
(okay, so this is what i was told yesterday evening, unrelated to mapping, but what you use to describe your changesets should be relevant, and without looking, i suspect you did not leave a many-metre long trail of ripped fabric, skin, blood, and various detachable body parts along a stretch of road that i am trying to find to add to the map)
d dint givebaeyugeuf

i'll stop there as i resolved not to go past a single history page, but this is not a recent deviation.

i can deal with cute descriptions if they are relevant to the edit, but to turn control of your descriptions to your cat(s) is most unwise. and it is disrespectful of your fellow mappers who may be trying to figure why things went titsup during an edit of yours, as i've done several times in the past before giving up as hopeless based on meaningless changeset descriptions.

you cannot, the changeset is immutable.

but by explaining as you did in your comment that google was secondary to your personal observations on the ground, you've done the correct thing, and so long as no google data (precise location, name, details) was copied that you did not observe in person, there should be no need for concern.

of course, IANAL, YMMV, YHBT, POTRZEBIE, HAND.

catnapping catburglar mappers make happy crappy cat-5e app catmappers in nappies caterwauling `cat /dev/random` on the catwalk. your tom obviously knows what that cat clinic will do to his masculinity; wipe down your walls

why in the first place are you uploading deleted nodes with low ID numbers? old nodes should never be re-used because it makes reverting to their original undeleted state impossible.

secondly, you are uploading these recycled nodes with rubbish tags,
gamification yes
player_id 451002118
slug report_network
among others.

the tag
creation_date_time 2019-10-25T22:38:03.140
does not reflect the upload time, so this is obviously being uploaded from some external database with no relation to osm.

this repeated abuse of meaningless data has no place in osm, and i suggest you figure out how this is happening, whether it is a malicious plugin for josm, or something you are doing, and fix it. this sort of activity has been going on too long and too often for it to be a simple mistake.

earlier edits of this type used a bogus josm version number that i can't immediately point to, so this may not be an josm edit but some malware that pretends to be josm, as that version number only appeared for non-serious mapping.

This changeset has been reverted fully or in part by changeset/76789584 where the changeset comment is: personal private info maps.me bogus viewpoint

i have seen where the arrow keys in potlatch2 work to both pan the map and to cycle between tag possibilities when not trapped properly.

i have also had oneway=no get added due to this bug on selected ways.

dunno if this is what happened here, but just thought i'd mention it, as my own such changes went unnoticed for a while.

i see a number of ways tagged as benches but also as building=yes that are rendered as irregular polygons - wouldn't there be a better way to mark these outlines, perhaps a wall or something, or would these be some sort of roof structure?
these are the first few entries below.

moin,

just wondering. in this changeset you seem to have created way/728934729/history which at present bears no tags, and is not a member of any of the three relations this changeset affects.

do you remember the purpose behind this way, which at least at time of creation, shares every node with a different mapped feature?

thanks

also, we write out names in full, rather than use abbreviations, so the street address of the school is likely to be East M36, or `East M 36' to match the existing highway spacing style.