<div dir="ltr">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:<div><br></div><div><p style="box-sizing:border-box;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px;margin-top:0px"><i>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.</i></p><p style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px"><i>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.</i></p><p style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px"><i>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></p><p style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px"><i>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].</i></p><p style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px"><i>Like overpass-turbo allowing a complex query expression with wildcards would be nice too.</i></p><p style="box-sizing:border-box;margin-top:0px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px;margin-bottom:0px"><i>For now a simple query for the specific item touched would be simple and adequate.</i></p></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 8, 2020 at 6:03 AM <<a href="mailto:talk-us-request@openstreetmap.org">talk-us-request@openstreetmap.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send Talk-us mailing list submissions to<br>
<a href="mailto:talk-us@openstreetmap.org" target="_blank">talk-us@openstreetmap.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.openstreetmap.org/listinfo/talk-us" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-us</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:talk-us-request@openstreetmap.org" target="_blank">talk-us-request@openstreetmap.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:talk-us-owner@openstreetmap.org" target="_blank">talk-us-owner@openstreetmap.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Talk-us digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Streaming JOSM -- suggestions? (stevea)<br>
2. Re: Streaming JOSM -- suggestions? (stevea)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 7 Jul 2020 17:19:57 -0700<br>
From: stevea <<a href="mailto:steveaOSM@softworkers.com" target="_blank">steveaOSM@softworkers.com</a>><br>
To: Tod Fitch <<a href="mailto:tod@fitchfamily.org" target="_blank">tod@fitchfamily.org</a>><br>
Cc: talk-us <<a href="mailto:talk-us@openstreetmap.org" target="_blank">talk-us@openstreetmap.org</a>>, Bob Gambrel<br>
<<a href="mailto:rjgambrel@gmail.com" target="_blank">rjgambrel@gmail.com</a>><br>
Subject: Re: [Talk-us] Streaming JOSM -- suggestions?<br>
Message-ID: <<a href="mailto:FBA59BC3-AB08-4CB8-8136-98EA61C7C466@softworkers.com" target="_blank">FBA59BC3-AB08-4CB8-8136-98EA61C7C466@softworkers.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On Jul 7, 2020, at 5:17 PM, Tod Fitch <<a href="mailto:tod@fitchfamily.org" target="_blank">tod@fitchfamily.org</a>> wrote:<br>
> Please accept my apology for implying using the search for an automated edit.<br>
> <br>
> 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.<br>
<br>
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.<br>
<br>
Be aware, the map will be fine.<br>
<br>
SteveA<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 7 Jul 2020 18:49:07 -0700<br>
From: stevea <<a href="mailto:steveaOSM@softworkers.com" target="_blank">steveaOSM@softworkers.com</a>><br>
To: Tod Fitch <<a href="mailto:tod@fitchfamily.org" target="_blank">tod@fitchfamily.org</a>>, talk-us<br>
<<a href="mailto:talk-us@openstreetmap.org" target="_blank">talk-us@openstreetmap.org</a>><br>
Subject: Re: [Talk-us] Streaming JOSM -- suggestions?<br>
Message-ID: <<a href="mailto:1C7EF49D-69C1-4208-8053-60B13118EB0B@softworkers.com" target="_blank">1C7EF49D-69C1-4208-8053-60B13118EB0B@softworkers.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
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."<br>
<br>
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.<br>
<br>
SteveA<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Talk-us mailing list<br>
<a href="mailto:Talk-us@openstreetmap.org" target="_blank">Talk-us@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-us" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-us</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Talk-us Digest, Vol 152, Issue 6<br>
***************************************<br>
</blockquote></div>