[Imports] US Forest Service Data

Samat K Jain lists at samat.org
Fri Feb 4 21:28:36 GMT 2011

On Thursday, February 03, 2011 07:17:46 PM Tom Ponte wrote:
> The FS data is much better than the tiger data spatially and it has the road
> numbers which correspond to the signs the Forest Service uses for signage
> unless they are shot to pieces by second amendment intellectuals.  I moved a
> few roads into place with the imagery west of town but quickly decided this
> would be a large undertaking especially adding road names. It appears that
> no one has touched the tiger data in the area of the FS land. I am guessing
> that is the case for much of the west but I have not checked that out. So if
> it has not been touched then importing new data would no doubt be a lot
> easier that if it had.  Many of the existing roads showing in OSM with the
> tiger data have been decommissioned. 

I'm the OSM mapper that's been (slowly) importing FS trails into New Mexico.

One thing pointing out is how wildly inconsistent TIGER data is—but you probably know this already. In some areas, TIGER appears to have used forest service data for roads (and is fairly accurate); in others, the TIGER dataset is divergent (and inaccurate).

The only resemblance of consistency I've found is that forest roads in the middle of nowhere appear to be identical in TIGER and FS data; roads in/near urban areas are divergent. I suppose this makes sense: urban area roads with residences/etc are likely to have things that need be monitored by the Census, so the US Census keeps their own, separate data.

> But before I get too far along with that is there any talk of updating these
> roads with newer data like the newer tiger data -(for all forest service
> districts)? I haven't looked into how much of that there is in the areas
> managed by the FS to see it is available or if it is any better - as good as
> etc. I sort of doubt it is better or as good unless it is now derived from
> FS data somehow. I am not an expert in all things tiger in case you couldn't
> tell.

There's been a *lot* of talk, but no solutions. Updating/replacing imported data is a major unsolved problem with OpenStreetMap.

My strategy with New Mexico is to just fix things, manually, as I see/survey them. Fortunately, (most) TIGER data contains forest service road numbers so most of the work required is just deleting nonexistent roads and fixing topology.

Samat K Jain <http://samat.org/> | GPG: 0x4A456FBA

What is wanted is not the will to believe, but the will to find out, which is the exact opposite.
-- Bertrand Russell (555)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20110204/9a41aad0/attachment.pgp>

More information about the Imports mailing list