Re: [Talk-us] TIGER 2007 files

2008-07-21 Thread Beau Gunderson
I unzipped the King County edges file and made do with that. Here's my proof
of concept:

   http://beaugunderson.com/osm/

The first map controls the second in terms of panning and zooming.

You can see that the 2007 data is leaps and bounds ahead of the TIGER data
that got imported (at least in this area). The freeway interchanges were
very bad and quite low resolution before, they're now quite good.

The map is centered on 47.61038, -122.20068; just East of Seattle.


Beau

On Sun, Jul 20, 2008 at 9:28 PM, Beau Gunderson [EMAIL PROTECTED]
wrote:

 I just tried to create the tool you proposed but the TIGER shapefiles are
 8gb zipped and after downloading them I've only got 6gb free on my
 webserver. :)

 To download all the shapefiles you can use:

# wget -r -A *edges* ftp://ftp2.census.gov/geo/tiger/TIGER2007FE/

 After that I was going to write a script to create a Mapnik XML file with
 them all in it and then display that with OpenLayers side-by-side with the
 current OSM map using Mapstraction and this as a reference:

http://www.mapstraction.com/ljn.php

 Maybe someone with more space can give it a try... I'm still clearing space
 on my server so I may get farther along at some point!


 Beau


 On Sun, Jul 20, 2008 at 6:39 PM, [EMAIL PROTECTED] 
 [EMAIL PROTECTED] wrote:

 Yeah, I knew trying to do sequential pulls would create a number of
 coordination issues, I just didn't know what the plan was.  I figured
 someone smarter than me had figured out a cool way to do it, like keying on
 the tiger_reviewed tag and automatically replacing centerline data that
 hadn't been reviewed with the revised entity in TIGER.  Things could still
 get messy where a user has added new subdivisions  features before the
 TIGER data release with the official position data for those streets.
 You'd need some sort of way to flag street centerlines that are too close to
 be reasonable, or cross, or whatever, and somehow keep it from flagging
 every divided highway in the system.  Doesn't sound fun.

 The idea of creating tools for users to pull thier county of interest and
 compare the new TIGER with OSM might be useful.  I thought I saw where Steve
 C had done a comparison of OSM's centerline info with Google/NAVTEQ's
 info for an area of interest in an automated way (although I could certainly
 be mistaken on that point).  A highlight tool for OSM vs. new TIGER for a
 county sized region with arial imagery in the background would be an awesome
 tool to rapidly scan for things that may have been missed...or areas where
 TIGER is really out of the loop :-)

 All in all I'm in awe of the data conversion process that has already
 taken place.  I've been playing around with the streets in my city
 (Stockton, CA) and I can't imagine having a situation similar to the UK
 where every single street had to be loaded by hand from scratch!  Thanks
 Dave for the great work!

  -Mike


 -- Beau Gunderson [EMAIL PROTECTED] wrote:
  Another alternative may be to be for the people working in an area they
 care about to do those steps manually. I'm very interested in the Seattle
 data because the TIGER data that's there now has some definite gaps. :)


 Beau

 On Sun, Jul 20, 2008 at 2:56 AM, Dave Hansen [EMAIL PROTECTED] wrote:

 On Thu, 2008-07-17 at 21:10 +, [EMAIL PROTECTED] wrote:
  Is the Census Bureau going to continue to make regular (ie. annual or
  semi-annual) data releases of street centerline data, or does the 2007
  TIGER/Line Shapefile release represent the end of the project?

 I can't imagine this will be their last release.  I'm sure they'll
 continuei

  If they plan on releasing incremental updates, is there an OSM plan in
  place for pulling from their updated information each time they
  release? or was the 2006 data intended to be a baseline that would
  then be improved and maintained only by OSM users?

 It was a real pain to import one static data set onto a blank slate.  I
 can't even imagine trying to:

 1. Read the new features
 2. Find out what those were mapped as in 2006 when we pulled the TIGER
   data
 3. Figure out where those features went in OSM
 4. Figure out if those features have been updated
 5. Which copy is better
 6. Update those features in a safe manner and at a speed that would
   allow us to complete by the time the next data set is out.

 Seriously, I always saw TIGER as a one-time thing.  If someone is really
 interested in doing this, I don't want to stop them.  But, as the dude
 who did a pretty big chunk of the work for the original import, I can
 say that I don't really even have the time to begin on this one. :)

 What we might be able to do is find holes in the original data and see
 if those holes have been filled in.  That might be a reasonably simple
 place to start if someone is interested.

 -- Dave


 ___
 Talk-us mailing list
 Talk-us@openstreetmap.org
 

Re: [Talk-us] TIGER 2007 files

2008-07-20 Thread Dave Hansen
On Thu, 2008-07-17 at 21:10 +, [EMAIL PROTECTED] wrote:
 Is the Census Bureau going to continue to make regular (ie. annual or
 semi-annual) data releases of street centerline data, or does the 2007
 TIGER/Line Shapefile release represent the end of the project?

I can't imagine this will be their last release.  I'm sure they'll
continuei

 If they plan on releasing incremental updates, is there an OSM plan in
 place for pulling from their updated information each time they
 release? or was the 2006 data intended to be a baseline that would
 then be improved and maintained only by OSM users?

It was a real pain to import one static data set onto a blank slate.  I
can't even imagine trying to:

1. Read the new features
2. Find out what those were mapped as in 2006 when we pulled the TIGER
   data
3. Figure out where those features went in OSM
4. Figure out if those features have been updated
5. Which copy is better
6. Update those features in a safe manner and at a speed that would 
   allow us to complete by the time the next data set is out. 

Seriously, I always saw TIGER as a one-time thing.  If someone is really
interested in doing this, I don't want to stop them.  But, as the dude
who did a pretty big chunk of the work for the original import, I can
say that I don't really even have the time to begin on this one. :)

What we might be able to do is find holes in the original data and see
if those holes have been filled in.  That might be a reasonably simple
place to start if someone is interested. 

-- Dave


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us


Re: [Talk-us] TIGER 2007 files

2008-07-20 Thread [EMAIL PROTECTED]
Yeah, I knew trying to do sequential pulls would create a number of 
coordination issues, I just didn't know what the plan was.  I figured someone 
smarter than me had figured out a cool way to do it, like keying on the 
tiger_reviewed tag and automatically replacing centerline data that hadn't been 
reviewed with the revised entity in TIGER.  Things could still get messy where 
a user has added new subdivisions  features before the TIGER data release with 
the official position data for those streets.  You'd need some sort of way to 
flag street centerlines that are too close to be reasonable, or cross, or 
whatever, and somehow keep it from flagging every divided highway in the 
system.  Doesn't sound fun.
The idea of creating tools for users to pull thier county of interest and 
compare the new TIGER with OSM might be useful.  I thought I saw where Steve C 
had done a comparison of OSM's centerline info with Google/NAVTEQ's info for an 
area of interest in an automated way (although I could certainly be mistaken on 
that point).  A highlight tool for OSM vs. new TIGER for a county sized region 
with arial imagery in the background would be an awesome tool to rapidly scan 
for things that may have been missed...or areas where TIGER is really out of 
the loop :-)
All in all I'm in awe of the data conversion process that has already taken 
place.  I've been playing around with the streets in my city (Stockton, CA) and 
I can't imagine having a situation similar to the UK where every single street 
had to be loaded by hand from scratch!  Thanks Dave for the great work!
 -Mike

-- Beau Gunderson [EMAIL PROTECTED] wrote:

Another alternative may be to be for the people working in an area they care 
about to do those steps manually. I'm very interested in the Seattle data 
because the TIGER data that's there now has some definite gaps. :)


Beau

On Sun, Jul 20, 2008 at 2:56 AM, Dave Hansen [EMAIL PROTECTED] wrote:
On Thu, 2008-07-17 at 21:10 +, [EMAIL PROTECTED] wrote:
 Is the Census Bureau going to continue to make regular (ie. annual or
 semi-annual) data releases of street centerline data, or does the 2007
 TIGER/Line Shapefile release represent the end of the project?

I can't imagine this will be their last release.  I'm sure they'll
continuei

 If they plan on releasing incremental updates, is there an OSM plan in
 place for pulling from their updated information each time they
 release? or was the 2006 data intended to be a baseline that would
 then be improved and maintained only by OSM users?

It was a real pain to import one static data set onto a blank slate.  I
can't even imagine trying to:

1. Read the new features
2. Find out what those were mapped as in 2006 when we pulled the TIGER
  data
3. Figure out where those features went in OSM
4. Figure out if those features have been updated
5. Which copy is better
6. Update those features in a safe manner and at a speed that would
  allow us to complete by the time the next data set is out.

Seriously, I always saw TIGER as a one-time thing.  If someone is really
interested in doing this, I don't want to stop them.  But, as the dude
who did a pretty big chunk of the work for the original import, I can
say that I don't really even have the time to begin on this one. :)

What we might be able to do is find holes in the original data and see
if those holes have been filled in.  That might be a reasonably simple
place to start if someone is interested.

-- Dave


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us


Click to get the coolest ring tones on your phone, fast and easy
http://thirdpartyoffers.juno.com/TGL2131/fc/Ioyw6iifCVPFv1cMm8bZA6J2elt4zxyi22JF15EFg2dhXcklOKozXM/___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us


Re: [Talk-us] TIGER 2007 files

2008-07-20 Thread Beau Gunderson
I just tried to create the tool you proposed but the TIGER shapefiles are
8gb zipped and after downloading them I've only got 6gb free on my
webserver. :)

To download all the shapefiles you can use:

   # wget -r -A *edges* ftp://ftp2.census.gov/geo/tiger/TIGER2007FE/

After that I was going to write a script to create a Mapnik XML file with
them all in it and then display that with OpenLayers side-by-side with the
current OSM map using Mapstraction and this as a reference:

   http://www.mapstraction.com/ljn.php

Maybe someone with more space can give it a try... I'm still clearing space
on my server so I may get farther along at some point!


Beau

On Sun, Jul 20, 2008 at 6:39 PM, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:

 Yeah, I knew trying to do sequential pulls would create a number of
 coordination issues, I just didn't know what the plan was.  I figured
 someone smarter than me had figured out a cool way to do it, like keying on
 the tiger_reviewed tag and automatically replacing centerline data that
 hadn't been reviewed with the revised entity in TIGER.  Things could still
 get messy where a user has added new subdivisions  features before the
 TIGER data release with the official position data for those streets.
 You'd need some sort of way to flag street centerlines that are too close to
 be reasonable, or cross, or whatever, and somehow keep it from flagging
 every divided highway in the system.  Doesn't sound fun.

 The idea of creating tools for users to pull thier county of interest and
 compare the new TIGER with OSM might be useful.  I thought I saw where Steve
 C had done a comparison of OSM's centerline info with Google/NAVTEQ's
 info for an area of interest in an automated way (although I could certainly
 be mistaken on that point).  A highlight tool for OSM vs. new TIGER for a
 county sized region with arial imagery in the background would be an awesome
 tool to rapidly scan for things that may have been missed...or areas where
 TIGER is really out of the loop :-)

 All in all I'm in awe of the data conversion process that has already taken
 place.  I've been playing around with the streets in my city (Stockton, CA)
 and I can't imagine having a situation similar to the UK where every single
 street had to be loaded by hand from scratch!  Thanks Dave for the great
 work!

  -Mike


 -- Beau Gunderson [EMAIL PROTECTED] wrote:
 Another alternative may be to be for the people working in an area they
 care about to do those steps manually. I'm very interested in the Seattle
 data because the TIGER data that's there now has some definite gaps. :)


 Beau

 On Sun, Jul 20, 2008 at 2:56 AM, Dave Hansen [EMAIL PROTECTED] wrote:

 On Thu, 2008-07-17 at 21:10 +, [EMAIL PROTECTED] wrote:
  Is the Census Bureau going to continue to make regular (ie. annual or
  semi-annual) data releases of street centerline data, or does the 2007
  TIGER/Line Shapefile release represent the end of the project?

 I can't imagine this will be their last release.  I'm sure they'll
 continuei

  If they plan on releasing incremental updates, is there an OSM plan in
  place for pulling from their updated information each time they
  release? or was the 2006 data intended to be a baseline that would
  then be improved and maintained only by OSM users?

 It was a real pain to import one static data set onto a blank slate.  I
 can't even imagine trying to:

 1. Read the new features
 2. Find out what those were mapped as in 2006 when we pulled the TIGER
   data
 3. Figure out where those features went in OSM
 4. Figure out if those features have been updated
 5. Which copy is better
 6. Update those features in a safe manner and at a speed that would
   allow us to complete by the time the next data set is out.

 Seriously, I always saw TIGER as a one-time thing.  If someone is really
 interested in doing this, I don't want to stop them.  But, as the dude
 who did a pretty big chunk of the work for the original import, I can
 say that I don't really even have the time to begin on this one. :)

 What we might be able to do is find holes in the original data and see
 if those holes have been filled in.  That might be a reasonably simple
 place to start if someone is interested.

 -- Dave


 ___
 Talk-us mailing list
 Talk-us@openstreetmap.org
 http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us




 
 Click to get the coolest ring tones on your phone, fast and 
 easyhttp://thirdpartyoffers.juno.com/TGL2132/fc/Ioyw6iifCVPFv1cMm8bZA6J2elt4zxyi22JF15EFg2dhXcklOKozXM/

 ___
 Talk-us mailing list
 Talk-us@openstreetmap.org
 http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us