This dataset contains the Florida Department of Transportation's (FDOT) Noise Abatement Barriers. Noise barriers are solid obstructions built between the highway and the homes along a highway. They do not completely block all noise they only reduce overall noise levels. Effective noise barriers typically reduce noise levels by 5 to 10 decibels (dB), cutting the loudness of traffic noise by as much as one half. For example, a barrier which achieves a 10-dB reduction can reduce the sound level of a typical tractor trailer pass-by to that of an automobile. Barriers can be formed from earth mounds or "berms" along the road, from high, vertical walls, or from a combination of earth berms and walls. Earth berms have a very natural appearance and are usually attractive. They also reduce noise by approximately 3 dB more than vertical walls of the same height. However, earth berms can require a lot of land to construct, especially if they are very tall. Walls require less space, but they are usually limited to eight meters (25 feet) in height for structural and aesthetic reasons.(https://www.fhwa.dot.gov/environment/noise/noise_barriers/design_construction/keepdown.cfm) This is an update to the NOISE_BARRIERS_MAR19.shp FGDL layer.
The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes.
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
publication date
None
605 Suwannee Street, MS 37
Additional Contact: Peter McGilvray peter.mcgilvray@dot.state.fl.us
Florida Department of Transportation, GeoPlan Center, FHWA
GeoPlan relied on the integrity of the attribute information within the original data.
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.
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.
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
Spatial and Attribute Information
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.
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.
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.
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.
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.
GeoPlan Center updated the noise barrier data layer with information provided by the FDOT Districts to Mariano Berrios during the summer of 2014. Updates included both spatial and tabular changes/additions to a large number of records. The attribute table of the dataset was then restructured to meet spec with the FHWA 2014 Noise Barrier Excel Workbook Federal Submission Requirements. The dataset attribute table was not uppercased in order to keep the attributes in the FHWA standard format for future submissions. FHWA Federal Submission Requirement fields are prefaced with FED_.
GeoPlan Center updated the noise barrier data layer with information provided by the FDOT Districts to Mariano Berrios during the winter/spring of 2017. Updates included both spatial and tabular changes/additions to a large number of records. The attribute table of the dataset was then restructured to meet spec with the FHWA 2017 Noise Barrier Excel Workbook Federal Submission Requirements. The dataset attribute table was not uppercased in order to keep the attributes in the FHWA standard format for future submissions. FHWA Federal Submission Requirement fields are prefaced with FED_.
GeoPlan Center updated the noise barrier data layer with information provided by the FDOT Districts to Mariano Berrios during the winter/spring of 2018. Updates included both spatial and tabular changes/additions to a large number of records. The attribute table of the dataset was then restructured to meet spec with the FHWA 2019 Noise Barrier Excel Workbook Federal Submission Requirements. The dataset attribute table was not uppercased in order to keep the attributes in the FHWA standard format for future submissions. FHWA Federal Submission Requirement fields are prefaced with FED_. Below is a summary of the Noise Barrier data both added and updated for the March 2018 version. Noise Barriers GIS Layer May 2017 version record count: 995 Noise Barriers GIS Layer March 2018 version records count: 1152 161 Noise Barrier Records Added 130 Existing Noise Barrier Records Updated Total = 291 Breakdown of Newly Added Records District: 1 6 Recommended District: 2 3 Constructed District: 3 None Provided District: 4 None Provided District: 5 9 Constructed 45 Recommended District: 6 None Provided District: 7 8 Planned District: Turnpike 1 Constructed 19 Planned 1 Recommended District: CFX 69 Constructed * Primarily SR 408 & SR 417 all values are estimates as noted in table. * FED_MDATE marked as "State Regulation" as previously used for CFX roads. During this update process 19 FDOT Noise Study Reports were reviewed. Metadata was updated.
GeoPlan Center updated the noise barrier data layer with information provided by the FDOT Districts to Mariano Berrios during the winter/spring of 2019. Updates included both spatial and tabular changes/additions to a large number of records. The attribute table of the dataset was then restructured to meet spec with the FHWA 2019 Noise Barrier Excel Workbook Federal Submission Requirements. The dataset attribute table was not uppercased in order to keep the attributes in the FHWA standard format for future submissions. FHWA Federal Submission Requirement fields are prefaced with FED_. Below is a summary of the Noise Barrier data both added and updated for the March 2019 version. Noise Barriers GIS Layer March 2018 version record count: 1152 Noise Barriers GIS Layer March 2019 version records count: 1172 20 Noise Barrier Records Added 156 Existing Noise Barrier Records Updated Total = 176 Breakdown of Newly Added Records District: 1 1 record (Recommended found via web search) District: 2 No updates (1/18/2019) District: 3 16 records Provided on 1/3/2019 District: 4 District: 5 1 record (In Construction Process) Provided on 1/31/2019 District: 6 No updates (1/29/2019) District: 7 No updates (1/3/2019) District: Turnpike 1 record (In Constructed Process) District: CFX 1 (Recommended found via web search) * SR 408 EASTERN EXTN: CREST AT WATERFORD LAKES AND TORTUGA BA (408-254) * All values came from NSR. * FED_MDATE marked as "State Regulation" as previously used for CFX roads. During this update process 9 FDOT Noise Study Reports were reviewed. Metadata was updated.
GeoPlan Center updated the noise barrier data layer with information provided by the FDOT Districts to Michael Sykes during the summer of 2019. Updates included both spatial and tabular changes/additions to a large number of records. The dataset attribute table was updated to include the following new fields: BEN_RCPTRS TOT_RCPTRS RCPTR_NOTE RCPTR_FLAG Tabular data was populated for the years 2014-2018. Below is a summary of the Noise Barrier data both added and updated for the September 2019 version. Noise Barriers GIS Layer March 2019 version record count: 1172 Noise Barriers GIS Layer September 2019 version records count: 1174 2 Noise Barrier Records Added 196 Existing Noise Barrier Records Updated Total = 198 During this update process 68 FDOT Noise Study Reports were reviewed. Metadata was updated.
Metadata imported.
Internal feature number.
ESRI
Feature geometry.
ESRI
Noise Barrier Federal Project Number/Identifier.
GeoPlan
Florida Department of Transportation Financial Management (FM) System Project Number/Identifier of the Noise Barrier.
GeoPlan
Florida Department of Transportation Work Program Instructions Project Number/Identifier of the Noise Barrier.
GeoPlan
Road system designation used by RCI as the roadway identifier of which the Noise Barrier abuts.
GeoPlan
Noise Barrier start measure of the route in miles from the RCI.
GeoPlan
Noise Barrier end measure of the route in miles from the RCI.
GeoPlan
Route/Highway/Roadway where the Noise Barrier is located.
GeoPlan
Approximate Location of the Noise Barrier.
GeoPlan
Florida Department of Transportation District Number in which the Noise Barrier falls.
GeoPlan
Noise Barrier Existance Type, Constructed/Planned etc.
GeoPlan
CONSTRUCTED BARRIERS
GeoPlan
PLANNED BARRIERS
GeoPlan
RECOMMENDED BARRIERS
GeoPlan
State Reference Name of the Noise Barrier.
GeoPlan
The state in which the Noise Barrier is located.
GeoPlan
The county in which the Noise Barrier is located
GeoPlan
The city in which the Noise Barrier is located
GeoPlan
The zip code in which the Noise Barrier is located
GeoPlan
FDOT District Noise Barrier Wall Identifier.
GeoPlan
FDOT District Noise Barrier Section Identifier.
GeoPlan
FDOT District Noise Barrier Identifier.
GeoPlan
Current Year Cost (2014) of the Noise Barrier.
GeoPlan
Original Construction Cost of the Noise Barrier.
GeoPlan
Construction Unit Cost per Square-Feet of the Noise Barrier.
GeoPlan
Average Height of Noise Barrier - Feet.
GeoPlan
Length of Noise Barrier - Feet.
GeoPlan
Area of Noise Barrier - Square Feet.
GeoPlan
Year of Original Noise Barrier Construction.
GeoPlan
Average Noise Reduction - Noise Reduction Benefit of the Noise Barrier.
GeoPlan
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
GeoPlan
Lands on which serenity and quiet are of extraordinary significance and serve an important public need and where the preservation of those qualities is essential if the area is to continue to serve its intended purpose. Analysis Location: Exterior
http://www.fhwa.dot.gov/environment/noise/regulations_and_guidance/faq_nois.cfm#note17
Residential. Analysis Location: Exterior
http://www.fhwa.dot.gov/environment/noise/regulations_and_guidance/faq_nois.cfm#note17
Active sport areas, amphitheaters, auditoriums, campgrounds, cemeteries, daycare centers, hospitals, libraries, medical facilities, parks, picnic areas, places of worship, playgrounds, public meeting rooms, public or nonprofit institutional structures, radio studios, recording studios, recreation areas, Section 4(f) sites, schools, television studios, trails, and trail crossings. Analysis Location: Exterior
http://www.fhwa.dot.gov/environment/noise/regulations_and_guidance/faq_nois.cfm#note17
Auditoriums, day care centers, hospitals, libraries, medical facilities, places of worship, public meeting rooms, public or nonprofit institutional structures, radio studios, recording studios, schools, and television studios. Analysis Location: Interior
http://www.fhwa.dot.gov/environment/noise/regulations_and_guidance/faq_nois.cfm#note17
Hotels, motels, offices, restaurants/bars, and other developed lands, properties or activities not included in A-D or F. Analysis Location: Exterior
http://www.fhwa.dot.gov/environment/noise/regulations_and_guidance/faq_nois.cfm#note17
Agriculture, airports, bus yards, emergency services, industrial, logging, maintenance facilities, manufacturing, mining, rail yards, retail facilities, shipyards, utilities (water resources, water treatment, electrical), and warehousing.
http://www.fhwa.dot.gov/environment/noise/regulations_and_guidance/faq_nois.cfm#note17
Undeveloped lands that are not permitted.
http://www.fhwa.dot.gov/environment/noise/regulations_and_guidance/faq_nois.cfm#note17
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).
GeoPlan
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.
GeoPlan
Receptor Notes.
GeoPlan
Receptor Flag.
GeoPlan
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.
GeoPlan
precast concrete
GeoPlan
berm
GeoPlan
block
GeoPlan
cast in place concrete
GeoPlan
brick
GeoPlan
metal
GeoPlan
wood
GeoPlan
fiberglass
GeoPlan
combination
GeoPlan
plastic transparent
GeoPlan
plastic opaque
GeoPlan
plastic other
GeoPlan
Other Noise Barrier Construction Material, see Primary values.
GeoPlan
Noise Barrier Special Safety Features.
GeoPlan
Fire Access
GeoPlan
Emergency Exit
GeoPlan
Maintenance Access
GeoPlan
Noise Barrier Surface Texture.
GeoPlan
Absorptive
GeoPlan
Reflective
GeoPlan
Noise Barrier Foundation Material. Most barriers will be Ground Mounted.
GeoPlan
Ground-mounted noise barrier systems are barriers constructed into or placed on top of the ground.
GeoPlan
On Structure noise barrier systems are barriers constructed on over-passes, bridges, and retaining walls.
GeoPlan
Noise Abatement Program Type, based on new or existing roadway.
GeoPlan
The Type I program covers noise barrier construction coincidental with construction of major highways on new location, or physical alteration of an existing highway such as substantial realignment or widening to increase the number of through traffic lanes thereby increasing capacity. Such major projects usually require either an Environmental Impact Statement (EIS) or Environmental Impact Report (EIR) to satisfy the National Environmental Policy Act. As part of this analysis, the need for a noise barrier is evaluated for each individual highway project. Under the Type I program, if a noise barrier is determined to be reasonable and feasible, it must be constructed as part of the project. What is a Type I project? (1) The construction of a highway on a new location; (2) The physical alteration of an existing highway where there is either:(i) Substantial Horizontal Alteration. A project that halves the distance between the traffic noise source and the closest receptor between the existing condition to the future build condition; (ii) Substantial Vertical Alteration. A project that removes shielding therefore exposing the line-of-sight between the receptor and the traffic noise source. This is done by either altering the vertical alignment of the highway or by altering the topography between the highway traffic noise source and the receptor; or,(3) The addition of a through-traffic lane(s). This includes the addition of a through-traffic lane that functions as a HOV lane, High-Occupancy Toll (HOT) lane, bus lane, or truck climbing lane; (4) The addition of an auxiliary lane, except for when the auxiliary lane is a turn lane; (5) The addition or relocation of interchange lanes or ramps added to a quadrant to complete an existing partial interchange; (6) Restriping existing pavement for the purpose of adding a through-traffic lane or an auxiliary lane; or,(7) The addition of a new or substantial alteration of a weigh station, rest stop, ride-share lot or toll plaza.(8) If a project is determined to be a Type I project under this definition then the entire project area as defined in the environmental document is a Type I. Highway agencies should take a broad approach to defining turn lanes when considering projects with auxiliary lanes. Generally, consideration for auxiliary lanes on local roads should be limited to those that could be used as a through lane rather than lanes used for parking, speed change, turning or storage for turning weaving. For interstates, limit consideration to auxiliary lanes between two closely spaced interchanges to accommodate weaving traffic and auxiliary lanes carried through one or more interchanges. http://www.fhwa.dot.gov/environment/noise/regulations_and_guidance/faq_nois.cfm#note2
GeoPlan
The Type I program covers noise barrier construction coincidental with construction of major highways on new location, or physical alteration of an existing highway such as substantial realignment or widening to increase the number of through traffic lanes thereby increasing capacity. Such major projects usually require either an Environmental Impact Statement (EIS) or Environmental Impact Report (EIR) to satisfy the National Environmental Policy Act. As part of this analysis, the need for a noise barrier is evaluated for each individual highway project. Under the Type I program, if a noise barrier is determined to be reasonable and feasible, it must be constructed as part of the project. What is a Type II project? Usually called a retrofit project, a Type II project is a proposed Federal or Federal-aid highway project for noise abatement on an existing highway. Type II projects are not mandatory and are at a State's discretion. Projects of this type are proposed solely at the option of a State DOT, and specific requirements for the project are determined by the individual State DOT. Federal participation in the funding of such projects is limited to those that propose abatement measures along lands that were developed prior to construction of the original highway. For guidance on a Type II program, please contact the FHWA noise team. http://www.fhwa.dot.gov/environment/noise/regulations_and_guidance/faq_nois.cfm#note2
GeoPlan
A Type III project is a Federal or Federal-aid highway project that does not meet the classifications of a Type I or Type II project. Type III projects do not require a noise analysis. http://www.fhwa.dot.gov/environment/noise/regulations_and_guidance/faq_nois.cfm#note2
GeoPlan
A Type S project is a State highway project that does not meet the classifications of a Type I or Type II or Type III.
GeoPlan
A Type C project is a County highway project that does not meet the classifications of a Type I or Type II or Type III or Type S
GeoPlan
Mandate for Noise Barrier Construction.
GeoPlan
Federal Regulation
GeoPlan
State Regulation
GeoPlan
Local Ordinance
GeoPlan
Turnpike Authority
GeoPlan
Private Initiative
GeoPlan
GIS Location of Noise Barrier FROM and TO Latitude/Longitude points. [FR_LAT] & " " & [FR_LONG] & "," & [T_LAT] & " " & [T_LONG]
GeoPlan
Noise Barrier Construction Mount Type.
GeoPlan
Noise Barrier Location Orientation to Roadway.
GeoPlan
Noise Barrier Location Orientation to Roadway Traffic Direction.
GeoPlan
Noise Barrier Original Construction Contractor.
GeoPlan
Comments on Noise Barrier.
GeoPlan
Notes on Noise Barrier.
GeoPlan
Picture Links of Noise Barrier.
GeoPlan
PDF Links of Noise Barrier.
GeoPlan
FROM Latitude - decimal degrees (WGS84).
GeoPlan
FROM Longitude - decimal degrees (WGS84).
GeoPlan
TO Latitude - decimal degrees (WGS84).
GeoPlan
TO Longitude - decimal degrees (WGS84).
GeoPlan
GIS spatially derived length of the Noise Barrier - Feet.
GeoPlan
How GIS data was reviewed.
GeoPlan
To Be Reviewed - Notes.
GeoPlan
To Be Reviewed - YES/NO.
GeoPlan
Source of Spatial Data.
GeoPlan
GeoPlan Center Internal Feature Identification.
GeoPlan
Based on the field FED_ROUTE.
GeoPlan
Flag field denotes if the Noise Barrier was spatially verified using GIS / Imagery in ArcMap.
GeoPlan
Future Not Verified
GeoPlan
Not Verified
GeoPlan
Verified
GeoPlan
Verified (Multipart Feature)
GeoPlan
The date the data was last updated by the Source.
GeoPlan
The date FGDL acquired the data from the SOURCE.
GeoPlan
Unique ID added by GeoPlan
GeoPlan
Length in meters
GeoPlan
431 Architecture PO Box 115706
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
605 Suwannee Street, MS 37
Additional Contact: Peter McGilvray peter.mcgilvray@dot.state.fl.us