Ken—
The analysis you saw comes from a PLOSONE academic article. Looked at it last week. The number crunching was done by Dash Nelson, a geographer at Dartmouth.
Dash Nelson’s paper is an exploration of: what if we used the same
data Census uses for metro area, but changed criteria, changed the parameters and cut-offs… The criteria used are extreme, and the result is extreme.
Questions that occur to me: Do you believe Des Moines is “mega region” – or are you instead looking at an artificial region populated by (few) people not tied in to any other surrounding regional
economy – and let’s call that Des Moines.
|
Todd Graham Principal Forecaster | Metropolitan Council | Regional Policy and Research todd.graham@metc.state.mn.us P. 651.602.1322 | F. 651.602.1674 390 North Robert Street | St. Paul, MN 55101 |
metrocouncil.org/data |
From: ctpp-news-bounces@chrispy.net [mailto:ctpp-news-bounces@chrispy.net]
On Behalf Of Cervenka, Kenneth (FTA)
Sent: Friday, December 02, 2016 3:41 PM
To: ctpp-news@chrispy.net
Subject: Re: [CTPP] Distance travveled to work
This is a little bit off-topic, but someone sent the following to me a few minutes ago, which is an interesting portrayal of the 2006-2010 CTPP-based travel patterns
across the country.
https://www.wired.com/2016/12/mesmerizing-commute-maps-reveal-live-mega-regions-not-cities/
Well, at least I thought it looked rather awesome.
Ken Cervenka
From: Kim, Kyeongsu [mailto:kkim@louisberger.com]
Sent: Friday, December 02, 2016 2:58 PM
To: ctpp-news@chrispy.net
Subject: Re: [CTPP] Distance travveled to work
I agree with Steve that LODES does not provide the distance. Find the linked document for LODES. https://lehd.ces.census.gov/data/lodes/LODES7/LODESTechDoc7.2.pdf
For my previous analysis, I used the centroid of census block group (you can go down to block level) OD and estimated (transit and driving) travel time using google api.
lehd.ces.census.gov 2 Rev. 20160303 The geography crosswalk is a relationship file that establishes the hierarchical connection between
each 2010 census tabulation block and all higher ... |
Kyeongsu (Steve) Kim
Senior Planner
direct +1.212.383.7233
mobile +1.732.425.1311
email
kkim@louisberger.com
web louisberger.com
Louis Berger
48 Wall Street, 16th Floor | New
York | NY | 10005 | USA
From:
ctpp-news-bounces@chrispy.net <ctpp-news-bounces@chrispy.net> on behalf of Steve Wilson <swilson@srfconsulting.com>
Sent: Friday, December 2, 2016 3:39:34 PM
To: ctpp-news@chrispy.net
Subject: Re: [CTPP] Distance travveled to work
I wonder if people are referring to the buffer tool available with the LEHD “On The Map” tool. That is distance, but it is not travel distance.
From: Cervenka, Kenneth (FTA) [mailto:Kenneth.Cervenka@dot.gov]
Sent: Friday, December 02, 2016 2:30 PM
To: ctpp-news@chrispy.net
Subject: Re: [CTPP] Distance travveled to work
Hello,
Both Kevin Tierney and Alex Karner are quite right about there not being a “distance” table in the ACS/CTPP files.
But now this brings up an interesting secondary question: exactly how is this being calculated in the LEHD product? Unless everyone who commutes to work drives their own car
in a mostly uncongested and non-tolled environment, this is actually a lot more complicated to “get right” than one might think, even if a road network-based find-the-minimum-path approach is used. I presume there is documentation about how the distance-based
calculations are being done (surely it is something more than a straight-line between two centroids, multiplied by a national factor to represent circuity for auto travelers, but that would be my guess), but a quick search of LEHD and LODE documents did not
reveal the answer.
Ken Cervenka
FTA Office of Planning
From:
ctpp-news-bounces@chrispy.net [mailto:ctpp-news-bounces@chrispy.net]
On Behalf Of Kevin Tierney
Sent: Friday, December 02, 2016 2:27 PM
To: ctpp-news@chrispy.net
Subject: Re: [CTPP] Distance travveled to work
No. Some users noted a desire for it in the recent CTPP Assessment, but others indicated they get that information from their travel models.
From:
ctpp-news-bounces@chrispy.net [mailto:ctpp-news-bounces@chrispy.net]
On Behalf Of Alex Karner
Sent: Friday, December 02, 2016 2:21 PM
To: ctpp-news@chrispy.net
Subject: Re: [CTPP] Distance travveled to work
ACS has commute time but not distance. With CTPP you can use OD flows to calculate distance using network approaches or assuming straight lines. No way to get distance directly as far as I know.
-Alex
--
Alex Karner, PhD
Assistant Professor
School of City & Regional Planning
Georgia Institute of Technology
alexkarner.com
From: Mara Kaminowitz <mkaminowitz@baltometro.org>
To: "ctpp-news@chrispy.net" <ctpp-news@chrispy.net>
Sent: Friday, December 2, 2016 2:07 PM
Subject: [CTPP] Distance travveled to work
Hello,
Is there a table in ACS or CTPP that gives the distance traveled to work? I know it's in LEHD but I'd like to pin down another source.
Mara
--
Mara Kaminowitz, GISP
GIS Coordinator
.........................................................................
Baltimore Metropolitan Council
Offices @ McHenry Row
1500 Whetstone Way
Suite 300
Baltimore, MD 21230
410-732-0500 ext. 1030
mkaminowitz@baltometro.org
www.baltometro.org
_______________________________________________
ctpp-news mailing list
ctpp-news@chrispy.net
https://www.chrispy.net/mailman/listinfo/ctpp-news
This message, including any attachments hereto, may contain privileged and/or confidential information and is intended solely for the attention and use of the intended addressee(s). If you are not the intended addressee, you may
neither use, copy, nor deliver to anyone this message or any of its attachments. In such case, you should immediately destroy this message and its attachments and kindly notify the sender by reply mail. Unless made by a person with actual authority conferred
by Louis Berger, the information and statements herein do not constitute a binding commitment or warranty by Louis Berger. Louis Berger assumes no responsibility for any misperceptions, errors or misunderstandings. You are urged to verify any information that
is confusing and report any errors/concerns to us in writing.