FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION
VERSION 2007

TITLE: FLORIDA LAW ENFORCEMENT 2007 Q3

Geodataset Name:       FDEM_POLICEDEPT_AUG07
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Point
Feature Count:         609
GENERAL DESCRIPTION:
This dataset contains Law Enforcement Locations in the State of Florida. This dataset defines Law Enforcement locations as 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. Although TGS's intention is to only include locations associated with agencies that meet the above definition, TGS has discovered a few locations that are associated with agencies that are not publicly funded. TGS is deleting these locations as we become aware of them, but some probably still exist in this dataset. 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] attribute. Based upon this attribute, the oldest record dates from 01/20/2006 and the newest record dates from 05/14/2007. This dataset was created by TechniGraphics, Inc. for the Florida Division of Emergency Management.
DATA SOURCE(S):                    Florida Division of Emergency Management
SCALE OF ORIGINAL SOURCE MAPS:     N/A
DATE OF AUTOMATION OF SOURCE:      20070820
GEODATASET EXTENT:                 State of Florida

FEATURE ATTRIBUTE TABLES:

Datafile Name: FDEM_POLICEDEPT_AUG07.DBF
ITEM NAME WIDTH TYPE N. DECIMAL DEGREES
OBJECTID
4 OID ---
ID
10 String ---
METLNKID
20 String ---
FEATTYPE
10 String ---
SECCLASS
30 String ---
NAME
254 String ---
AREA_
3 String ---
PHONE
8 String ---
FAX
12 String ---
ADDRESS
80 String ---
ADDRESS2
80 String ---
CITY
120 String ---
STATE
2 String ---
ZIP
5 String ---
ZIPP4
4 String ---
COUNTY
50 String ---
FIPS
5 String ---
DIRECTIONS
254 String ---
EMERGTITLE
40 String ---
EMERGPHONE
12 String ---
EMERGEXT
10 String ---
CONTDATE
8 Date ---
CONTHOW
10 String ---
GEODATE
8 Date ---
GEOHOW
10 String ---
NAICSCODE
6 String ---
NAICSDESCR
120 String ---
GEOLINKID
10 String ---
X
19 Number 7
Y
19 Number 7
ST_VENDOR
10 String ---
ST_VERSION
10 String ---
GEOPREC
32 String ---
PHONELOC
3 String ---
QC_QA
3 String ---
STATE_ID
20 String ---
EFCLASS
5 String ---
TRACT
11 String ---
USNG_FL_1K
10 String ---
DESCRIPT
115 String ---
FGDLAQDATE
8 Date ---
AUTOID
6 Number ---
SHAPE
4 Geometry ---

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description
OBJECTID Internal feature number.

ID Unique identifier for feature.

METLNKID Link to Metadata.

FEATTYPE Geometry type of feature.
POINT = Feature is represented by point.


SECCLASS Security classification of feature.
UNCLASSIFIED = Entity is unclassified.


NAME Name of entity.

AREA_ Three (3) digit telephone area code for entity.

PHONE Seven (7) digit telephone number for entity formatted as nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit.

FAX Fax number for entity formatted as nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit. The values for this attribute have not been verified by TGS.

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 attribute. 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 they are located on is listed in this attribute. Some rural areas may not have named roads. In these rare cases, this attribute will be blank.

ADDRESS2 Location within physical address, e.g., floor, suite, building.

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] attribute 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 attribute 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.

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 attribute. Also, the state in which an entity appears to be located may change depending on the scale of the state boundary theme being used.

ZIP Five (5) digit USPS zip code for entity's physical location.

ZIPP4 Four (4) digit USPS zip code extension. This attribute was automatically assigned using the entity's physical address and USPS address information system (AIS) data.

COUNTY County name where entity is located.

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.

DIRECTIONS Directions to entity location, or description of the entity's location.

EMERGTITLE Title of person or name of office for emergency point of contact.

EMERGPHONE 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.

EMERGEXT Telephone extension for emergency point of contact.

CONTDATE Date entity was contacted by TGS.

CONTHOW Method by which entity was contacted.
PHONE = Entity was contacted by phone.

FAX = Entity was contacted by fax.

MAIL = Entity was contacted by mail.

EMAIL = Entity was contacted by email.

WEB = Entity information was gathered and/or verified by official entity website as a last resort.

ALT REF = Geospatial reference information obtained from local authorities, e.g., downloadable parcel maps, 911 streets.


GEODATE Date entity was geocoded by TGS.

GEOHOW Method by which entity was geocoded.
AUTO = Entity was automatically geocoded.

MANUAL = Entity was manually geocoded.

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.

PROVIDED = Entity was geocoded using coordinates provided by the state.


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.

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.
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.

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 involved in the specific sector of preventing and/or investigating of fires are classified under this description, unless they are primarily involved in general fire fighting.

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.

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.

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 ACADEMIES = POLICE ACADEMIES-[NAICS Code 922120]:  Entities that are primarily involved in the specific sector of training police officers 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.

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] attributes for the street vendor and version that was used to geocode the entity.

X Longitude in WGS 84 Decimal Degrees.

Y Latitude in WGS 84 Decimal Degrees.

ST_VENDOR Indicates name of vendor providing original street data used for geocoding.
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.

<BLANK> = Entity was geocoded using coordinates provided by the state; therefore, the street vendor is unknown.


ST_VERSION Indicates the year and quarter of streets used for geocoding.
2006Q3 = 2006Q3 NAVTEQ Street Data used for geocoding.

<BLANK> = Entity was geocoded using coordinates provided by the state; therefore, the street version is unknown.


GEOPREC Geocoding precision.
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 phone field rings to the actual location of the entity.
YES = Phone number rings to the actual entity location.

NO = Phone number does not ring to the actual entity location. It might 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.
TGS = TGS has performed Quality Control/Quality Assurance on the entity record after 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 Police Department Data ID. For states that contributed data, this attribute is populated with the unique ID used by the state for police departments. In cases where the state only tracks departments and not stations, we have generated a unique ID for stations other than the main station for a department by appending a sequential number.

EFCLASS Indicates the classification of the entity. The values for this attribute have not been verified by TGS.
EFPS = "Emergency Response - Police station"

<BLANK> = Unknown or not provided.


TRACT Definition not provided. The values for this attribute have not been verified by TGS.

USNG_FL_1K Facility's 1-kilometer United States National Grid (USNG) address. The USNG is an alpha-numeric reference system based on the UTM coordinate system and is similar to the Military Grid Reference System. Use of the USNG ensures a uniform grid mapping and positional reporting system for search and rescue, emergency planning, response, and recovery. How to Read a United States National Grid (USNG) Spatial Address Website - http://www.fgdc.gov/usng/how-to-read-usng/index_html

DESCRIPT Based on NAME.

FGDLAQDATE The date FGDL acquired the data from the Source.

AUTOID GeoPlan feature identification number.

SHAPE Feature geometry.


USER NOTES:
See "Attribute_Accuracy_Report". 
Many of the checks described in that section check for both 
attribute accuracy and logical consistency.
This dataset is based on information provided by Post, Buckley, Schuh, and 
Jernigan, Incorporated (PBSJ) with the permission from the Florida Department of 
Emergency Management (FLDEM)
>
Completeness of the Law Enforcement database is ongoing. If an entity provided 
information for a station or stations not already in the database, those stations 
were added by TGS.
>
Locations that are administrative offices only are excluded from the dataset. 
>
Although TGS's intention is to only include locations associated with agencies that 
meet the definition of a Law Enforcement Agency, TGS has discovered a few 
locations that are associated with agencies that are not publicly funded. TGS is 
deleting these locations as we become aware of them, but some probably still exist 
in this dataset.
GeoPlan relied on the integrity of the attribute information within
the original data.

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] 
attribute. 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] attribute is not blank and all IDs are 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 2 characters. Name does not contain punctuation characters 
that can interfere with database operations, such as " (quote) and * (asterisk). 

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. 

City Check: Entity city is not blank and is found in the named places file within 25 
miles.

County FIPS to State Compare Check: The county represented by the tabular 
FIPS Code attribute is actually in the state specified by the state attribute. 

County Name to State Compare Check: The county represented by the tabular 
county name attribute is actually in the state specified by the state attribute. 

Phone Number Format Check: Phone numbers (including area code) were verified
to be formatted as nnn-nnn-nnnn. 

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: Area code (NPA) is valid and is within its area code 
boundary. 

Zip Code Check: The 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] attribute,
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). 

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.
Florida Division of Emergency Management (FDEM)
Home / Preparedness / Information Management / Critical Facilities
 http://www.floridadisaster.org/gis/criticalfacilities/index.htm

Critical Facilities

To assist in emergency response and planning, the GIS Lab, working with local, 
state, and federal agencies maintains shelters, emergency operations centers, 
critical facilities, and hazardous material facilities datasets.

"Critical facilities" are defined as those structures from which essential services 
and functions for victim survival, continuation of public safety actions, and disaster 
recovery are performed or provided. Shelters, emergency operation centers, public 
health, public drinking water, sewer and wastewater facilities are examples of 
critical facilities. Though not explicitly included in the definition, supporting life-line 
infrastructure essential to the mission of critical facilities must also be included in 
the inventory when appropriate.

"Critical infrastructure" is defined as those systems and assets, whether physical 
or virtual, so vital that the incapacity or destruction of such systems and assets 
would have a debilitating impact on security, economy, public health or safety, or 
any combination of these elements.

The domain of the GIS Lab is specifically related to "critical facilities", while 
working closely with Florida's Regional Domestic Security Task Forces to ensure a
safe and secure Florida.

Several critical facilities data layers are maintained by other agencies, and the GIS
Lab works closely with these agencies to make sure updated data is readily 
available. Examples include:

    * Drinking Water Facilities - Florida Department of Environmental Protection
    * Environmental Health Facilities - Florida Department of Health
    * Fire Stations - Florida State Fire Marshal
    * Health Care Facilities - Agency for Health Care Administration
    * Petroleum Storage Tanks - Florida Department of Environmental Protection
    * Schools - Florida Department of Education
    * Solid Waste Facilities - Florida Department of Environmental Protection

Other data layers, like Hazardous Materials Facilities, Mobile Home Parks, and 
Hotel/Motels, while not specifically critical facilities, are facilities of interest for 
emergency managers, and the GIS Lab is also actively involved in facilitating 
access to these data layers.

Homeland Security Infrastructure Program

The Homeland Security Infrastructure Program (HSIP) is a collection of base map 
layers and homeland security related geospatial data. Currently, the emphasis of 
this program is on sharing and improving data to create uniform state & federal 
information. Working with contractors, the GIS Lab is providing data from state 
and local sources for QA/QC under the HSIP Freedom project.

    * Correctional Facilities - delivered April 2007
    * Emergency Operations Centers - July 2007
    * Fire Stations - t.b.a.
    * Police Stations - t.b.a.
    * Emergency Medical Services - t.b.a.
    * Hospitals - t.b.a.
    * Urgent Care Facilities - t.b.a.

Emergency Management GIS Data Downloads

At this time, FDEM does not provide datasets for download, but may be contacted 
(Richard Butgereit 850-413-9907) for further information.

Homeland Security                  

Use Cases: Use cases describe how the data may be used and to help 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.

The geographic location of contacted entities was verified to be correct relative to
the street data and version indicated by the [ST_VENDOR] and [ST_VERSION] 
attributes. The horizontal accuracy is indicated by the [GEOPREC] attribute.  A 
value of "BLOCKFACE" indicates the entity was geocoded on the correct 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 block and correct side of the street.

This data is provided 'as is' and its vertical positional accuracy
has not been verified by GeoPlan

THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED
AS LEGALLY BINDING. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER SHALL
NOT BE LIABLE FOR ANY DAMAGES SUFFERED AS A RESULT OF USING,
MODIFYING, CONTRIBUTING OR DISTRIBUTING THE MATERIALS.

A note about data scale: 

Scale is an important factor in data usage.  Certain scale datasets
are not suitable for some project, analysis, or modeling purposes.
Please be sure you are using the best available data. 

1:24000 scale datasets are recommended for projects that are at the
county level.
1:24000 data should NOT be used for high accuracy base mapping such
as property parcel boundaries.
1:100000 scale datasets are recommended for projects that are at the
multi-county or regional level.
1:125000 scale datasets are recommended for projects that are at the
regional or state level or larger.

Vector datasets with no defined scale or accuracy should be
considered suspect. Make sure you are familiar with your data
before using it for projects or analysis. Every effort has been
made to supply the user with data documentation. For additional
information, see the References section and the Data Source Contact
section of this documentation. For more information regarding
scale and accuracy, see our webpage at:
http://geoplan.ufl.edu/education.html

REFERENCES:
TechniGraphics, Inc.
http://www.tgstech.com/gis.asp

Florida Division of Emergency Management
http://www.floridadisaster.org/index.asp
http://www.floridadisaster.org/gis

DATA LINEAGE SUMMARY:
TGS 2007 Q3 Processing
>
>1) Verified name, physical address, and phone numbers by contacting the entity 
or an authority responsible for the entity.
>
>2) Determined or verified the geospatial location for the entity through contact 
with entity or authority responsible for entity. Entities were asked to describe their 
geospatial location relative to land marks visible in ortho imagery.
>
>3) All text fields were set to upper case.
>
>4) Leading and trailing spaces were trimmed from all text fields. These spaces 
can interfere with some database queries.
>
>5) Non printable and diacritic characters were removed from all text fields. These 
values have been found to prevent data from being loaded into some spatial 
database engines.
Process Date: 20070820

GeoPlan Center received the data via FTP from the Florida Division of Emergency Management (FDEM) on March 18, 2008. The original dataset was named: 2007_08_20_FL_PoliceStationsQ307.shp The original dataset projection was: Spatial_Reference_Information: Horizontal_Coordinate_System_Definition: Geographic: Latitude_Resolution: 0.000000 Longitude_Resolution: 0.000000 Geographic_Coordinate_Units: Decimal degrees Geodetic_Model: Horizontal_Datum_Name: D_WGS_1984 Ellipsoid_Name: WGS_1984 Semi-major_Axis: 6378137.000000 Denominator_of_Flattening_Ratio: 298.257224 The dataset was renamed to: fdem_policedept_aug07.shp The dataset was reprojected to the FGDL Albers NAD83 HARN projection. The dataset features were matched to their 1-kilometer United States National Grid (USNG) address via a spatial join, the USNG address can be found in the USNG_FL_1K field. The USNG is an alpha-numeric reference system based on the UTM coordinate system and is similar to the Military Grid Reference System. Use of the USNG ensures a uniform grid mapping and positional reporting system for search and rescue, emergency planning, response, and recovery. How to Read a United States National Grid (USNG) Spatial Address http://www.fgdc.gov/usng/how-to-read-usng/index_html Three additional fields were added. DESCRIPT field based on NAME FGDLAQDATE field based on the date the data was acquired by FGDL from the source. AUTOID field based on FID + 1, GeoPlan Center feature identification number. Finally the attribute table was upper-cased and the metadata was updated. Process Date: 20080319
Data imported to ArcSDE and exported as a shapefile. Process Date: 20080327
MAP PROJECTION PARAMETERS:

Projection                          ALBERS
Datum                               HPGN
Units                               METERS
Spheroid                            GRS1980
1st Standard Parallel               24  0  0.000
2nd Standard Parallel               31 30  0.000
Central Meridian                   -84 00  0.000
Latitude of Projection's Origin     24  0  0.000
False Easting (meters)              400000.00000
False Northing (meters)             0.00000

DATA SOURCE CONTACT (S):

Name:
Abbr. Name:
Address:


Phone:

Web site:
E-mail:
Contact Person:
         Phone:
        E-mail:
Florida Division of Emergency Management
FDEM
2555 Shumard Oak Boulevard
Tallahassee, FL
32399-2100
850-413-9907

www.floridadisaster.org/gis gis@em.myflorida.com Richard Butgereit

FGDL CONTACT:
Name:                   FLORIDA GEOGRAPHIC DATA LIBRARY
Abbr. Name:             FGDL
Address:                Florida Geographic Data Library
                        431 Architecture Building
                        PO Box 115706
                        Gainesville, FL  32611-5706
Web site:               http://www.fgdl.org

Contact FGDL: 

      Technical Support:	        http://www.fgdl.org/fgdlfeed.html
      FGDL Frequently Asked Questions:  http://www.fgdl.org/fgdlfaq.html
      FGDL Mailing Lists:		http://www.fgdl.org/fgdl-l.html
      For FGDL Software:                http://www.fgdl.org/software.html