georg, many thanks for cleaning this poorly-designed-app spam.

i would guess from the name (if it is not just a description for personal use - and it needs capitalisation to Peachtree, and if the proper name, Highrise), that it should be tagged like the nearby way/269196206 as a block of flats - or, None Of The Above :-)

thank you for that feedback, before i have bothered to add addresses.

my eyes glaze over before understanding what little italian i know, and it is a good thing i have not added any addresses, because what if one address has three or more residential entrances? i would have put the address i know on the building.

secondly, were i to do a survey of missing housenumbers, i would probably do so by printing the crudly mapped outlines and making notes onto that, and where a building is separated from its adjacent neighbours, mark the way because of GPS inaccuracy and poor aerial imageries, so that the address info follows any corrections and refinement to the building outline.

but i do not know if i will reach that point - i seem to be spending more time fixing things that continue to break rather than to bring my lightning-damaged workstation/server back to working order, so my earlier map improvements have come to a standstill, while i simply use outdated map data to try and plan my daily walks to places that may be there, or not. today, more shopping!!!

grazie

ciao,

please check what you have used for naming of the area way/499539138 that is shown prominently on the map.

is there really signage using this name? it reads to me as a generic description that can be inferred from its mapped location, and not something that should be in the name= field.

merci vielmal

please tell me how node/7117686288 is useful and should be kept. it's clear only from the nearby 69 as to which side of the street, assuming all-odd numbering, but unless the mapper updates this edit (which s/he has done elsewhere i have seen and commented), this info is of no use to anyone, sited outside of and equidistant from two candidate buildings.

the node added in the other commented (by martin) changeset was also on the highway, far from the address 7 martin had also added, again no clue if 5 were in the same building as 7 and the others, or the nearby building.

i agree, maps.me is totally unsuitable for this type of additions unless the user corrects the position and value promptly, rather than leaving randomly placed nodes, or geographically-centred items far from their actual position. but we all know that.

sorry for my change of tone from earlier; after taking a few days break, i'm back to resolving the flood of spam notes across the us of a, that has taken my time since sundown, and where i ask meself why do i bother ...

the `q' (quadrilateralise() ) key in the most common online editors including current iD will do this for you.

please explain this lake. you've made two edits both of which added implausible lakes, almost as if you want to fake the map data to cheat at some irrelevant game or something. this looks like it should be reverted too.

why have you added a lake here that does not jive with the rest of the map data? i've a feeling this changeset should be reverted without a good clarification, something i can't do at present

A. Dama, to go off-topic but to throw in two pence, a character limit on changeset comments seems pointless, as i've not seen the abuse in comments (that can't be anonymous), unlike the osm notes we worked in common in the past where complete junk was posted.

i've hit the recent notes character limit fairly often when going into detail, which can be annoying to me, while a relief to others.

a character limit here won't do anything about going off-topic, deviation, repetition, or ... um ... ah ... ehhh ... hesitation. these are the issues i need to work on, and i can just as well write a short off-topic or unclear message or loaded with insults and attacks without reaching the limit.

in these two verbal volleys i've come across this morning, i've not felt what y'all have written is too long as such, but rather that the other flaws come to the fore. i believe i understand what stevea has been doing although it's expressed a bit unclearly, and without looking at the actual data changes, i do know that Potlatch 1 is very prone to slightly moving a way when selected (probably nodes too) and throws up a warning; this was likely made worse for me by remote-X11 editing. i don't intend it and sometimes may not catch it.

anyway, i'm not back to the recovery point where i can analyse and explain what's happened, if these were wholesale polygon drag-and-drops like i'm interpreting the description. so i probably shouldn't say anything.

anyway a character count lim

if it's just a storage area of no public interest (apart from what it is), a warehouse without sales, then rental storage is not the right tag, as that's something the public is supposed to be able to rent.

if the public can buy from here, as i did at places that were storage warehouses but with wholesale-oriented offices that also willingly served the infrequent drunk as i stumbled in off the street, then a shop or office tag would seem appropriate.

if it's a completely private object, then i suggest it not be tagged as more than just a name and description to document what is there, rather than trying to shoehorn a public tag that would be searchable, and here would show up if i'm looking for some commercial locker to stash my extra wine bottles and empties. probably not what the occupant wants.

note i'm going from personal experience in a completely different part of the world with an emphasis on wine growing, very much unlike here.

i suspect this is an early extension to the five digit postal codes in the us, known by the trademark or whatever, ZIP Code, where to subdivide the area covered by the earlier single shared postcode, a four-digit hyphen-separated number was appended in order to, if memory serves, narrow it down to a single city block or something.

that is, 30306-4279 would be the ZIP-plus-four (or whatever it is called, i'm sure it's documented out on the Intertubes) address of the area; i believe two additional digits can be added to refer to a particular building number, and two more probably gets you to one particular postbox in denser areas.

i don't know if this sort of addressing has caught on in general personal use, or how things might be today.

that's how i interpret this form of postcode, without verifying my guess...

'giorno,

if iD appears to freeze for you, then you should try to figure out the reason for this. years ago i would have suspected memory pressure causing disk writes and reads due to paging and swapping, where adding more memory would help.

these days i've been degraded to non-swap hardware and yet i still see regular freezes with other applications that result in weird behaviour. like just then where it took a couple seconds for that last `r' to appear after mashing the kezboard.

i'd suggest some patience to see how long the freeze is, whether one-to-two seconds just now as i typoed blindly, or if it recovers some time after you normally would refresh the page, at which time it springs to life and exhibits the behaviour you see, i'm guessing.

that will help to determine if your hardware needs an upgrade, or if iD is a victim of the language in which it is written or some OS quirk where garbage collection or similar housekeeping results in the freezes you - and i right now with linux firefox from a live-usb to test if this replacement yet damaged computer is reliable - are observing.

i cannot guess at your hardware environment, but there must be someone in your organisation experienced enough to advise you.

that said, i've been completely unprepared for the memory management on the discarded android devices i've been using where the performance is what i used to consider totally unacceptable on a multitasking server, but seems to be the new norm, though these were low-end devices when introduced many years ago.

probably due to my age, i have no problem waiting for a hung process to recover, while in production i can understand it's a productivity killer, and the yoof of today don't know what it's like to queue all day in wartime rationing to get a single lousy loaf of bread. ah, ze good old days.

now take yer modern dubstep and grime wax cylinders and get off me lawn.

thank you for adding the address info properly to this building. however, nearby there is a so-called `shower' with this number, please delete it and do not add these as address markers - the majority of your changesets i see consist of adding bogus showers, and these should not be uploaded to osm.

please do not upload these misplaced, improperly tagged personal bookmarks to osm. this changeset should be reverted, the address info is useless where placed

this looks like a private bookmark, badly tagged and in the road and unsuitable for osm

unfortunately this is the mapper's first and only edit so far, so it's not clear if their background is in a country where maps.me sees high usage and an Autobahn amenity is frequently abused to tag a park-bench or similar. with no user description, hard to tell.

or a completely different common maps.me issue.

this description is pointless. please review your tagging of way/711132566/history and touched in later edits, also failing a meaningful description, i do not believe a building exists as mapped, engulfing other buildings correctly mapped by others.

i agree, checking a small number of objects shows no common theme. a mechanical wikidata tagging to way/156844543/history that suggests no on-the-ground visit is mixed with further edits around alaska in geographically diverse areas:

adding a name tag to relation/10201147/history which cannot be inferred from the listed sources, as well as way/93700149/history

there are mappers whom i trust to have personally visited the places where they add notes or make map edits. however, i find it difficult to believe that is the case here, and with no feedback i've seen despite repeated changeset commentaries, i am led to believe that the adding of the names does not come from the personal knowledge that is acceptable, but may well be sourced from a map that may not be used for osm.

i have no proof of this, i have not verified the names against legal sources, nor have i checked to see if the names are present in forbidden sources. however osm chooses to err on the side of caution and insists on a paper trail to the original source, which is absent here for the added names.

i have not inspected more than the listed items to be able to say if there are worldwide mechanical edits and that changes requiring local knowledge are limited to one small area, like the alaska here and nearby russia in a previously-commented changeset. i trust others are checking in more detail than i can be arsed to do at present.

by the way, all, i think i was mistaken in my claim that potlatch2 would highlight this sort of overlap, haven given meself time to digest the random drivel i wrote.

i likely confused my investigative work on this error with that performed earlier, several months ago, on a different iD irregular infrequent occurrence also revealed by amazon edits, that one actually involving duplicate and overlapping nodes, sometimes up to a dozen in a single location.

if i remember, there was no obvious visual clue for the road overlaps like here, but then, it's been about a couple months since a lightning strike took out my machine capable of invoking p2, and i've been taking me good ol' time bringing a replacement, also a victim of lightning damage about a year earlier, into full service. so i can't fire up the editor to actually see what is visualised for these overlap errors.

i'm pretty sure the visual indication was useful to identify where new additions had been made to one but not both of the segments, with the presence or absence of a distinctive junction node.

apologies if i raised any false hopes.

i should caution that if one does use p2 as you describe, there is an extensive undo stack logic but you can't totally rely on it as it appears to lose track of an initial node that seems to get left behind when deleting a stray way, or at least that's the visual representation. just thought i'd mention that to confirm that no software is perfect. (cobol maybe, let's port iD to cobol)

by the way, in p2, as i've mentioned before, upon selecting a node, it's possible to toggle the different ways sharing the node, if memory serves, with the / key, which comes in handy when multiple polygons like landuses overlap or join linear ways, or a way like a boundary shares nodes with a road.

in the case where a boundary is defined by the road but mapped separately in osm, not sharing nodes, *then* these overlapping nodes get the no-vehicle-sign prominent indication i thought was the case here. but logic tells me that while the way gets cloned and trimmed to v1, there's no reason to clone and overlap the nodes; the error is somehow the original way randomly and infrequently fails to be truncated at the junction with the new way.

i'll take a look to see if there are other non-visual indications of this, but i think as osm delivers the present repaired state of the ways in question, i won't see how it was at that point in time where i suspect the list of component nodes would show extended sharing with the same (and identically-named) way.

anyway i'll let this issue simmer and fester in the back of me brane, as you mention keepright isn't suitable for an immediate review, and i'm pretty sure my tip with p2 was totally wrong and reveals me own idiocy and stupidity rather than shedding useful light, and i should crawl back under my rock and hibernate with the slugs and fungi that are my peers these days, how my foot fits me mouth oh so well.

back to ye ole drawing board

salut, gps-systematic-offset,

thanks for the tip. normally one is never too old to learn something new, but there's always an exception to every rule.

i agree, not detecting these promptly is an issue as errors that take more effort to correct get compunded. in the case of the two ways you listed, the newer one with larger number created at v1 should have been checked for an overlap. it seems to be an infrequent issue, and i can't guess if it averages to once per ten edits, or once per fifty, or what.

if one were using the online web-browser entry to stock iD, i'd suggest that one could, needed pre-conditions permitting, change quickly from iD after saving to, say, potlatch2 by the pulldown menu, which will present a different view of the updated data, and while the overlapping ways themselves will not be obvious (paths and walkways an exception), the presence of overlapping nodes at road bends or intersections, displayed by a distinctive red-bordered white circle akin to traffic sign osm.wiki/File:Zeichen_250_-_Verbot_f%C3%BCr_Fahrzeuge_aller_Art,_StVO_1992.svg

there would be, in case of an overlap, a row of these in place of normal red nodes on the selected way, on one side of the added turn restriction. these also appear in p2 without the need to highlight/select the way.

however, amazon uses a slightly modified iD and without logging the host used to invoke it, i can't be sure but i suspect there's not the same choice of editor offered by the OSM main website, which i've assumed by offering this quick visualisation of the changes.

a frequent turn-restriction iD mapper would soon figure out how frequently this issue occurs, with vigilance to check each edit, until such time as the bug is swatted, and the untouched original way can be manually split before it is further edited and the overlap discarded, or at least checked as i had done for inconsistencies needing further meddling, in case the new way has failed to inherit something from the original.

i need to learn to write better, simpler english

the value (?) of the auto-generated comment is that when looking at the history of the object, one does not need to pull up the changeset proper to know immediately it is a maps.me rubbish edit and very probably rubbish content, as any real castles will have been mapped by a Real Editor, and pretty much all maps.me castles will be bogus personal bookmarks of private residences that have no place in osm.

other bogus maps.me node abuse includes adding highway rest areas for benches, and in latin america i see a lot of waste bins used to mark some type of shop. public shelter nodes are used to mark private residences with comments indicating that the translated-to-english use of shelter is not what osm means. alpine huts are seen in coastal cities.

language translation issues, or icons in maps.me that people like a lot?