FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: LAW ENFORCEMENT FACILITIES 2008 Geodataset Name: GC_LAWENFORCE_FEB08 Geodataset Type: SHAPEFILE Geodataset Feature: Point Feature Count: 988 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): University of Florida GeoPlan Center SCALE OF ORIGINAL SOURCE MAPS: Varies DATE OF AUTOMATION OF SOURCE: 20080227 GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: GC_LAWENFORCE_FEB08.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
STATUS
|
1 | String |
SCORE
|
2 | SmallInteger |
SIDE
|
1 | String |
MATCH_ADDR
|
83 | String |
NAME
|
100 | String |
ADDRESS
|
65 | String |
CITY
|
40 | String |
ZIPCODE
|
4 | Integer |
COUNTY
|
20 | String |
PHONE
|
20 | String |
CONTACT
|
30 | String |
TITLE
|
40 | String |
AGENCY_ID
|
20 | String |
TYPE
|
40 | String |
SUBTYPE
|
25 | String |
OPERATING
|
50 | String |
OP_CLASS
|
40 | String |
COMMON_USE
|
4 | String |
USE
|
50 | String |
YR_BUILT
|
2 | SmallInteger |
SOURCE
|
20 | String |
USNG_FL_1K
|
10 | String |
DESCRIPT
|
40 | String |
OLD_AUTOID
|
4 | Integer |
FLAG
|
5 | String |
UPDATE_DAY
|
36 | Date |
FGDLAQDATE
|
36 | Date |
AUTOID
|
4 | Integer |
SHAPE
|
4 | Geometry |
LAT_DD
|
8 | Double |
LONG_DD
|
8 | Double |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
STATUS |
ESRI item which denotes the status of the geocoded address whether it was matched or not). |
|
SCORE |
ESRI item which denotes the score with which the address was matched to a feature in the reference data. |
|
SIDE |
ESRI item which denotes the side of the street to which the address was matched (for geocoding service styles that can match an address to a particular side of a street). Records markerd with an "*" have not been GeoCoded, these records have another type of spatial reference source, see source field for more information. |
|
MATCH_ADDR |
ESRI item which denotes the full street layer address to which the address was matched. |
|
NAME |
Law enforcement agency designation. |
|
ADDRESS |
A description of a facility's physical location providing direction for delivery and provision of emergency services. |
|
CITY |
City of facility's physical location. |
|
ZIPCODE |
US postal delivery designation of facility's physical location. |
|
COUNTY |
County of facility's physical location. |
|
PHONE |
Phone number of the facility. |
|
CONTACT |
Name of the contact at the facility. |
|
TITLE |
Title of the contact at the facility. |
|
AGENCY_ID |
Agency identification number. |
|
TYPE |
The type of Law Enforcement faciltiy (Corrections, FDLE, Federal, Highway Patrol, Law Enforecement, Police, Police-University, and Sheriff). |
|
SUBTYPE |
SUBTYPE Category of agency. |
|
OPERATING |
The responsible organization for management and operation of a facility (e.g., public, private, quasi-public). |
|
OP_CLASS |
Classification of the operating entity. |
|
COMMON_USE |
Location of two or more uses in one facility or on common grounds so as to share common facilities. |
|
USE |
Description of co-located use, if applicable. |
|
YR_BUILT |
The year a structure was built for determining possible historical significance. |
|
SOURCE |
Source of the data. |
|
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 |
FGDL added item based on TYPE. |
|
OLD_AUTOID |
The AUTOID from the original source dataset. For the source = DATA TRANSFER SOLUTIONS the OLD_AUTOID field represents AUTOIDs from the lawstat_d5_jan07.shp dataset. For the source = NCFRPC and NEFRPC the OLD_AUTOID field represents AUTOIDs from the lawstat_d2_jun06.shp dataset. |
|
FLAG |
Type of update that occurred.
|
|
UPDATE_DAY |
The last day the file was updated by the Source. |
|
FGDLAQDATE |
The date FGDL aquired the data from the source. |
|
AUTOID |
GeoPlan Center feature identification number. |
|
SHAPE |
Feature geometry. |
|
LAT_DD |
Latitude in Decimal Degrees |
|
LONG_DD |
Longitude in Decimal Degrees |
This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology |
This data is provided 'as is' by GeoPlan and is complete to our knowledge. |
GeoPlan relied on the integrity of the attribute information within the original data. |
What is Geocoding? Geocoding is term used to describe the act of address matching. Geocoding is the process of finding a geographic location (x, y point) for an address (such as street number and name, city, state, and ZIP Code) on a map. Geocoding is based off the typical address scheme for the US, in which one side of the street contains even house numbers while the other side of the street contains odd house numbers. The geocoding process uses an algorithm to find the geographic location of addresses. First, a street segment is identified using the zip code and street name. Next, the geographic location of the address is matched using the building number to determine how far down the street and on which side of the street the building is located. Geocoding Accuracy The locational accuracy of geocoded addresses may vary from urban to rural areas due to the algorithm used to generate the geographic locations of addresses. The algorithm assumes that the size of parcels are equivalent along a road route. This assumption tends to be more consistent in urban areas, where the size of parcels vary less than in rural areas. Consequently, the results of geocoded addresses in urban areas are usually more reliable than those in rural areas. For example, the locational accuracy of rural addresses can be slightly off because some parcels along a rural route may be 15 acres while others may be 2.5 acres, but the geocoding algorithm assumes that the addresses are distributed evenly along the route. |
The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes. |
This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan |
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 |
Yellow Pages Online: www.yellowpages.com Super Pages Online: www.superpages.com Florida Department of Law Enforcement FDLE Mailing Address: Florida Department of Law Enforcement P.O. Box 1489 Tallahassee, FL 32302-1489 Phone: 1-850-410-7000 E-Mail: info@fdle.state.fl.us Website: http://www.fdle.state.fl.us/ |
The GeoPlan Center performed the following steps in order to create the 2008 statewide law enforcement facilities data layer. 32 Different Sources Comprise the Law Enforcement Facility Dataset. The following sources were either reprojected to the FGDL Albers NAD83 HPGN map projection or if no spatial data existed they were geocoded to a statewide 2007 TelAtlas Streets dataset. Once the point sources were created via geocoding or reprojected they were merged into one statewide layer. Record (facility) duplications were removed by manually viewing the table for each of the 67 counties. Where record duplication existed source information of previously corrected FDOT Districts and Regional Planning Council data took preference followed by, County data, and finally geocoded data. Below are the data Sources as described in the Source field in the attribute table. Process Date: 20080227 |
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: |
University of Florida GeoPlan Center GeoPlan 431 Architecture, PO Box 11570 Gainesville, FL 32611-570 |
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