Oldham County Hydrographics, Line

+ Resource Description

Citation

Information used to reference the data.

Title: Oldham County Hydrographics, Line

Originators: Various Mapping Vendors

Publication date: 2006

Data type: vector digital data

Data location: Server=lojicOra1; Service=esri_sde; User=oldham; Version=SDE.DEFAULT

Description

A characterization of the data, including its intended use and limitations.

Abstract:

Water Bodies such as Streams, Rivers and Lakes in Oldham County.  The Oldham County layers use the Horizontal 1983 North American Datum, Kentucky State Plane North Zone.

Purpose:

Planimetric reference for general cartographics, overlay and query operations.

Supplemental information:

ASPRS Class One Accuracy Standards for 1" = 100' mapping. Contours have two foot interval.
The Oldham Data was updated using 2006 aerial imagery.

Important Note: Single line streams are only found in the arc layer of the HL coverage. To display the numerous HL single line streams the arc layer must be used.

Language of dataset: en

Point Of Contact

Contact information for the individual or organization that is knowledgeable about the data.

Person: Bruce Carroll

Organization: LOJIC

Phone: (502) 540-6543

Fax: (502) 540-6499

Email: carroll@lojic.org

Address type: mailing and physical address

Address:

700 W. Liberty St.

City: Louisville

State or Province: KY

Postal code: 40203

County: USA

Data Type

How the data are represented, formatted and maintained by the data producing organization.

File or table name: OLDHAM.hl_arc

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: 2006

Currentness reference:

publication date

Status

The state of and maintenance information for the data.

Data status: Complete

Update frequency: Irregular

Key Words

Words or phrases that summarize certain aspects of the data.

Theme:

Keywords: oldham hl stream lake pond reservoir river swamp marsh island hydrologic water planimetric ptd

Place:

Keywords: oldham 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	1242320.778750 (survey feet)
Right	1343941.848750 (survey feet)
Top	375551.145000 (survey feet)
Bottom	287876.150000 (survey feet)

In Unprojected coordinates (geographic)

GCS North American 1983

Boundary	Coordinate
West	-85.641537 (longitude)
East	-85.282921 (longitude)
North	38.526689 (latitude)
South	38.282287 (latitude)

Altitude

Minimun altitude: 0.000000

Maximum altitude: 0.000000

+ 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 Oldham County Hydrographics, Line

Detailed descriptions of entity type, attributes, and attribute values for the data.

Name: OLDHAM.hl_arc

Type of object: Feature Class

Geometry type: Polyline

Number of records: 41880

Attributes

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

HL_TYPE

Definition:

Classification of Water Bodies

Alias: HL_TYPE Type: SmallInteger Width: 2 Precision: 5 Scale: 0

Attribute domain values


Lake, Pond, Reservoir
Ohio River
Holding Pond, Sewage Pond
Double-Sided River, Stream
Wet Area (Swamp, Marsh, etc.)
Hydrographic Feature Under Structure
Single-Sided River, Stream, Creek
Island

Value	Definition
1	Lake, Pond, Reservoir
2	Ohio River
3	Holding Pond, Sewage Pond
4	Double-Sided River, Stream
5	Wet Area (Swamp, Marsh, etc.)
6	Hydrographic Feature Under Structure
7	Single-Sided River, Stream, Creek
8	Island

HL_DATE

Definition:

Photography Year Feature was mapped

Alias: HL_DATE Type: Date Width: 36 Precision: 0 Scale: 0

Attribute domain values

Value	Definition
3/31/2000	(definition not provided)
4/11/2006	(definition not provided)

BOUNDARY

Definition:

Code indicating if feature is inside Oldham County (Code 1) or outside Oldham County (Code = 0)

Alias: BOUNDARY Type: SmallInteger Width: 2 Precision: 5 Scale: 0

Attribute domain values

Value	Definition
0	Feature not inside Oldham County
1	Feature inside Oldham County

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

OLDHAM.hl_arc

ESRI feature type: Simple

Geometry type: Polyline

Topology: FALSE

Feature count: 41880

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

OLDHAM.hl_arc

Type: String

Count: 41880

+ Data Source and Process Information

Data Sources

Information about the source data used to construct or derive the data.

Data source information

Data Source 1

Originators: Mapped from 2000 aerial photography with a photo scale of 1" = 660'.

Process Steps

Information about events, parameters, tolerances and techniques applied to construct or derive the data.

Process step information

Process Step 1

Process description:

Oldham PTD layers were created using standard photogrammetric mapping techniques by various
mapping firms using 2000 and 2006 aerial imagery.

Process Step 2

Process description:

Dataset copied.

Process date: 20100112 Process time: 14461400

Data Source used

\\pc\data\lojic\A_Final_Oldham_PTD\Oldham_2006_PTD_Layers\Oldham_Water_Features_1.gdb

Process Step 3

Process description:

Dataset copied.

Process date: 20100112 Process time: 14552800

Data Source used

\\pc\data\lojic\A_Final_Oldham_PTD\Oldham_2006_PTD_Layers\Temp.gdb

Process Step 4

Process description:

Metadata imported.

Process date: 20100125 Process time: 07511200

Data Source used

J:\lojic\MetaData_Transfer\Oldham\Oldham_HL_Arc.xml

ESRI geoprocessing history

Description of ESRI geoprocessing commands, settings, and tolerances applied to the data.

ESRI geoprocessing command information

1 Process

Date: 20091008 Time: 145455

Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Analysis Tools.tbx\Intersect

Command issued: Intersect "HLLINE #;lojic_clip #" V:\Temp\LOJIC_Clipping\Joan\Water_Features.mdb\HLLINE_Intersect NO_FID # INPUT

2 Process

Date: 20091008 Time: 145555

Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\DeleteField

Command issued: DeleteField V:\Temp\LOJIC_Clipping\Joan\Water_Features.mdb\HLLINE DocVer V:\Temp\LOJIC_Clipping\Joan\Water_Features.mdb\HLLINE

3 Process

Date: 20091014 Time: 092753

Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\CopyFeatures

Command issued: CopyFeatures "Y:\Mapping\5037001\Info From Client\Clipped_Existing_Oct2009\Water_Features.mdb\HLLINE" Y:\Mapping\5037001\Working\GRW\Converted_NoUpdate_Oct2009\HLLINE.shp # 0 0 0

4 Process

Date: 20091015 Time: 123507

Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\Merge

Command issued: Merge HLLINE;OtherGRW_HLLine Y:\Mapping\5037001\Working\GRW\Compiled\HL_merge.shp "HL_TYPE 'HL_TYPE' true true false 4 Short 0 4 ,First,#,HLLINE,HL_TYPE,-1,-1,OtherGRW_HLLine,HL_TYPE,-1,-1;HL_DATE 'HL_DATE' true true false 8 Date 0 0 ,First,#,HLLINE,HL_DATE,-1,-1,OtherGRW_HLLine,HL_DATE,-1,-1;SHAPE_Leng 'SHAPE_Leng' true true false 19 Double 0 0 ,First,#,HLLINE,SHAPE_Leng,-1,-1;LENGTH 'LENGTH' true true false 19 Double 0 0 ,First,#,OtherGRW_HLLine,LENGTH,-1,-1;BOUNDARY 'BOUNDARY' true true false 2 Short 0 2 ,First,#,OtherGRW_HLLine,BOUNDARY,-1,-1"

5 Process

Date: 20091015 Time: 151117

Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\Merge

Command issued: Merge Y:\Mapping\5037001\Working\GRW\Compiled\HL_merge.shp;Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ1_HLLINE.shp;Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ2_HLLINE.shp;Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ3_HLLINE.shp;Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ4_HLLINE.shp;Y:\Mapping\5037001\Working\PS_MTZ\WF\PS1_HLLINE.shp;Y:\Mapping\5037001\Working\PS_MTZ\WF\PS2_HLLINE.shp;Y:\Mapping\5037001\Working\PS_MTZ\WF\PS3_HLLINE.shp;Y:\Mapping\5037001\Working\PS_MTZ\WF\PS4_HLLINE.shp Y:\Mapping\5037001\Working\GRW_PSI_MTZ\All_HL_Merge.shp "HL_TYPE 'HL_TYPE' true true false 4 Short 0 4 ,First,#,Y:\Mapping\5037001\Working\GRW\Compiled\HL_merge.shp,HL_TYPE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ1_HLLINE.shp,HL_TYPE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ2_HLLINE.shp,HL_TYPE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ3_HLLINE.shp,HL_TYPE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ4_HLLINE.shp,HL_TYPE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS1_HLLINE.shp,HL_TYPE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS2_HLLINE.shp,HL_TYPE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS3_HLLINE.shp,HL_TYPE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS4_HLLINE.shp,HL_TYPE,-1,-1;HL_DATE 'HL_DATE' true true false 8 Date 0 0 ,First,#,Y:\Mapping\5037001\Working\GRW\Compiled\HL_merge.shp,HL_DATE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ1_HLLINE.shp,HL_DATE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ2_HLLINE.shp,HL_DATE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ3_HLLINE.shp,HL_DATE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ4_HLLINE.shp,HL_DATE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS1_HLLINE.shp,HL_DATE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS2_HLLINE.shp,HL_DATE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS3_HLLINE.shp,HL_DATE,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS4_HLLINE.shp,HL_DATE,-1,-1;SHAPE_Leng 'SHAPE_Leng' true true false 19 Double 0 0 ,First,#,Y:\Mapping\5037001\Working\GRW\Compiled\HL_merge.shp,SHAPE_Leng,-1,-1;LENGTH 'LENGTH' true true false 19 Double 0 0 ,First,#,Y:\Mapping\5037001\Working\GRW\Compiled\HL_merge.shp,LENGTH,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ1_HLLINE.shp,LENGTH,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ2_HLLINE.shp,LENGTH,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ3_HLLINE.shp,LENGTH,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ4_HLLINE.shp,LENGTH,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS1_HLLINE.shp,LENGTH,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS2_HLLINE.shp,LENGTH,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS3_HLLINE.shp,LENGTH,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS4_HLLINE.shp,LENGTH,-1,-1;BOUNDARY 'BOUNDARY' true true false 2 Short 0 2 ,First,#,Y:\Mapping\5037001\Working\GRW\Compiled\HL_merge.shp,BOUNDARY,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ1_HLLINE.shp,BOUNDARY,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ2_HLLINE.shp,BOUNDARY,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ3_HLLINE.shp,BOUNDARY,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\MTZ4_HLLINE.shp,BOUNDARY,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS1_HLLINE.shp,BOUNDARY,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS2_HLLINE.shp,BOUNDARY,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS3_HLLINE.shp,BOUNDARY,-1,-1,Y:\Mapping\5037001\Working\PS_MTZ\WF\PS4_HLLINE.shp,BOUNDARY,-1,-1"

6 Process

Date: 20091015 Time: 163723

Tool location: C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Conversion Tools.tbx\FeatureClassToFeatureClass

Command issued: FeatureClassToFeatureClass Y:\Mapping\5037001\Working\GRW_PSI_MTZ\All_HL_Merge.shp Y:\Mapping\5037001\Working\GRW_PSI_MTZ\Oldham_Water_Features.mdb HLLINE # "HL_TYPE 'HL_TYPE' true true false 4 Short 0 4 ,First,#,Y:\Mapping\5037001\Working\GRW_PSI_MTZ\All_HL_Merge.shp,HL_TYPE,-1,-1;HL_DATE 'HL_DATE' true true false 8 Date 0 0 ,First,#,Y:\Mapping\5037001\Working\GRW_PSI_MTZ\All_HL_Merge.shp,HL_DATE,-1,-1;SHAPE_Leng 'SHAPE_Leng' true true false 19 Double 0 0 ,First,#,Y:\Mapping\5037001\Working\GRW_PSI_MTZ\All_HL_Merge.shp,SHAPE_Leng,-1,-1;LENGTH 'LENGTH' true true false 19 Double 0 0 ,First,#,Y:\Mapping\5037001\Working\GRW_PSI_MTZ\All_HL_Merge.shp,LENGTH,-1,-1;BOUNDARY 'BOUNDARY' true true false 2 Short 0 2 ,First,#,Y:\Mapping\5037001\Working\GRW_PSI_MTZ\All_HL_Merge.shp,BOUNDARY,-1,-1" # Y:\Mapping\5037001\Working\GRW_PSI_MTZ\Oldham_Water_Features.mdb\HLLINE

7 Process

Date: 20091201 Time: 074514

Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\CopyFeatures

Command issued: CopyFeatures Z:\Revised_Final_2006_Oldham_Data\Oldham_Water_Features_2009.mdb\HLLINE Z:\Final_Oldham_2006_Data\Oldham_Water_Features.gdb\HLLINE # 0 0 0

8 Process

Date: 20100112 Time: 144845

Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Analysis Tools.tbx\Clip

Command issued: Clip J:\lojic\A_Final_Oldham_PTD\Oldham_2006_PTD_Layers\Temp.gdb\HLLINE J:\lojic\A_Final_Oldham_PTD\Oldham_2006_PTD_Layers\Temp.gdb\OC_Boundary J:\lojic\A_Final_Oldham_PTD\Oldham_2006_PTD_Layers\Temp.gdb\HLLINE_Inside_Clip #

9 Process

Date: 20100112 Time: 160626

Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Analysis Tools.tbx\Clip

Command issued: Clip J:\lojic\A_Final_Oldham_PTD\Oldham_2006_PTD_Layers\Temp.gdb\HLLINE_All J:\lojic\A_Final_Oldham_PTD\Oldham_2006_PTD_Layers\Temp.gdb\OC_Boundary_Buffer J:\lojic\A_Final_Oldham_PTD\Oldham_2006_PTD_Layers\Oldham_Water_Features.gdb\HLLINE_Final #

10 Process

Date: 20100126 Time: 021057

Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\ChangePrivileges

Command issued: ChangePrivileges "Database Connections/pu_oldham.sde\oldham.hl_arc" LOJIC_ROLE GRANT # "Database Connections/pu_oldham.sde\oldham.hl_arc"

+ 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.000

Transfer size: 0.000

+ Metadata Reference

Metadata Date

Dates associated with creating, updating and reviewing the metadata.

Last updated: 20100909

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.