salut,

the osm inspector should update the overlays once daily, time of day depending on overlay. it seems to take about four to six hours from the approximate snapshot time shown, until the overlay is processed and the updated data (dis)appear, so if that is too long, fine, or if you've expected otherwise, that's what i've observed from experience.

or, just random words, any meaning implied is unintentional monkeys typewriter potrzebie

pedantically speaking, this was trivial to review - a way at v1 and points at v1, and a second way at v2 with an added tag.

now, if this were more extensive or i were wedded to a particular tool, i'd agree, and there are other legit reasons for limiting changeset scope, but here checking the two items gave me no problem. well, one v2 item, i didn't bother with the v1 after seeing the v2 was a refinement of this mapper's earlier addition.

carry on.

hoi andy,

this is sort of a dilemma if one wants to check the rendering toolchain, like for the correct direction of island coastlines, or if one has the suspicion that the non-immediate updates, of which coastlines are an example, are getting hung up (partition fills when unpacking data flooding parts of the world in some tileservers some months ago being an example), maybe.

luckily i've never progressed beyond the thought experiment of how i would justify introducing such clear examples as tests into the database, but i'm sure i could find something unmapped to test were i to feel the need, rather than adding fiction.

whatever. it's late and the dog ate my homework.

serwoas,

also, you should not add this tag data to OSM regardless of what someone has mistakenly told you, it is of no use to OSM or any mappers, and is just private junk that should be kept private as it is meaningless.

further, the changeset description should reflect what was done or intended, which a #random #assortment of pointless #hastags does not do, as the description is an aid to other mappers, and serves no social media function.

thanks

To be fair to the original mapper, as I understand it, maps.me is largely responsible for these original sins by taking control away from the user and automatically uploading the way it wants.

And further, despite the range of this edit, there are only three nodes at v1 added, so even on my inconvenient Handy, I made three taps to inspect all items to see nothing obviously wrong, though the position of one node did raise eyebrows.

This is not the case where dozens or hundreds of unrelated items at varying revisions are touched, so that it truly is difficult to see if the mapper is trying to slip past a fast one; here it's just low-level noise annoying other mappers but almost guaranteeing multiple inspections and a quick fix for the usual maps.me bogosities.

Georg, looks like they are the same business, the other being a scammy on-line front to appeal to those that seek that sort of thing and not suitable for a serious map like OSM, while the data here seems realistic to reflect the physical reality one hopes to find with a visit, and not a virtual service.

is Rochester still a Thing? I thought that sock-puppetry had ceased, based on the lack of new user blocks since a three-pronged (at least) attack on that vandal's changes one nice day some months back. Well, it was probably rainy. First and only time I was involved.

Your work here is appreciated, much like TravGW whom I don't recall noticing in my recent sporadic forays back into OSM culture.

No, really. When I feed `arsonist' and `Callewaert' into the search engine of my choice, there are too many results off-limits to europe, so you're going to have to help me out, as a different Callewaert perished in an inferno in Tennessee; Willy, don't be a hero, don't be a fool with your life. Why so shy? I mean, help us yurpeens out of our Fake News state-run propaganda organs, and explain why Will set fire to his ant farm, then had a change of heart and rescued them. Else your local hero won't get the praise as fundraising nature-lovin' bahamas life-savin' board director that he deserves.

Which Board? and why has this fiction as well as the others not yet been reverted?

if you check @PaulBrown2/history you will see a lot of these changes that have not yet been reverted and for which google provides absolutely no hints. looks to be completely bogus, as such a great benefit to society should not need to be hidden in the results redacted from european eyes.

and Zoe(y) is class of '22, certain to be worthy of a news article.

no. my lengthy reply got lost

To pick nits, this was not worldwide (with Gilles Peterson, arrgh, someone extract that earworm from me brane) but spread geographically thinly.

To defend the mapper, the two items I checked were completion hig->highway; had that specific info, and not the generic `typo' been in the changeset description, it would be clear it's a failed autocomplete correction, like I've done many a time in individual changesets, and I'd give it a pass for being reasonable as a lump correction. If I were to be in a forgiving mood.

thanks - a minute freeze is definitely a productivity killer, and i don't blame you for taking action.

i take it you are accessing iD through a browser - as the rest of the system is responsive, is it just the iD tab that goes nowhere - that is, are you able to open a new browser tab and work on something else there, in that minute or two?

that will point to a browser issue in general, or some issue with the child process, javascript interpreter, or iD design proper.

i would hope you would be able to open a new browser tab and complete a separate task during the wait, which would be a workaround to keep the workflow trickling along during the freezes, and returning later to the hung task, i'd hope you could pick up where you leave off and also avoid these geographically diverse changesets, that are more an annoyance to others rather than a serious breach of protocol (manual review of the isolated changes is still relatively easy, even where other tools break).

off-topic, as i type this, i'm getting regular freezes of a few seconds. as soon as the length of the freezes extends well past that into the tens of seconds, i groan knowing that in that time my browser is dumping its cached tab contents due to memory pressure, and they will all have to be re-downloaded over the slow network. but that's a peculiarity of the mobile OS i'm enduring.

wait - child process, that's what i get invoking potlatch, maybe i'm thinking of a thread of the main browser for iD. in any case, my normal OS will kill off my potlatch while leaving my browser work-in-progress untouched. whatever,

cheers

not only that, the node i investigated happened to be in italia, where the change to type=bell_tower failed to include the wiki page subclassification of bell_tower=campanile , thereby losing information present in the previous mapping.

hola alan,

i see a weirdness in the map rendering, a discontinuity that when investigated shows a line attempting to represent a bollard that is not rendered (should be a point along the way) as well as a discontinuity along the way.

a bollard does not imply a road break, quite the opposite, as it is physically possible for pedestrians and cyclists, among other narrow vehicles, to pass.

if motor vehicles like mofas and motorcycles are legally forbidden, that should be noted, rather than breaking the continuity of the way.

if properly mapped, the bollard(s) will be represented on osm-carto as a black dot, and routing for pedestrians and cyclists and the like can continue to use this unbroken road, which is not possible at present.

as seen in way/645169783/history the access tag was already present and there is no grounds for this deletion, which IMHO should be reverted as the mapping reflected the actual situation that there are in fact driveways (not all mapped yet) branching from the roads to reach the mapped houses.

what the bl**dy f*??? ghost-touch has infected a further device. take two:

> "Thumbs up emoji"

shows up as a black box with my device font. are people going to start using obscure emojis to replace entire words soon rather than bothering to type out the full word? i say, when i was young, we had to bang out our bits with pieces of rock; paper and scissors not having been invented yet.

i hope that the two of you will not mind if i decide to harbour a grudge and continue the crusade of reverts of bogus and/or private info, as i suspect these footpaths are not open to the public as the map rendering applies. now if only i could be arsed to overcome the last unmet dependency to get the revert scripts fully functional, then i can wreak havoc again across vast stretches of tourist amenities at null island and lakes drowning out shopping centres and residences like i've been threatening or i could get a life instead, too.

nah. cockwombles deserve a good and persistent stalking.

> "Thumbs up emoji"

mapman, there are many thousands of governments which are paid for by taxpayers but whose data is not made public domain, worldwide. the us government is a notable exception, but one cannot extrapolate from that to regional and local governments. texas is known to be particularly problematic despite collecting texas taxes.

the situation is far clearer outside of the us of a, in select areas where tax-collecting government agencies have made their data open to the public but under restrictive licences, and for example in germany there is a limited number of government sources that are free to source for osm, but a significant number which are not free, even to the point where legal action has been taken against osm for the use of their data, so that the german community (of which Georg here is a member) is very careful about checking the compatibility of sources used with osm and reverting additions from incompatible government sources.

the key point is not that osm is itself a non-profit non-commercial organisation, but that its primary product, the map database and data within, is open to all use, *including commercial usage*, that complies with its terms. and many commercial services now make use of osm data in a for-profit setting, such as mapbox, maps.me, facebook, and i don't know what all.

it is for this reason that sources which limit end-usage to personal and non-commercial use are incompatible with osm, and may not be used as-is, and it is necessary to obtain a waiver or permission for the clauses that conflict (normally non-commercial limitations, or attribution requirements that osm cannot meet).

you may doubt that entity X, here fairfax county, will act against osm, but this is not grounds to copy their data, as it has happened in the past and continues to do so, if you were to monitor data working group redactions.

there is a difference between using non-compatible data to verify an item in osm, and copying from that source or making changes based on that source. i take it that the street in question where i see a name now, previously had no name. and i also take it that this name was sourced from the topic of this discussion, which would be a no-go, unless:

1) the source terms are in fact compatible with osm - i have not looked and am not a legal expert about these matters but as i note, commercial use and attribution requirements need to be compatible as the most frequent bones of contention;

b) you or someone contacts the organisation responsible for the data to obtain documented permission that osm may use that data, if 1) above is not the case.

if 1) turns out to be true, then b) is unnecessary, but if not, then to carry out b) with success would be of much greater value to osm (and i hope fits in with your threat as i read it to do something else with your time) as it would allow that source be not just used for this single addition, but to check/add data throughout the whole county, and possibly open up further data (building footprints?) for import into osm.

to respond to your claim that osm will get nowhere without relying on potentially incompatible data, i give the example of germany where the bulk of the data was added by mappers without imports, lacking TIGER equivalent. it is not perfect, and it is a very different community and ideology than one seems to find in the us where the default is google and there is less a hands-on approach that i see, but the philosophy behind osm is not to be the most complete or correct map, but the best it can be with the allowed resources, and where it comes to a choice between complete but questionable data, osm has chosen to err on the side of caution, leaving a blank rather than to include legally risky sources.

where there is a shortage of mappers, as in the us, or ropey data has been imported, the proper channel to go through is to obtain and most importantly, document permission to use external data sources to enhance mapper input.

i'm writing too much for this apparently minor infraction, and had adamant's proposal for a comment character count limit been put into production, you'd have been spared thi

another buggy app, dumping things at null island? should be reverted, i'm trying my best but don't mind if someone beats me to it