private in terms of ownership is not what osm maps, but in terms of access.

that is, all the forest roads i walk are privately owned but the law requires the public have access, and so they appear in osm without any sort of access restriction.

i suspect the same should be true here.

hallo amazon,

it has happened here too.

by using the iD editor to add a turn restriction, you have again introduced buggy map data by duplicating part of the way starting at this (buggy) relation.

are you able to fix this? i fixed the last time i reported this, but i will not have the time to do the same. you may need to use josm or potlatch as another mapper was unable to make progress in iD.

thanks

This changeset has been reverted fully or in part by changeset/75633419 where the changeset comment is: maps.me rubbish with totally bogus tags. only add real facts to osm

This changeset has been reverted fully or in part by changeset/75623094 where the changeset comment is: bogus maps.me autobahn rest area

second try.

based on the name, i'd have guessed amenity=laundry but that shows how little i know as it should be shop=laundry.

i'll turn in my osm mapper badge for this faux pas. and yes, i did google the shop name to confirm my guess.

this is a simple worldwide mechanical edit carried out by the spiffy *NEW!* functionality of the iD editor in order to force a uniform worldwide tagging norm, that a handful of iD enthusiasts have been carrying out. i've reverted many tens of thousands of such changes across the us of a where i felt the data was degraded by such mechanical edits.

a similar edit in greece also caused an objection earlier today.

good lord, achavi runs out of memory when i try to visualise this. thanks for the revert. this seems to be a new breed of spammer, and probably should be nuke-on-sight rather than turn repair work over to osm volunteers given how many dozens of malformed entries they pump in per day.

second try, netwerking probs as shown within

is it possible that this continuing minor flood (dozen or so detected by me per day) originates not from the main face:b00c website proper, but from an app, Marquette place [sic] related, that got b0rked on late 23.09.2019 ?

my firefox, where i've kept the notes i resolve open in separate tabs, is up to 80+% MEMORY (OH HERE WE GO AGAIN) memory hogging, so i've been reviewing the comments, and one of them refers to a specific android device, standing out from the others.

in any case, allowing for a few older or false positives, as well as a bunch of spanish bug-reports that look suspicious (i'm not familiar with the language enough yet), my count is now up to
Connecting to api.openstreetmap.org (api.openstreetmap.org)|2001:978:2:2c::172:c|:443... connected.
[tumbleweeds, the occasional cricket]
GAAAH
132635/92995 packets, 29% loss, min/avg/ewma/max = 0.840/11.580/8.978/4066.278 ms
TRY AGAIN. OR SEE IF I CAN TOGGLE THIS BLEEDIN' CAPS-LOCK BACK TO NORMAL.

2019-10-10 15:09:48 (207 KB/s) - written to stdout [370810]

319

sorry for having to fight with my equipment/software in this reply. just wanna let you know things never go right for me, so i have sympathy for whatever has happened that is resulting in a marked increase of irrelevant-to-osm bug-reports and frustration both from myself as self-appointed grand poobah guardian of the sanctity of osm Notes, and your users whose complaints are going into an osm blackhole.

prosit,
freebeer
guarduian of te osm blackhole
and chief typoist

[p.s.: when proofreading this, i somehow toggled Caps Lock to its usual annoying four-way toggle so at least no harm was done here by this reply, cheers]

the advantage of the lifecycle prefix is that by prefixing shop, it immediately prevents it from being parsed as an active shop and rendered. regardless of the prefix - proposed, construction, disused, razed, not, was.

otherwise one needs a special rule that `vacant' is a special case, like building=no, as new values for shop= can appear at any time, to be presented as a generic icon, or dot on osm-carto.

the lifecycle prefix is more flexible and does not lose info as to the type of shop it used to be, for example if an out-of-date Note points to the location advising the previous type of use.

vacant is not false, but it is limiting.

if they actually cared, they would have followed osm conventions in the first place.

but all they care about is to dump several dozen pois per day all with similar non-osm tags, onto the map. they probably don't care if they get fixed up or not, they've been paid regardless of the quality of work and whether it appears on osm-carto. a pop-up notice is a plus.

the name should also include just the name and not a description as well.

the problem is that a tourist attraction is very broad and can cover virtually anything, and gives no clue as to what it really is, and is widely abused in osm.

natural=geyser is far more specific and accurately describes the feature so that someone seeking such things can find it without having to wade through bubbling mud also tagged as a tourist attraction should someone decide to tag things based on potential tourist interest.

in both p1 and p2:
`s' saves the present work. no new changeset is opened for the following hour. you may continue to work and incrementally upload your work so as not to lose it.
`c' will close the present changeset. if you continue to work in potlatch, your next save will open a new changeset.

it is good to get in the habit of `c'losing your changesets explicitly, so that others may immediately comment, and whatever server resources are held for an open changeset can be freed.

there are still fields needing work:
addr:street includes an abbreviation that should be written out in full
contact:phone and phone are missing the country code prefix
description should be rewritten to be less like advert cory
office field is not an osm value
opening_hours is not in osm format, and should refer to the physical location office opening hours
unit number got lost from the address

not to be critical or anything

regarding
way/379674429/history

i am having a slight mental disconnect, trying to relate a two-level building that is 30 metres tall.

i suppose it is possible for a cathedral or similar, but these appear to be condominiums

This changeset has been reverted fully or in part by changeset/75448919 where the changeset comment is: get rid of a bogus maps.me personal castle with private info

try again?

i didn't know one could use a node for highway=service, but as i look closer at this SPAM i see it is abusing =serviceS which is something so far removed from either and irrelevant to this entry. it's like the maps.me highway=rest_area being used to tag benches and non-motorway amenities.

lock'n'load...

i bet it was 35;45. as to units, i'm not going to guess. i think in one only. and it's used in all but a small handful of countries. greetz

are you planning to re-add the removed names, or just leave them like this? thanks