Louisville Metro Police Department Districts & Beats
SDE Feature Class - JEFLIB.lmpd
FGDC, ESRI Metadata
DescriptionSpatialData StructureData SourceData DistributionMetadata
+ Resource Description
Citation
Information used to reference the data.
Title: Louisville Metro Police Department Districts & Beats
Originators: Louisville Metro Police Districts, Sectors and Zones
Publication date: 9/2004
Data type: vector digital data
Data location: Server=lojicora1; Service=esri_sde; User=jeflib; Version=SDE.DEFAULT
Description
A characterization of the data, including its intended use and limitations.
Abstract: 
Polygons of Louisville metro Police Districts and Police Beats. Polygons have attributes for identifying Metro Police Districts, Police Beats, Police Reporting Areas (PRA), sectors and zones.
Purpose: 
Creation of Metro Police Maps and other general use.
Language of dataset: en
Point Of Contact
Contact information for the individual or organization that is knowledgeable about the data.
Person: Mike Tully
Organization: Louisville Metro Planning and Design Services
Phone: (502) 574-0105
Fax: (502) 574-5163
Email: Michael.Tully@metrolouky.gov
Address type: mailing and physical address
Address: 
444 South fifth street
City: Louisville
State or Province: Kentucky
Postal code: 40202
Data Type
How the data are represented, formatted and maintained by the data producing organization.
File or table name: JEFLIB.lmpd
Data type: vector digital data
Data format: SDE Feature Class
Native dataset environment: Microsoft Windows Vista Version 6.1 (Build 7600) ; ESRI ArcCatalog 9.3.1.3000
Time Period of Data
Time period(s) for which the data corresponds to the currentness reference.
Date: 10/2004
Currentness reference: 
ground condition
Status
The state of and maintenance information for the data.
Data status: Complete
Update frequency: As needed
Key Words
Words or phrases that summarize certain aspects of the data.
Theme:
Keywords: jeflib lmpd emergency police response cad e911
Place:
Keywords: Louisville Jefferson Kentucky KY
Data Access Constraints
Restrictions and legal prerequisites for accessing or using the data after access is granted.
Access constraints: 
Data access is restricted to LOJIC Participants, their contractors and Licensees only
Use constraints: 
LIMITATION OF LIABILITY: MSD and the participants of the Louisville/Jefferson County Information Consortium (LOJIC) have no indication or reason to believe that there are any inaccuracies or defects of information incorporated in this work and make NO REPRESENTATIONS OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, THE WARRANTIES OF MERCHANTBILITY OR FITNESS FOR A PARTICULAR USE, NOR ARE ANY SUCH WARRANTIES TO BE IMPLIED, WITH RESPECT TO THE INFORMATION OR DATA, FURNISHED HEREIN.

The attached data is owned by the LOJIC participants and is protected by United States Copyright laws and applicable international copyright treaties and/or conventions.
+ Spatial Reference Information
Horizontal Coordinate System
Reference system from which linear or angular quantities are measured and assigned to the position that a point occupies.
Projected coordinate system:
Name: NAD 1983 StatePlane Kentucky North FIPS 1601 Feet
Map units: survey feet
Geographic coordinate system:
Name: GCS North American 1983
Coordinate System Details
Map projection
Map projection name: Lambert Conformal Conic
Standard parallel: 37.966667
Standard parallel: 38.966667
Longitude of central meridian: -84.250000
Latitude of projection origin: 37.500000
False easting: 1640416.666667
False northing: 0.000000
Planar Coordinate Information
Planar coordinate encoding method: coordinate pair
Coordinate representation:
Abscissa resolution: 0.001250
Ordinate resolution: 0.001250
Planar distance units: survey feet
Geodetic model
Horizontal datum name: North American Datum of 1983
Ellipsoid name: Geodetic Reference System 80
Semi-major axis: 6378137.000000
Denominator of flattening ratio: 298.257222
Vertical Coordinate System
Reference system from which vertical distances (altitudes or depths) are measured.
Altitude system definition:
Altitude resolution: 1.000000
Altitude encoding method: Explicit elevation coordinate included with horizontal coordinates
Spatial Domain
The geographic areal domain of the data that describes the western, eastern, northern, and southern geographic limits of data coverage.
Bounding Coordinates
In Projected or local coordinates
NAD 1983 StatePlane Kentucky North FIPS 1601 Feet
Boundary Coordinate
Left 1150904.250000 (survey feet)
Right 1309162.375000 (survey feet)
Top 323711.500000 (survey feet)
Bottom 185470.160000 (survey feet)
In Unprojected coordinates (geographic)
GCS North American 1983
Boundary Coordinate
West -85.957657 (longitude)
East -85.399628 (longitude)
North 38.383214 (latitude)
South 37.996911 (latitude)
+ Data Structure and Attribute Information
Overview
Summary of the information content of the data, including other references to complete descriptions of entity types, attributes, and attribute values for the data.
Direct spatial reference method: Vector
Attributes of JEFLIB.lmpd
Detailed descriptions of entity type, attributes, and attribute values for the data.
Name: JEFLIB.lmpd
Type of object: Feature Class
Geometry type: Polygon
Number of records: 207
Attributes
DISTRICT
Definition: 
Metro Police District
Alias: DISTRICT Type: String Width: 20 Precision: 0 Scale: 0
PRA
Definition: 
Metro Police Reporting Area
Alias: PRA Type: String Width: 5 Precision: 0 Scale: 0
ZONE
Definition: 
Metro Police Dispatching Zone
Alias: ZONE Type: String Width: 3 Precision: 0 Scale: 0
BEAT
Definition: 
Metro Police Beat
Alias: BEAT Type: String Width: 5 Precision: 0 Scale: 0
OBJECTID
Definition: 
Internal feature number.
Alias: OBJECTID Type: OID Width: 4 Precision: 10 Scale: 0
Attribute values: Sequential unique whole numbers that are automatically generated.
Attribute definition source: 
ESRI
SECTOR
Definition: 
Metro Police Sector
Alias: SECTOR Type: String Width: 5 Precision: 0 Scale: 0
LMPD_WEB
Alias: LMPD_WEB Type: String Width: 75 Precision: 0 Scale: 0
DIST_DESC
Alias: DIST_DESC Type: String Width: 75 Precision: 0 Scale: 0
CAD_PRA
Alias: CAD_PRA Type: String Width: 5 Precision: 0 Scale: 0
JEFLIB.lmpd.AREA
Alias: AREA Type: Double Width: 8 Precision: 38 Scale: 8
JEFLIB.lmpd.LEN
Alias: LEN Type: Double Width: 8 Precision: 38 Scale: 8
SHAPE
Definition: 
Feature geometry.
Alias: Shape Type: Geometry Width: 4 Precision: 0 Scale: 0
Attribute values: Coordinates defining the features.
Attribute definition source: 
ESRI
SHAPE.AREA
Alias: SHAPE.AREA Type: Double Width: 0 Precision: 0 Scale: 0
SHAPE.LEN
Alias: SHAPE.LEN Type: Double Width: 0 Precision: 0 Scale: 0
ESRI Feature Description
Description of spatial objects in the data using the Environmental Systems Research Institute (ESRI) terminology.
Environmental Systems Research Institute (ESRI) terms
JEFLIB.lmpd
ESRI feature type: Simple
Geometry type: Polygon
Topology: TRUE
Feature count: 207
Spatial index: TRUE
Linear referencing: FALSE
XY Rank: 1
Z Rank: 1
Topology weight: 5.000000
Events on validation: FALSE
Participates in topology rules:
Rule Id: 4896, 4897
SDTS Feature Description
Description of point and vector spatial objects in the data using the Spatial Data Transfer Standards (SDTS) terminology.
Spatial data transfer standard (SDTS) terms
JEFLIB.lmpd
Type: G-polygon
Count: 207
+ Data Source and Process Information
Process Steps
Information about events, parameters, tolerances and techniques applied to construct or derive the data.
Process step information
Process Step 1
Process description: 
Using Metro Police Maps as a source lines and polygon were created through ArcMap using the street centerlines as boundary delineators.
Process Step 2
Process description: 
Metadata imported.
Data Source used
V:\a2metadata\JEFLIB\LMPD.xml
Process Step 3
Process description: 
Metadata imported.
Data Source used
H:\MetaData_Transfer\Jeflib\lmpd.xml
Process Step 4
Process description: 
Dataset copied.
Data Source used
Server=lojicora1; Service=esri_sde; User=jeflib; Version=SDE.DEFAULT
ESRI geoprocessing history
Description of ESRI geoprocessing commands, settings, and tolerances applied to the data.
ESRI geoprocessing command information
1 FeatureClassToFeatureClass_3
Date: 20080726 Time: 082015
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Conversion Tools.tbx\FeatureClassToFeatureClass
Command issued: FeatureClassToFeatureClass "Database Connections\pu_jeflib.sde\JEFLIB.CAD\JEFLIB.lmpd" "Database Connections\pu_jeflib.sde\JEFLIB.CAD_1" JEFLIB_lmpd # "DISTRICT DISTRICT true true false 20 Text 0 0 ,First,#,Database Connections\pu_jeflib.sde\JEFLIB.CAD\JEFLIB.lmpd,DISTRICT,-1,-1;SECTOR SECTOR true true false 5 Text 0 0 ,First,#,Database Connections\pu_jeflib.sde\JEFLIB.CAD\JEFLIB.lmpd,SECTOR,-1,-1;BEAT BEAT true true false 5 Text 0 0 ,First,#,Database Connections\pu_jeflib.sde\JEFLIB.CAD\JEFLIB.lmpd,BEAT,-1,-1;PRA PRA true true false 5 Text 0 0 ,First,#,Database Connections\pu_jeflib.sde\JEFLIB.CAD\JEFLIB.lmpd,PRA,-1,-1;LMPD_WEB LMPD_WEB true true false 75 Text 0 0 ,First,#,Database Connections\pu_jeflib.sde\JEFLIB.CAD\JEFLIB.lmpd,LMPD_WEB,-1,-1;DIST_DESC DIST_DESC true true false 75 Text 0 0 ,First,#,Database Connections\pu_jeflib.sde\JEFLIB.CAD\JEFLIB.lmpd,DIST_DESC,-1,-1;ZONE ZONE true true false 3 Text 0 0 ,First,#,Database Connections\pu_jeflib.sde\JEFLIB.CAD\JEFLIB.lmpd,ZONE,-1,-1;CAD_PRA CAD_PRA true true false 5 Text 0 0 ,First,#,Database Connections\pu_jeflib.sde\JEFLIB.CAD\JEFLIB.lmpd,CAD_PRA,-1,-1;AREA AREA false false true 0 Double 0 0 ,First,#,Database Connections\pu_jeflib.sde\JEFLIB.CAD\JEFLIB.lmpd,SHAPE.AREA,-1,-1;LEN LEN false false true 0 Double 0 0 ,First,#,Database Connections\pu_jeflib.sde\JEFLIB.CAD\JEFLIB.lmpd,SHAPE.LEN,-1,-1" # "Database Connections\pu_jeflib.sde\JEFLIB.CAD_1\JEFLIB.JEFLIB_lmpd"
+ Data Distribution Information
General
Description of the data known by the party from whom the data may be obtained, liability of party distributing data, and technical capabilities required to use the data.
Resource description: 
Downloadable Data
+ Metadata Reference
Metadata Date
Dates associated with creating, updating and reviewing the metadata.
Last updated: 20100907
Language of metadata: en
Metadata Point of Contact
Contact information for the individual or organization responsible for the metadata information.
Organization: LOJIC
Person: Jeff Ackerman
Phone: (502) 540-6372
Fax: (502) 540-6499
Email: ackerman@lojic.org
Address type: mailing and physical address
Address: 
700 West Liberty St.
City: Louisville
State or Province: Kentucky
Postal code: 40203
Metadata Standards
Description of the metadata standard used to document the data and reference to any additional extended profiles to the standard used by the metadata producer.
Standard name: FGDC Content Standards for Digital Geospatial Metadata
Standard version: FGDC-STD-001-1998
Time convention: local time
Metadata profiles defining additonal information:
Profile: ESRI Metadata Profile
Online linkage: http://www.esri.com/metadata/esriprof80.html
Profile: ESRI Metadata Profile
Online linkage: http://www.esri.com/metadata/esriprof80.html
FGDC Plus Metadata Stylesheet
Stylesheet: FGDC Plus Stylesheet
File name: FGDC Plus.xsl
Version: 2.2
Description: This metadata is displayed using the FGDC Plus Stylesheet, which is an XSL template that can be used with ArcGIS software to display metadata. It displays metadata elements defined in the Content Standard for Digital Geospatial Metadata (CSDGM) - aka FGDC Standard, the ESRI Profile of CSDGM, the Biological Data Profile of CSDGM, and the Shoreline Data Profile of CSDGM. CSDGM is the US Federal Metadata standard. The Federal Geographic Data Committee originally adopted the CSDGM in 1994 and revised it in 1998. According to Executive Order 12096 all Federal agencies are ordered to use this standard to document geospatial data created as of January, 1995. The standard is often referred to as the FGDC Metadata Standard and has been implemented beyond the federal level with State and local governments adopting the metadata standard as well. The Biological Data Profile broadens the application of the CSDGM so that it is more easily applied to biological data that are not explicitly geographic (laboratory results, field notes, specimen collections, research reports) but can be associated with a geographic location. Includes taxonomical vocabulary. The Shoreline Data Profile addresses variability in the definition and mapping of shorelines by providing a standardized set of terms and data elements required to support metadata for shoreline and coastal data sets. The FGDC Plus Stylesheet includes the Dublin Core Metadata Element Set. It supports W3C DOM compatible browsers such as IE7, IE6, Netscape 7, and Mozilla Firefox. It is in the public domain and may be freely used, modified, and redistributed. It is provided "AS-IS" without warranty or technical support.
Instructions: On the top of the page, click on the title of the dataset to toggle opening and closing of all metadata content sections or click section links listed horizontally below the title to open individual sections. Click on a section name (e.g. Description) to open and close section content. Within a section, click on a item name (Status, Key Words, etc.) to open and close individual content items. By default, the Citation information within the Description section is always open for display.
Download: FGDC Plus Stylesheet is available from the ArcScripts downloads at www.esri.com.
Federal Geographic Data Committee