Re: [OSM-talk] New OSM Quick-Fix service

[Yuri Astrakhan]

Simon, thanks for the constructive criticism, as it allows improvements
rather than aggravation. I propose that "rejections" are saved as a new
tag, for example "_autoreject".  In a way, this is very similar to the
"nobot" proposal - users reject a specific bot by hand.

_autoreject will store a semicolon-separated multivalue tag.  A query will
contain some "ID", e.g. "amenity-sanatorium", and that ID will be added to
the _autoreject whenever user clicks "reject suggestion" button.

Benefits:
* use existing tools to analyse, search, and edit this tag, without
creating anything new
* we can use it inside the queries themselves to say "only suggest to fix X
if the users have rejected Y", or if someone creates a bad query and most
values are rejected, we can easily find them and clean them up
* very easy to implement, few chances for bugs, no chances to loose
rejection data by accident
* other tools can also use this field to store rejections, e.g. mapRoulette
or Omose.
* Query authors can easily search for it to see why they showed up in the
query result, and fix the original query

The biggest problem is the tag name, any suggestions?
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] [Tagging] New OSM Quick-Fix service

[Steve Doerr]

Way to go!

 

This looks like just the kind of productivity tool OSM is crying out for. Great 
idea, Yuri.

 

Steve

 

 

From: Yuri Astrakhan [mailto:yuriastrak...@gmail.com] 
Sent: 13 October 2017 22:25
To: Tag discussion, strategy and related tools ; 
OpenStreetMap talk mailing list 
Subject: [Tagging] New OSM Quick-Fix service

 

I would like to introduce a new quick-fix editing service.  It allows users to 
generate a list of editing suggestions using a query, review each suggestion 
one by one, and click "Save" on each change if they think it's a good edit.

 

For example, RU community wants to convert  amenity=sanatorium  ->  
leisure=resort + resort=sanatorium.  Clicking on a dot shows a popup with the 
suggested edit. If you think the edit is correct, simply click Save.

Try it:  http://tinyurl.com/y8mzvk84

 

I have started a Quick fixes wiki page, where we can share and discuss quick 
fix ideas.

* Quick fixes  

* Documentation 

 

 

This is a very new project, and bugs are likely. Please go slowly, and check 
the resulting edits. Let me know if you find any problems. Your technical 
expertise is always welcome, see the code at 
https://github.com/nyurik/wikidata-query-gui  The service has adapted some code 
from the Osmose project (thanks!)

 

TODO:

* Allow multiple edits per one change set

* Show objects instead of the dots

* Allow users to change comment before saving

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] New OSM Quick-Fix service

[Simon Poole]

My major issue with this: you don't actually "confirm" that something is
a good edit or not. You only have the choice of making an edit or
leaving it to others to do. This is substantially different to
maproulette, osmose, keepright and so on.

This makes the whole thing entirely equivalent to a mechanical edit.

Simon


On 13.10.2017 23:25, Yuri Astrakhan wrote:
> I would like to introduce a new quick-fix editing service.  It allows
> users to generate a list of editing suggestions using a query, review
> each suggestion one by one, and click "Save" on each change if they
> think it's a good edit.
>
> For example, RU community wants to convert  amenity=sanatorium  -> 
> leisure=resort + resort=sanatorium.  Clicking on a dot shows a popup
> with the suggested edit. If you think the edit is correct, simply
> click Save.
> Try it:  http://tinyurl.com/y8mzvk84
>
> I have started a Quick fixes wiki page, where we can share and discuss
> quick fix ideas.
> * Quick fixes 
> * Documentation
> 
>
> This is a very new project, and bugs are likely. Please go slowly, and
> check the resulting edits. Let me know if you find any problems. Your
> technical expertise is always welcome, see the code
> at https://github.com/nyurik/wikidata-query-gui  The service has
> adapted some code from the Osmose project (thanks!)
>
> TODO:
> * Allow multiple edits per one change set
> * Show objects instead of the dots
> * Allow users to change comment before saving
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] New OSM Quick-Fix service

[Frederik Ramm]

Yuri,

On 13.10.2017 23:25, Yuri Astrakhan wrote:
> I would like to introduce a new quick-fix editing service.  It allows
> users to generate a list of editing suggestions using a query, review
> each suggestion one by one, and click "Save" on each change if they
> think it's a good edit.

I am appalled that after your abysmal OSM editing history where you more
often than not ignored existing customs rules, while *claiming* to
follow them, you're now building a service that entices others to do the
same.

You know full well that your "review suggestions one by one" is a
fig-leaf and that most people will not do that - because it wouldn't be
a quick fix otherwise, would it? How should anyone confirm that
something is "a good edit" when you allow them to make the edit on a map
at ZOOM LEVEL 3? What, in your mind, should someone do to verify that
something is "a good edit"?

You have proven that you have a very different outlook on OSM than what
our community lives by. You think OSM is just a database; if it were for
you, you'd prefer to log in to the database server and do a quick UPDATE
query to change every occurrence of tag A to tag B, and you look down on
the idea that such edits should not be made.

> For example, RU community wants to convert  amenity=sanatorium  -> 
> leisure=resort + resort=sanatorium.  

... yet the map shows world-wide results. Have the RU community decided
they would like to change this tag world-wide?

This service is going to create only trouble, and you know that
perfectly well.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[OSM-talk] New OSM Quick-Fix service

[Yuri Astrakhan]

I would like to introduce a new quick-fix editing service.  It allows users
to generate a list of editing suggestions using a query, review each
suggestion one by one, and click "Save" on each change if they think it's a
good edit.

For example, RU community wants to convert  amenity=sanatorium  ->
leisure=resort + resort=sanatorium.  Clicking on a dot shows a popup with
the suggested edit. If you think the edit is correct, simply click Save.
Try it:  http://tinyurl.com/y8mzvk84

I have started a Quick fixes wiki page, where we can share and discuss
quick fix ideas.
* Quick fixes 
* Documentation


This is a very new project, and bugs are likely. Please go slowly, and
check the resulting edits. Let me know if you find any problems. Your
technical expertise is always welcome, see the code at
https://github.com/nyurik/wikidata-query-gui  The service has adapted some
code from the Osmose project (thanks!)

TODO:
* Allow multiple edits per one change set
* Show objects instead of the dots
* Allow users to change comment before saving
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Redacting 75, 000 street names contributed by user chdr

[Pierre Béland]

Hi Frederik
The Overpass query shows me this morning that with your last redaction the 
names are back for the 620 highways.
Thanks
 
Pierre 
 

Le mercredi 11 octobre 2017 13:08:42 HAE, Pierre Béland  
a écrit :  
 
 Re-visiting this changeset I see that of the 620 ways with tag 
"source:name"="geobase.ca", 552 ways have no name restored. See for example way 
32798176 where I validated the name + added source:name Overpass query 
http://overpass-turbo.eu/s/sh6

Pierre 
 
  ___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk