| Description | |||
| Abstract: Represents 2000 Census Tracts. It is the larger of the geographical units (Blocks, Block Groups, Tracts) for which the bureau publishes sample data, i.e data which is only collected from a fraction of all households. | |||
| Purpose: The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of decennial census data. Census Tract level data from the 2000 Census is mapped, analyzed, and compared to prior and subsequent Census years' Tract data in order to determine trends and patterns of change in the City of Richmond's population. This GIS layer is used to relate properties (hence addresses) to the correlating census tract for use in the City's data warehousing and central address systems. | |||
| Supplemental Information: Census tracts are small, relatively permanent statistical subdivisions of a county delineated by local participants as part of the U.S. Census Bureau's Participant Statistical Areas Program. The U.S. Census Bureau delineated census tracts in situations where no local participant existed or where local or tribal governments declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of decennial census data. This is the first decennial census for which the entire United States is covered by census tracts. For the 1990 census, some counties had census tracts and others had block numbering areas (BNAs). In preparation for Census 2000, all BNAs were replaced by census tracts, which may or may not cover the same areas. Census tracts generally have between 1,500 and 8,000 people, with an optimum size of 4,000 people. Counties with fewer people have a single census tract.) When first delineated, census tracts are designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Census tract boundaries are delineated with the intention of being maintained over many decades so that statistical comparisons can be made from decennial census to decennial census. However, physical changes in street patterns caused by highway construction, new developments, and so forth, may require occasional boundary revisions. In addition, census tracts occasionally are split due to population growth or combined as a result of substantial population decline. Census tracts are identified by a four-digit basic number and may have a two-digit numeric suffix; or example, 6059.02. The decimal point separating the four-digit basic tract number from the two-digit suffix is shown in the printed reports and on census maps. In computer-readable files, the decimal point is implied. Many census tracts do not have a suffix; in such cases, the suffix field is either left blank or is zero-filled. Leading zeros in a census tract number (for example, 002502) are shown only in computer-readable files. Census tract suffixes may range from .01 to .98. For the 1990 census, the .99 suffix was reserved for census tracts/block numbering areas (BNAs) that contained only crews-of-vessels population; for Census 2000, the crews-of-vessels population is part of the related census tract. Census tract numbers range from 1 to 9999 and are unique within a county or statistically equivalent entity. The U.S. Census Bureau reserves the basic census tract numbers 9400 to 9499 for census tracts delineated within or to encompass American Indian reservations and off-reservation trust lands that exist in multiple states or counties. The number 0000 in computer-readable files identifies a census tract delineated to provide complete coverage of water area in territorial seas and the Great Lakes. US Census Bureau: http://www.census.gov/ Census Tracts (US Census Bureau): http://www.census.gov/geo/www/cob/tr_metadata.html | |||
| Contact | |||
| Custodian: | John Taylor | ||
| Department: | Planning and Development Review | ||
| Position: | Planner II | ||
| Address: | 900 E Broad St, Rm 510 | ||
| City: | Richmond | ||
| State: | Virginia | ||
| Zip Code: | 23219 | ||
| Email: | John.W.Taylor@richmondgov.com | ||
| Time Period of Content | |||
| Date: | REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground. | ||
| Status | |||
| Progress: | Complete | ||
| Update Frequency: | REQUIRED: The frequency with which changes and additions are made to the data set after the initial data set is completed. | ||
| Spatial Domain | |||
| West Coordinate: | -77.602332 | ||
| East Coordinate: | -77.384518 | ||
| North Coordinate: | 37.604067 | ||
| South Coordinate: | 37.446257 | ||
| Spatial Data Information | |||
| Data Type: | vector digital data | ||
| Data Format: | SDE Feature Class | ||
| Data Projection: | Lambert Conformal Conic | ||
| Access and Usage Information | |||
| Access Constraints: | none | ||
| Use Constraints: | All GIS layers and datasets are owned by the City of Richmond and cannot be modified, re-used, re-distributed, and/or re-sold without a sub-licensing agreement. All guarantees of validity expire once a dataset leaves the City of Richmond firewall or physical premises. Acknowledgement of the City of Richmond GIS would be appreciated in products derived from these data. | ||
| Entity and Attribute Information | |||
| Entity Name: | vector.ric.area_Tract2000 | ||
| Entity Type: | Feature Class | ||
| Entity Count: | 65 | ||