Municipal Boundary, Polygon
SDE Feature Class - JEFLIB.municbnd
FGDC, ESRI Metadata
DescriptionSpatialData StructureData SourceData DistributionMetadata
+ Resource Description
Citation
Information used to reference the data.
Title: Municipal Boundary, Polygon
Originators: Louisville Metro Planning and Design Services
Publication date: 01/06/2003
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 all classes of cities in Jefferson County; polygons have attributes for city names, classes and codes.
Purpose: 
Cartographics and overlay for spatial analysis on municipality.
Supplemental information: 
Suburban city boundaries were digitized against 1:1200 digital plan/topo base map from 1:4800 local zoning maps and annexation descriptions. County boundary at the 1792 low water mark of the Ohio River Data was generated from coordinates from a 1985 survey resulting from a 1980 U.S. Supreme Court decision (Ohio v Kentucky, 444 U.S. 335). County boundary inland from the Ohio River was digitized from 1:24000 USGS Topographic Quadrangle maps. Data maintenance has involved only correction of major boundary errors discovered through actual use of the data.
Language of dataset: en
Point Of Contact
Contact information for the individual or organization that is knowledgeable about the data.
Person: Ron Reynolds
Organization: Louisville Metro Planning and Design Services
Phone: (502) 574-8243
Fax: (502) 574-5163
Email: Ron.reynolds@louisvilleky.gov
Address type: mailing and physical address
Address: 
444 S. Fifth St.
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.municbnd
Data type: vector digital data
Data format: SDE Feature Class
Native dataset environment: Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.3.1.3000
Time Period of Data
Time period(s) for which the data corresponds to the currentness reference.
Date: 2002
Currentness reference: 
publication date
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 municbnd political municipal municipality city cities
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 1151431.750000 (survey feet)
Right 1308825.953750 (survey feet)
Top 323544.000000 (survey feet)
Bottom 185470.156250 (survey feet)
In Unprojected coordinates (geographic)
GCS North American 1983
Boundary Coordinate
West -85.955806 (longitude)
East -85.400795 (longitude)
North 38.382743 (latitude)
South 37.996938 (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.municbnd
Detailed descriptions of entity type, attributes, and attribute values for the data.
Name: JEFLIB.municbnd
Type of object: Feature Class
Geometry type: Polygon
Number of records: 84
Description: 
Municipal Boundary, Polygon
Source: 
LOJIC
Attributes
MUNI_CODE
Definition: 
12; value given to all cities in Louisville Metro (Jefferson County)
Alias: MUNI_CODE Type: Integer Width: 4 Precision: 10 Scale: 0
MUNI_NAME
Definition: 
City Names
Alias: MUNI_NAME Type: String Width: 30 Precision: 0 Scale: 0
Attribute domain values
Value Definition
ANCHORAGE (definition not provided)
AUDUBON PARK (definition not provided)
BANCROFT (definition not provided)
BARBOURMEADE (definition not provided)
BEECHWOOD VILLAGE (definition not provided)
BELLEMEADE (definition not provided)
BELLEWOOD (definition not provided)
BLUE RIDGE MANOR (definition not provided)
BRIARWOOD (definition not provided)
BROECK POINTE (definition not provided)
BROWNSBORO FARM (definition not provided)
BROWNSBORO VILLAGE (definition not provided)
CAMBRIDGE (definition not provided)
COLDSTREAM (definition not provided)
CREEKSIDE (definition not provided)
CROSSGATE (definition not provided)
DOUGLAS HILLS (definition not provided)
DRUID HILLS (definition not provided)
FINCASTLE (definition not provided)
FOREST HILLS (definition not provided)
GLENVIEW (definition not provided)
GLENVIEW HILLS (definition not provided)
GLENVIEW MANOR (definition not provided)
GOOSE CREEK (definition not provided)
GRAYMOOR/DEVONDALE (definition not provided)
GREEN SPRING (definition not provided)
HICKORY HILL (definition not provided)
HILLS AND DALES (definition not provided)
HOLLOW CREEK (definition not provided)
HOLLYVILLA (definition not provided)
HOUSTON ACRES (definition not provided)
HURSTBOURNE (definition not provided)
HURSTBOURNE ACRES (definition not provided)
INDIAN HILLS (definition not provided)
JEFFERSONTOWN (definition not provided)
KEENELAND (definition not provided)
KINGSLEY (definition not provided)
LANGDON PLACE (definition not provided)
LINCOLNSHIRE (definition not provided)
LOUISVILLE/JEFFERSON METRO GOV (definition not provided)
LYNDON (definition not provided)
LYNNVIEW (definition not provided)
MANOR CREEK (definition not provided)
MARYHILL ESTATES (definition not provided)
MEADOW VALE (definition not provided)
MEADOWBROOK FARM (definition not provided)
MEADOWVIEW ESTATES (definition not provided)
MIDDLETOWN (definition not provided)
MINOR LANE HEIGHTS (definition not provided)
MOCKINGBIRD VALLEY (definition not provided)
MOORLAND (definition not provided)
MURRAY HILL (definition not provided)
NORBOURNE ESTATES (definition not provided)
NORTHFIELD (definition not provided)
NORWOOD (definition not provided)
OLD BROWNSBORO PLACE (definition not provided)
PARKWAY VILLAGE (definition not provided)
PLANTATION (definition not provided)
POPLAR HILLS (definition not provided)
PROSPECT (definition not provided)
RICHLAWN (definition not provided)
RIVERWOOD (definition not provided)
ROLLING FIELDS (definition not provided)
ROLLING HILLS (definition not provided)
SENECA GARDENS (definition not provided)
SHIVELY (definition not provided)
SOUTH PARK VIEW (definition not provided)
SPRING MILL (definition not provided)
SPRING VALLEY (definition not provided)
ST MATTHEWS (definition not provided)
ST REGIS PARK (definition not provided)
STRATHMOOR MANOR (definition not provided)
STRATHMOOR VILLAGE (definition not provided)
SYCAMORE (definition not provided)
TEN BROECK (definition not provided)
THORNHILL (definition not provided)
WATTERSON PARK (definition not provided)
WELLINGTON (definition not provided)
WEST BUECHEL (definition not provided)
WESTWOOD (definition not provided)
WHIPPS MILLGATE (definition not provided)
WILDWOOD (definition not provided)
WINDY HILLS (definition not provided)
WOODLAND HILLS (definition not provided)
WOODLAWN PARK (definition not provided)
WORTHINGTON HILLS (definition not provided)
MUNI_CLASS
Definition: 
Class of City (1,2,3,4,5 or 6)
Alias: MUNI_CLASS Type: Integer Width: 4 Precision: 10 Scale: 0
Attribute domain values
Value Definition
1 
1st Class City
2 
2nd Class City
3 
3rd Class City
4 
4th Class City
5 
5th Class City
6 
6th Class City
MUNCODE
Definition: 
Municipal code from Land Mgt Information System (LMIS)
Alias: MUNCODE Type: Integer Width: 4 Precision: 10 Scale: 0
Attribute domain values
Value Definition
1 
ANCHORAGE
2 
AUDUBON PARK
3 
BANCROFT
4 
BARBOURMEADE
5 
BEECHWOOD VILLAGE
6 
BELLEMEADE
7 
BELLEWOOD
8 
BLUE RIDGE MANOR
9 
BRIARWOOD
11 
BROECK POINTE
12 
BROWNSBORO FARM
13 
BROWNSBORO VILLAGE
14 
CAMBRIDGE
95 
COLDSTREAM
16 
CREEKSIDE
17 
CROSSGATE
19 
DOUGLAS HILLS
20 
DRUID HILLS
22 
FINCASTLE
23 
FOREST HILLS
98 
GLENVIEW
24 
GLENVIEW HILLS
25 
GLENVIEW MANOR
26 
GOOSE CREEK
27 
GRAYMOOR/DEVONDALE
28 
GREEN SPRING
29 
HICKORY HILL
30 
HILLS AND DALES
31 
HOLLOW CREEK
32 
HOLLYVILLA
33 
HOUSTON ACRES
91 
HURSTBOURNE
34 
HURSTBOURNE ACRES
35 
INDIAN HILLS
37 
JEFFERSONTOWN
38 
KEENELAND
39 
KINGSLEY
40 
LANGDON PLACE
41 
LINCOLNSHIRE
999 
LOUISVILLE/JEFFERSON METRO GOV
43 
LYNDON
44 
LYNNVIEW
45 
MANOR CREEK
46 
MARYHILL ESTATES
48 
MEADOW VALE
47 
MEADOWBROOK FARM
49 
MEADOWVIEW ESTATES
50 
MIDDLETOWN
51 
MINOR LANE HEIGHTS
52 
MOCKINGBIRD VALLEY
53 
MOORLAND
92 
MURRAY HILL
54 
NORBOURNE ESTATES
55 
NORTHFIELD
56 
NORWOOD
57 
OLD BROWNSBORO PLACE
58 
PARKWAY VILLAGE
59 
PLANTATION
93 
POPLAR HILLS
61 
PROSPECT
62 
RICHLAND
63 
RIVERWOOD
65 
ROLLING FIELDS
66 
ROLLING HILLS
69 
SENECA GARDENS
70 
SHIVELY
71 
SOUTH PARK VIEW
99 
SPRING MILL
96 
SPRING VALLEY
67 
ST MATTHEWS
68 
ST REGIS PARK
74 
STRATHMOOR MANOR
75 
STRATHMOOR VILLAGE
76 
SYCAMORE
77 
TEN BROECK
78 
THORNHILL
79 
WATTERSON PARK
82 
WELLINGTON
83 
WEST BUECHEL
80 
WESTWOOD
81 
WHIPPS MILLGATE
85 
WILDWOOD
86 
WINDY HILLS
87 
WOODLAND HILLS
88 
WOODLAND PARK
89 
WORTHINGTON HILLS
BND_VERIFY
Definition: 
The date the last section of boundary for a municipality is verified.  The date is a four (4) character year, two (2) character month and two (2) character date.
Alias: BND_VERIFY Type: Date Width: 36 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
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.municbnd
ESRI feature type: Simple
Geometry type: Polygon
Topology: FALSE
Feature count: 84
Spatial index: TRUE
Linear referencing: FALSE
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.municbnd
Type: G-polygon
Count: 84
+ Data Source and Process Information
Data Sources
Information about the source data used to construct or derive the data.
Data source information
Zoning maps and annexation descriptions
Originators: Louisville Metro Planning and Design Services
Map scale denominator: 4800
Media: Local zoning maps, annexation descriptions
1:1200 Plan/topo mapping
Map scale denominator: 1200
Media: Local plan/topo mapping
County boundary along Ohio River
Map scale denominator: 1200
Media: Survey coordinates
Inland county boundary
Map scale denominator: 24000
Media: USGS Topo Quad maps
Process Steps
Information about events, parameters, tolerances and techniques applied to construct or derive the data.
Process step information
Process Step 1
Process description: 
Suburban city coundaries originally digitized from zoning maps; boundaries adjusted to fit parcel boundaries; boundaries corrected against official annexation records. County boundary at 1792 low water mark of the Ohio River generated from coordinates from 1985 survey. Inland county boundary was digitized from 1:24000 USGS Topographic Quadrangle maps.
Data Source used
Server=lojicora1; Service=esri_sde; User=jackerman; Version=SDE.DEFAULT
Process Step 2
Process description: 
Metadata imported.
Data Source used
C:\DOCUME~1\carroll\LOCALS~1\Temp\xml45.tmp
Process Step 3
Process description: 
Metadata imported.
Data Source used
V:\a2metadata\JEFLIB\MUNICBND.xml
Process Step 4
Process description: 
Metadata imported.
Process date: 20081204 Process time: 15160600
Data Source used
H:\MetaData_Transfer\Jeflib\municbnd.xml
Process Step 5
Process description: 
Dataset copied.
Process date: 20090508 Process time: 10385300
Data Source used
Server=lojicora1; Service=esri_sde; User=cbynum; Version=SDE.DEFAULT
Process Step 6
Process description: 
Metadata imported.
Process date: 20100630 Process time: 09441300
Data Source used
J:\lojic\MetaData_Transfer\Jeflib\municbnd.xml
ESRI geoprocessing history
Description of ESRI geoprocessing commands, settings, and tolerances applied to the data.
ESRI geoprocessing command information
1 Process
Date: 20100701 Time: 021021
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\ChangePrivileges
Command issued: ChangePrivileges "Database Connections/pu_jeflib.sde\jeflib.municbnd" LOJIC_ROLE GRANT # "Database Connections/pu_jeflib.sde\jeflib.municbnd"
2 Process
Date: 20100803 Time: 020959
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\ChangePrivileges
Command issued: ChangePrivileges "Database Connections/pu_jeflib.sde\jeflib.municbnd" LOJIC_ROLE GRANT # "Database Connections/pu_jeflib.sde\jeflib.municbnd"
+ 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
Standard Order Process
Common ways in which data may be obtained.
Digital form:
Size of the data: 0.422
Transfer size: 0.422
+ Metadata Reference
Metadata Date
Dates associated with creating, updating and reviewing the metadata.
Last updated: 20100908
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
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