| Title | Municipal Boundaries | | Date | 12/20/2019 | | Date Type | publication | | Edition | 2008 | | Organization Name | U.S. Department of Commerce, U.S. Census Bureau, Geography Division | |
Role
| originator | |
Presentation Form
| mapDigital | |
Abstract
| This is an ESRI shapefile of State-wide municipal boundaries for Oklahoma State. Boundaries are based on information provided by the Oklahoma Tax Commission. | |
Purpose
| US Census TIGER 2010 Based Municipal Boundaries for Oklahoma, created by the Center for Spatial Analysis (University of Oklahoma).
This municipal boundaries shapefile was prepared by Center for Spatial Analysis at the University of Oklahoma in cooperation with the Oklahoma Tax Commission for the purpose of capturing data related to municipal boundaries for all counties in the State. | |
Status
| completed | |
Descriptive Keywords
| Census Designated Place, State or equivalent entity, Town, CDP, City, Cities, Village, Administrative Units, Polygon, 40, State or Equivalent Entity, United States, OK, Oklahoma, U.S., Downloadable Data | |
Access Constraints
| otherRestrictions | |
Other Constraints
| access constraints: None | |
Use Constraints
| otherRestrictions | |
Other Constraints
| | |
Language
| | |
Topic Category Code
| boundaries | |
Geographic Bounding Box
| | North bound latitude | | | 36.999378 | | | West bound longitude | | East bound longitude | | -102.52186 | | -94.432245 | | South bound latitude | | | 33.765786 | |
|
| |
Distribution Information
| | Name | TGRSHP (compressed) | | Version | unknown | | Individual Name | | | Organization Name | Office of Geographic Information | | Position Name | | | Voice | 405-521-4813 | | Facsimile | 405-521-6686 | | Address | 405-521-6686 | | City | Oklahoma City | | State | OK | | Postal Code | 73105 | | Country | United States | | Electronic mail address | mike.sharp@conservation.ok.gov | | Hours of Service | | | Role | pointOfContact | | Fees | The online copy of the TIGER/Line files may be accessed without charge. | | Ordering Instructions | To obtain more information about ordering TIGER/Line shapefiles visit http://www.census.gov/geo/www/tiger | | Transfer Size | 3.715 |
|
| |
Spatial Representation Information
| | Geometric Object Type | surface | | Geometric Object Count | 693 |
|
| |
Reference System
| | Code | Federal Information Processing Standards (FIPS), ANSI, and feature names. |
|
| |
Data Quality
| | Evaluation Method | The Census Bureau performed automated tests to ensure logical consistency and limits of shapefiles. Segments making up the outer and inner boundaries of a polygon tie end-to-end to completely enclose the area. All polygons are tested for closure. The Census Bureau uses its internally developed geographic update system to enhance and modify spatial and attribute data in the Census MAF/TIGER database. Standard geographic codes, such as FIPS codes for states, counties, municipalities, county subdivisions, places, American Indian/Alaska Native/Native Hawaiian areas, and congressional districts are used when encoding spatial entities. The Census Bureau performed spatial data tests for logical consistency of the codes during the compilation of the original Census MAF/TIGER database files. Most of the codes for geographic entities except states, counties, urban areas, Core Based Statistical Areas (CBSAs), American Indian Areas (AIAs), and congressional districts were provided to the Census Bureau by the USGS, the agency responsible for maintaining FIPS 55. Feature attribute information has been examined but has not been fully tested for consistency. For the TIGER/Line Shapefiles, the Point and Vector Object Count for the G-polygon SDTS Point and Vector Object Type reflects the number of records in the shapefile attribute table. For multi-polygon features, only one attribute record exists for each multi-polygon rather than one attribute record per individual G-polygon component of the multi-polygon feature. TIGER/Line Shapefile multi-polygons are an exception to the G-polygon object type classification. Therefore, when multi-polygons exist in a shapefile, the object count will be less than the actual number of G-polygons. | | Topological Consistency | | | Absolute Positional Accuracy | | | Attribute Accuracy | Accurate against Federal Information Processing Standards (FIPS), FIPS Publication 6-4, and FIPS-55 at the 100% level for the codes and base names. The remaining attribute information has been examined but has not been fully tested for accuracy. | | Process Step | TIGER/Line Shapefiles are extracted from the Census MAF/TIGER database by nation, state, county, and entity. Census MAF/TIGER data for the nation, state, county, and entity are then distributed among 58 shapefiles each containing attributes for line, polygon, or landmark geographic data. | | Source | The selected geographic and cartographic information (line segments) are derived from the U.S. Census Bureau's Master Address File Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. | | Responsible Party | U.S. Department of Commerce, U.S. Census Bureau, Geography Division | | Role | originator |
|
| |
Metadata
| | Metadata Standard | ISO 19115:2003/19139 | | Version | 1.0 |
|
|
|
