TARC Routes
SDE Feature Class - JEFLIB.tarcroute
FGDC, ESRI Metadata
DescriptionSpatialData StructureData SourceData DistributionMetadata
+ Resource Description
Citation
Information used to reference the data.
Title: TARC Routes
Originators: KIPDA for the TARC GoAbility Study, updated by LOJIC with TARC updates
Publication date: 2005.
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: 
Transit Authority of River City (TARC)  Bus Routes in the Fall of 2005
Purpose: 
General Query and cartographics. Not setup for routing or network purposes
Supplemental information: 
This data has created by KIPDA for TARC's GoAbility Study in 2004. It was edited in 2005 by LOJIC with updates provided by TARC.
Language of dataset: en
Point Of Contact
Contact information for the individual or organization that is knowledgeable about the data.
Person: Jane Poole/Carrie Butler
Organization: LOJIC/TARC
Position: LOJIC Products Specialist/Director of Planning
Phone: (502) 540-6435/(502) 213-3490
Fax: (502) 540-6499/(502) 213-3253
Email: poole@lojic.org/cbutler@ridetarc.org
Data Type
How the data are represented, formatted and maintained by the data producing organization.
File or table name: JEFLIB.tarcroute
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: 2005
Currentness reference: 
ground condition
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: jeflib transportation tarc bus busline
Place:
Keywords: Louisville Jefferson Oldham Bullitt Kentucky KY Clark Floyd Indiana IN
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 1164459.768750 (survey feet)
Right 1317772.663750 (survey feet)
Top 330798.500000 (survey feet)
Bottom 180562.373750 (survey feet)
In Unprojected coordinates (geographic)
GCS North American 1983
Boundary Coordinate
West -85.910825 (longitude)
East -85.369542 (longitude)
North 38.402966 (latitude)
South 37.984114 (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.tarcroute
Detailed descriptions of entity type, attributes, and attribute values for the data.
Name: JEFLIB.tarcroute
Type of object: Feature Class
Geometry type: Polyline
Number of records: 46
Description: 
TARC Routes
Source: 
LOJIC
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
ROUTE_NUM
Alias: ROUTE_NUM Type: Double Width: 8 Precision: 11 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
ROUTE_NAME
Definition: 
Route Name
Alias: ROUTE_NAME Type: String Width: 50 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.tarcroute
ESRI feature type: Simple
Geometry type: Polyline
Topology: FALSE
Feature count: 46
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.tarcroute
Type: String
Count: 46
+ 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: 
Dataset copied.
Data Source used
C:\metadata_exports\tarcroutes
Process Step 2
Process description: 
Metadata imported.
Process date: 20100713 Process time: 15244800
Data Source used
J:\lojic\MetaData_Transfer\Jeflib\tarcroutes.xml
ESRI geoprocessing history
Description of ESRI geoprocessing commands, settings, and tolerances applied to the data.
ESRI geoprocessing command information
1 Process
Date: 20100714 Time: 020930
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\ChangePrivileges
Command issued: ChangePrivileges "Database Connections/pu_jeflib.sde\jeflib.tarcroute" LOJIC_ROLE GRANT # "Database Connections/pu_jeflib.sde\jeflib.tarcroute"
+ 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: 
Offline Data
Standard Order Process
Common ways in which data may be obtained.
Digital form:
Transfer size: 0.000
+ 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: REQUIRED: The organization responsible for the metadata information.
Person: REQUIRED: The person responsible for the metadata information.
Phone: REQUIRED: The telephone number by which individuals can speak to the organization or individual.
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
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