Street and Roadway Traffic Control Signs
SDE Feature Class - jeflib.signs
FGDC, ESRI Metadata
DescriptionSpatialData StructureData SourceData DistributionMetadata
+ Resource Description
Citation
Information used to reference the data.
Title: Street and Roadway Traffic Control Signs
Originators: Louisville Metro Public Works
Publication date: 3/1/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: 
The sign layer consists of points representing traffic control signs. The data is the result of field surveys by Metro Public Work?s staff. Detailed attribute characteristics are contained in the Hansen Oracle relational databases. The sign graphics and Hansen Oracle attributes have been merged to create the signs layer. The primary use of this layer is to facilitate mapping of sign locations through the Hansen ArcView project for Public Works.
Purpose: 
General query and display.
Supplemental information: 
Sign locations are approximate and must be verified in the field. This data is a graphic representation and should not be scaled.

Presently sign data is only being collected on streets designated as Metro Through Roads. Eventually signs on other Metro roads will be added to this layer.
Language of dataset: en
Point Of Contact
Contact information for the individual or organization that is knowledgeable about the data.
Person: Laura Moore
Organization: Metro Public Works
Phone: 502-574-3883
Email: laura.moore@louisvilleky.gov
Address type: mailing and physical address
Address: 
444 S 5th Street
City: Louisville
State or Province: Ky
Postal code: 40202
County: USA
Data Type
How the data are represented, formatted and maintained by the data producing organization.
File or table name: jeflib.signs
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: 9/1/2004
Currentness reference: 
publication date
Status
The state of and maintenance information for the data.
Data status: In work
Update frequency: Daily
Key Words
Words or phrases that summarize certain aspects of the data.
Theme:
Keywords: jeflib mpw traffic sign
Place:
Keywords: Louisville Jefferson Kentucky KY
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.
+ 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 1154432.750000 (survey feet)
Right 1306564.500000 (survey feet)
Top 310750.000000 (survey feet)
Bottom 188611.968750 (survey feet)
In Unprojected coordinates (geographic)
GCS North American 1983
Boundary Coordinate
West -85.944519 (longitude)
East -85.408780 (longitude)
North 38.347535 (latitude)
South 38.005716 (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.signs
Detailed descriptions of entity type, attributes, and attribute values for the data.
Name: jeflib.signs
Type of object: Feature Class
Geometry type: Multipoint
Number of records: 25421
Attributes
SIGN_ID
Alias: SIGN_ID Type: Integer Width: 4 Precision: 10 Scale: 0
MUTCD_CODE
Definition: 
Uniform code for each sign type from Manual of Uniform Traffic Control Devices.
Alias: MUTCD_CODE Type: String Width: 10 Precision: 0 Scale: 0
FACING
Definition: 
Octet direction that sign faces.
Alias: FACING Type: String Width: 3 Precision: 0 Scale: 0
Attribute domain values
Value Definition
E 
East
W 
West
S 
South
E 
East
NE 
Northeast
NW 
Northwest
SE 
Southeast
SW 
Southwest
SUPTYP
Definition: 
Type of support on which sign is mounted.
Alias: SUPTYP Type: String Width: 6 Precision: 0 Scale: 0
Attribute domain values
Value Definition
METP 
Metal Pole
MSTARM 
Mast Arm
MSTLTP 
Metal Street Light Pole
OTHER 
Other
PIPE 
Pipe
SIGNP 
Sign Post
SPNWIR 
Span Wire
UP 
Utility Pole
X_COORD
Definition: 
X coordinate of sign in state plane coordinate system.
Alias: X_COORD Type: Double Width: 8 Precision: 18 Scale: 2
Y_COORD
Definition: 
Y coordinate of sign in state plane coordinate system.
Alias: Y_COORD Type: Double Width: 8 Precision: 18 Scale: 2
SIGNTEXT
Definition: 
Text displayed on the sign.
Alias: SIGNTEXT Type: String Width: 150 Precision: 0 Scale: 0
SYMBOL
Definition: 
Graphic symbol (if applicable) on sign.
Alias: SYMBOL Type: String Width: 8 Precision: 0 Scale: 0
CAPT_DATE
Definition: 
Initial date each sign was inventoried.
Alias: CAPT_DATE Type: Date Width: 36 Precision: 0 Scale: 0
COMMENTS
Definition: 
Field notes.
Alias: COMMENTS Type: String Width: 150 Precision: 0 Scale: 0
COMPKEY
Definition: 
Unique identifier assigned by Hansen application.
Alias: COMPKEY Type: Integer Width: 4 Precision: 9 Scale: 0
COMPTYPE
Definition: 
Type of feature; in this case always 20 for sign assets.
Alias: COMPTYPE Type: SmallInteger Width: 2 Precision: 3 Scale: 0
RWCOMPKEY
Definition: 
Unique identifier for each streetcl feature.
Alias: RWCOMPKEY Type: Integer Width: 4 Precision: 9 Scale: 0
CATEGORY
Definition: 
Category corresponding to the MUTCD code.
Alias: CATEGORY Type: String Width: 4 Precision: 0 Scale: 0
Attribute domain values
Value Definition
D 
Directional
I 
Informational
M 
Guide
O 
Other
R 
Regulatory
S 
School
W 
Warning
SIZE_
Definition: 
Dimensions (in Inches) of sign.
Alias: SIZE_ Type: String Width: 8 Precision: 0 Scale: 0
CONDITION
Definition: 
Condition of the sign.
Alias: CONDITION Type: String Width: 4 Precision: 0 Scale: 0
Attribute domain values
Value Definition
EXAM 
Examine
NONC 
Noncompliant
REMV 
Remove
REPL 
Replace
SAT 
Satisfactory
EXP 
Expired
OP_HEIGHT
Definition: 
Clearance height (in inches) on overpass warning signs.
Alias: OP_HEIGHT Type: SmallInteger Width: 2 Precision: 3 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
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.signs
ESRI feature type: Simple
Geometry type: Multipoint
Topology: FALSE
Feature count: 25421
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.signs
Type: Composite object
Count: 25421
+ 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: Louisville Metro Public Works
Process Steps
Information about events, parameters, tolerances and techniques applied to construct or derive the data.
Process step information
Process Step 1
Process description: 
Sign facilities were captured in the field utilizing a customized ESRI ArcPad application. Sign data was gathered at large scale (approximately 1"=10?). Signs were located relative to existing LOJIC PTD data (driveways, utility points, road edges, and buildings). Multiple signs at a given location are indicated as points adjacent to one another in a direction perpendicular to the street centerline on which the signs occur.
Process Step 2
Process description: 
Metadata imported.
Data Source used
Q:\wsxprice\jeff\JEFLIB_SIGNS.xml
Process Step 3
Process description: 
Metadata imported.
Data Source used
Q:\MetaData_Transfer\Jeflib\signs.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 ChangePrivileges_12
Date: 20070329 Time: 021325
Tool location: S:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\ChangePrivileges
Command issued: ChangePrivileges "Database Connections\p_jeflib.sde\JEFLIB.signs" LOJIC_ROLE GRANT # "Database Connections\p_jeflib.sde\JEFLIB.signs"
2 Process
Date: 20080531 Time: 171823
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\UpgradeSpatialReference
Command issued: UpgradeSpatialReference "Database Connections/pl_JEFLIB.sde/jeflib.signs" 0.00125 0.025 0.025 "Database Connections/pl_JEFLIB.sde/jeflib.signs"
3 Process
Date: 20080811 Time: 084438
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\Analyze
Command issued: Analyze "Database Connections/pl_jeflib.sde\jeflib.signs_1" BUSINESS;FEATURE "Database Connections/pl_jeflib.sde\jeflib.signs_1"
4 Process
Date: 20080811 Time: 090025
Tool location: C:\Program Files (x86)\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\ChangePrivileges
Command issued: ChangePrivileges "Database Connections/pl_jeflib.sde\jeflib.signs" LOJIC_ROLE GRANT # "Database Connections/pl_jeflib.sde\jeflib.signs"
+ 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
+ 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
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