FLORIDA DEPARTMENT OF TRANSPORTATION NOISE ABATEMENT BARRIERS - 2013

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator:
Florida Department of Transportation, Environmental Management Office
Publication_Date: 20131209
Title:
FLORIDA DEPARTMENT OF TRANSPORTATION NOISE ABATEMENT BARRIERS - 2013
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Tallahassee, FL
Publisher:
Florida Department of Transportation, Environmental Management Office
Other_Citation_Details: State of Florida
Online_Linkage: <http://www.dot.state.fl.us/emo/>
Description:
Abstract:
This dataset contains the Florida Department of Transportation's (FDOT) noise abatement barriers. This is an update to the NOISE_BARRIERS_SEP13.shp FGDL layer.
Purpose:
The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes.
Supplemental_Information:
Summary of Noise Barriers Constructed by December 31, 2010 Publication Number - FHWA-HEP-12-044 Abstract: This paper contains a listing of all noise barriers constructed with highway program monies since 1973, as reported by State highway agencies. The listing is updated every three years and contains information on length, height, cost, material, location, and year constructed for each State. It is intended for all audiences. <http://www.fhwa.dot.gov/environment/noise/noise_barriers/inventory/summary/sstates7.pdf>

APPLICATIONS OF GEOGRAPHIC INFORMATION SYSTEMS (GIS) FOR HIGHWAY TRAFFIC NOISE ANALYSIS Case Studies of Select Transportation Agencies November 2012 <http://www.gis.fhwa.dot.gov/documents/GIS_for_Highway_Traffic_Noise_Analysis.htm>
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20040101
Ending_Date: 20091106
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
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: Road Noise
Theme_Keyword: Sound Barrier
Theme_Keyword: Noise Barrier
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Category
Theme_Keyword: transportation
Theme_Keyword: infrastructure
Place:
Place_Keyword: Florida
Access_Constraints: None
Use_Constraints: None
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Florida Department of Transportation, Environmental Management Office
Contact_Person: Mariano Berrios
Contact_Address:
Address_Type: mailing and physical address
Address: 605 Suwannee Street
City: Tallahassee
State_or_Province: FL
Postal_Code: 32399
Country: USA
Contact_Voice_Telephone: 1-866-374-3368 ext. 4447
Contact_Facsimile_Telephone: 850-414-4443
Contact_Electronic_Mail_Address: peter.mcgilvray@dot.state.fl.us
Data_Set_Credit: Florida Department of Transportation, GeoPlan Center
Cross_Reference:
Citation_Information:
Other_Citation_Details:
Detailed metadata provided by CUES: NOISE_ABATEMENT_BARRIERS.pdf Contact Christina Bryk Center of Urban and Environmental Solutions (CUES) Florida Atlantic University 111 East Las Olas Blvd, Suite 709 Fort Lauderdale, Fl 33301
(954) 762-5255 / Fax: (954) 762-5666
Center for Urban Environmental Solutions: <http://www.cuesfau.org/> <http://www.cuesfau.org/projects/project.asp?ProjectID=107>
FDOT June 2000 Noise Barrier Status Report (Spreadsheet) Contact: win.lindeman@dot.state.fl.us for details.
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
GeoPlan relied on the integrity of the attribute information within the original data.
Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Explanation:
Noise Barriers were compiled based upon locational information in the FDOT - Noise Barrier Status Report, June 2000. Based upon telephone interviews and surveys, the Noise Barriers in Districts 1, 2, 5, and 7 were identified. District 4 Noise Barriers were collected via GPS and provided as a line feature class and point feature class within a personal geodatabase from District 4. District 6 collected the start and end nodes for each wall via GPS and provided the information as a point feature in Shapefile format.
Relative scale was utilized as opposed to field measurements that define absolute scale. This is not to say GPS technology was excluded, in fact during this project, nearly every barrier was identified and/or verified using a Trimble GXT. However, the X/Y coordinates collected through the use of GPS were no longer positionally aligned relative to the scale used for FDOT FGDL layers. Therefore, spatial editing was used to adjust the positional location of the barriers to align them to based upon the relative accuracy of the existing GIS layers
The Noise Abatement Barriers personal geodatabase has attributes that can be related to Roadway Characteristics Inventory (RCI) data with the 'ROADWAY' field.
Logical_Consistency_Report:
This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology
Completeness_Report:
This data is provided 'as is' by GeoPlan and is complete to our knowledge.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan
Lineage:
Source_Information:
Source_Scale_Denominator: Varies
Type_of_Source_Media: electronic mail system
Source_Citation_Abbreviation: FDOT
Source_Contribution: Spatial and Attribute Information
Process_Step:
Process_Description:
Primary Data Collection - GPS In late May 2004, the Center for Urban and Environmental Solutions deployed a field team to ground-truth the original 30 noise abatement walls in the June 2000 Report. Utilizing a Trimble GeoXT with GPS correct for real-time post-processing, the field team collected GPS information to verify the location of these barriers. During the GPS field work, three (3) new walls were identified in District 1 along the I-4 Corridor, the GPS information was collected for these walls as well. Once research staff confirmed these were owned by FDOT, they were included into the Statewide Noise Abatement Geodatabase. GPS coordinates were collected by the research field team for 33 noise abatement walls. District 4 and District 6 indicated that they would be initiating their own GPS collection during the summer and fall of 2004. Rather then replicate this effort, CUES coordinated with these two districts to obtain the completed GPS information and import it into the Statewide Geodatabase. However, approximately seven walls were not included in these two Districts inventories. Therefore, CUES field team used GPS to collect wall information mainly for the Sawgrass Expressway and the Florida Turnpike. Overall GPS coordinates were collected for 40 walls by CUES.
The internal setting of the GeoXT's GPS were set to ensure the highest possible accuracy. The settings utilized are as follows: PDOP: (Position Dilution of Precision) : 6 or less SNR (Signal To Noise Ratio): 4 Elevation Mask: 15% Number of Satellites: 4 or Higher Differential Correction: WAAS
Each noise barrier wall in the region was surveyed to obtain both spatial, attribute and photographic information necessary for the project. Upon arrival to the particular barrier wall, the team would investigate the following conditions before undertaking the survey: · Traffic volume & Safety conditions · Survey Obstacles · GPS Satellite Visibility · GPS Availability Upon arrival to the location, traffic volume was determined by the amount of traffic traveling adjacent to the wall of interest. The estimated volume determined whether it was judged safe for a foot survey or required use of a vehicle. Hard hats and florescent safety vests were worn at all times while conducting the surveys.
Numerous barrier walls surveyed had large swaths of vegetation planted next to them. Major types of vegetation included: Sable Palm trees, Sea Grape and various other bushes. These vegetation lines often followed the length of the given wall an ranged on an average from 10-75 feet. Since many of the walls had some type of vegetation, an offset was incorporated into the survey. Generally all surveys were done on an average of 20 feet in front of the wall. Many of the walls not only had a vegetation line in front but also a layer of standing water. This situation occurred in areas where the walls possessed a gully or depression directly in front of the vegetation line. In many situations, the accumulated water actually formed a small linear wetland including typical wetland flora and fauna which included unfortunately high concentrations of biting insects. If these water bodies existed, the offset was increased to account for the additional obstacle so that the survey could continue. Other barriers to the survey included manmade structures such as tollbooths, embankments, bridges and narrow walks. If such obstacles were encountered, the situation was noted in the attribute table and the offset increased as needed.
GPS is a line of sight technology which relies on the ground based receiver the ability to have a clear and unobstructed line of sight to the GPS satellites. noise barrier walls provide a unique problem in that they can obstruct half of the sky depending on how close the survey is conducted to them. Due to this fact, an offset was also needed to obtain the best possible satellite lock. GPS uses a measurement called PDOP (Position Dilution of Precision) to indicate accuracy. To ensure high accuracy GPS positioning, it is recommended that the PDOP value be less than 6. During all wall surveys, PDOP was monitored very closely and any measurement greater than 6 was resurveyed.
Once the Noise Barrier Wall was cleared to survey, the walking team member would activate the Mobile GIS/GPS unit and begin logging the poly-line feature. At the beginning of the logging, an initial starting coordinate would be relayed to the vehicle team member for input into handwriting log. If a walking Survey was done, the survey team member would walk the length of the wall with the vehicle team member following along to provide a look out for traffic. At the halfway point of the survey, the walking team member would again call out the coordinate of the middle of the wall to the vehicle team member. Once the entire length of the wall had been traversed, the walking team member would stop the logging and fill in the custom input form in the ArcPad software. Digital photos were also taken at each survey location.
After each wall was surveyed, the team would back up the data on the GeoXT mobile device and then download the data onto a laptop computer. This procedure was completed at the location incase data was lost and the survey would have to be redone. Once back at the office, all data for that day was downloaded onto the project server to be used by the GIS section.
Acquisition from Individual Districts of Walls in GIS format According to interviews conducted during this project among FDOT personnel, at the time of interviews, District offices were not maintaining an inventory of their noise barriers in GIS. However, in the summer and fall of 2004, two District offices used GPS technology to store their noise abatement walls in GIS.
District Four utilized GPS to store both the point (begin/end points) and line feature classes representing 95 noise abatement walls. District 4 provided the research team with their personal geodatabase. Next, the point and line feature classes were merged and spatially projected into the Statewide Geodatabase. District 4 also created a hyperlink to the photos collected during their GPS work. This hyperlink is included as part of the Statewide Geodatabase.
District Six utilized GPS technology to capture the begin node and end node for each wall. However, no line feature classes were created. Utilizing the GPS begin and end nodes, the research team digitized the line feature class representing the noise barriers for approximately 84 out of 96 total walls in District 6. A Trimble GeoXT was used to collect the points and linear features depicting the remaining 12 barriers. On Screen (Heads-up) Digitizing
This spatial data collection technique, based on utilizing high quality, rectified aerial photos and other georeferenced GIS layers, was used to primarily to edit the spatial data collected through GPS for relative positional accuracy purposes. The level of accuracy of the derived dataset is taken from the initial accuracy of the digital image along with georeferenced GIS layers.
One of the challenges was to utilize aerial photos in GIS at an acceptable resolution needed to create and edit spatial features for all District offices that have noise abatement walls. The central problem is that most ortho photos in GIS are collected by county governments who collected this raster information at varying scales, different data formats (e.g. MrSID, TIF, JPEG, SDE) and/or captured at different time frames. Based upon these challenges as well as the degree of acquiring these raster features, it was decided to utilize ESRI's ArcWeb Services.
One of ArcWeb Services offered is access to GlobeXplorer's 'Citipix/Digital Ortho' which was used to perform the spatial edits required to verify and/or 're-align' the GPS collected data relative to scale of FDOT's GIS base map layers. Citipix is the largest high-resolution aerial imagery dataset available online through ArcWeb Services. Captured at six-inch resolution and in 24-bit color, Citipix is precision geo-referenced and ortho-rectified. It covers over 7,000 cities and towns in over 73 metropolitan areas in the United States, with a total area of over 90,000 square miles.
Because of Citipix high resolution, it provided the optimal back ground layer to digitize, edit, and verify the linear features representing the walls. Using GPS points collected by District 6 which represent the begin and end nodes for each wall along with GlobeXplorer's digital orthophotography, the line feature classes for these walls were digitized. 96 out of the 217 walls within the Statewide Geodatabase were digitized. District 6 accounts for approximately 44% of all noise barriers in the Statewide Geodatabase.
Source_Used_Citation_Abbreviation: CUES
Process_Date: 20040101
Process_Step:
Process_Description:
GeoPlan took the data from the Statewide Noise Barrier GeoDatabase two disk set in May 2005. The layer was called NBGD_ALL and located in the Feature Dataset NBGD of the FDOT_NAB_GDB.mdb (on disk 1). This feature class was in Albers HPGN. A DESCRIPT field was added and based on the field ROAD_DESCR.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20050501
Process_Step:
Process_Description:
Noise barrier locations were received from the Florida Department of Transportation via email as a spreadsheet in excel format in November of 2009. These noise barriers have been built since the initial CUES data was created or are planned to be built in the future.
Noise barrier records containing TO and FROM, Latitude and Longitude information were formatted to Decimal Degrees. Once in Decimal Degrees the records were brought into ArcMap. Using the XY Tool in ArcMap the records were then converted to point features. These point features were then used as a guide along with Google Maps Street View to properly locate these noise barrier line features.
Noise barriers without to and from latitude and longitude information were created using the RCI road id associated with the barrier and the beginning and ending mile post. Line route events were created using the basemap.route.road RCI basemap coverage and a table provided by FDOT that contained noise barrier locations. The route events were created in ArcMap 9.3.1 using the Add Route Events tool. Barriers that have already been constructed were verified when possible using Google maps street view or aerial imagery. Planned barriers rely on the accuracy of the RCI Road ID, Beginning Mile Post, and End Mile Post data provided by FDOT.
Noise barrier records with no TO and FROM latitude and longitude or RCI Road ID and Beginning and Ending Mile Post information have been placed when possible based on the approximate location, group, and Highway / Route Number fields. In some instances not enough information is available to confidently locate these barriers. At this time these records have been omitted until further information on their location can be obtained.
There are currently 45 noise barrier locations that have been omitted.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20100410
Process_Step:
Process_Description:
GeoPlan reviewed the original table of unlocated constructed sound barriers. During this process 5 of the 8 existing missing sound barriers were located.
There are currently 40 noise barrier locations that have been omitted.
It was noted that a few roadways maybe creating new sound barriers in the future.
US 27 from Ritchie Road to south of Barry Road <ftp://ftp.dot.state.fl.us/LTS/d1/profserv/12155/AECOM%20Presentation.pdf>
I-75 and Palmetto,Express Lanes workshop 16 locations for new or replacement sound barriers, pg 28 <http://75-express.com/wp-content/uploads/2013/01/FINAL-I-75-ELs-Industry-Workshop.pdf>
It was also noted that a large number of the proposed sound barriers in the original table are for FDOT District 7, using aerial photography and street view to located these missing features was not possible at this time.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20130904
Process_Step:
Process_Description:
Per a request by FDOT District 4, four features were removed by the GeoPlan Center on December 9th, 2013.
These four features can be identified in noise_barriers_sep13.shp by the following FPN_NO number 249035-1
These features were removed because no sound barriers currently exist at this location and at this time none are planned for future construction at this location.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20131209
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 489
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.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.002048
Ordinate_Resolution: 0.002048
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: D_North_American_1983_HARN
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: NOISE_BARRIERS_DEC13
Entity_Type_Definition: NOISE_BARRIERS_DEC13.DBF
Entity_Type_Definition_Source: FDOT
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: NBID
Attribute_Definition:
Key identifer created by CUES. The Key Identifier developed for this project is a combination of FDOT's multiple unique identifiers including identifiers that distinguish each individual District office as well as the county the wall is located in. See NOISE_ABATEMENT_BARRIERS.pdf
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: ROADWAY
Attribute_Definition: Roadway characteristic ID index
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: BEGIN_POST
Attribute_Definition:
Beginning Mile Post. For Center for Urban and Environmental Solutions created featurs this is derived from D6 fields
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: END_POST
Attribute_Definition:
End Mile Post. For Center for Urban and Environmental Solutions created featurs this is derived from D6 fields
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: FPN_NO
Attribute_Definition: FPN number
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: RCI
Attribute_Definition: Roadway characteristic index from 2000 inventory
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: GROUP_
Attribute_Definition: No definition available.
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: APPROX_LOC
Attribute_Definition: Approximate barrier location
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: STATE_FIPS
Attribute_Definition: Statewide FIPS code
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: FDOT_DISTR
Attribute_Definition: FDOT district ID
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: COUNTY_FIP
Attribute_Definition: County FIPS code
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: COUNTY_F_1
Attribute_Definition: County FIPS code 2
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: COUNTY_NAM
Attribute_Definition: County name
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: ROAD_DESCR
Attribute_Definition: RCI roadway description
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: WALL_ID
Attribute_Definition: Wall ID - 2000 inventory
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: SECTION_
Attribute_Definition: Section - 2000 inventory
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: BARRIER_ID
Attribute_Definition: Barrier ID - 2000 inventory
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: WPI_ID
Attribute_Definition: WPI_ID - 2000 inventory
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: FM_ID
Attribute_Definition: Derived from D6 fields - Recommended fields by D6
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: CONTRACTOR
Attribute_Definition: Contractor
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: MATERIAL
Attribute_Definition: Construction material
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: BLOC_ONRTE
Attribute_Definition: Barrier location on route
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: B_LOC_SIDE
Attribute_Definition: Side of road where barrier is located
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: LEN_METER
Attribute_Definition: Length in meters
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: LEN_FEET
Attribute_Definition: Length in feet
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: HGT_METER
Attribute_Definition: Height in meters
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: HGT_FEET
Attribute_Definition: Height in feet
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: AREA_METER
Attribute_Definition: Area in meters
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: AREA_FT
Attribute_Definition: Area in feet
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: G_LENGTH
Attribute_Definition: Length generated by GIS
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: OVERLAP
Attribute_Definition: Overlapping walls
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: TOTAL_COST
Attribute_Definition: Total cost
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: COST_MET
Attribute_Definition: Cost per meter
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: COST_FT
Attribute_Definition: Cost per feet
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: PREDICTED
Attribute_Definition: Predicted
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: MEASUE
Attribute_Definition: Measure
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: B_COORD
Attribute_Definition: Coordinates of barrier beginning
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: E_COORD
Attribute_Definition: Coordinates of barrier ending
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: BEG_X
Attribute_Definition: Derived from D6 fields
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: BEG_Y
Attribute_Definition: Derived from D6 fields
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: END_X
Attribute_Definition: Derived from D6 fields
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: END_Y
Attribute_Definition: Derived from D6 fields
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: FR_LAT
Attribute_Definition: From latitude
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: FR_LONG
Attribute_Definition: From longitude
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: T_LAT
Attribute_Definition: To latitude
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: T_LONG
Attribute_Definition: To longitude
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: COMMENTS
Attribute_Definition: Comments
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: NOTES
Attribute_Definition:
General notes about barrier. If available contains online linkage to view barrier.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: NOTES2
Attribute_Definition: General notes continued
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: PIC
Attribute_Definition: Pic hyperlink to path
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: PDF_LINKS
Attribute_Definition: PDF hyperlink to path
Attribute_Definition_Source: FDOT
Attribute:
Attribute_Label: REVIEWED
Attribute_Definition:
How barrier was reviewed/verified. The majority of barriers were reviewed using google street view and ESRI's online imagery.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: TYPE
Attribute_Definition: Type of barrier, either planned or constructed
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SOURCE
Attribute_Definition:
Source of feature. The actual source of all barrier info is FDOT. This field denotes which organization created the feature in this dataset for FDOT.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: YR_BUILT
Attribute_Definition: Year built
Attribute_Definition_Source: FDOT
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: TBD
Enumerated_Domain_Value_Definition: To be determined
Enumerated_Domain:
Enumerated_Domain_Value: 0
Enumerated_Domain_Value_Definition: Unknown
Attribute:
Attribute_Label: DESCRIPT
Attribute_Definition: FGDL added field based on ROAD_DESCR
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: FGDLAQDATE
Attribute_Definition: The date FGDL acquired the data from the source.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: AUTOID
Attribute_Definition: Unique ID added by GeoPlan
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SHAPE.LEN
Attribute_Definition: Length in meters
Attribute_Definition_Source: GeoPlan
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Florida Geographic Data Library (FGDL)
Contact_Person:
Contact_Position:
Contact_Address:
Address_Type: mailing address
Address: 431 Architecture PO Box 115706
City: Gainesville
State_or_Province: Florida
Postal_Code: 32611-5706
Country: United States
Contact_Voice_Telephone:
Contact_TDD/TTY_Telephone:
Contact_Facsimile_Telephone:
Contact_Electronic_Mail_Address: Web site: <http://www.fgdl.org>
Contact_Electronic_Mail_Address: Technical Support: <http://www.fgdl.org/fgdlfeed.html>
Contact_Electronic_Mail_Address: For FGDL Software: <http://www.fgdl.org/software.html>
Contact_Electronic_Mail_Address:
FGDL Frequently Asked Questions: <http://www.fgdl.org/fgdlfaq.html>
Contact_Electronic_Mail_Address: Mailing list for FGDL: <http://www.fgdl.org/fgdl-l.html>
Hours_of_Service:
Contact_Instructions:
Resource_Description: DOWNLOADABLE DATA
Distribution_Liability:
The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist.
Furthermore, the GIS data available in the FGDL are provided 'as is'. 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 data sources. 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 shall not be liable for any damages suffered as a result of using, modifying, contributing or distributing the materials.
A note about data scale:
Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data.
1:24000 scale datasets 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 datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets 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 analysis. 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 webpage at: <http://geoplan.ufl.edu/education.html>
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 0.165
Technical_Prerequisites:
This data is intended for use with a Geographic Information Systems or Remote Sensing software package.
Metadata_Reference_Information:
Metadata_Date: 20131209
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Florida Department of Transportation, Environmental Management Office
Contact_Person: Mariano Berrios
Contact_Address:
Address_Type: mailing and physical address
Address: 605 Suwannee Street
City: Tallahassee
State_or_Province: FL
Postal_Code: 32399
Country: USA
Contact_Voice_Telephone: 1-866-374-3368 ext. 4447
Contact_Facsimile_Telephone: 850-414-4443
Contact_Electronic_Mail_Address: peter.mcgilvray@dot.state.fl.us
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Generated by mp version 2.9.6 on Fri Jan 10 14:58:01 2014