Re: [Talk-us] Rural US: Correcting Original TIGER Imported Ways

[Kevin Kenny]

On Tue, Feb 13, 2018 at 5:06 PM, Martijn van Exel  wrote:

>> I'd also suggest that leaving tiger:reviewed at no is appropriate if you
>> haven't been able to travel the road/track in question and determine whether
>> it is really an unclassified road or a track, so it remains flagged for
>> further review if someone has the time and proximity to do so.
>>
>
> Agreed on that point. Leaving reviewed=no in place seems like a sensible
> approach to avoid the suggestion of higher data accuracy.

We're unanimous on that part. If you want to try to trace the road, or
change it from 'residential' to 'unclassified' or 'track, I don't mind. But
as I said, in the rural areas around here, it's really impossible to tidy
things up without surveying in person, so the handful of mappers
still need some sort of support for the "things to do" list.

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

Re: [Talk-us] Rural US: Correcting Original TIGER Imported Ways

[Martijn van Exel]

On Mon, Feb 12, 2018 at 4:02 PM, Kevin Broderick 
wrote:

> ...
> Downgrading some ways to tracks without doing so to a whole localized
> network creates the appearance of a higher level of data accuracy than
> actually exists, which IMO is more likely to bite someone in the ass than
> having a localized network of roads that are mislabeled. I know it would
> make some of the exploring I've done via on/off-road motorcycle more
> difficult.
>
> I'd also suggest that leaving tiger:reviewed at no is appropriate if you
> haven't been able to travel the road/track in question and determine
> whether it is really an unclassified road or a track, so it remains flagged
> for further review if someone has the time and proximity to do so.
>
>
Agreed on that point. Leaving reviewed=no in place seems like a sensible
approach to avoid the suggestion of higher data accuracy.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Whole-US Garmin Map update - 2018-02-10

[Bill Ricker]

> Map to visualize what each file contains:
> http://daveh.dev.openstreetmap.org/garmin/Lambertus/2018-02-10/kml/kml.html


Map is not loading for me in either Chrome or FF. (Nor Chromium).
"Loading data, please wait :spinner:"

(Previously I have not used these maps because the half-gig files
split i-95 (since the coast is inclined) and my old 76csx didn't
behave well with larger, so I did me own subsets on Lambertus's tool,
but since I've upgraded to a newer Garmin 78, your 1G or 2G files will
 be worth trying.)

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

Re: [Talk-us] Rural US: Correcting Original TIGER Imported Ways

[Jack Burke]

I've been leaving all the TIGER tags and just changing reviewed from no to 
yes

The main reason I've been leaving them is I don't know who might want to make 
use of that information. 

-jack

-- 
Typos courtesy of fancy auto spell technology

On February 13, 2018 5:13:16 AM EST, Mark Wagner  wrote:
>On Mon, 12 Feb 2018 13:25:02 -0800
>OSM Volunteer stevea  wrote:
>
>> On Feb 12, 2018, at 1:07 PM, Tod Fitch  wrote:
>
>> > Anyway, what is the current best practice dealing with TIGER tags
>> > once the road has been surveyed and corrected? Remove all TIGER
>> > tags or just the reviewed tag?  
>> 
>> As I am not familiar with the "things you've read," while also
>> wondering myself whether additional TIGER tags (tiger:cfcc,
>> tiger:zip, etc.) should remain or be deleted, I also pose this
>> question to the greater talk-us community.  What DO we do with these
>> additional TIGER tags as we endeavor to "clean up TIGER" in the USA?
>> Is there consensus on a definitive "best practice" for removing or
>> leaving them?  (Consensus is clear that we remove tiger:reviewed=no
>> after we've reviewed the way).
>> 
>> Our wiki https://wiki.osm.org/wiki/TIGER_fixup is silent on this
>> particular issue (of removing or leaving additional tags).  BTW
>> another wiki of ours, https://wiki.osm.org/wiki/TIGER_Edited_Map
>> gives a nice overview/documentation of the Ito map.
>> 
>> We might create a new thread or keep it in this one:  but even as a
>> seasoned TIGER cleanup volunteer, I don't know what to do with
>> additional TIGER tags, and I guarantee everybody reading this that
>> I'm not alone there!
>
>I find the "tiger:county" tag to be useful as a quick way to figure out
>where I am when looking at a changeset or otherwise am zoomed in on the
>map while editing.  "tiger:zip" would be useful when adding addresses
>if
>I could trust it, but it's wrong too often.  The rest of the tags
>aren't useful because either they can be derived from the OSM-relevant
>tags on the road, or they're wrong/outdated.
>
>-- 
>Mark
>
>___
>Talk-us mailing list
>Talk-us@openstreetmap.org
>https://lists.openstreetmap.org/listinfo/talk-us
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] SPAM-LOW: Re: Rural US: Correcting Original TIGER Imported Ways

[Kevin Broderick]

On Mon, Feb 12, 2018 at 6:23 PM, Brian May  wrote:

> ...
>


> Many times, a residential street having no name is a strong tip as well
> that it is not a residential street.
>
> Kevin, I hear where you are coming from, but I think your case is somewhat
> unique. Most people aren't going to look at a GPS with OSM data in it, see
> a bunch of residential roads in a rural un-populated area and think, OK,
> that must be unedited TIGER, but I know there's a few navigable roads in
> there somewhere, I just need to find them, record what I found and make
> some OSM edits. If they know the area, they are going to think this data is
> junk. If they don't know the area and they head into it they will then
> figure out pretty quickly the data is junk. I agree with others that these
> roads should probably not be in OSM at all - let the locals add the real
> roads and tracks. But we are living with the old TIGER, and there is some
> potential usefulness that can come from it. So as others have said, we are
> willing to leave them there, downgrade them to track without a grade
> assigned for now, maybe make some spatial corrections, delete roads that
> are obviously pure fantasy, etc.
>
> I don't think there should be any requirement to cover a certain size area
> when reviewing these areas. We need to be thankful that someone has taken
> the time to look at even a small area of rural areas that don't get much
> attention normally at all, especially private lands.
>

Perhaps I'm even weirder than I realized ;).

I know that I'm not the *only* one, and yes, it's more of a recognizing
bunk data then actually saying, "oh, that's got to be uncorrected TIGER"; I
could recognize areas of questionable data on my Garmin well before I got
involved in OSM and even knew what TIGER was, and as you noted, "Turn left
on Unnamed Road" was one of the warning signs that the route was likely to
be interesting (others being minor roads that allegedly go arrow-straight
in Vermont for more than half a mile, roads in minimally populated areas
that show as higher-grade than the main road connecting two hamlets, etc.).

>From what I've seen in both Montana and Vermont, the uncorrected TIGER data
generally bears a strong resemblance to *something* on the ground; it does
often include long driveways, some private roads, and occasionally paper
roads, but in the areas I'm familiar with, a TIGER road usually does have
some on-the-ground counterpart, even if many of them are not
sedan-friendly. For a lot of reasons, Vermont has very little questionable
TIGER left, Montana has a lot more, and I do agree that anyone who can pick
away at it is a good thing. I'd still suggest that, whenever possible,
modifying a localized road network in one swoop (and thus removing some of
the clues that weirdos like me would see as evidence of a good place to
explore and a bad shortcut if pressed for time) is helpful and probably
less likely to confuse routing engines.

-- 
Kevin Broderick
k...@kevinbroderick.com
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] SPAM-LOW: Re: Rural US: Correcting Original TIGER Imported Ways

[Paul Johnson]

On Feb 12, 2018 19:24, "Brian May"  wrote:

Kevin, I hear where you are coming from, but I think your case is somewhat
unique. Most people aren't going to look at a GPS with OSM data in it, see
a bunch of residential roads in a rural un-populated area and think, OK,
that must be unedited TIGER, but I know there's a few navigable roads in
there somewhere, I just need to find them, record what I found and make
some OSM edits. If they know the area, they are going to think this data is
junk. If they don't know the area and they head into it they will then
figure out pretty quickly the data is junk.


Hindsight being 20/20, it would have been nice if we had picked
highway=road as the catchall.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] SPAM-LOW: Re: Rural US: Correcting Original TIGER Imported Ways

[Dave Swarthout]

I do a lot of mapping in Alaska and the quality of the Tiger roads in rural
Alaska is simply horrendous. For some of the small communities I've worked
on the Tiger ways are so far out of position I simply delete them and start
fresh. There is no way to know where they should actually be. The main
reason to keep them and why I sometimes make a guess about their positions
is to preserve the street names. I'm never going to be able to visit these
tiny communities because they are remote and exceedingly difficult to
reach. Nobody can ever drive to them, there will probably never be any
OSMers living in a town like Alakanuk, for example, nor is any resident
likely to use the OSM data but it looks exceedingly bad to leave those ways
as they are. So I often try to fix them. It's a tedious job at best. Along
with that, there are the ugly coastlines to fix everywhere as well. Take a
look at Alakanuk here (62.684314, -164.652965) to get an idea of what
Alaska OSM mappers are up against.

Anyway, my point is that most Tiger data I've encountered is so bad I wish
it wasn't there at all. I would rather sketch in the roads (roads that I
and 99.% of data consumers will never see or use), and toss the Tiger
data completely. In my example town, I can make a reasonable guess about
the position of the roads but it's a ton of work, especially when you
realize that _all_ of Alaska's rural towns have data like this or, more
often, worse.

On Tue, Feb 13, 2018 at 8:23 AM, Brian May  wrote:

> I have spent a very large amount of time cleaning up TIGER in rural areas
> of Florida. I agree with others that the vast majority of untouched TIGER
> ways in un-populated rural areas classified as residential are forest roads
> for logging trucks at best and pure fantasy at worst, with tons of barely
> grass paths all over the place. Many of these roads are on private lands
> that you can't (or shouldn't) access anyway. Spatially accuracy is often
> horrific. I've reviewed a decent amount of 2017 TIGER and many areas have
> not been fixed. The best secondary source of data I have found are county
> streets from the county GIS departments, but those vary widely in quality.
> At the very least the county data shows you where all the forest tracks,
> farms tracks and imaginary TIGER streets are, because they are not there in
> the county data sets. Many times, a residential street having no name is a
> strong tip as well that it is not a residential street.
>
> Kevin, I hear where you are coming from, but I think your case is somewhat
> unique. Most people aren't going to look at a GPS with OSM data in it, see
> a bunch of residential roads in a rural un-populated area and think, OK,
> that must be unedited TIGER, but I know there's a few navigable roads in
> there somewhere, I just need to find them, record what I found and make
> some OSM edits. If they know the area, they are going to think this data is
> junk. If they don't know the area and they head into it they will then
> figure out pretty quickly the data is junk. I agree with others that these
> roads should probably not be in OSM at all - let the locals add the real
> roads and tracks. But we are living with the old TIGER, and there is some
> potential usefulness that can come from it. So as others have said, we are
> willing to leave them there, downgrade them to track without a grade
> assigned for now, maybe make some spatial corrections, delete roads that
> are obviously pure fantasy, etc.
>
> I don't think there should be any requirement to cover a certain size area
> when reviewing these areas. We need to be thankful that someone has taken
> the time to look at even a small area of rural areas that don't get much
> attention normally at all, especially private lands.
>
> Brian
>
> On 2/12/2018 6:02 PM, Kevin Broderick wrote:
>
> If you can cover an entire area (which I'd define as a swath between the
> nearest state highways), I agree that downgrading to track absent other
> clues is one reasonable solution. One of my key points is that anyone who's
> spent a fair bit of time trying to use GPS maps (of any origin) in
> poorly-mapped areas will quickly recognize an area that is clearly an
> unverified TIGER import, which signals both (a) that the data is clearly
> questionable and (b) that it might be an interesting place to explore to
> find out if the roads do go through or not. The questionable map data can
> be very useful, especially in conjunction with other data sources, in
> attempting to piece together a route through an area that lacks fully
> maintained roadways. If a track doesn't actually exist, yes, then it should
> certainly be deleted, but I've ridden right-of-ways that were damn near
> impossible to see with leaf-on imagery and also found other routes that
> looked more road-like via the same imagery impassable, so I definitely
> wouldn't delete anything unless you can get there in person and look for
> evidence of a roadway, perhaps 

Re: [Talk-us] Rural US: Correcting Original TIGER Imported Ways

[Mark Wagner]

On Mon, 12 Feb 2018 13:25:02 -0800
OSM Volunteer stevea  wrote:

> On Feb 12, 2018, at 1:07 PM, Tod Fitch  wrote:

> > Anyway, what is the current best practice dealing with TIGER tags
> > once the road has been surveyed and corrected? Remove all TIGER
> > tags or just the reviewed tag?  
> 
> As I am not familiar with the "things you've read," while also
> wondering myself whether additional TIGER tags (tiger:cfcc,
> tiger:zip, etc.) should remain or be deleted, I also pose this
> question to the greater talk-us community.  What DO we do with these
> additional TIGER tags as we endeavor to "clean up TIGER" in the USA?
> Is there consensus on a definitive "best practice" for removing or
> leaving them?  (Consensus is clear that we remove tiger:reviewed=no
> after we've reviewed the way).
> 
> Our wiki https://wiki.osm.org/wiki/TIGER_fixup is silent on this
> particular issue (of removing or leaving additional tags).  BTW
> another wiki of ours, https://wiki.osm.org/wiki/TIGER_Edited_Map
> gives a nice overview/documentation of the Ito map.
> 
> We might create a new thread or keep it in this one:  but even as a
> seasoned TIGER cleanup volunteer, I don't know what to do with
> additional TIGER tags, and I guarantee everybody reading this that
> I'm not alone there!

I find the "tiger:county" tag to be useful as a quick way to figure out
where I am when looking at a changeset or otherwise am zoomed in on the
map while editing.  "tiger:zip" would be useful when adding addresses if
I could trust it, but it's wrong too often.  The rest of the tags
aren't useful because either they can be derived from the OSM-relevant
tags on the road, or they're wrong/outdated.

-- 
Mark

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

Re: [Talk-us] Rural US: Correcting Original TIGER Imported Ways

[Mark Wagner]

On Mon, 12 Feb 2018 12:11:29 -0800
OSM Volunteer stevea  wrote:

> Remember, after you review tags and alignment of TIGER data, REMOVE
> the tiger:reviewed=no tag, don't change its value to yes.

I don't remove the "tiger:reviewed=no" tag unless I've verified the
name and approximate classification of the road, in addition to the
alignment.  I've found too many cases where TIGER has the wrong name
for a road.

-- 
Mark

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