ROAD 100K

Metadata also available as - [Questions & Answers]

Metadata:

Identification_Information
Data_Quality_Information
Spatial_Reference_Information
Entity_and_Attribute_Information
Distribution_Information
Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: Bureau of Transportation Statistics, (BTS)
Publication_Date: 19990000
Title: ROAD 100K
Edition: 20010000
Geospatial_Data_Presentation_Form: SHAPE
Online_Linkage: <http://www.bts.gov/>

Description:

Abstract:: This dataset contains the Rail Network, which is a comprehensive database of Florida's railway system at the 1:100,000 scale. The data set provides location and partial attribute information for use in regional network analysis application.
Purpose:: BTS strives to make high-quality data and information available for the transportation community and other individuals or groups interested in transportation. Strong leadership, planning, educational outreach, and the pursuit of a superior working team frame our vision. The 1991 Intermodal Surface Transportation Efficiency Act (ISTEA) established the Bureau of Transportation Statistics (BTS) for data collection, analysis, and reporting and to ensure the most cost-effective use of transportation-monitoring resources. We strive to increase public awareness of the nation's transportation system and its implications and improve the transportation knowledge base of decisionmakers.
Federal Railroad Administration contributed the reference location base map dated 1994 -Rail Industry contributed Railroad terminal identification ownership and commodity handling capabilities

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 19990000

Currentness_Reference: Ground Condition

Status:

Progress: Complete
Maintenance_and_Update_Frequency: Irregular

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -87.429040
East_Bounding_Coordinate: -79.872251
North_Bounding_Coordinate: 30.983191
South_Bounding_Coordinate: 24.492815

Keywords:

Theme:

Theme_Keyword_Thesaurus: NONE
Theme_Keyword: Bureau of Transportation Statistics
Theme_Keyword: Rail network
Theme_Keyword: Planning

Place:

Place_Keyword_Thesaurus: NONE
Place_Keyword: Florida
Place_Keyword: Existing Railroad Network

Temporal:

Temporal_Keyword_Thesaurus: NONE
Temporal_Keyword: 1990's

Access_Constraints: NONE

Use_Constraints:

THE DATA INCLUDED IN THIS APPLICATION ARE BASED ON INTERPRETATION OF AVAILABLE INFORMATION AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING.

Scale is an important factor in data usage. Certain scale data sets are not suitable for some projects, analysis, or modeling purposes. Please be sure you are using the best available data.

1:24000 scale data sets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries.

1:100000 scale data sets are recommended for projects that are at the multi-county or regional level. 1:250000 scale data sets are recommended for projects that are at the regional or state level or larger.

Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: <http://www.geoplan.ufl.edu/education.html>

Native_Data_Set_Environment: For more information, visit: <http://www.bts.gov/>

Cross_Reference:

Citation_Information:

Originator: Bureau of Transportation Statistics, (BTS)
Publication_Date: 19990000
Title: Unavailable
Geospatial_Data_Presentation_Form: Map

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:: Relied on the integrity of the attribute information within the original data layer.

Logical_Consistency_Report:

After completing topological and attribute verification using ARC/INFO, the data was extracted and reformatted into the BTS ACSII format.Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s."

Completeness_Report:

Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s."

Lineage:

Source_Information:

Source_Citation:

Citation_Information:

Originator: Bureau of Transportation Statistics, (BTS)
Publication_Date: 19990000
Title: Unavailable
Geospatial_Data_Presentation_Form: Map

Source_Scale_Denominator: 100,000

Type_of_Source_Media: Map

Source_Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 19990000

Source_Currentness_Reference: Ground Condition

Source_Citation_Abbreviation: BTS

Source_Contribution:

Data representing the Rail Network of FLorida at 1:100,000 scale.

Process_Step:

Process_Description:: The process step describes, in general, the process used in the production of data sets. The originating agencies created the original spatial coverage. GeoPlan, during the QA/QC process included the following aspects: (1) Reprojected data to FGDL Albers (2) Set Tolerances to FGDL Standard (3) Dropped item featureid (repeat of featureid) (4) Moved descript to the end of table (5) Changed records in DESCRIPT item to uppercase (6) Related attribute tables were joined
Process_Date: 20000000

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Map_Projection:

Map_Projection_Name: Albers Conical Equal Area

Albers_Conical_Equal_Area:

Standard_Parallel: 24.000000
Standard_Parallel: 31.500000
Longitude_of_Central_Meridian: -84.000000
Latitude_of_Projection_Origin: 24.000000
False_Easting: 400000.00000
False_Northing: 0.00000

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: Coordinate Pair

Coordinate_Representation:

Abscissa_Resolution: 0.001024
Ordinate_Resolution: 0.001024

Planar_Distance_Units: METERS

Geodetic_Model:

Horizontal_Datum_Name: D_North_American_1983_HARN

Ellipsoid_Name: GRS1980
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: RR100K.DBF
Entity_Type_Definition: Database File
Entity_Type_Definition_Source: None

Attribute:

Attribute_Label: RECTYPE

Attribute_Definition: Record type, 'L' for line

Attribute_Definition_Source: BTS record