i'll speak to the considerations. in addition to what fhwa/fta is saying
and the federal
let me offer my own two-cents (ie opinion).
when changing (defining, creating, shaping, etc) your metropolitan planning
area keep in mind that this will be the area where the MPO will do its planning
and programming. from a planning perspective keep in mind that planning
requires data and data tends to fit defined geographies.
also, keep an eye on your local bylaws and other memos or working agreements.
i suspect that in some areas planning boundaries could affect policy board
composition. in some areas planning area boundaries may even be set by state
or other local laws.
finally, keep in mind that the metropolitan planning area is the space for
which the MPO has certain programming responsibilities. since programming, in
the way that ISTEA bought it to the MPOs doorstep is relatively new and
evolving, there may be some considerations as they relate to programming that
may play a role.
Sweson Yang wrote:
I used Maptitude's TIGER/Line Import function
without any problem. The
TIGER Version is 2000. Feature to import is "Census Urban Areas." I
converted the projection to NAD83. Now, I have to join all 9 Counties
together and get pertinent Census 2000 Block or Block Group demographics
for further analysis. I would welcome any suggestions as to steps for
doing this and procedures and considerations for revising the
Metropolitan Planning Area.
Sweson Yang, AICP
Chief Transportation Planner
Indianapolis Metro Planning Organization
200 E. Washington St., Suite 1841
Indianapolis, IN 46204
Midwest Resource Center
Federal Highway Administration
19900 Governors Drive
Olympia Fields, Illinois 60461