It isn't worth it, I'm afraid you're loosing your time.
Given that the two tags aren't the same (amenity=atm is an atm, atm=yes
contains an atm) you'll soon have this one art piece that definitely deserves
amenity=atm + atm=no. Or not.
If you're not ready to consume OSM data using NOT, AND or OR
On Fri, 14 Jun 2019 10:02:59 +0100
Dave F via talk wrote:
> On 14/06/2019 07:57, Mateusz Konieczny wrote:
> > Edits would be split to not create overly large bounding boxes.
>
> As long as it's clearly commented, I wouldn't loose any sleep over
> the physical size of the changeset. OSM should
On 6/14/2019 9:50 AM, Dave F via talk wrote:
On 14/06/2019 14:10, Jmapb wrote:
If there's a problem with a well-thought-out mechanical edit, it's
highly likely to be localized,
For mechanical/bot/automated edits, errors are more likely to be
duplicated across all amendments.
If 'local mappin
14 Jun 2019, 14:55 by dieterdre...@gmail.com:
> Looking at the actual sustenance values (total usage around 200 only), these
> are all duplicating words which are already tagged as amenity values
> (restaurant, fast_food etc.), I also haven't found specific documentation for
> this key (and
On 14/06/2019 14:10, Jmapb wrote:
If there's a problem with a well-thought-out mechanical edit, it's
highly likely to be localized,
For mechanical/bot/automated edits, errors are more likely to be
duplicated across all amendments.
If 'local mapping communities' have 'different ideas' it s
On 6/14/2019 5:02 AM, Dave F via talk wrote:
That the main website is antiquated & unable to display details of
edits is not a reason to improve the database efficiently. Performing
edits in one go makes them easier to keep track of & revert, if
there's a problem.
DaveF
IMO, smaller and more
Am Fr., 14. Juni 2019 um 09:00 Uhr schrieb Mateusz Konieczny <
matkoni...@tutanota.com>:
> So in total I propose to remove
>
> atm=yes from amenity=atm http://overpass-turbo.eu/s/JW8
> transportation=fuel from amenity=fuel http://overpass-turbo.eu/s/JWe
> sustenance=restaurant from amenity=restaur
On 14/06/2019 07:57, Mateusz Konieczny wrote:
Edits would be split to not create overly large bounding boxes.
As long as it's clearly commented, I wouldn't loose any sleep over the
physical size of the changeset. OSM should be concerning itself with
quality rather than quantity.
That the ma
It's taken you longer to write your email than it would to write a line
of extra code to search for them.
Easier to distinguish between the two:
http://overpass-turbo.eu/s/JWq
DaveF
On 14/06/2019 08:27, Johnparis wrote:
For ATMs, at least, I would propose the opposite: add the atm=yes tag to
Please no.
Essentially you are saying that all attribute tags that indicate that a
specific facility is present should be duplicated on the standalone
objects of the same type.
bin=yes on amenity=waste_basket, bench=yes on amenity=bench and so on.
Am 14.06.2019 um 09:27 schrieb Johnparis:
> For
Hi,
On 14.06.19 08:57, Mateusz Konieczny wrote:
> So in total I propose to remove
[...]
Makes sense to me. Please document it on the wiki as per the automated
editing guidlines,
"You should normally document your proposed edit at an English-language
wiki page named "Automated edits/username" (w
I think this proposed edit is reasonable, it makes things simpler without
loosing any information.
On Fri, 14 Jun 2019 at 17:30, Johnparis wrote:
> From a user perspective, I want to be able to search for atm=yes to obtain
> all the nearby ATMs. Removing this tag leaves me without standalone ATM
sent from a phone
> On 14. Jun 2019, at 09:27, Johnparis wrote:
>
> For ATMs, at least, I would propose the opposite: add the atm=yes tag to all
> amenity=atm
this doesn‘t seem reasonable, atm=yes is a property to state that the feature
provides an atm. With amenity=yes it is already impli
For ATMs, at least, I would propose the opposite: add the atm=yes tag to
all amenity=atm
>From a user perspective, I want to be able to search for atm=yes to obtain
all the nearby ATMs. Removing this tag leaves me without standalone ATMs,
so I would have to search for atm=yes OR amenity=atm
Thus,
Recently in mapping I encountered amenity=atm with atm=yes
I manually removed atm=yes, but it turns that there is more of such objects.
I propose to run an automatic edit that will remove atm=yes from all such
objects.
In addition I propose to remove also some other blatant and unnecessary
dupli
15 matches
Mail list logo
