FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: FLORIDA DEPARTMENT OF TRANSPORTATION NOISE ABATEMENT BARRIERS - 2019 Geodataset Name: NOISE_BARRIERS_SEP19 Geodataset Type: SDE Feature Class Geodataset Feature: Polyline Feature Count: 1174 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): Florida Department of Transportation, Environmental Management Office SCALE OF ORIGINAL SOURCE MAPS: Varies GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: NOISE_BARRIERS_SEP19.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
Shape
|
4 | Geometry |
FPN_NO
|
10 | String |
FM_ID
|
15 | String |
WPI_ID
|
8 | Double |
ROADWAY
|
25 | String |
BEGIN_POST
|
13 | String |
END_POST
|
13 | String |
FED_ROUTE
|
40 | String |
APPROX_LOC
|
60 | String |
FDOT_DISTR
|
10 | String |
TYPE
|
20 | String |
FED_STREF
|
35 | String |
FED_STATE
|
10 | String |
FED_COUNTY
|
25 | String |
FED_CITY
|
50 | String |
ZIPCODE
|
8 | Double |
WALL_ID
|
8 | Double |
SECTION
|
8 | Double |
BARRIER_ID
|
25 | String |
FED_CYCOST
|
8 | Double |
FED_COST
|
8 | Double |
FED_COSTFT
|
8 | Double |
FED_HEIGHT
|
8 | Double |
FED_LENGTH
|
8 | Double |
FED_AREA
|
8 | Double |
FED_YRCON
|
8 | Double |
FED_ANR
|
8 | Double |
FED_NAC
|
5 | String |
BEN_RCPTRS
|
4 | Integer |
TOT_RCPTRS
|
4 | Integer |
RCPTR_NOTE
|
100 | String |
RCPTR_FLAG
|
10 | String |
FED_MATERL
|
50 | String |
FED_OMAT
|
50 | String |
FED_FEATRS
|
50 | String |
FED_STEXTR
|
20 | String |
FED_FNDTN
|
25 | String |
FED_PTYPE
|
5 | String |
FED_MDATE
|
25 | String |
FED_GISLOB
|
100 | String |
BLOC_ONRTE
|
30 | String |
BLOC_SIDE
|
20 | String |
BLOC_BND
|
20 | String |
CONTRACTOR
|
40 | String |
COMMENTS
|
250 | String |
NOTES
|
250 | String |
PIC_LINKS
|
80 | String |
PDF_LINKS
|
80 | String |
FR_LAT
|
8 | Double |
FR_LONG
|
8 | Double |
T_LAT
|
8 | Double |
T_LONG
|
8 | Double |
G_LENGTH
|
8 | Double |
REVIEWED
|
20 | String |
TBR_NOTE
|
100 | String |
TBR
|
5 | String |
SOURCE
|
50 | String |
GCID
|
8 | Double |
DESCRIPT
|
40 | String |
FLAG
|
5 | String |
UPDATE_DAY
|
36 | Date |
FGDLAQDATE
|
36 | Date |
AUTOID
|
4 | Integer |
SHAPE.LEN
|
0 | Double |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
Shape |
Feature geometry. |
|
FPN_NO |
Noise Barrier Federal Project Number/Identifier. |
|
FM_ID |
Florida Department of Transportation Financial Management (FM) System Project Number/Identifier of the Noise Barrier. |
|
WPI_ID |
Florida Department of Transportation Work Program Instructions Project Number/Identifier of the Noise Barrier. |
|
ROADWAY |
Road system designation used by RCI as the roadway identifier of which the Noise Barrier abuts. |
|
BEGIN_POST |
Noise Barrier start measure of the route in miles from the RCI. |
|
END_POST |
Noise Barrier end measure of the route in miles from the RCI. |
|
FED_ROUTE |
Route/Highway/Roadway where the Noise Barrier is located. |
|
APPROX_LOC |
Approximate Location of the Noise Barrier. |
|
FDOT_DISTR |
Florida Department of Transportation District Number in which the Noise Barrier falls. |
|
TYPE |
Noise Barrier Existance Type, Constructed/Planned etc.
|
|
FED_STREF |
State Reference Name of the Noise Barrier. |
|
FED_STATE |
The state in which the Noise Barrier is located. |
|
FED_COUNTY |
The county in which the Noise Barrier is located |
|
FED_CITY |
The city in which the Noise Barrier is located |
|
ZIPCODE |
The zip code in which the Noise Barrier is located |
|
WALL_ID |
FDOT District Noise Barrier Wall Identifier. |
|
SECTION |
FDOT District Noise Barrier Section Identifier. |
|
BARRIER_ID |
FDOT District Noise Barrier Identifier. |
|
FED_CYCOST |
Current Year Cost (2014) of the Noise Barrier. |
|
FED_COST |
Original Construction Cost of the Noise Barrier. |
|
FED_COSTFT |
Construction Unit Cost per Square-Feet of the Noise Barrier. |
|
FED_HEIGHT |
Average Height of Noise Barrier - Feet. |
|
FED_LENGTH |
Length of Noise Barrier - Feet. |
|
FED_AREA |
Area of Noise Barrier - Square Feet. |
|
FED_YRCON |
Year of Original Noise Barrier Construction. |
|
FED_ANR |
Average Noise Reduction - Noise Reduction Benefit of the Noise Barrier. |
|
FED_NAC |
NAC Code of the Noise Barrier. The FHWA NAC are objective absolute noise levels for varying land use categories where an impact is triggered. Traffic noise impacts occur based upon the definitions contained in 23 CFR 772.5. If impacts are identified, noise abatement measures must be considered and, if found to be feasible and reasonable must be implemented. http://www.fhwa.dot.gov/environment/noise/regulations_and_guidance/faq_nois.cfm#note17
|
|
BEN_RCPTRS |
Number of Impacted Potentially Benefited Receptors (Benefited Property Owners and Residents). A noise barrier must demonstrate that it will benefit at least two impacted receptors by providing a reduction in traffic-related noise of at least 5 dB(A). |
|
TOT_RCPTRS |
Number of Total Potentially Benefited Receptors (Benefited Property Owners and Residents). Total includes impacted/benefited residences and residences with a predicted noise level that does not approach or exceed 66 dBA, but are incidentally benefited. |
|
RCPTR_NOTE |
Receptor Notes. |
|
RCPTR_FLAG |
Receptor Flag. |
|
FED_MATERL |
Primary Noise Barrier Construction Material. Noise barriers can be constructed from earth, concrete, masonry, wood, metal, and other materials. To effectively reduce sound transmission through the barrier, the material chosen must be rigid and sufficiently dense (at least 20 kilograms/square meter). All noise barrier material types are equally effective, acoustically, if they have this density.
|
|
FED_OMAT |
Other Noise Barrier Construction Material, see Primary values. |
|
FED_FEATRS |
Noise Barrier Special Safety Features.
|
|
FED_STEXTR |
Noise Barrier Surface Texture.
|
|
FED_FNDTN |
Noise Barrier Foundation Material. Most barriers will be Ground Mounted.
|
|
FED_PTYPE |
Noise Abatement Program Type, based on new or existing roadway.
|
|
FED_MDATE |
Mandate for Noise Barrier Construction.
|
|
FED_GISLOB |
GIS Location of Noise Barrier FROM and TO Latitude/Longitude points. [FR_LAT] & " " & [FR_LONG] & "," & [T_LAT] & " " & [T_LONG] |
|
BLOC_ONRTE |
Noise Barrier Construction Mount Type. |
|
BLOC_SIDE |
Noise Barrier Location Orientation to Roadway. |
|
BLOC_BND |
Noise Barrier Location Orientation to Roadway Traffic Direction. |
|
CONTRACTOR |
Noise Barrier Original Construction Contractor. |
|
COMMENTS |
Comments on Noise Barrier. |
|
NOTES |
Notes on Noise Barrier. |
|
PIC_LINKS |
Picture Links of Noise Barrier. |
|
PDF_LINKS |
PDF Links of Noise Barrier. |
|
FR_LAT |
FROM Latitude - decimal degrees (WGS84). |
|
FR_LONG |
FROM Longitude - decimal degrees (WGS84). |
|
T_LAT |
TO Latitude - decimal degrees (WGS84). |
|
T_LONG |
TO Longitude - decimal degrees (WGS84). |
|
G_LENGTH |
GIS spatially derived length of the Noise Barrier - Feet. |
|
REVIEWED |
How GIS data was reviewed. |
|
TBR_NOTE |
To Be Reviewed - Notes. |
|
TBR |
To Be Reviewed - YES/NO. |
|
SOURCE |
Source of Spatial Data. |
|
GCID |
GeoPlan Center Internal Feature Identification. |
|
DESCRIPT |
Based on the field FED_ROUTE. |
|
FLAG |
Flag field denotes if the Noise Barrier was spatially verified using GIS / Imagery in ArcMap.
|
|
UPDATE_DAY |
The date the data was last updated by the Source. |
|
FGDLAQDATE |
The date FGDL acquired the data from the SOURCE. |
|
AUTOID |
Unique ID added by GeoPlan |
|
SHAPE.LEN |
Length in meters |
This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology |
This data is provided 'as is' by GeoPlan and is complete to our knowledge. |
GeoPlan relied on the integrity of the attribute information within the original data. |
Noise barriers are not always required at locations where an absolute threshold is met. There is no "number standard" which requires the construction of a noise barrier. Federal requirements for noise barriers may be found in Title 23 of the U.S. Code of Federal Regulations, Part 772, "Procedures for Abatement of Highway Traffic Noise and Construction Noise." The Federal Highway Administration noise regulations apply only to projects where a State transportation department has requested Federal funding for participation in the improvements. The State transportation department must determine if there will be traffic noise impacts, when a project is proposed for (1) the construction of a highway on new location or (2) the reconstruction of an existing highway to either significantly change the horizontal or vertical alignment or increase the number of through-traffic lanes. If the State transportation department identifies potential impacts, it must implement abatement measures, possibly including the construction of noise barriers, where reasonable and feasible. Federal law and Federal Highway Administration regulations do not require State transportation departments to build noise barriers along existing highways where no other highway improvements are planned. They may voluntarily do so, but they are solely responsible for making this decision. 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 |
The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes. |
This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan |
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan |
None |
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 |
Florida Department of Transportation, Environmental Management Office https://www.fdot.gov/environment/default.shtm 2004 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 United States Department of Transportation (USDOT or DOT) Federal Highway Administration (FHWA) Noise Barrier Inventory Tool https://www.fhwa.dot.gov/ENVIRONMENT/noise/noise_barriers/inventory/inventory_tool/index.cfm FDOT June 2000 Noise Barrier Status Report (Spreadsheet) Contact: win.lindeman@dot.state.fl.us for details. |
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 than 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. Process Date: 20040101 |
Projection ALBERS Datum HPGN Units METERS Spheroid GRS1980 1st Standard Parallel 24 0 0.000 2nd Standard Parallel 31 30 0.000 Central Meridian -84 00 0.000 Latitude of Projection's Origin 24 0 0.000 False Easting (meters) 400000.00000 False Northing (meters) 0.00000
DATA SOURCE CONTACT (S):
Name: Abbr. Name: Address: Phone: Web site: E-mail: Contact Person: Phone: E-mail: |
Florida Department of Transportation, Environmental Management Office FDOT 605 Suwannee Street, MS 37 Tallahassee, FL 32399-0450 850-414-5226 |
Name: FLORIDA GEOGRAPHIC DATA LIBRARY Abbr. Name: FGDL Address: Florida Geographic Data Library 431 Architecture Building PO Box 115706 Gainesville, FL 32611-5706 Web site: http://www.fgdl.org Contact FGDL: Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html