Missouri Census Data Center

MABLE/Geocorr2K: Geographic Correspondence Engine with Census 2000 Geography

Version 1.3.3 (August, 2010)

There is now a version of this application that works with 2010 geography. Access it at
http://mcdc.missouri.edu/websas/geocorr12.html.

This application accesses the MABLE07 data base (rev. 7/10) with 2000 (and later) geographic codes, and generates "correlation list" reports / files.

Links:  Cure for Common Codes (related app)    |    What's new in Version 1.3    |    Previous Version (with 1990 vintage geos)    |    Tutorial (ppt)

There is now a tutorial comprised of videos of geocorr2k sample runs.

Note: The Help page has not been updated for the new 2k version. But an awful lot of what was true then still applies.

This form has 5 main sections. Only the first 2 are required.
Input | Output | Geographic Filter | Point & Distance | Bounding Box

Input Options

Select state(s) to process.

For background info re the geocodes used in the MABLE database (Source/Target geocodes) see the
Master Area Geographic Glossary Of Terms:    MAGGOT file.   (Rev. Nov 2009)

 
Select 1 or more "SOURCE" Geocode(s) Select 1 or more "TARGET" Geocode(s)
Notes:
- Process time for large areas/many states may be several minutes. IE users see microsoft note on how to avoid having your browser time out.
+ If you chose census block then you may not choose more than 10 states.
* If you chose "Concentric Ring Pseudo-Geocode" from either list (above) then you must specify the "Point and Distance" or "Ring Geocode" options below.
Weighting Variable:
Specify the variable to use for determining the portion of the source geocodes corresponding to the target geocodes:

Note: Do NOT use the 2009 estimate as weighting variable when working with small (sub-county) geographic areas. The '09 estimate for each block is just the pop2k value multiplied by a county-based change-in-pop factor. .
Ignore Census Blocks with a value of 0 for the weighting variable. New default value for option (now defaults to checked).

Output Options


Have weighted centroids calculated and kept on the output file(s)
Generate 2nd allocation factor (AFACT2): portion of target geocodes in source geocodes
Sort by target geocodes, then source geocodes (default is by source, then target)

You have your choice of 2 output formats: a comma-separated-value (".csv") file and/or a report format ("listing") file. For each file you can specify whether you want just the geographic codes, or the codes and the names associated with them (where applicable), or just the names.

Comma Separated Value File Listing File
Generate a CSV file    Use tabs as delimiter Generate a listing file    Format:
(Optional) Title for output report:


  Processing time for large areas may be several minutes.

Geographic Filtering Options

NOTE: This section allows you to specify options that will limit the geographic universe to be processed. If you just want to process the entire state(s) that you have selected then you can ignore this section.
You can specify any or all of 4 types of geography to limit the universe to be processed. You may, for example, only want to see a file with geography for a set of counties, or for a specific metro area (or areas), or possibly for a city (place). You can do so by entering the appropriate FIPS (Federal Information Processing Standard) codes in the text entry boxes that follow. If you need to look up the codes you can click on the links to the code-list files in each section or use the Cure for the Common Codes web app.

By default, if you specify more than one kind of geography here then the application assumes that you want to "and" the selections, keeping only areas that satisfy all criteria. For example, if you specified three counties and a metro area, you would only get data based on blocks that were in both the counties and the metro area (i.e. the intersection of the selected areas.) To override this default and choose geographies that satisfy any (rather than all) of your select criteria -- click here:

All selections made below are in addition to the state-level or distance-based filtering which you specify

County codes . Enter 5-digit FIPS county codes with leading zeroes separated by blanks. You may enter 3-digit codes if you selected only one state. Your output will be limited to the counties specified.
Examples:

Metro Area codes. Enter 4-digit FIPS metro area codes with leading zeroes separated by blanks. MSA, CMSA and PMSA codes may be used (4-digit only). The 2000 definitions will be used. Your output will be limited to the metro areas specified. New England NECMA codes can not be used.
A code of 9999 can be entered to select non-metro areas (alone or as part of a list of metro area codes). Enter -9999 to specify that you want to exclude all non-metro areas. The -9999 code must be entered as the entire value for the list.

Alternatively, you can enter 5-digit Core-Based Statistical Area codes here to filter based on these more current and more inclusive (they include micropolitan as well as metropolitan) areas. You can use the special value -99999 to select only those places which are outside any metro or micropolitan area. See our Metro Pops report (for the larger Metropolitan SA's) or Micro Pops report (for the smaller Micropolitan SA's)to obtain these codes. (Or, you can also use Cure for the Common Codes). Examples:

Urbanized Area and Urban Clusters . Enter 5-digit FIPS urbanized area or urban cluster codes with leading zeroes separated by blanks. Your output will be limited to the UA/UC areas (which are mutually exclusive) specified. Enter -9999 to specify that you want to exclude all non-urban (i.e., rural) areas. The -9999 code must be entered as the entire value for the list. Examples:

Place codes. Enter 7-digit FIPS place codes with leading zeroes separated by blanks. You can enter 5-digit codes if only one state has been selected. Your output will be limited to the official city limits of these cities as of the 2000 census.
Enter a value of -9999 to indicate that you want to exclude all areas that are not inside any place. You will get all areas that are either incorporated or within a Census Designated Place.
Examples:

Point-and-Distance Options

Specify a point (location) and distance to be used as filter:
Value for radius of Circle or radius of largest Ring: (In miles, unless you check here to specify kilometers.)
See just below for links to help find coordinates. If you just want to do a test you can enter the values 38.7070 & 90.3127 which are the coordinates of UMSL in St Louis county, MO.
Coordinates of Point:     degrees latitude,     degrees longitude.
Label of Point:   (optional)
Define Ring criteria (if Concentric ring geocode selected above) specifying only one of the following two options:
  1. # of equi-distant rings (integer value 1 to 10). Radius specified above will be divided by this to derive width of each Ring.
    -OR-
  2. Specify your own custom list of up to 10 ring radii values in ascending order (values must be greater than zero, may be fractional, and largest should equal the radius of the Circle specified above):
    #1 #2 #3 #4 #5 #6 #7 #8 #9 #10
Note: A ring is identified on output files by its outer radius. E.g., a ring of 4 to 8 miles will have code 8.

Links are provided here to facilitate obtaining coordinates for your location. These links have been known to disappear or change the rules regarding free access. Please send a note if you find a link that no longer works.

Note: If you specify a lat-long location the variable "distance" will be added to your output. This requires that weighted centroids also be calculated (set automatically). The "distance" variable will be between the weighted centroid and the specified Point. If you specify Ring Pseudo-Geocodes then distance and weighted centroid values will not be calculated or stored (because weighted centroids of donuts are misleading).

Bounding Box Filter Options

If you want to limit processing to blocks with center points that fall in a specified rectangular area you can enter the coordinates for such a "bounding box" here.

Define the "bounding box" coordinates in decimal degrees:
Northern-most Latitude
 Southern-most Latitude
Western-most Longitude
 Eastern-most Longitude


Internal use only (ignore):

Please direct all questions and comments to John Blodgett at OSEDA.