Page 1 of 3   1 2 3 > last >>
Bookmark this page: Add How many streets are there in the USA  to Yahoo MyWeb Add How many streets are there in the USA  to Google Bookmarks Add How many streets are there in the USA  to Windows Live Add How many streets are there in the USA  to Del.icio.us Digg How many streets are there in the USA ! Add How many streets are there in the USA  to Netscape
  •  
  • Subject
  • Author
  • Date
If you were  Registered and logged in, you could reply and use other advanced thread options
Posted by Le Chaud Lapin on November 29, 2007, 12:52 am
Hi All,

I'm about to run through all 24GB+ of TIGER Line files and convert the
data to a different format. The size of my target data structure can
be computed as a function of the number of streets in the TIGER data.

Does anyone have a rough idea of how many streets/roads/etc. to
expect? I need to know so I can determine whether my process will have
enough virtual memory to hold the entire data structure or if I will
have to do some trickery.

TIA,

-Le Chaud Lapin-

Posted by Uffe Kousgaard on November 30, 2007, 2:08 am
> Does anyone have a rough idea of how many streets/roads/etc. to
> expect?

Somewhere between 30 and 40 million streets.



Posted by Le Chaud Lapin on December 7, 2007, 3:44 pm
> > Does anyone have a rough idea of how many streets/roads/etc. to
> > expect?
> Somewhere between 30 and 40 million streets.

Yup.

I just processed District of Columbia and all 50 US states except
Connecticut, because the table I copied from a US government web site
with state codes was missing CT. Unfortunately, I can't find the
link, but I am pretty certain CT was missing because I checked and
rechecked when I noticed the fault.

Anyhow, after processing DC and these 49 states, looking for cases
where census feature class code (CFCC) began with 'A', I got around
27.1 million streets, which would, indeed, make the answer 30-40
million streets if Connecticut were included, along with Puerto Rico
and U.S. territories, taking into acount that CFCC 'A' is not the only
indicator of an addressable feature.

I guess I see why people like GIS so much. There are so many data-
intensive things you can do with it, and it seems relevant to just
about everything. ;)

Much thanks.

-Le Chaud Lapin-

Posted by Le Chaud Lapin on December 9, 2007, 4:21 pm
> I just processed District of Columbia and all 50 US states except
> Connecticut, because the table I copied from a US government web site
> with state codes was missing CT. Unfortunately, I can't find the
> link, but I am pretty certain CT was missing because I checked and
> rechecked when I noticed the fault.

Found it: http://www.itl.nist.gov/fipspubs/fip55-3.htm

Look at Table 1 in this document. Notice that Connecticut is missing.

Or it could just be my misreading.

I find it hard to believe that such an important omission would be
overlooked for so long.

-Le Chaud Lapin-

Posted by Le Chaud Lapin on December 21, 2007, 8:19 pm
> > I just processed District of Columbia and all 50 US states except
> > Connecticut, because the table I copied from a US government web site
> > with state codes was missing CT. =A0Unfortunately, I can't find the
> > link, but I am pretty certain CT was missing because I checked and
> > rechecked when I noticed the fault.
> Found it:http://www.itl.nist.gov/fipspubs/fip55-3.htm
> Look at Table 1 in this document. =A0Notice that Connecticut is missing.
> Or it could just be my misreading.
> I find it hard to believe that such an important omission would be
> overlooked for so long.

It is not overlooked. The GNIS people have been aware of it for quite
a while. The erroneous data is simply stale and will not die. They
pointed me to the correct list at USGS:

"For the official site, go to <http://geonames.usgs.gov>; click
domestic, and then either download (scroll to FIPS 55), or click
search for interactive retrieval. "

-Le Chaud Lapin-

Page 1 of 3   1 2 3 > last >>