North Carolina Law Enforcement 2009 Q4

Frequently-anticipated questions:

• What does this data set describe?
  1. How should this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  3. What similar or related data should the user be aware of?
• How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

What does this data set describe?

1. How should this data set be cited?

   TechniGraphics, Inc., 20091230, North Carolina Law Enforcement 2009 Q4.

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -84.091716

   East_Bounding_Coordinate: -75.532920

   North_Bounding_Coordinate: 36.528787

   South_Bounding_Coordinate: 33.858286

3. What does it look like?

4. Does the data set describe conditions during a particular time period?

   Beginning_Date: 10-Aug-2006

   Ending_Date: 22-Oct-2009

   Currentness_Reference: ground condition

5. What is the general form of this data set?

   Geospatial_Data_Presentation_Form: vector digital data

6. How does the data set represent geographic features?
   1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • Entity point (830)

   2. What coordinate system is used to represent geographic features?

      Grid_Coordinate_System_Name: State Plane Coordinate System 1983

      State_Plane_Coordinate_System:

      SPCS_Zone_Identifier: 3200

      Lambert_Conformal_Conic:

      Standard_Parallel: 34.333333

      Standard_Parallel: 36.166667

      Longitude_of_Central_Meridian: -79.000000

      Latitude_of_Projection_Origin: 33.750000

      False_Easting: 609601.220000

      False_Northing: 0.000000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 1
      Ordinates (y-coordinates) are specified to the nearest 1
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 1980.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298.257.
      

7. How does the data set describe geographic features?

   Law Enforcement Locations in North Carolina

   Any location where sworn officers of a law enforcement agency are regularly based or stationed.
   Law enforcement agencies "are publicly funded and employ at least one full-time or part-time sworn officer with general arrest powers". This is the definition used by the US Department of Justice - Bureau of Justice Statistics (DOJ-BJS) for their Law Enforcement Management and Administrative Statistics (LEMAS) survey. Although LEMAS only includes non Federal Agencies, this dataset includes locations for federal, state, local, and special jurisdiction law enforcement agencies.
   Law enforcement agencies include, but are not limited to, municipal police, county sheriffs, state police, school police, park police, railroad police, federal law enforcement agencies, departments within non law enforcement federal agencies charged with law enforcement (e.g., US Postal Inspectors), and cross jurisdictional authorities (e.g., Port Authority Police).
   In general, the requirements and training for becoming a sworn law enforcement officer are set by each state. Law Enforcement agencies themselves are not chartered or licensed by their state. County, city, and other government authorities within each state are usually empowered by their state law to setup or disband Law Enforcement agencies. Generally, sworn Law Enforcement officers must report which agency they are employed by to the state. (Source: TGS)

   FID

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   SHAPE

   Feature geometry. (Source: ESRI)

   Coordinates defining the features.

   ID

   Unique identifier for feature. (Source: TGS)

   Text

   SECCLASS

   Security classification of feature. (Source: TGS)

   Value	Definition
   UNCLASSIFIED	Entity is unclassified.

   NAME

   Name of entity. (Source: TGS)

   Text

   TELEPHONE

   Ten (10) digit telephone number for entity formatted as nnn-nnn-nnnn. (Source: TGS)

   Phone numbers formatted as nnn-nnn-nnnn. Only numeric digits are used. The area code and exchange must form a valid combination. A list of valid area code and exchange combinations can be obtained from <http://www.nanpa.com>.

   ADDRESS

   Physical street address for entity. "PO Box", "General Delivery", "Rural Route", and "Highway Contract" addresses are not considered physical addresses and should not appear in this field. Some areas do not have regular city style addressing, so entities in those areas may not have a street number. In such cases, the name of the road on which they are located is listed in this field. Some rural areas may not have named roads. In these rare cases, this field will be blank. (Source: TGS)

   Text

   ADDRESS2

   Location within physical address, e.g., floor, suite, building. (Source: TGS)

   Text

   CITY

   The name of the city associated with the entity's physical address. For physical addresses that the U.S. Postal Service (USPS) delivers to, this should be a "city" acceptable to the USPS as defined in their Address Information System (AIS). Sometimes the USPS does not deliver mail to a physical address but recognizes the location (i.e., they list the location as "undeliverable"). The cities associated with these locations are acceptable. In some cases, the USPS does not recognize individual physical addresses in a city, rather, they list the city as having "General Delivery". In these cases, the city and associated zip code are acceptable (the entity's [ADDRESS] field will contain a street address, not "general delivery"). The entity may not actually be located within the city limits of the "city" specified in its [CITY] field. Instead, it may actually be located within the city limits of another city. In some cases, the "city" that appears in this field may not even be a city in an administrative sense, but it is still an acceptable "city" to the USPS. An example of this is "Notre Dame, IN". There is no city in Indiana called "Notre Dame", but this is considered an acceptable city by the USPS for any delivery going to the University of Notre Dame which is actually located in the city of South Bend. "Notre Dame", like most USPS cities, is an easily recognized place, and it gives the user of the data a good general idea of where the entity is located (if the entity is located in a small municipality, the USPS "city" may be more recognizable than the name of the municipality), and it would be part of the address one would use to send a shipment to the entity's location. Using the USPS acceptable "city" also allows someone to do a logical consistency check between the zip code and the city by using the USPS AIS.
   Sometimes an entity may report a city that is not accepted by the USPS, and although TGS has tried to replace those cities with an acceptable alternative, some of them may remain in this dataset. (Source: TGS)

   Text

   STATE

   Two (2) character abbreviation for state associated with the entity's physical address. In almost all cases, this is the same as the state where the entity has been depicted geospatially. However, there are cases, particularly where an entity is part of a larger facility that cuts across state lines, where the entity's location may be depicted in a state other than the one indicated in this field. Also, the state in which an entity appears to be located may change depending on the scale of the state boundary theme being used. (Source: TGS)

   Formal codeset
   Codeset Name:	Official USPS Abbreviations - State Abbreviations
   Codeset Source:	United States Postal Service <http://www.usps.com/ncsc/lookups/usps_abbreviations.html>

   ZIP

   Five (5) digit USPS zip code for entity's physical location. (Source: TGS)

   Formal codeset
   Codeset Name:	USPS Address Information System - Domain is further restricted by only allowing physical (non PO Box) zip codes.
   Codeset Source:	United States Postal Service

   ZIPP4

   Four (4) digit USPS zip code extension. These values are automatically assigned using the entity's physical address and USPS address information system (AIS) data. (Source: TGS)

   Formal codeset
   Codeset Name:	USPS Address Information System (AIS) - ZIP9
   Codeset Source:	United States Postal Service

   COUNTY

   County name where entity is located. (Source: TGS)

   Formal codeset
   Codeset Name:	Geographic Names Information System (GNIS)
   Codeset Source:	US Department of the Interior - US Geologic Survey

   FIPS

   Five (5) digit FIPS (Federal Information Processing Standards) Code for the County where entity is located. The first two (2) digits represent the state and the last three (3) digits identify the county within the state. (Source: TGS)

   Formal codeset
   Codeset Name:	Federal Information Processing Standards Publications - Counties and Equivalent Entities of the U.S., Its Possessions, and Associated Areas.
   Codeset Source:	National Institute of Standards and Technology (NIST) <http://www.itl.nist.gov/fipspubs/co-codes/states.txt>

   DIRECTIONS

   Directions to entity location, or a description of the entity's location or status. (Source: TGS)

   Text

   EMERGTITLE

   Title of person or name of office for emergency point of contact. (Source: TGS)

   Text

   EMERGTEL

   Ten (10) digit telephone number of emergency point of contact formatted as nnn-nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit. (Source: TGS)

   Phone numbers, including area code, formatted as nnn-nnn-nnnn. A list of valid area code and exchange combinations can be found at <http://www.nanpa.com>

   EMERGEXT

   Telephone extension for emergency point of contact. (Source: TGS)

   Text

   CONTDATE

   Date entity was contacted by TGS. (Source: TGS)

   Date

   CONTHOW

   Method by which entity was contacted. (Source: TGS)

   Value	Definition
   ALT REF	Geospatial reference information obtained from local authorities, e.g., downloadable parcel maps, 911 streets, and shape files.
   FAX	Entity was contacted by fax.
   MAIL	Entity was contacted by mail.
   PHONE	Entity was contacted by phone.
   <BLANK>	Entity has not been contacted by TGS.

   GEODATE

   Date entity was geocoded by TGS. (Source: TGS)

   Date

   GEOHOW

   Method by which entity was geocoded. (Source: TGS)

   Value	Definition
   ADJUSTED	Entity was shifted by TGS to an updated set of NAVTEQ streets. This only applies if the entity was manually geocoded by TGS to a previous version of NAVTEQ streets.
   MANUAL	Entity was manually geocoded.

   NAICSCODE

   NAICS (North American Industry Classification System) Code for entity. NAICS Codes (and NAICS Descriptions) have been assigned based upon the entity's primary function, regardless of if that is the function that qualified it to be included in this dataset. (Source: TGS)

   Formal codeset
   Codeset Name:	North American Industry Classification System (NAICS 2007)
   Codeset Source:	US Census Bureau - <http://www.census.gov/epcd/www/naics.html>

   NAICSDESCR

   NAICS (North American Industry Classification System) Description for entity. The "Index Entries" that appear on the NAICS webpage (<http://www.census.gov/epcd/www/naics.html>) are being used to populate this attribute as opposed to the "NAICS Title". While there is a one to one correspondence between NAICS Codes and "NAICS Titles", there is a one to many relationship between NAICS Codes and the "Index Entries". By using the "Index Entries", we have placed the entities that make up this layer into more specific categories; however, the user of this data should be aware that this was not the intended purpose of these "Index Entries". The "Index Entries" were intended as a way to search the NAICS database and as a way of enumerating ways in which establishments falling under the given NAICS Code may be named. Thus, there are often two or more "Index Entries" that are synonyms, for example: "Prisons" and "Penitentiaries". In cases like this, we have standardized on one "Index Entry". NAICS Descriptions (and NAICS Codes) have been assigned based upon the entity's primary function, regardless of the function that qualified it to be included in this dataset. (Source: TGS)

   Value	Definition
   ALCOHOL, TOBACCO, AND FIREARMS CONTROL	ALCOHOL, TOBACCO, AND FIREARMS CONTROL-[NAICS Code 922120]: Entities that are involved in the specific sector of enforcing federal laws concerning alcohol, tobacco products, firearms, and explosives are classified under this description.
   BOOT CAMPS FOR DELINQUENT YOUTH	BOOT CAMPS FOR DELINQUENT YOUTH - [NAICS Code 623990]: Entity is a correctional camp for juveniles. In such facilities, the nature of the correctional / reform methods are similar to those used in military boot camps or otherwise involve outdoor labor and/or intense exercise. These entities may be seasonal in nature.
   BOYS' AND GIRLS' RESIDENTIAL FACILITIES (E.G., HOMES, RANCHES, VILLAGES)	BOYS' AND GIRLS' RESIDENTIAL FACILITIES (E.G., HOMES, RANCHES, VILLAGES) - [NAICS Code 623990]: Entity is a NON CORRECTIONAL facility for juveniles. In other words, a facility that houses (and perhaps detains) problematic juveniles that have not necessarily been convicted of, or charged with, a crime.
   CORRECTIONAL FACILITY OPERATION ON A CONTRACT OR FEE BASIS	CORRECTIONAL FACILITY OPERATION ON A CONTRACT OR FEE BASIS - [NAICS Code 561210]: Entity is a correctional facility, other than a jail, operated by a private firm under contract to a government agency.
   CORRECTIONAL INSTITUTIONS	CORRECTIONAL INSTITUTIONS - [NAICS Code 922140]: Entity is a correctional institution, but we were unable to determine if it was a jail or a prison. This includes juvenile detention centers if the primary purpose of the center is corrections. Juvenile facilities that deal with problematic youth not convicted of a crime have been categorized under BOYS' and GIRLS' RESIDENTIAL FACTILITIES (E.G., HOMES, RANCHES, VILLAGES) - [NAICS Code 623990]
   CRIMINAL INVESTIGATION OFFICES, GOVERNMENT	CRIMINAL INVESTIGATION OFFICES, GOVERNMENT-[NAICS Code 922120]: Entities that are involved in the specific sector of criminal investigations are classified under this description.
   DEA (DRUG ENFORCEMENT ADMINISTRATION)	DEA (DRUG ENFORCEMENT ADMINISTRATION)-[NAICS Code 922120]: Entities that are involved in the specific sector of enforcing laws and regulations governing narcotics and controlled substances at the federal level are classified under this description, unless they are primarily involved at the state and local levels.
   DRUG ENFORCEMENT AGENCIES AND OFFICES	DRUG ENFORCEMENT AGENCIES AND OFFICES-[NAICS Code 922120]: Entities that are involved in the specific sector of enforcing laws and regulations governing narcotics and controlled substances at the local and state level are classified under this description, unless they are primarily involved at the federal level.
   FEDERAL BUREAU OF INVESTIGATION (FBI)	FEDERAL BUREAU OF INVESTIGATION (FBI)-[NAICS Code 922120]: Entities that are involved in the specific sector of enforcing federal laws and investigations are classified under this description, unless they are primarily involved in federal police services.
   FEDERAL POLICE SERVICES	FEDERAL POLICE SERVICES-[NAICS Code 922120]: Entities that are involved in the specific sector of federal police services are classified under this description, unless they are primarily involved in federal investigations.
   FIRE MARSHALS' OFFICES	FIRE MARSHALS' OFFICES-[NAICS Code 922160]: Entities that are primarily engaged in fire fighting and other related fire protection activities are classified under this description.
   HIGHWAY PATROLS, POLICE	HIGHWAY PATROLS, POLICE-[NAICS Code 922120]: Entities that are involved in the specific sector of patrolling public highways are classified under this description.
   HONOR CAMPS, CORRECTIONAL	HONOR CAMPS, CORRECTIONAL-[NAICS Code 922140]: Entity is a work camp which houses inmates whose primary duties involve outdoor labor. Entities are also sometimes known as a "Conservation Camp".
   HOUSING POLICE, GOVERNMENT	HOUSING POLICE, GOVERNMENT-[NAICS Code 922120]: Entities that are involved in the specific sector of securing and delivering police services to people using public housing are classified under this description.
   IMMIGRATION SERVICES	IMMIGRATION SERVICES-[NAICS Code 928120]: Entities that are responsible for the specific sector of the administration of immigration and naturalization adjudication functions and establishing immigration services, policies, and priorities are classified under this description.
   JAILS (EXCEPT PRIVATE OPERATION OF)	JAILS (EXCEPT PRIVATE OPERATION OF) - [NAICS Code 922140]: Entity is a jail. A jail is a facility that holds inmates beyond arraignment (usually 72 hours) and prior to sentencing. Jails may also hold inmates serving short sentences (up to a year) for minor crimes. This includes locally administered jails that are staffed by municipal or county employees. This also includes regional jails operated for two or more jail authorities and Federal Bureau of Prisons facilities that function as jails. The above definition is consistent with that used by the Bureau of Justice Statistics (BJS) Census of Jails (<http://www.ojp.usdoj.gov/bjs/pub/pdf/cj99.pdf>), except that the BJS includes "private jails operating under contract to governments". Also included under this category are temporary holding facilities, sometimes referred to as "police lock ups" or "drunk tanks". Temporary holding facilities are used to detain people prior to arraignment. Although these are included under this category, the BJS excludes them from their Census of Jails.
   MARSHALS' OFFICES	MARSHALS' OFFICES-[NAICS Code 922120]: Entities that are responsible for the specific sector of providing protection for the federal judiciary, transporting federal prisoners, protecting endangered federal witnesses and managing assets seized from criminal enterprises are classified under this description.
   MILITARY POLICE	MILITARY POLICE-[NAICS Code 928110]: Entities that are involved in the specific sector of the Armed Forces, including the National Guard, primarily engaged in national security and related activities are classified under this description.
   PARK POLICE	PARK POLICE-[NAICS Code 922120]: Entities that are involved in the specific sector of protecting the national, state, and local parks are classified under this description.
   POLICE AND FIRE DEPARTMENTS, COMBINED	POLICE AND FIRE DEPARTMENTS, COMBINED-[NAICS Code 922120]: Entities that are involved in the specific sector of both police and fire protection are classified under this description, unless they are primarily involved in the prevention and/or investigation of fire.
   POLICE DEPARTMENTS (EXCEPT AMERICAN INDIAN OR ALASKA NATIVE)	POLICE DEPARTMENTS (EXCEPT AMERICAN INDIAN OR ALASKA NATIVE)-[NAICS Code 922120]: Entities that are involved in the specific sector of general police protections are classified under this description, unless they are primarily involved in a more specific sector of law enforcement.
   POLICE, AMERICAN INDIAN OR ALASKA NATIVE TRIBAL	POLICE, AMERICAN INDIAN OR ALASKA NATIVE TRIBAL-[NAICS Code 921150]: Entities that are involved in the specific sector of general police protections for the American Indian and Alaskan Native population are classified under this description, unless they are primarily involved in a more specific sector of law enforcement.
   PRISON FARMS	PRISON FARMS - [NAICS Code 922140]: Entities where the inmate population works on a farm or ranch as part of their punishment / rehabilitation.
   PRISONS	PRISONS - [NAICS Code 922140]: Entity is a prison. A prison is a facility where persons convicted of the commission of a felony are held. Prisons may be called "Prisons", "Reformatories", "Penitentiaries", "Detention Centers", or "Correctional Centers", although the use of one of these terms in an entity's name does not necessarily indicate that the entity is in fact a "Prison" in the narrow sense used here.
   REHABILITATION SERVICES, CORRECTIONAL, GOVERNMENT	REHABILITATION SERVICES, CORRECTIONAL, GOVERNMENT-[NAICS Code 922150]: Entity is a treatment center that attempts to change or reform a convicted person so that he or she will not commit another criminal act. These entities facilitate reintegration into the community with a greater chance of succeeding.
   SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)	SHERIFFS' OFFICES (EXCEPT COURT FUNCTIONS ONLY)-[NAICS Code 922120]: Entities that are involved in the specific sector of general law enforcement at the county level are classified under this description, unless they primarily conduct court functions only.
   SHERIFFS' OFFICES, COURT FUNCTIONS ONLY	SHERIFFS' OFFICES, COURT FUNCTIONS ONLY-[NAICS Code 922110]: Entities that are involved in the specific sector of general law enforcement at the county level that conduct court functions only are classified under this description.
   STATE POLICE	STATE POLICE-[NAICS Code 922120]: Entities that are involved in the specific sector of general law enforcement at the state level are classified under this description, unless they are primarily involved in a more specific sector of law enforcement.
   TRANSIT POLICE	TRANSIT POLICE-[NAICS Code 922120]: Entities that are involved in the specific sector of a specialized type of police who prevent and investigate crimes committed against a transportation carrier or against passengers and other customers of the carrier are classified under this description.

   GEOLINKID

   Link ID for the street segment to which the entity was geocoded. Refer to the [ST_VENDOR] and [ST_VERSION] fields for the street vendor and version that was used to geocode the entity. (Source: TGS)

   Text

   X

   Longitude in WGS 84 Decimal Degrees. (Source: TGS)

   Range of values
   Minimum:	-180
   Maximum:	180
   Units:	WGS 84 Decimal Degrees

   Y

   Latitude in WGS 84 Decimal Degrees. (Source: TGS)

   Range of values
   Minimum:	-90
   Maximum:	90
   Units:	WGS 84 Decimal Degrees

   ST_VENDOR

   Indicates name of vendor providing original street data used for geocoding. (Source: TGS)

   Value	Definition
   NAVTEQ	NAVTEQ streets were used for geocoding.
   TGS	TGS drew in a new street segment that does not exist in the file supplied by NAVTEQ.

   ST_VERSION

   Indicates the year and quarter of streets used for geocoding. (Source: TGS)

   Value	Definition
   2006Q3	3rd Quarter 2006 NAVTEQ street data was used for geocoding.
   2006Q4	4th Quarter 2006 NAVTEQ street data was used for geocoding.
   2008Q1	1st Quarter 2008 NAVTEQ street data was used for geocoding.

   GEOPREC

   Geocoding precision. (Source: TGS)

   Value	Definition
   BLOCKFACE	Entity is geocoded to correct block and correct side of street per street data indicated by [ST_VENDOR] and [ST_VERSION].
   ONENTITY	Entity is geocoded on entity rooftop per aerial imagery (in most cases USGS DOQQs).

   PHONELOC

   Indicates whether the phone number in the [TELEPHONE] field rings to the actual location of the entity. (Source: TGS)

   Value	Definition
   YES	Phone number rings to the actual entity location.
   NO	Phone number does not ring to the actual entity location. It may ring to an administrative office or central location.
   <BLANK>	Unknown - It is not known if the entity's phone number rings to the entity's location.

   QC_QA

   Organization that performed Quality Control/Quality Assurance on the record. (Source: TGS)

   Value	Definition
   TGS	TGS has performed Quality Control/Quality Assurance on all TGS added records and all records contacted since 01/01/2005.
   <BLANK>	The record is not TGS added or has not had Quality Control/Quality Assurance performed by TGS, or Quality Control/Quality Assurance was performed prior to 01/01/2005.

   STATE_ID

   State Law Enforcement Data ID. For states that contributed data, this field is populated with the unique ID used by the state to track law enforcement locations. (Source: TGS)

   Text

   ORI

   The ORI is a nine-character identifier assigned by FBI CJIS staff to an agency which has met the established qualifying criteria for ORI assignment to identify the agency in transactions on the NCIC 2000 System. The structure of law enforcement ORIs (those ORIs ending with a zero) and other criminal justice ORIs (those ORIs ending with an alphabetic character) are as follows:
   1. POSITIONS 1 THROUGH 5>Positions 1 and 2 are the alphabetic characters representing the state or country in which the agency is located. For example: PA0040100 Positions 3, 4, and 5 are numeric characters indicating the county in which the agency is located. For example: PA0040100 Exceptions to this are some state-level and federal agencies, which have the acronym for that agency, or alphabetic variations thereof, in positions 3, 4, and 5, i.e., DCATF0000 and TXDPD0000 for the Bureau of Alcohol, Tobacco and Firearms and the Dallas, Texas, Police Department, respectively.
   2. POSITIONS 6 THROUGH 9 OF LAW ENFORCEMENT ORIs The criterion FBI CJIS staff uses for assigning a law enforcement ORI (one ending with a zero) is that the agency is a governmental agency or subunit thereof having statutory power of arrest and whose primary function is that of apprehension and detection. Positions 6 and 7 in a law enforcement ORI are used to distinguish one agency from another within the same county. For example: PA0040100 Positions 8 and 9 of a law enforcement ORI are always double zero. NCIC 2000 users, particularly large city/urban police departments, may vary the last two positions (8 and 9) to identify internal divisions, units, substations, or multiple terminals for the same agency within the same city. Any variation of the last two positions is acceptable with the exception that an alphabetic character cannot be used in position 9. NCIC 2000 does not assign these variations. The variations will not translate when a ZO inquiry is made.
   3. POSITIONS 6 THROUGH 9 OF CRIMINAL JUSTICE ORIs FBI CJIS staff determines the numeric and alphabetic characters assigned to positions 6 through 9 for criminal justice ORIs as follows: Positions 6 and 7 are numeric characters uniquely distinguishing one agency from other agencies of the same type and level within the same county. They do not indicate location (e.g., city) of the agency. For example: PA004023C Position 8 is a unique numeric character indicating the government level of the agency: 1 - Local, Municipal, City 3 - County 5 - State 7 - Federal 9 - Nongovernmental For example: PA004023C Position 9 is an alphabetic character representing the type of agency: A - Prosecuting Attorney's Offices (includes District Attorney's Offices, Attorney General's Offices, etc.). B - Pretrial service agencies and pretrial release agencies. C - Correctional Institutions (includes jails, prisons, detention centers, etc.). D - Civil Courts for use in domestic violence and stalking cases. E - Nongovernmental railroad or campus police departments qualifying for access to III. (This section provides criteria for assignment of a limited access ORI.) G - Probation and Parole Offices. H - Department of State National Visa Center. I - INTERPOL. J - Courts and Magistrates Offices. K - Medical examiners and coroners offices for access to Missing Person and Unidentified Person Files. M - Custodial facilities in medical or psychiatric institutions and some medical examiners' offices which are criminal justice in function. N - Regional dispatch centers which are criminal justice agencies or under the management control of criminal justice agencies. O - National Insurance Crime Bureau. P - Nongovernmental agencies that qualify for access to some NCIC 2000 files other than III. Also, 911 centers that do not have a management control agreement. Q - Department of Housing and Urban Development approved Public Housing Agencies. R - Agencies authorized by Public Law 99-169 for national security purposes. U - Federal and state governmental child support enforcement agencies. V - Department of Motor Vehicles. W - National Center for Missing and Exploited Children (NCMEC). Y - Local, county, state, or federal agencies that are classified as criminal justice agencies by statute but do not fall into one of the aforementioned categories, e.g., Arkansas Crime Information Center. For example: PA004023C
   Please note that these ORI numbers are provided "as-is" by individual sources and TGS has not verified the accuracy of these ids. (Source: NCIC 2000)

   Text

   LEMAS_ID

   Agency identification number provided by LEMAS.
   Please note that these numbers are provided "as-is" and TGS has not verified the accuracy of these ids. (Source: TGS)

   Text

   SECLEVEL

   Indicates the security level the facility operates under.
   The definitions for the values that are in this field were taken from the Federal Bureau of Prisons. Where possible, these categories have been applied to facilities other than those operated by the Federal Bureau of Prisons.
   The values in this field were provided by individual sources and are not verified by TGS. (Source: TGS)

   Text

   FACTYPE

   Type of facility.
   The values in this field were provided by individual sources and are not verified by TGS. (Source: TGS)

   Text

   AGENCY

   Agency name.
   The values in this field were assigned by TGS based on the entity's source data. (Source: TGS)

   Text

   INMATE_MEN

   Indicates whether or not the inmate population is male.
   The values in this field were provided by individual sources and are not verified by TGS. (Source: TGS)

   Value	Definition
   YES	Facility has a male population.
   NO	Facility does not have a male population.
   <BLANK>	Unknown or not provided

   INMATE_WOM

   Indicates whether or not the inmate population is female.
   The values in this field were provided by individual sources and are not verified by TGS. (Source: TGS)

   Value	Definition
   YES	Facility has a female population.
   NO	Facility does not have a female population.
   <BLANK>	Unknown or not provided

   INMATE_JUV

   Indicates whether or not the inmate population is juvenile.
   The values in this field were provided by individual sources and are not verified by TGS. (Source: TGS)

   Value	Definition
   YES	Facility has a juvenile population.
   NO	Facility does not have a juvenile population.
   <BLANK>	Unknown or not provided

   INMATE_COE

   Indicates whether or not the inmate population is Co-Ed.
   The values in this field were provided by individual sources and are not verified by TGS. (Source: TGS)

   Value	Definition
   YES	Facility has a Co-Ed population.
   NO	Facility does not have a Co-Ed population.
   <BLANK>	Unknown or not provided

   CAPACITY

   Design capacity of inmates.
   The values in this field were provided by individual sources and are not verified by TGS. (Source: TGS)

   Number

   TOTALPOP

   Total population of entity.
   The values in this field were provided by individual sources and are not verified by TGS. (Source: TGS)

   Number

   EMERPHONE

   Emergency Contact Number as provided by individual sources. Some values also include telephone extensions and/or alternate telephone numbers. All alphabetic characters have been translated to the corresponding numeric digit.
   The values in this field were provided by individual sources and are not verified by TGS. (Source: TGS)

   Phone numbers, including area code, formatted as nnn-nnn-nnn. A list of valid area code and exchange combinations can be found at <http://www.nanpa.com>

   PERM_ID

   The unique permanent identifier of The National Structures Dataset.
   The values in this field were provided by individual sources and are not verified by TGS. (Source: TGS)

   Text

   GNIS_ID

   The unique permanent identifier of the Geographic Names Information System. Values are up to eight (8) digits in length and are unique within the nation.
   The values in this field were provided by individual sources and are not verified by TGS. (Source: TGS)

   Text

   CI

   Indicates if the entity is also a part of the Correctional Institution layer. (Source: TGS)

   Value	Definition
   Y	Entity is also a part of the Correctional Institution layer.
   N	Entity is a law enforcement facility only.
   <BLANK>	Unable to determine if entity also belongs in the Correctional Institution layer.

Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • TechniGraphics, Inc.

2. Who also contributed to the data set?

3. To whom should users address questions about the data?
   Mike Thompson
   TechniGraphics, Inc.
   Director of Research and Development
   3351 Eastbrook Drive
   Fort Collins, CO 80525
   USA
   

   970-224-4996 (voice)
   970-224-3001 (FAX)
   mike.thompson@tgstech.com
   

   Hours_of_Service: Monday - Friday 0800 - 1700 MST

Why was the data set created?

Homeland Security
Use Cases: Use cases describe how the data may be used and help to define and clarify requirements.
1. An assessment of whether or not the total police capability in a given area is adequate.
2. A list of resources to draw upon in surrounding areas when local resources have temporarily been overwhelmed by a disaster - route analysis can help to determine those entities who are able to respond the quickest.
3. A resource for emergency management planning purposes.
4. A resource for catastrophe response to aid in the retrieval of equipment by outside responders in order to deal with the disaster.
5. A resource for situational awareness planning and response for federal government events.

How was the data set created?

1. From what previous works were the data drawn?

   LawEnforcement_2007_Q3 (source 1 of 22)

   Techni Graphic Systems, Inc., 20070718, Law Enforcement 2007 Q3.

   Type_of_Source_Media: Digital Database File

   Source_Contribution:

   The basic attribution (name, address, city, state, zip code, and telephone number) came from this dataset unless the entity was updated by TGS during Q407 processing.

   LawEnforcement_2007_Q4 (source 2 of 22)

   TechniGraphics, Inc., 20071030, Law Enforcement 2007 Q4.

   Type_of_Source_Media: Digital Database File

   Source_Contribution:

   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.

   Law_Enforcement_2008_Q1 (source 3 of 22)

   TechniGraphics, Inc., 20080321, Law Enforcement 2008 Q1.

   Type_of_Source_Media: Digital Database File

   Source_Contribution:

   The basic attribution (name, address, city, state, zip code, and telephone number) came from this dataset unless the entity was updated by TGS during Q208 processing.

   LawEnforcement_2008_Q2 (source 4 of 22)

   TechniGraphics, Inc., 20080530, Law Enforcement 2008 Q2.

   Type_of_Source_Media: Digital Database File

   Source_Contribution:

   The basic attribution (name, address, city, state, zip code, and telephone number) came from this dataset unless the entity was updated by TGS during Q409 processing.

   BIA (source 5 of 22)

   Department of the Interior Offi, Security & Emergency Management (DOI), 20080131, BIA.

   Type_of_Source_Media: File Transfer Protocol

   Source_Contribution:

   This was used as a source for Law Enforcement and Correctional Institutions in the United States during the Q208 processing.

   BLM (source 6 of 22)

   Department of the Interior Offi, Security & Emergency Management (DOI), 20080131, BLM.

   Type_of_Source_Media: File Transfer Protocol

   Source_Contribution:

   This was used as a source for Law Enforcement in the United States during the Q208 processing.

   BOR (source 7 of 22)

   Department of the Interior Offi, Security & Emergency Management (DOI), 20080131, BOR.

   Type_of_Source_Media: File Transfer Protocol

   Source_Contribution:

   This was used as a source for Law Enforcement and Correctional Institutions in the United States during the Q208 processing.

   FWS (source 8 of 22)

   Department of the Interior Offi, Security & Emergency Management (DOI), 20080131, FWS.

   Type_of_Source_Media: File Transfer Protocol

   Source_Contribution:

   This was used as a source for Law Enforcement and Correctional Institutions in the United States during the Q208 processing.

   NPS (source 9 of 22)

   Department of the Interior Offi, Security & Emergency Management (DOI), 20080226, NPS.

   Type_of_Source_Media: File Transfer Protocol

   Source_Contribution:

   This was used as a source for Law Enforcement and Correctional Institutions in the United States during the Q208 processing.

   USPP (source 10 of 22)

   Department of the Interior Offi, Security & Emergency Management (DOI), 20080131, USPP.

   Type_of_Source_Media: File Transfer Protocol

   Source_Contribution:

   This was used as a source for Law Enforcement and Correctional Institutions in the United States during the Q208 processing.

   ATF (source 11 of 22)

   U.S. Department of Justice Bure, Tobacco, Firearms and Explosives (ATF), Unknown, Field Offices.

   Online Links:

   • <http://www.atf.gov/field/index.htm>

   Other_Citation_Details: Publication date is unknown - downloaded on 20080222

   Type_of_Source_Media: Online

   Source_Contribution:

   This was used as a source for ATF locations in the United States during the Q208 processing.

   FBOP (source 12 of 22)

   Federal Bureau of Prisons (FBOP), Unknown, Address Directory.

   Online Links:

   • <http://www.bop.gov/DataSource/execute/dsFacilityAddressLoc?startPageRedirect=facilityAddressLookup.jsp>

   Other_Citation_Details: Publication date is unknown - downloaded on 20080130

   Type_of_Source_Media: Online

   Source_Contribution:

   This was used as a source for Federal Prisons in the United States during the Q208 processing.

   USCBP_DIS (source 13 of 22)

   United States Customs and Border Protection (USCBP), Unknown, Deferred Inspection Sites.

   Online Links:

   • <http://www.cbp.gov/linkhandler/cgov/toolbox/contacts/deferred_inspection/deferred_inspection_sites.ctt/deferred_inspection_sites.pdf>

   Other_Citation_Details: Publication date is unknown - downloaded on 20080317

   Type_of_Source_Media: Online

   Source_Contribution:

   This was used as a source for United States Customs and Border Protection deferred inspection site locations in the United States during the Q208 processing.

   USCBP_FOO (source 14 of 22)

   United States Customs and Border Protection (USCBP), Unknown, Field Operations Offices.

   Online Links:

   • <http://www.cbp.gov/xp/cgov/toolbox/contacts/cmcs/>

   Other_Citation_Details: Publication date is unknown - downloaded on 20080220

   Type_of_Source_Media: Online

   Source_Contribution:

   This was used as a source for United States Customs and Border Protection field operations office locations in the United States during the Q208 processing.

   USCBP_POE (source 15 of 22)

   United States Customs and Border Protection (USCBP), Unknown, Ports of Entry.

   Online Links:

   • <http://www.cbp.gov/xp/cgov/toolbox/contacts/ports/>

   Other_Citation_Details: Publication date is unknown - downloaded on 20080220

   Type_of_Source_Media: Online

   Source_Contribution:

   This was used as a source for United States Customs and Border Protection ports of entry locations in the United States during the Q208 processing.

   USMS (source 16 of 22)

   United States Marshals Service (USMS), Unknown, Local District Offices.

   Online Links:

   • <http://www.usmarshals.gov/district/index.html>

   Other_Citation_Details: Publication date is unknown - downloaded on 20080227

   Type_of_Source_Media: Online

   Source_Contribution:

   This was used as a source for United States Marshals Service locations in the United States during the Q208 processing.

   LEMAS (source 17 of 22)

   United States Department of Jus, Bureau of Justice Statistics (USDOJ-BJ, 2003, Law Enforcement Management and Administrative Statistics (LEMAS).

   Online Links:

   • <http://www.ojp.usdoj.gov/bjs/lawenf.htm>

   Type_of_Source_Media: Online

   Source_Contribution:

   This was used as a source for law enforcement for the entire United States during the Q207 processing.

   NC_PS (source 18 of 22)

   North Carolina State Center For Health Statistics (NCSCHS), 200307, Police.

   Type_of_Source_Media: Electronic Mail System

   Source_Contribution:

   This was used as a source for law enforcement in North Carolina during the Q108 processing.

   NSD (source 19 of 22)

   United States Geological Survey (USGS), Unknown, National Structures Dataset Hurricane 50 mi Buffer Police Stations.

   Other_Citation_Details: Publication date is unknown - downloaded on 20080328

   Type_of_Source_Media: File Transfer Protocol

   Source_Contribution:

   This was used as a source to populate [GNIS_ID] and [PERM_ID] for law enforcement in the United States.

   NAVTEQ_Streets_2006_Q3 (source 20 of 22)

   NAVTEQ, 2006, NAVSTREETS.

   Type_of_Source_Media: CD-ROM

   Source_Contribution:

   This version of NAVTEQ streets was used as reference for automatic geocoding and for the manual geolocating of entities during Q307 processing.

   NAVTEQ_Streets_2006_Q4 (source 21 of 22)

   NAVTEQ, 2006, NAVSTREETS.

   Type_of_Source_Media: CD-ROM

   Source_Contribution:

   This version of NAVTEQ streets was used as a reference for automatic geocoding and for the manual geolocating of entities during Q407, Q108, and Q208 processing.

   NAVTEQ_Streets_2008_Q1 (source 22 of 22)

   NAVTEQ, 2008, NAVSTREETS.

   Type_of_Source_Media: CD-ROM

   Source_Contribution:

   This version of NAVTEQ streets was used as a reference for automatic shifting of entities that were previously manually geocoded and for the automatic geocoding and manual geolocating of entities during the final processing.

2. How were the data generated, processed, and modified?

   Date: 30-Dec-2009 (process 1 of 1)

   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.

   Person who carried out this activity:
   

   Nicole Hackworth
   TechniGraphics, Inc.
   Production Manager
   2000 Noble Drive
   Wooster, OH 44691
   USA
   

   330-263-6222 (voice)
   330-263-1034 (FAX)
   nicole.hackworth@tgstech.com
   

   Hours_of_Service: Monday - Friday 0800 - 1700 EST

   Data sources used in this process:

   • LawEnforcement_2007_Q3
   • LawEnforcement_2007_Q4
   • LawEnforcement_2008_Q1
   • LawEnforcement_2008_Q2
   • ATF
   • BIA
   • BOR
   • FBOP
   • FWS
   • LEMAS
   • NPS
   • NSD
   • USCBP_DIS
   • USCBP_FOO
   • USCBP_POE
   • USMS
   • NC_PS
   • NAVTEQ_STREETS_2006_Q3
   • NAVTEQ_STREETS_2006_Q4
   • NAVTEQ_STREETS_2008_Q1

   Data sources produced in this process:

   • LawEnforcement_2009_Q4

3. What similar or related data should the user be aware of?

How reliable are the data; what problems remain in the data set?

1. How well have the observations been checked?

   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.

2. How accurate are the geographic locations?

   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.

3. How accurate are the heights or depths?

4. Where are the gaps in the data? What is missing?

   TGS has made a concerted effort to include all local police; county sheriffs; state police and/or highway patrol; Bureau of Indian Affairs; Bureau of Land Management; Bureau of Reclamation; U.S. Park Police; 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 in North Carolina.
   Correctional institutions are included in this dataset because they also serve as a police or sheriff's office, not because they have staff with arrest powers.
   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.

5. How consistent are the relationships among the observations, including topology?

   See "Attribute_Accuracy_Report". Many of the checks described in that section check for both attribute accuracy and logical consistency.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: None

Use_Constraints: None

1. Who distributes the data set? (Distributor 1 of 1)
   NC CGIA
   301 N. Wilmington Street, Suite 700
   Raleigh, North Carolina 27601-2825
   U.S.A.
   

   (919)754-6580 (voice)
   (919)715-8551 (FAX)
   dataq@its.nc.gov
   

   Hours_of_Service: 8am to 5pm

   Contact_Instructions: Phone and electronic mail preferred

2. What's the catalog number I need to order this data set?

   Natural Heritage Element Occurrences

3. What legal disclaimers am I supposed to read?

   NCCGIA is charged with the development and maintenance of NC OneMap and, in cooperation with other mapping organizations, is committed to offering its users accurate, useful, and current information. Although every effort has been made to ensure the accuracy of information, errors and conditions originating from physical sources used to develop this dataset may be reflected in the data supplied. The user must be aware of possible conditions and bear responsibility for the appropriate use of the information with respect to possible errors, original map scale, collection methodology, currency of data, and other conditions specific to certain data. NCCGIA does not support secondary distribution of this dataset without its current, compliant metadata record. The use of trade names or commercial products does not constitute their endorsement by NCCGIA or North Carolina State Government.

4. How can I download or order the data?
   • Availability in digital form:

     Data format:	ESRI shapefile (*.shp)
     Network links:	NC OneMap

   • Cost to order the data: None. Download from www.nconemap.com is free of charge.

5. Is there some other way to get the data?

   Data can be customized on a cost-recovery basis. Contact dataq@its.nc.gov or 919-754-6580 for more information.

6. What hardware or software do I need in order to use the data set?

   All formats available from www.nconemap.com are in ESRI shapefile. Other formats are available on a cost-recovery basis - contact dataq@its.nc.gov or 919.754.6580 for more information. Format compatibility is the user's responsibility.

Who wrote the metadata?

Dates:

Last modified: 17-Feb-2010

Metadata author:

Mike Thompson
TechniGraphics, Inc.
Director of Research and Development
3351 Eastbrook Drive
Fort Collins, CO 80525
USA

970-224-4996 (voice)
970-224-3001 (FAX)
mike.thompson@tgstech.com

Hours_of_Service: Monday - Friday 0800 - 1700 MST

Metadata standard:

FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)