As an ID editor user I thought of an improvement to it overnight wrt Tiger
data. I submitted a feature request. Just thought that something like this
might be useful within other editors too (if your workflow is like mine). I
was inspired by the Tiger reviewed=no discussion and my desire to tame the
tiger. I was concerned about effort (to find a bunch of ways to delete the
tag that I have just recently edited enough to remove the tag, but didn't
remove the tags) to switch back and forth between OT and ID. Text of my
request:

*Use case: I am systematically updating a long highway or extended bike
route consisting of many ways, and for each new way (segment) that I touch,
I want to be warned in the editor that the way meets certain criteria that
I select (such as tiger:reviewed=no). As in overpass-turbo, I would be
allowed to type in the query. If the particular way I am now touching some
distinctive message or visual indicator would appear informing me that the
way meets the criteria.*

*Value to me: I can systematically walk the extended route and whenever a
specific way meets the criteria I specify I am notified and I can address
it.*

*The visual indicator could be something like: the selected item blinks if
the criteria is [sic] met. Or, a message pops up in the editing window
(left pane) that tells me the criteria are met. (Similar to the
notifications that I should consider a tunnel or bridge when I am on a way
that crosses a river).*

*I can imagine using many different criteria just as I would in
overpass-turbo. I might be interested in criteria for buildings. So ways,
areas, points might all have some sort of criteria filter. (Cool if you
could allow me to set 3 different criteria). But not neccessary [sic].*

*Like overpass-turbo allowing a complex query expression with wildcards
would be nice too.*

*For now a simple query for the specific item touched would be simple and
adequate.*

On Wed, Jul 8, 2020 at 6:03 AM <talk-us-requ...@openstreetmap.org> wrote:

> Send Talk-us mailing list submissions to
>         talk-us@openstreetmap.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.openstreetmap.org/listinfo/talk-us
> or, via email, send a message with subject or body 'help' to
>         talk-us-requ...@openstreetmap.org
>
> You can reach the person managing the list at
>         talk-us-ow...@openstreetmap.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Talk-us digest..."
>
>
> Today's Topics:
>
>    1. Re: Streaming JOSM -- suggestions? (stevea)
>    2. Re: Streaming JOSM -- suggestions? (stevea)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 7 Jul 2020 17:19:57 -0700
> From: stevea <stevea...@softworkers.com>
> To: Tod Fitch <t...@fitchfamily.org>
> Cc: talk-us <talk-us@openstreetmap.org>, Bob Gambrel
>         <rjgamb...@gmail.com>
> Subject: Re: [Talk-us] Streaming JOSM -- suggestions?
> Message-ID: <fba59bc3-ab08-4cb8-8136-98ea61c7c...@softworkers.com>
> Content-Type: text/plain;       charset=us-ascii
>
> On Jul 7, 2020, at 5:17 PM, Tod Fitch <t...@fitchfamily.org> wrote:
> > Please accept my apology for implying using the search for an automated
> edit.
> >
> > I assumed the same type of work flow I am doing now: Using the results
> of the query to direct my attention to what I want to fix. Still need to
> examine the location and available information to decide, on an object by
> object basis, if the data in OSM meets your standards or needs further
> improvement before doing something like removing the tiger:reviewed tag.
>
> Sure, I don't think an apology is necessary, as we're all adults here (I
> think!) and take responsibility for our actions.  Sometimes, we are not
> aware that our actions are like pulling a machine gun trigger or tipping
> over an entire bucket of paint:  relatively minor actions on our part but
> which have a profound effect on the map's data.
>
> Be aware, the map will be fine.
>
> SteveA
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 7 Jul 2020 18:49:07 -0700
> From: stevea <stevea...@softworkers.com>
> To: Tod Fitch <t...@fitchfamily.org>, talk-us
>         <talk-us@openstreetmap.org>
> Subject: Re: [Talk-us] Streaming JOSM -- suggestions?
> Message-ID: <1c7ef49d-69c1-4208-8053-60b13118e...@softworkers.com>
> Content-Type: text/plain;       charset=us-ascii
>
> I think we're saying the same thing:  I use OT to curate datasets and
> sometimes I'll specifically clean up their TIGER data, like when that is
> exactly what I curate in my query.  Other times, I'll fix TIGER data
> otherwise.  I'm deliberate in all cases and I believe all good OSM editors
> are deliberate, too.  (Those who find themselves faced with TIGER data, as
> some of us are).  As long as "OT query results" don't ridiculously get
> out-of-control turning into automated edits, we're good.  I don't think
> that happens (often), but if you wanted to make it a short distance between
> those two, you could.  Even if your intentions are nefarious, which they
> are not and is what I mean by "all good OSM editors."
>
> So, yeah, lots of sharp edges that might cut, there.  I don't mean to hurt
> anybody by suggesting that they tend towards that, not my intentions at
> all.  Let's all be careful growing these wonderful map data.  They are
> wonderful, often beautiful.
>
> SteveA
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
>
> ------------------------------
>
> End of Talk-us Digest, Vol 152, Issue 6
> ***************************************
>
_______________________________________________
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Reply via email to