Bookmark this page:
- How-many-streets-are-there-in-the-USA
- 11-29-2007
If you were Registered and logged in, you could reply and use other advanced thread options
news:0fcf835d-8bc0-44ed-a6de-
You didn't specify "uniquely-named" in your original question, so I just
replied what was most relevant to me.
What happens in your code, if 2 streets far apart (different counties or
states) has the same name?
What happens in your code, if the same street crosses a county / state
border and changes or doesn't change name?
The counting will depend a lot on this.
Regards
Uffe Kousgaard
You didn't specify "uniquely-named" in your original question, so I just
replied what was most relevant to me.
> As my code is now, I am counting uniquely named features (roads) for
> which Census Feature Class Code = 'A', which roughly means "street".
> I count streets, not line segments, so naturally, I check the FENAME
> field to eliminate streets already encountered.
> which Census Feature Class Code = 'A', which roughly means "street".
> I count streets, not line segments, so naturally, I check the FENAME
> field to eliminate streets already encountered.
What happens in your code, if 2 streets far apart (different counties or
states) has the same name?
What happens in your code, if the same street crosses a county / state
border and changes or doesn't change name?
The counting will depend a lot on this.
Regards
Uffe Kousgaard
> news:0fcf835d-8bc0-44ed-a6de-
> > For the record, that is not the count of uniquely-named streets in the
> > USA.
> > USA.
> You didn't specify "uniquely-named" in your original question, so I just
> replied what was most relevant to me.
> replied what was most relevant to me.
Ah..makes sense, after all, I did mention concern was on processing
speed.
> > As my code is now, I am counting uniquely named features (roads) for
> > which Census Feature Class Code =3D 'A', which roughly means "street".
> > I count streets, not line segments, so naturally, I check the FENAME
> > field to eliminate streets already encountered.
> > which Census Feature Class Code =3D 'A', which roughly means "street".
> > I count streets, not line segments, so naturally, I check the FENAME
> > field to eliminate streets already encountered.
> What happens in your code, if 2 streets far apart (different counties or
> states) has the same name?
> states) has the same name?
I'm counting them as separate. I use the place name to provide context
for the street name, the place name being any of the various
geographic entities that the US Census uses for what a commoner would
simply call a "city".
> What happens in your code, if the same street crosses a county / state
> border and changes or doesn't change name?
> border and changes or doesn't change name?
If it crosses a border of different city even, I count that as
different, even if name states same.
> The counting will depend a lot on this.
Yes, it would.
So, I guess I should have said I am counting the number of streets by
adding up all the counts that would be obtained by asking the "mayors"
of all the "cities" in the USA, "How many streets are in your city?".
Incidentally, while debugging, I found a street named:
"Kickapoo Lane"
Some cowboy had sense of humor when recommending name for this
street. :)
-Le Chaud Lapin-
- TOMTOM
- Tomtom GPS
- 2011-11-25
- POI Mega File for Microsoft Streets & Trips has been updated [Apr 2010]
- Global Positioning System
- 2010-04-21
- POI Mega File for Microsoft Streets & Trips has been updated [April 2010]
- Satellite Navigation
- 2010-04-21
- Map accuracy
- UK GPS Discussions
- 2011-05-03
- Microsoft Streets and Trips
- Satellite Navigation
- 2010-02-22
- Too many choices
- UK GPS Discussions
- 2011-08-08
> USA.