{D6E43E8E-7CBC-48B9-BE69-676D50EE3A71}2004070615381500FALSE20041022152910002004102215291000enThis dataset contains 2003 Law Enforcement Information for the
State of Florida. It is a combination of Law Enforcement addresses
from (1) the Florida Department of Law Enforcement and (2) the
Yellow Pages online. The data contains selected fields denoting
the physical address, number, regions, and contact information for
Law Enforecement Facilities and Agencies located in Florida.The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes.POINTFlorida Department of Law Enforcement / Yellow Pages20030000LAW ENFORCEMENTgc_lawenforcevector digital datahttp://www.fdle.state.fl.us/State of Florida2003publication date20030000As needed-87.429040-79.87225130.98319124.49281575242.755207793759.28502863408.063441775399.388776NONELaw EnforcementFloridaNONETHE 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 modelling 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.htmlSHAPEFILEWeb site: http://www.fgdl.orgTechnical Support: http://www.fgdl.org/fgdlfeed.htmlFor FGDL Software: http://www.fgdl.org/software.htmlFGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.htmlFGDL Mailing Lists: http://www.fgdl.org/fgdl-l.htmlmailing address431 Architecture PO Box 115706GainesvilleFlorida32611-5706Florida Geographic Data Library (FGDL)Web site: http://www.fgdl.orgYellow Pages Online:
www.yellowpages.com
FDLE:
http://www.fdle.state.fl.us/Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 9.0.0.535Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 9.0.0.535gc_lawenforce75242.755207793759.285028775399.38877663408.0634411-87.401027-79.87683930.98689924.5162811enFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local timeFlorida Department of Law Enforcementmailing address20041022http://www.esri.com/metadata/esriprof80.htmlESRI Metadata ProfileISO 19115 Geographic Information - MetadataDIS_ESRI1.0datasetThis data is intended for use with a Geographic Information Systems or Remote Sensing software package.THE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE 'MATERIALS') ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE 'DATA PROVIDERS'). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED 'AS IS'. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE QUALITY OR SUITABILITY OF THE MATERIALS, EITHER EXPRESSLY OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. 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.Florida Geographic Data Library (FGDL)mailing address431 Architecture PO Box 115706GainesvilleFlorida32611-5706United StatesWeb site: http://www.fgdl.orgTechnical Support: http://www.fgdl.org/fgdlfeed.htmlFor FGDL Software: http://www.fgdl.org/software.htmlFGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.htmlMailing list for FGDL: http://www.fgdl.org/fgdl-l.htmlGC_LAWENFORCE, FGDL Version 20040.0130.013This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlanThis data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlanThis data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topologyThis 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.Relied on the integrity of the attribute information within the originl data layerRelied on the integrity of the attribute information within the originl data layerThis dataset is a combination of law enforcement addresses from (1)
the Florida Department of Law Enforcement and (2) the Yellow Pages
online. Since more sherif facilities exist than were included in the
FDLE website, addresses were also obtained from the Yellow Pages to
insure a complete spatial representation of law enforcement facility
locations.The following dataset was Geocoded against ARC Logistics Route GDT
Roads. Address information was obtained via a website or through a
spreadsheet gained from an agency. The data was reformatted using a
text editor in order to create data that could be imported into
excel. From this data, dbfs were created that could then be used
for Geocoding/Address Matching.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.publication dateSpatial and Attribute InformationFlorida Department of Law Enforcement / Yellow Pages20030000LAW ENFORCEMENTvector digital datahttp://www.fdle.state.fl.us/N/A20030000publication dateFDLEonlinevector digital dataLaw Enforcement addresses were obtained through the FDLE website or
the Yellow Pages Online. These addresses were copied into a textfile,
which was converted to a database file. The database file was geocoded
against ARC Logistics Route GDT Roads, and converted into a shapefile
with the FGDL Albers HPGN map projection.
-Obtained Law Enforcement addresses through FDLE website
www.fdle.state.fl.us and Yellow Pages Online.
-Copied law enforcement addresses into textfile
-Converted text file to database file format
-Geocoded against ARC Logistics Route GDT Roads
Shapefile created using FGDL Albers HPGN map projection (See "Map
Projection Parameters" below).
Process Steps for FDLE Law Enforcement Data:
-Downloaded Law Enforcment facility data in textfile format from
the FDLE website:
http://www.fdle.state.fl.us/cjst/Professionalism/AgencyAddresses
-Converted the facility locations text file to database file format
Process Steps for Yellow Pages Law Enforcement Data:
-Searched for law enforcment addresses in www.yellowpages.com
-Selected law enforcement addresses under following categories:
Sheriffs Office (326)
-All addresses from sections above were copied and pasted into a
textfile, which was then formatted so that it could be imported
into Excel and converted to a database file format.
Process Steps for Both USFA and Yellow Pages data:
-Both database files of law enforcement facilities were compared to
remove duplicate addresses.
-Both database files were combined
The addresses were geocoded against ARC Logistics Route GDT Roads
Shapefile created using FGDL Albers HPGN map projection
-Added DESCRIPT field based on NAMEGeoPlan2003Socio-Cultural Effect data fields and definitions were added.
FLAG, UPDATE_DAY, AUTOID, NAME, ADDRESS, CITY,
ZIPCODE, OPERATING, OP_CLASS, SUBTYPE,
COMMON_USE, USE, YR_BUILT.GeoPlan20041021coordinate pair0.0020480.002048metersAlbers Conical Equal Area24.00000031.500000-84.00000024.000000400000.0000000.000000Albers Conical Equal AreaHPGNGeodetic Reference System 806378137.000000298.257222GCS_North_American_1983_HARND_North_American_1983_HARNGeodetic Reference System 806378137.000000298.257222Jason ShieldsMarin County, Govt.GIS Analyst6166 Kansas StreetSausalitoCalifornia94920usjpshields@ci.saulsalito.ca.us(415)289-1010(415)289-0000002file://\\atlas\qaqc\data_output\kate\socialcultural_data\sce_point_poly_data\gc_lawenforce.shpLocal Area Network0.013ShapefileVectorSimplePointFALSE493TRUEFALSEEntity point493Albers Conical Equal Area (Florida Geographic Data Library)493GC_LAWENFORCEFeature Class493GC_LAWENFORCE.DBFFDLEFIDFIDOID400Internal feature number.ESRISequential unique whole numbers that are automatically generated.ShapeShapeGeometry000Feature geometry.ESRICoordinates defining the features.StatusStatusString1ESRI item which denotes the status of the geocoded address whether it was matched or not).ScoreScoreNumber4ESRI item which denotes the score with which the address was matched to a feature in the reference data.SideSideString1ESRI 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).IDIDString15Internal ID #NAMENAMEString100Law enforcement agency designationADDRESSADDRESSString65A description of a facility's physical location providing direction for delivery and provision of emergency servicesCITYCITYString40City of facility's physical locationZIPCODEZIPCODENumber9US postal delivery designation of facility's physical locationTYPETYPEString40The type of Law Enforcement faciltiy.FDLESUBTYPESUBTYPEString25Category of agencyOPERATINGOPERATINGString50The responsible organization for management and operation of a facility (e.g., public, private, quasi-public)OP_CLASSOP_CLASSString40Classification of the operating entityCOMMON_USECOMMON_USEString4Location of two or more uses in one facility or on common grounds so as to share common facilitiesUSEUSEString50Description of co-located use, if applicableYR_BUILTYR_BUILTNumber4The year a structure was built for determining possible historical significanceDESCRIPTDESCRIPTString33FGDL added item based on TYPEFLAGFLAGString5AAttribute editSSpatial editBBoth attribute and spatial editNNewDDeleteType of update that occurredUPDATE_DAYUPDATE_DAYDate8The last day the file was updatedAUTOIDAUTOIDNumber6Internal ID #20041022