FLORIDA DEPARTMENT OF TRANSPORTATION 1997 TRAFFIC METER DATA

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: Florida Department of Transportation
Publication_Date: 19970000
Title:
FLORIDA DEPARTMENT OF TRANSPORTATION 1997 TRAFFIC METER DATA
Edition: 19970000
Geospatial_Data_Presentation_Form: SHAPE
Publication_Information:
Publisher: Florida Department of Transportation
Online_Linkage: http://www.dot.state.fl.us/
Description:
Abstract:
This dataset contains 1997 traffic data for the state of Florida from all portable and telemetered traffic meters.
Purpose:
The purpose of these data is to provide Florida Department of Transportation transportation statistic meter locations and highway traffic flow information for the purposes of planning and research.
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 19970000
Ending_Date: 19970000
Currentness_Reference:
Converted from original ESRI Shapefile format to ESRI Coverage format. Appended separate coverages to form a single dataset containing both Telemetered and Portable sites differentiated by the SITETYPE Item.
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: ISO 19115 Topic Category
Theme_Keyword: transportation
Place:
Place_Keyword_Thesaurus: NONE
Place_Keyword: Florida
Temporal:
Temporal_Keyword_Thesaurus: NONE
Temporal_Keyword: 1990s
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.
Native_Data_Set_Environment:
Data was ordered from the website: http://www.dot.state.fl.us/MapsAndPublications/manuals/pub-tmap.htm
Cross_Reference:
Citation_Information:
Originator: FDOT Transportation Statistics Office
Publication_Date: 19970000
Title:
Unavailable
Geospatial_Data_Presentation_Form: Map
Back to Top
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
Relied on the integrity of the attribute information within the original data layer.  However, during the QA process a new item, DESCRIPT was added.  It is based on CW_DIST attribute information. Likewise, USACE_CIVIL was renamed from the original coverage to CW_DIST set to REQUIRED.
Logical_Consistency_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.
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: Florida Department of Transportation (FDOT)
Publication_Date: 19970000
Title:
Unavailable
Geospatial_Data_Presentation_Form: Map
Source_Scale_Denominator: None
Type_of_Source_Media: Map
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 19970000
Ending_Date: 19970000
Source_Currentness_Reference:
FDOT
Source_Citation_Abbreviation:
FDOT
Source_Contribution:
Vector data representing the average daily traffic statistics.
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 Precision to DOUBLE
(3) Set Tolerances to FGDL Standards
Process_Date: 2000
Back to Top
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
Back to Top
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: ADTLOC.DBF
Entity_Type_Definition:
Database File
Entity_Type_Definition_Source:
None
Attribute:
Attribute_Label: COSITE
Attribute_Definition:
FDOT County site number
Attribute_Definition_Source:
Unknown
Attribute_Domain_Values:
Unrepresentable_Domain:
Unknown
Attribute:
Attribute_Label: SECTION
Attribute_Definition:
FDOT road section number on which road telemeter is located
Attribute_Definition_Source:
Unknown
Attribute_Domain_Values:
Unrepresentable_Domain:
Unknown
Attribute:
Attribute_Label: LOCATION
Attribute_Definition:
Milepost number of road section
Attribute_Definition_Source:
Unknown
Attribute_Domain_Values:
Unrepresentable_Domain:
Unknown
Attribute:
Attribute_Label: AADT
Attribute_Definition:
(Annual average daily traffic) =  the total volume of traffic on highway segment for one year divided by the total number of days in a year.
Attribute_Definition_Source:
Unknown
Attribute_Domain_Values:
Unrepresentable_Domain:
Unknown
Attribute:
Attribute_Label: KFCTR
Attribute_Definition:
(Design hour traffic) = proportion of aadt occurring in an hour.
Attribute_Definition_Source:
Unknown
Attribute_Domain_Values:
Unrepresentable_Domain:
Unknown
Attribute:
Attribute_Label: DFCTR
Attribute_Definition:
(Directional distribution factor) = the percent of the total two-way hourly traffic that occurs in the peak direction.
Attribute_Definition_Source:
Unknown
Attribute_Domain_Values:
Unrepresentable_Domain:
Unknown
Attribute:
Attribute_Label: TFCTR
Attribute_Definition:
(Truck factor) = the percent of truck traffic for a 24 hour period.
Attribute_Definition_Source:
Unknown
Attribute_Domain_Values:
Unrepresentable_Domain:
Unknown
Back to Top
Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Operator
Contact_Organization: FLORIDA GEOGRAPHIC DATA LIBRARY
Contact_Address:
Address_Type: Physical
Address:
431 Architecture Building
PO Box 115706
City: Gainesville
State_or_Province: Florida
Postal_Code: 32611-5706
Contact_Voice_Telephone: (352) 3920997, Operator
Contact_Electronic_Mail_Address: http://www.fgdl.org/fgdldocs/document/techsupp.htm
Hours_of_Service: 24 Hours / Day
Contact Instructions:
Please visit the web site, http://www.fgdl.org, for all
questions or concerns.
Resource_Description: Downloadable Data
Distribution_Liability:
Florida Geographic Data Library is a product of the University of Florida GeoPlan Center with support from the Florida Department of Transportation and the Florida Department of Environmental Protection. THE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE "MATERIALS") ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE "DATA PROVIDERS"). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED "AS IS". THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE QUALITY OR SUITABILITY OF THE MATERIALS, EITHER EXPRESSLY OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED AS A RESULT OF USING, MODIFYING, CONTRIBUTING OR DISTRIBUTING THE MATERIALS.
Back to Top
Metadata_Reference_Information:
Metadata_Date: 19970000
Metadata_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Transtat Office
Contact_Address:
Address_Type: Physical
Address:
605 Suwannee St. MS27
City: Tallahassee
State_or_Province: FL
Postal_Code: 32399
Contact_Voice_Telephone: (850) 488-4111 X-119
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Back to Top