Spencer County Street Centerline
SDE Feature Class - SPENCER.spc_stcl
FGDC, ESRI Metadata
DescriptionSpatialData StructureData QualityData SourceData DistributionMetadata
+ Resource Description
Citation
Information used to reference the data.
Title: Spencer County Street Centerline
Originators: Kentucky Transportation Cabinet, Division of Planning
Publisher: Kentucky Transportation Cabinet (KYTC)
Publication place: Frankfort, Kentucky
Publication date: 2006 Publication time: July
Data type: vector digital data
Data location: LOJIC GIS Database
Description
A characterization of the data, including its intended use and limitations.
Abstract:
Digital map containing state-maintained and local-road centerlines for Spencer County, Kentucky.
Purpose:
Produced by the Kentucky Transportation Cabinet (KYTC), this data is to provide a base transportation network for use in Geographic Information Systems (GIS).
Supplemental information:
Highway centerline data was created with Global Positioning System (GPS) technology.   See data-standard information in the "Cross Reference" tab.
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
Data Type
How the data are represented, formatted and maintained by the data producing organization.
File or table name: SPENCER.spc_stcl
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.0.1770
Time Period of Data
Time period(s) for which the data corresponds to the currentness reference.
Date: 1991
Currentness reference:
publication date
Status
The state of and maintenance information for the data.
Data status: In work
Update frequency: Monthly
Key Words
Words or phrases that summarize certain aspects of the data.
Theme:
Keywords: structure
Keyword thesaurus: ArcIMS Metadata Server Theme Codes
Place:
Keywords: Kentucky, Spencer County, Roads, Streets, Centerlines
Keyword thesaurus: None
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.
Data Security Information
Handling restrictions imposed on the data because of national security, privacy or other concerns.
Security classification: Unclassified
Cross Reference
Information about other, related data sets that are likely to be of interest.
Title: GPS Maintenance Standards
Originators: Kentucky Transportation Cabinet, Divison of Planning
Publication date: June 30, 2004 Publication time: Unknown
Data type: document
+ 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
BoundaryCoordinate
Left 1276852.500000 (survey feet)
Right 1395068.125000 (survey feet)
Top 237670.000000 (survey feet)
Bottom 162220.026250 (survey feet)
In Unprojected coordinates (geographic)
GCS North American 1983
BoundaryCoordinate
West-85.514233 (longitude)
East-85.100764 (longitude)
North38.149531 (latitude)
South37.938630 (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 SPENCER.spc_stcl
Detailed descriptions of entity type, attributes, and attribute values for the data.
Name: SPENCER.spc_stcl
Type of object: Feature Class
Geometry type: Polyline
Number of records: 1107
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
LENGTH
Alias: LENGTH Type: Double Width: 8 Precision: 38 Scale: 8
SPEN_GPS_
Alias: SPEN_GPS_ Type: Double Width: 8 Precision: 38 Scale: 8
SPEN_GPS_I
Alias: SPEN_GPS_I Type: Double Width: 8 Precision: 38 Scale: 8
LRS_ID
Alias: LRS_ID Type: String Width: 17 Precision: 0 Scale: 0
BEGIN_MP
Alias: BEGIN_MP Type: Double Width: 8 Precision: 38 Scale: 8
END_MP
Alias: END_MP Type: Double Width: 8 Precision: 38 Scale: 8
DRAWCODE
Alias: DRAWCODE Type: SmallInteger Width: 2 Precision: 4 Scale: 0
RD_NAME
Alias: RD_NAME Type: String Width: 40 Precision: 0 Scale: 0
SURFTYPE
Alias: SURFTYPE Type: SmallInteger Width: 2 Precision: 4 Scale: 0
ROUTE
Alias: ROUTE Type: String Width: 13 Precision: 0 Scale: 0
ROUTE_NBR
Alias: ROUTE_NBR Type: String Width: 10 Precision: 0 Scale: 0
GRAPHIC_LE
Alias: GRAPHIC_LE Type: Double Width: 8 Precision: 38 Scale: 8
DMI_LEN_MI
Alias: DMI_LEN_MI Type: Double Width: 8 Precision: 38 Scale: 8
GOV_LEVEL
Alias: GOV_LEVEL Type: SmallInteger Width: 2 Precision: 4 Scale: 0
RSE_UNIQUE
Alias: RSE_UNIQUE Type: String Width: 17 Precision: 0 Scale: 0
LOCAL_KEY
Alias: LOCAL_KEY Type: String Width: 50 Precision: 0 Scale: 0
CO_NUMBER
Alias: CO_NUMBER Type: SmallInteger Width: 2 Precision: 4 Scale: 0
RT_PREFIX
Alias: RT_PREFIX Type: String Width: 2 Precision: 0 Scale: 0
RT_NUMBER
Alias: RT_NUMBER Type: SmallInteger Width: 2 Precision: 4 Scale: 0
RT_SUFFIX
Alias: RT_SUFFIX Type: String Width: 2 Precision: 0 Scale: 0
RT_SECTION
Alias: RT_SECTION Type: SmallInteger Width: 2 Precision: 4 Scale: 0
ROUTE_TYPE
Alias: ROUTE_TYPE Type: String Width: 4 Precision: 0 Scale: 0
ROUTE_LBL
Alias: ROUTE_LBL Type: String Width: 9 Precision: 0 Scale: 0
SHIELD_LBL
Alias: SHIELD_LBL Type: String Width: 6 Precision: 0 Scale: 0
CO_NAME
Alias: CO_NAME Type: String Width: 35 Precision: 0 Scale: 0
LAST_UPDT
Alias: LAST_UPDT Type: Date Width: 36 Precision: 0 Scale: 0
OWNER_DATE
Alias: OWNER_DATE Type: Date Width: 36 Precision: 0 Scale: 0
STATUS
Alias: STATUS Type: String Width: 25 Precision: 0 Scale: 0
KYGEONET
Alias: KYGEONET Type: String Width: 100 Precision: 0 Scale: 0
ZIPCODE
Alias: ZIPCODE Type: String Width: 10 Precision: 0 Scale: 0
PO_NAME
Alias: PO_NAME Type: String Width: 20 Precision: 0 Scale: 0
STATE
Alias: STATE Type: String Width: 2 Precision: 0 Scale: 0
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.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
SPENCER.spc_stcl
ESRI feature type: Simple
Geometry type: Polyline
Topology: FALSE
Feature count: 1107
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
SPENCER.spc_stcl
Type: String
Count: 1107
+ Data Quality and Accuracy Information
General
Information about the fidelity of relationships, data quality and accuracy tests, omissions, selection criteria, generalization, and definitions used to derive the data.
Logical consistency report:
Node, geometry and topology relationships are collected or generated to satisfy topological requirements.  Some of these requirments include:  arcs must begin and end at nodes, arcs must connect to each other at nodes, and arcs do not extend through nodes.
Completeness report:
Data completeness for unrevised digital files reflects the content of the source graphic ie. DRGs, DOQQs, realignments, As-Builts, field maps and other agencies' documents.  All future updates will be collected following the current Standards for KYTC Road Centerlines (see http://giac.ky.gov/giac_standards_trans.htm).
Attribute Accuracy
Accuracy of the identification of data entities, features and assignment of attribute values.
Attribute accuracy report:
Attributes fall within three categories: structural attributes, descriptive attributes, and calculated attributes.  Structural attributes uniquely identify individual arcs and are verified against fields in related Oracle tables.  Descriptive attributes are compared against KYTC internal documents and field inspections. Calculated attribute fields are populated via script routines.
Positional Accuracy
Accuracy of the positional aspects of the data.
Horizontal accuracy report:
Accuracy of unrevised/pre-GPS files are based on the use of source graphics ie. 1:24000 DRGs.  The target horizontal accuracy for the road layers was 1:24,000 (+/- 40 feet). Given the variety of sources for the data, it is recognized that the older centerlines do not always meet published national map accuracy standards. 
For data currently being collected and all GPS-based road centerline data, the KYTC Division of Planning uses the geospatial positional accuracy standards proposed by the Federal Geodetic Control Subcommittee (FGCS 1994). Road centerline collection methods are based on pseudorange measurements (FGCS Classification Band IX). These differential GPS (DGPS) methods, either in post processed or real-time modes, provide a resulting horizontal accuracy of less than 4 meter radius of the relative positional error circle with a 95% confidence.  The target accuracy for new collection is sub-meter (< 1.0 meter), but it is recognized that some field conditions prevent attaining this. All county level coverages will have a published accuracy statement containing a relative positional error radius and a confidence level.
+ 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
Map scale denominator: variable
Media: online
Source contribution:
KYTC Divison of Planning, KY Area Development Districts
Process Steps
Information about events, parameters, tolerances and techniques applied to construct or derive the data.
Process step information
Process Step 1
Process description:
The centerline data goes through the following processes:  data collection, data clean up, verification of accuracy, formatting into distributable GIS files, and publication/sharing.  The foundation for non-GPS centerlines was captured through heads-up digitizing of scanned and registered USGS 7.5' topographic quadrangles.  New roads and alignment changes to the existing road layers were added using As-Builts, field maps, and a variety of external agencies' documents.  

Each county's centerline collection must conform to criteria defined by KYTC's Division of Planning. While
alternative methods for data collection can be used (photogrammetry, etc.), all data to be incorporated
into KYTC coverages must meet or exceed the accuracy level defined by the Division of Planning and are subject
to independent accuracy validation. The methods described below are provided as a successful
blueprint for collecting centerline data at the KYTC defined accuracy level.

KYTC DATA COLLECTION METHOD

All public roads (defined above) are to be collected. The primary technology designated for use in
road centerline collection is GPS. A GPS unit is mounted on vehicles (with the antenna on the
driver's side) and roads are driven at normal traffic speeds. Antenna location on the vehicle &
height (in feet & meters) is recorded in order to offset properly the centerline from the collection
point. At least 95% of the mileage of all state maintained roads are located with differential GPS. At
least 95% of the total mileage should be collected with DGPS. KYTC and its current contractors
are using ASPEN software for the collection of road centerline GPS data. Epoch recording rate is
to be 1 second for all roads except for Interstates. The epoch rate for Interstate should be 5
seconds. This provides efficient data capture while meeting the accuracy requirements.
Alternative less accurate methods for collecting road position can be employed, such as DOQQs,
but cannot exceed 5% of the total arc mileage but may exceed 5% of the total maintained road mileage.
Two important data attributes that should be addressed in field data collection are directionality
and arc breaks. KYTC's experience has found that more errors occur if these are left to the office
cleanup phase.

Directionality: All non-divided state roads were driven in two directions and then
collapsed to generate a centerline. Divided Highways (where medians exist) were driven in
both directions and then retained separately in the coverage. All local and one-way roads
were driven in one direction and the appropriate offset applied.
Arc Breaks: Arcs must break at pavement changes and the beginning and ending points of
all ramps, Y-intersections, crossovers, and connectors. (Post-fieldwork processing will add
breaks at city and county boundaries).

DATA CLEAN-UP

After field GPS collection centerline data is brought into a GIS and processed to remove
obvious errors (both spatial and attribute). This involves cleaning up a variety of errors including
spatial (multipath, over and undershoots, arc directionality reversals, etc.) and attribute errors (data entry
miscoding, omission, transposition and "fat-finger". The data is also compared to known
test points and lines for spatial verification of accuracy.


HORIZONTAL ACCURACY VERIFICATION METHODS

KYTC's spatial accuracy verification methodology is an adoption of the National Standard For Spatial
Data Accuracy (NSSDA) testing methodology (FGDC-SBCD 1998:3-4). A minimum of 20 road
intersection test points is taken within each county using DGPS. These locations are distributed
proportionately throughout each county to reflect the geographic area of interest and distribute any
error. Each test point is monumented with a P-K (a hardened masonry nail with a central dimple)
or MAG nail (magnetized nail that is detectable even if buried). A DGPS unit is mounted onto a tripod
over the point and a minimum of 180 positions is taken using a 1-second point-logging interval.
KYTC then randomly tests a subset of these control points for each county to corroborate accuracy of
the centerlines. Please note that these test points are for GPS centerline accuracy testing purposes
only. They should not be used for land surveying purposes.
Process date: ongoing
Data Source used
Server=lojicora1; Service=esri_sde; User=spencer; Version=SDE.DEFAULT
Process Step 2
Process description:
Dataset copied.
Data Source used
Server=lojicora1; Service=esri_sde; User=spencer; Version=SDE.DEFAULT
Process Step 3
Process description:
Dataset copied.
Process date: 20090217 Process time: 09230100
Data Source used
Server=lojicora1; Service=esri_sde; User=jackerman; Version=SDE.DEFAULT
Process Step 4
Process description:
Metadata imported.
Process date: 20090219 Process time: 07363700
Data Source used
J:\lojic\MetaData_Transfer\Updates\Spencer_stcl.xml
+ 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
Distribution liability:
Although this data set has been processed successfully on a computer system at the State of  Kentucky, Department of Transportation , Division of  Planning,  in our GPS/GIS  Section as a  Statewide GIS Mapping Project, no warranty expressed or implied is made by the State of Kentucky regarding the utility of the data on any system, nor shall the act of distribution constitute such a warranty. The State of Kentucky and Department of Transportation,  Department of  Highways, Division of  Planning makes no expressed or implied warranties (including warranties of merchantability and fitness) with respect to the character, function, or capabilities of the electronic services or products or their appropriateness for any user purposes. In no event will the State of Kentucky and/or The Department of Transportation, Division of  Planning be liable for any incidental, indirect, special, consequential or other damages suffered by the user or any other person  or entity whether from the use of the electronic services or products, any failure thereof or otherwise, and in no event will the State of Kentucky and/or The Department of Transportation, Division of Planning liability to the requestor or anyone else exceed the
fee paid for the electronic service or product.
Technical prerequisites:
Must have software compatible with ESRI based file types.
Distribution Point of Contact
Contact information for the individual or organization distributing the data.
Organization: Office of Geographic Information http://ogi.ky.gov/
Standard Order Process
Common ways in which data may be obtained.
Fees: Free
Ordering instructions:
Download from OGI 
http://ogi.ky.gov
+ Metadata Reference
Metadata Date
Dates associated with creating, updating and reviewing the metadata.
Last updated: 20090219
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: REQUIRED: The mailing and/or physical address for the organization or individual.
City: REQUIRED: The city of the address.
State or Province: REQUIRED: The state or province of the address.
Postal code: REQUIRED: The ZIP or other postal code of the address.
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
Profile: ESRI Metadata Profile
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.