| Title | Oklahoma Correctional Institutions | | Date | 2009-12-30 | | Date Type | publication | | Edition | 4th Quarter 2009 | | Organization Name | TechniGraphics, Inc. | |
Role
| originator | |
Presentation Form
| mapDigital | |
Abstract
| Jails and Prisons (Correctional Institutions). The Jails and Prisons sub-layer is part of the Emergency Law Enforcement Sector and the Critical Infrastructure Category. A Jail or Prison consists of any facility or location where individuals are regularly and lawfully detained against their will. This includes Federal and State prisons, local jails, and juvenile detention facilities, as well as law enforcement temporary holding facilities. Work camps, including camps operated seasonally, are included if they otherwise meet the definition. A Federal Prison is a facility operated by the Federal Bureau of Prisons for the incarceration of individuals. A State Prison is a facility operated by a state, commonwealth, or territory of the US for the incarceration of individuals for a term usually longer than 1 year. A Juvenile Detention Facility is a facility for the incarceration of those who have not yet reached the age of majority (usually 18 years). A Local Jail is a locally administered facility that holds inmates beyond arraignment (usually 72 hours) and is staffed by municipal or county employees. A temporary holding facility, sometimes referred to as a "police lock up" or "drunk tank", is a facility used to detain people prior to arraignment. Locations that are administrative offices only are excluded from the dataset. This definition of Jails is consistent with that used by the Department of Justice (DOJ) in their "National Jail Census", with the exception of "temporary holding facilities", which the DOJ excludes. Locations which function primarily as law enforcement offices are included in this dataset if they have holding cells. If the facility is enclosed with a fence, wall, or structure with a gate around the buildings only, the locations were depicted as "on entity" at the center of the facility. If the facility's buildings are not enclosed, the locations were depicted as "on entity" on the main building or "block face" on the correct street segment. Personal homes, administrative offices, and temporary locations are intended to be excluded from this dataset; however, some personal homes of constables are included due to the fact that many constables work out of their homes. TGS has made a concerted effort to include all correctional institutions. This dataset includes non license restricted data from the following federal agencies: Bureau of Indian Affairs; Bureau of Reclamation; U.S. Park Police; Federal Bureau of Prisons; Bureau of Alcohol, Tobacco, Firearms and Explosives; U.S. Marshals Service; U.S. Fish and Wildlife Service; National Park Service; U.S. Immigration and Customs Enforcement; and U.S. Customs and Border Protection. This dataset is comprised completely of license free data. The Law Enforcement dataset and the Correctional Institutions dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. With the merge of the Law Enforcement and the Correctional Institutions datasets, NAICS Codes & Descriptions were assigned based on the facility's main function which was determined by the entity's name, facility type, web research, and state supplied data. In instances where the entity's primary function is both law enforcement and corrections, the NAICS Codes and Descriptions are assigned based on the dataset in which the record is located (i.e., a facility that serves as both a Sheriff's Office and as a jail is designated as [NAICSDESCR]="SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)" in the Law Enforcement layer and as [NAICSDESCR]="JAILS (EXCEPT PRIVATE OPERATION OF)" in the Correctional Institutions layer). Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard fields that TGS populated. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on the values in this field, the oldest record dates from 04/07/2005 and the newest record dates from 10/16/2009 | |
Purpose
| Homeland Security Use Cases: Use cases describe how the data may be used and help to define and clarify requirements. 1. A threat to cause the mass release of prisoners by an outside terrorist group has been identified. Steps need to be taken to provide extra security at the targeted prisons. 2. Massive civil unrest has resulted in a large number of arrests. Appropriate space is needed outside of the immediate area to house the arrested individuals. 3. Massive civil unrest has resulted in a large number of arrests. A "holding camp" has been established to hold those arrested. Trained security guards are needed to staff the holding camp. 4. A disaster has caused the need for an emergency labor force (e.g., sandbagging during a flood) and prisoners may fill that need. 5. Inmates may need to be evacuated, or appropriate steps may need to be taken at a prison to protect the inmates and to ensure that a disaster does not present an opportunity for escape. | |
Status
| completed | |
Descriptive Keywords
| United States. Bureau of Reclamation., United States marshals., United States. Bureau of Indian Affairs., U.S. Customs and Border Protection., Police., Police, State., United States. Bureau of Alcohol, Tobacco, Firearms, and Explosives, Traffic police., Secret service., Indian reservation police, Transit police, Prisons., Peace officers, Constables, Sheriffs, Police stations, United States. National Park Service., Jails, Community policing., Campus police, U.S. Immigration and Customs Enforcement., Juvenile detention, Drug enforcement agents, U.S. Fish and Wildlife Service., Correctional institutions., Railroad police, Military police, Law enforcement., Border patrols., School police, Airport police, Work camps, Criminal investigation., Fire marshals, Administrative Units, Oklahoma | |
Access Constraints
| otherRestrictions | |
Other Constraints
| access constraints: None | |
Use Constraints
| otherRestrictions | |
Other Constraints
| | |
Language
| | |
Topic Category Code
| structure | |
Geographic Bounding Box
| | North bound latitude | | | 36.881514 | | | West bound longitude | | East bound longitude | | -102.513166 | | -94.436459 | | South bound latitude | | | 33.89275 | |
|
| |
Distribution Information
| | Name | | | Version | | | Individual Name | | | Organization Name | | | Position Name | | | Voice | | | Facsimile | | | Address | | | City | | | State | | | Postal Code | | | Country | | | Electronic mail address | | | Hours of Service | | | Role | | | Fees | | | Ordering Instructions | | | Transfer Size | |
|
| |
Spatial Representation Information
| | Geometric Object Type | point | | Geometric Object Count | 237 |
|
| | |
Data Quality
| | Evaluation Method | | | Topological Consistency | | | Absolute Positional Accuracy | The geographic location of entities was verified to be correct relative to the street vendor and version indicated by the [ST_VENDOR] and [ST_VERSION] fields. The horizontal accuracy is indicated by the [GEOPREC] field. A value of "BLOCKFACE" indicates the entity was geocoded on the correct street segment (block) and correct side of the street. A value of "ONENTITY" indicates that the location is on the entity's facility, as determined by USGS DOQQ imagery, and that it is on the correct street segment (block) and correct side of the street. Entities that are part of a larger institution (e.g., University Campus or Military Base) with "BLOCKFACE" precision may be located at the main entrance to the larger institution. Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. | | Attribute Accuracy | For entities that were contacted, the name, address, city, state, and five (5) digit zip codes were verified to be correct as of the date indicated by the [CONTDATE] field. The existence of the entity was also verified, as well as whether or not it met the criteria for inclusion in this dataset. Four (4) digit zip code extensions were derived from USPS (United States Postal Service) data and were not verified. ID Check: The [ID] field is not blank and each of its values is unique. Coordinate Check: Coordinates are not null or zero and the [X] and [Y] fields match the shape. Basic Address Check: Physical addresses were verified to be non blank and to not be a "PO Box", "General Delivery", "Highway Contract", or "Rural Route" address. Highway Address without Type Check: Physical addresses containing the word "Highway" or "Route" were verified to also contain a type designator such as "State", "US", or "County", if one actually exists for the highway or route. These type designators are often missing from addresses, leading to confusion if more than one "Highway" of the given number exists in an area. Basic Name Check: Entity name is not blank, is not the same as entity city, and has a minimum of two (2) characters. Name does not contain punctuation characters that can interfere with database operations, such as " (quote) and * (asterisk). City Check: Entity's [CITY] field is not blank, and entity is located within 25 miles of its tabular city as found in the NAVTEQ Named Places reference file. State Check: The entity is located within its tabular state. County Check: The entity is located within its tabular county. FIPS Check: The tabular FIPS Code matches the entity's tabular county and tabular state. County in Name vs. Geographic Location Check: If an entity's [NAME] field contains the word "county" or "co", the same county value should also be in the entity's [COUNTY] field. Basic Phone Check: All phone numbers (including the area code) are ten (10) numeric digits. Alphabetic characters have been converted to the corresponding numeric digit. NPA_NXX Check: Area codes (sometimes called "Number Planning Areas", or NPA's) and central office codes (sometimes known as exchanges, or NXX's) were validated against data from the North American Number Planning Administration (NANPA). In some cases, NPA-NXX combinations did not show up in the NANPA data but were verified to work. Area Code Distance Check: The entity's area code (NPA) is valid, and the entity is not more than 25 miles from its area code boundary, as defined by data from the North American Number Planning Administration (NANPA), unless TGS has previously verified that the phone number rings to a headquarters location or otherwise does not ring to the entity's location. Zip Code Check: The entity's zip code is five (5) or nine (9) numeric digits, is listed in the postal database, is in the same state as indicated by the entity's [STATE] value, and is not a PO Box only zip code. Zip City Check: The entity's zip code and its city were verified to match according to the USPS Address Information System (AIS). Zip Code Distance Check: The entity is located within 25 miles of its zip code boundary, as defined by the U.S. Census Bureau's 1999 Zip Code file. NAICS Code Check: The NAICS field is not blank, the NAICS Code is one of the accepted codes for this layer, the NAICS Description is an acceptable Index Entry for the NAICS Code, and certain key words in the entity name do not conflict with the NAICS Code. Collocation Check: Entities with different addresses must not share the exact same geospatial location. Geographic Spell Check: Words that appear in the entity name were checked against a standard English word list (and Spanish word list for entities in Puerto Rico). Words not appearing in these standard word lists were then checked against names appearing in the Geographic Names Information System (GNIS) of geographic features that are located within 25 miles of the entity. Proper names were manually reviewed for correct spelling. Supplied Coordinates Distance Check: Entity is located within 3 miles of coordinates supplied by the original source. | | Process Step | 1) The Correctional Institutions dataset and the Law Enforcement dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. 2) Entities were processed to determine or verify their name, physical address, city, state, five (5) digit zip code, phone number, and geospatial location. Entities that were contacted were also asked if they provided law enforcement services, correctional institution services, or both. Entities not located on military bases were contacted and asked to describe their location relative to landmarks in reference data (mainly streets) and features visible in ortho imagery. A phone number was not available for some entities, so their information was verified using other verbal contacts made through a telephone call. 3) Due to a request made by the Department of Defense, TGS made every effort to not contact military bases starting 03/27/2007 and ending 05/28/2008. During this time, entities located on military bases were verified through alternate resources, such as maps and ortho imagery. These records have not been contacted by TGS, and therefore, do not have directions. 4) All text fields were set to all upper case. 5) Leading and trailing spaces were trimmed from all text fields. 6) Non printable and diacritic characters were removed from all text fields. | | Source | The basic attribution (name, address, city, state, zip code, and telephone number) came from this dataset unless the entity was updated by TGS during Q108 processing. | | Responsible Party | TechniGraphics, Inc. | | Role | originator |
|
| |
Metadata
| | Metadata Standard | ISO 19115:2003/19139 | | Version | 1.0 |
|
|
|
