FGDL Documentation

FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION
VERSION 2006

TITLE: FDOT DISTRICT 2 - LAW ENFORCEMENT ZONES

Geodataset Name:       LAWZONES_D2_JUN06
Geodataset Type:       Shapefile
Geodataset Feature:    POLYGON
Feature Count:         152

GENERAL DESCRIPTION:

This dataset contains law enforcement zones located in FDOT District 2. This layer includes the primary responsible department . This GIS layer was produced by the North Central Florida Regional Planning Council (NCFRPC) under contract with FDOT District 2 in early 2005, and by the Northeast Florida Regional Planning Council (NEFRPC) under contract with FDOT District 2 in early 2006.

DATA SOURCE(S):                    NCFRPC, NEFRPC, GeoPlan Center
SCALE OF ORIGINAL SOURCE MAPS:     VARIES
DATE OF AUTOMATION OF SOURCE:      20060614
GEODATASET EXTENT:                 FDOT District 2

FEATURE ATTRIBUTE TABLES:

Datafile Name: LAWZONES_D2_JUN06.DBF

ITEM NAME	WIDTH	TYPE
AUTOID	6	Number
Shape
NAME	100	String
ZONE	75	String
MUNICIPAL	30	String
ZONE_NMBR	15	String
COUNTY	20	String
DESCRIPT	100	String
SOURCE	20	String
FLAG	5	String
UPDATE_DAY	8	Date
OBJECTID	4	OID
SHAPE	4	Geometry
SHAPE.AREA	0	Double
FGDLAQDATE	8	Date
SHAPE.LEN	0	Double

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description

AUTOID GeoPlan Center internal feature number

Shape Feature geometry.

NAME Law enforcement agency designation

ZONE Abbreviation of law enforcement agency.

MUNICIPAL Responsible governing unit, county or city.

ZONE_NMBR Zone number designation.

COUNTY County of operating law enforcment agency.

DESCRIPT Based on 'NAME'

SOURCE The source from which FGDL acquired the data

FLAG Type of update that occured

A = Attribute edit
S = Spatial edit.
B = Both spatial and attribute edit.
N = New
D = Delete
NIN = Not in the new.

UPDATE_DAY The last day the file was updated by the source

OBJECTID Internal feature number.

SHAPE Feature geometry.

SHAPE.AREA No description

FGDLAQDATE The date FGDL acquired the data from the source.

SHAPE.LEN No description

USER NOTES:

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. Sub-zones not provided by the cities.

GeoPlan relied on the integrity of the attribute information within the original data.

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

A note concerning data scale: Scale is an important factor in data usage. Certain scale datasetsare 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:250000 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 analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References sectionand the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: http://www.geoplan.ufl.edu/education.html

REFERENCES:

North Central Florida Regional Planning Council NCFRPC 2009 N.W. 67th Place, Suite A Gainesville, FL 32653 407-314-8683 http://www.ncfrpc.org/ Carol Laine laine@ncfrpc.org Northeast Florida Regional Planning Council NEFRPC 6850 Belfort Oaks Place Jacksonville, FL 32216 (904) 279-0880 Fax (904) 279-0881 http://www.nefrpc.org/ info@nefrc.org Keith Joiner KJoiner@nefrc.org

DATA LINEAGE SUMMARY:

North Central Florida Regional Planning Council - Process Steps: ALACHUA: Used Alachua County Growth Management "Municipal" shape file from their web site downloads, select by attribute "Gainesville, Alacuha, High Springs, Waldo" which are cities with their own police force. The used the "Florida Counties" shape file from GeoPlan and selected "Alachua County". Performed a "union' on the resiltant seltects from "counties and municipals" to create data set "Q" which is all municipalities and the rest of the county. From the Alachua County Property Appraiser "2005 Parcel" data set, "select by attribute" all parcels whos "GIS.Lastname" was equal to "STATE UNIVERSITY" or "STATE OF FLORIDA IIF" or "UNIVERSITY ATHLETIC ASSOCIATION" or STATE OF FLA IIF" or "U OF F FOUNDATION INC" or "U OF F FOUNDATION TRUSTEE" or "UNIVERSITY OF FLORIDA" or "STATE BOARD OF EDUCATION" or "SANTA FE COMMUNITY COLLEGE" or "DISTRICT BOARD OF TRUSTEES OF" or "SOUTHEASTERN HEATHCARE FOUNDATION" or "SHANDS TEACHING HOSPITAL &". Classified parcels as UF or SANTA FE, then did a dissolve on the parcels and did a "union" to the "Q" data set to create the final "AC_leszones" shapefile. ALACHUA: Intersected the file with Alachua County E911 sheriff zone map. BRADFORD: Used county EOC provided shapefile to determine boundaries and coverage area. COLUMBIA: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time. DIXIE: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time. GILCHRIST: Copied Gilchrist county property appreaiser cities data set and FGDL county data set and selected Gilchrist county and Trenton and Trenton Annex. Exported selected to new shape file. Dissolved Trenton and Trenton Annex. to have 2 zone. HAMILTON: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time. Used Hamilton county provided data set to digitize clean polygons for data set and identify zomes. LAFEYETTE: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time. LEVY: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time. MADISON: Used county EOC provided shapefile to determine boundaries and coverage area. SUWANNEE: Used information from talking to Suwannee County EOC to determine boundaries and coverage area. Used cities 2002 for LEZ coverage area. TAYLOR: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time. UNION: Used county EOC provided shapefile to determine boundaries and coverage area. Process Date: 20050601
Northeast Florida Regional Planning Council - Process Steps: The polygons were obtained from the respective agencies then the St. Johns River Water District county boundaries polygon coverage was used as the defining boundary between each county. Some of the boundaries had to be appended in order to clip each seperate county to match the SJRWMD county boundary. After each county was clipped to it's respective SJRWMD county boundary all of the counties were merged together as a singel featureclass(shapefile). Process Date: 20060501
GeoPlan Center - Process Steps: GeoPlan received this data and performed the following: -Reprojected to the FGDL Albers HPGN map projection -Merged datasets together to create one FDOT District-wide shapefile. -added the fields 'COUNTY' based on actual county. -added FGDLAQDATE field based on the date FGDL acquired the data from the source. -added DESCRIPT field based on 'NAME'. Process Date: 20060614
Metadata imported. Process Date:

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:

GeoPlan Center - University of Florida
GeoPlan Center
431 ARCH BLDG
Gainesville, FL
32611




image@fgdl.org
Kate Norris

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