One thing that I only recently figured out: You can include a search for your OSM user ID in the Overpass query. That might help to find roads you’ve edited in the past so you can remove the tiger:reviewed tag.
I am using that to find all those highway=stop I mapped back when the Wiki said
that the render/consumer could figure out which direction is was for based on
distance to the nearest intersection. Since that time tagging practice has
changed and a “direction=forward | backward” tag is now supposed to be on nodes
tagged with “highway=stop | yield”.
Since Osmose is nagging me, I thought I should go back and clean up the several
thousand instances. About 2/3rds of the way done on that task. The Overpass
search I currently use is:
> [out:xml][timeout:25];
> (
> node(user:"n76")["direction"!~".*"]["highway"="stop"]({{bbox}});
> node(user:"n76")["direction"!~".*"]["highway"="give_way"]({{bbox}});
> );
> out meta;
> >;
> out meta qt;
p.s. Thanks Steve! I was not aware I could use a geocode area like California
for my Overpass search boundary. That will come is handy!
—Tod
> On Jul 7, 2020, at 4:37 PM, Bob Gambrel <[email protected]> wrote:
>
> A very good answer stevea. I suspect the changes I have been making would be
> appropriate enough for removing tiger_reviewed=no.
>
> 1) almost always have driven the road as passenger taking notes in OSMAND+
> about pavement type
> 2) in ID carefully aligning the roads
> 3) in ID verifying that an extra road doesn't exist by looking at several
> aerial phots sources before deleting
> 4) setting pavement tpe
> 5) setting lane counts
> 6) putting in traffic signals where known
> 7) noting stop signs where possible and adding stop sign nodes
>
> Have been less likely to change road type. For example have left minor rural
> roads as residential if there are farms on it. I have made sure that service
> roads and driveways are not naked as residential.
>
> From now on I will get rid of the tag as I walk through an area.
>
> Thanks for the two links and advice. Am not ready to exhaustively do an area
> by using OT. For now just concentration on roads that I have been on and
> taken notes about and have created and uploaded traces for.
>
> On Tue, Jul 7, 2020 at 5:43 PM stevea <[email protected]
> <mailto:[email protected]>> wrote:
> Bob, thank you for asking.
>
> Good entry points for the history and what to do with TIGER data are
> https://wiki.osm.org/wiki/TIGER <https://wiki.osm.org/wiki/TIGER> and
> https://wiki.osm.org/wiki/TIGER_fixup <https://wiki.osm.org/wiki/TIGER_fixup>
> (respectively). One of the more important things you CAN do is that if you
> truly do "fix up" TIGER data to about as good as it can be today (given local
> knowledge — best — or aerial / satellite data like Esri or Bing) is to remove
> the tiger_reviewed=no tag. As the latter wiki says, "the practice to remove
> this tag varies" but I believe you should feel confident removing it when you
> are personally proud of the resultant data in OSM being truly reflective of
> what is in reality as you upload the changeset containing it. And, it isn't
> simply "alignment" being accurate, all of the tags on that datum should be
> snappy, modern and correct, too. It's not hard, and can even be fun with
> some practice.
>
> There used to be some excellent tools for visualizing areas where TIGER
> Review is needed, unfortunately, these are either old, fully deprecated or
> replaced by less-than-as-useful tools (imo). It may be that Overpass Turbo
> (OT) queries suit you, I use them in my large (data, geographically) state of
> California on TIGER rail data, and the results (while somewhat large) are not
> overwhelming, either to browsers, editors (like JOSM) where you might edit
> them (or subsets of them) or humans. However, for highway=* data, especially
> in a large (data, geographically) state where little TIGER Review has already
> completed, you may very well find OT does get overwhelmed. Try the query I
> (and others) use for California/Railroads:
>
> http://overpass-turbo.eu/s/PSt <http://overpass-turbo.eu/s/PSt>
>
> noting that it is easy to change the geocodeArea to your state and
> "way[railway]" to something like "way[highway=tertiary]"
>
> Of course, you are asking the OT server to digest large amounts of data as
> you do so, be prepared to (first) increase the timeout value (try
> one-minute-at-a-time bump-ups, from 180 to 240, from 240 to 300...) and
> (second) you might need to decrease the geocodeArea to a (unique) county,
> rather than a whole state-at-a-time. Good luck, have fun, share with your
> OSM friends how this can be a fun activity in your local area and let's slay
> the TIGER dragon!
>
> SteveA
> _______________________________________________
> Talk-us mailing list
> [email protected]
> https://lists.openstreetmap.org/listinfo/talk-us
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Talk-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-us
