|
|
Main Page Ordering Information Register Q & A Features • MetroProfile • Comparative Analysis • Ranking Analysis • Metro MapViewer • Database & Updates |
MetroDynamics: Comparative Analysis 
Metro Comparative Analyses. Select two metros in the dialog box
and then view the MD Comparative Analysis (CA) Report. Click on the graphic at the right and press F11 key
to view a sample CA Report. The CA Report is presented in three sections.
The top section summarizes attributes of the first metro. The middle section summarizes characteristics
of the second metro. The third section presents a comparative analysis index for each subject matter data
cell in the metro profile. In this example, it is observed that the comparative analysis index for
payroll in the Austin-Round Rock, TX MSA relative to payroll in the San Antonio,
TX MSA is 126 -- the
ratio of the metro total wages values multiplied by 100.
Stated differently, the payroll in the Austin-Round Rock, TX MSA is 1.26 times the
payroll in the San Antonio metro.
It is difficult to make a meaningful comparison
of wages or pay based on the dollar amount alone. The index provides an easier
way to associate the relationship between the metros.
Compare several metros of interest using one as the normalizing basis.
Select one metro as a basis of comparison for several other metros for an apples-to-apples comparison.
Examples & Details. Without MetroDynamics, it is often difficult to determine if and where the most relevant metro decision-making data might exist. Further complicating the matter is making sure that you are using current definition metros -- they have changed dramatically since Census 2000. If you determine that the right data exist for the right geography, the next challenge is to access the most recent version of those data. Next, one set of key data must be associated with another key set of data. And then, after the data have become assembled and accessible, comes the challenge of determining what these data mean -- what do the data tell you that can have a beneficial outcome on your decision-making? MetroDynamics is designed to help you address all of these needs. Consider the simple case of the 2005 county population estimates -- official estimates released by the Census Bureau in March 2006. These data are not immediately aggregated to the metro level by Census. That will occur later in the year and different datasets will be developed containing the metro and county level data. Without MetroDynamics, someone interested in knowing how the composition of county components of a metro changed must go through an expensive, time-consuming, and error-prone process of merging these data and then getting them into a form for use by some type of software, possibly that requires custom development. Equally important are the 2005 city/place demographic estimates. These data will become available at a later point in the year. Since places are often not wholly contained within a metro (potentially crossing boundaries), it is difficult to associate places with metros. MetroDynamics does this for you. A next analytical step is to examine what these changing patterns tell you about the dynamics within a metro. It is desirable to be able to examine how city/place demographic change is occurring with a metro -- which city/places are growing faster or slower and what part of the metro they individually comprise. Similarly, it is desirable to be able to examine how county demographic change is occurring with a metro -- which counties are growing faster or slower and what part of the metro they individually comprise. MetroDynamics does this for you. You have a component table for demographic change by county and a component tables for demographic change by city/place. See links in the left column for information about other MD features. |
|
|