Many counties have incomplete roadway inventories, but lack asset management programs, which are often cost-prohibitive and require advanced technical training and staff to maintain. The Upper Great Plains Transportation Institute at North Dakota State University (NDSU), has developed a low-cost asset inventory program called the Geographic Roadway Inventory Tool (GRIT). The program, which is currently available to North Dakota counties, will be offered to all Minnesota counties following further development and testing by the Minnesota Local Road Research Board.
NDSU created the asset inventory program as the first step for asset management to allow local roadway managers to document and understand their existing infrastructure using the latest mobile technology and Geographic Information System technology.
The goal of the research study is to expand the program to include roadway forecasting based on the American Association of State and Highway Transportation Officials(AASHTO) 93 model with inventory, pavement condition and traffic forecasting data.
Existing input data from GRIT, such as pavement thickness, roadway structural information and construction planning information, will be spatially combined with current Pathway pavement condition and traffic data from MnDOT to automatically forecast the future condition and age of roadways using the AASHTO 93 model. This forecasting model will then allow roadway managers to use this information with comprehensive GIS web maps to prioritize roadways in construction schedule or multi-year plans.
The additional information contained in the pavement forecast system will allow county roadway managers to prioritize projects that can benefit from lower cost pavement preservation activities and understand how long roadways can last before a high cost reconstruction must take place. The online GIS output maps will also enable the public to see what projects will be conducted on a year-to-year basis.
The research team will work with Beltrami, Pope, Faribault, Pennington, and Becker counties and the city of Moorhead in Minnesota to research, develop, test and implement an additional forecasting function of the existing asset management program. This will be done using the AASHTO 93 empirical model to calculate a future pavement serviceability rating (PSR) based on the existing pavement structure and age, forecasted traffic and the latest pavement condition. While existing pavement structure and age information will come from data entered into the GRIT program by counties, processes and procedures will be researched and developed to automatically access pavement condition and traffic data from MnDOT and geospatially combine it with inventory data.
With pavement forecast information, county roadway managers will be able to better understand which roadways will deteriorate first and which will benefit from more effective, low-cost maintenance programs rather than full-depth reconstructions. The model will not forecast suggested future projects or project costs, but rather just output the future condition of the roadways on a yearly basis. The AASHTO model can be applied for both flexible and rigid pavement sections.
Local agencies are increasingly looking at converting low-trafficked paved roads to gravel at the end of their life span to make budgets stretch. However, agencies have few resources to guide them in this process.
The Minnesota Local Road Research Board recently approved funding for a guidebook on effective practices for converting severely distressed paved roads to unpaved roads. The document will help engineers select roads for conversion, safely conduct conversions and communicate the rationale to the public. No such published document currently exists.
The guidebook will be divided into chapters, which will cover:
Methods to determine if a road is a candidate for conversion and determine the existing road materials and condition.
Methods to convert a road from paved to unpaved.
Methods to assess the life-cycles cost of construction and maintenance of the unpaved road.
Tools to effectively inform and communicate with the public
Safety implications of converting a severely distressed paved road to an unpaved road.
While low- volume roads are typically identified as having an annual average daily traffic (AADT) of less than 400, roads that are appropriate candidates for conversion will typically have an AADT of less than 150.
These roads are often used by agricultural and extraction industries or to access homes and recreational areas. The type of road users, traffic patterns and vehicle types are all factors that need to be considered in the decision to unpave a road. Other factors include road condition, safety, agency maintenance and maintenance capabilities, as well as a life-cycle cost comparison of maintenance options (continued maintenance of the deteriorating road, rehabilitation of the paved road or conversion to an unpaved surface).
According to the research team, very limited information is available about converted roads, and what information is available often comes in the form of newspaper articles and anecdotal accounts of road conversions.
The document will serve as a formal and peer-reviewed information source. The use of the guide and acceptance of the practice of converting from paved to unpaved surfaces (unpaving) where warranted will provide a case for the acceptance of road conversions as another low-volume road management strategy.
The city of Shoreview, Minnesota was on the right track when it took the unusual step of paving a residential neighborhood with pervious concrete to help control stormwater and pollutant runoff into a nearby lake, according to a recently released seven-year performance study.
Typically used for parking lots and sidewalks, porous paving material allows stormwater to filter through the pavement and an aggregate base into the soil rather than run off the pavement and drain into storm sewers.
Shoreview bucked convention by using pervious concrete in a traffic application — low-volume, low-speed roads in the Woodbridge neighborhood near Lake Owasso. The city thought pervious pavement could help meet community sustainability goals and federal clean water regulations by reducing pollutants in waterways and groundwater while keeping water safely off driving surfaces.
Traditionally, pervious concrete hadn’t been used for roadways because engineers didn’t consider it strong enough for traffic (this and other projects have now demonstrated its application for low-volume roads like neighborhood streets). The impact on ride quality, tire-pavement noise and filtration was also not well understood, particularly in cold climates with freeze-thaw cycles like those in Minnesota.
Pervious concrete also presented a maintenance challenge: Organic debris, sand and other grit can clog the pavement’s pores. Periodic vacuuming is required to maintain the intended flow of water through the pavement. Concerned about how best to maintain the pavement and interested in tire-pavement noise levels and filtering performance, Shoreview, MnDOT and the Local Road Research Board monitored the Woodbridge roadways for seven years.
Installation and Evaluation
Shoreview replaced 9,000-square -feet of asphalt roads with 7 inches of pervious concrete over 18 inches of coarse aggregate base; near the lake, highly drainable sand served as the base. About twice each year for five years, researchers tested sound absorption, water infiltration and ride quality one day after the pavement had been vacuumed. In 2015, they repeated these tests without vacuuming the day before.
The pervious pavement performed well in filtering stormwater. By 2012, at least 1.3 acre-feet of water had filtered through the pavement and ground, and by 2015, nearly 2 acre-feet of water had filtered through the surface—all of which would otherwise have run directly into Lake Owasso.
Water infiltration and sound absorption rates were higher than traditional concrete, although rates declined over time because organic material continued to clog pavement pores despite vacuuming twice a year.
Initial construction of the pervious concrete streets and stormwater filtration system was slightly more costly than construction of comparable asphalt pavement with culverts. Life-cycle costs, including projections of maintenance costs over 15 years, however, showed somewhat lower costs for pervious pavement. While the pervious concrete pavement may require diamond grinding after 10 years, monthly vacuuming could make this unnecessary. Asphalt pavement would typically require a mill-and-overlay at year 15, and culverts would require periodic cleaning.
Additional benefits of the pervious pavement system that were not included in cost calculations—but were clearly significant—included complying with the federal Clean Water Act, recharging groundwater and avoiding direct pollution of Lake Owasso. Shoreview’s investment in pervious concrete has paid off economically and environmentally.
For additional information about this line of research, see these resources:
Researchers have developed a tool to help Minnesota local agencies make cost-effective pavement marking decisions in their counties. The spreadsheet-based tool was developed as part of a recently completed research study by the Minnesota Local Road Research Board.
What Was the Need?
Minnesota has many miles of low-volume roads, most marked with yellow centerline and white edge lines. Applying and maintaining these markings is a significant financial investment for local agencies, which typically work within very constrained budgets. These agencies needed more information about the value and the initial and ongoing costs of typical 4-inch and enhanced 6-inch pavement markings on low-volume roadways. They also needed clarification and guidance for prioritizing pavement marking installation and maintenance that could work within their limited budgets.
What Was Our Goal?
The goal of this research was to develop a prioritization approach and a decision-making tool for using pavement markings on low-volume roads based on the benefits and costs of these markings. Local agencies could then use these resources to make cost-effective decisions about installing and maintaining pavement markings.
What Did We Do?
Researchers took a multistep approach to identifying critical pavement marking information and practices:
• Conducted a literature search of existing research on typical (4-inch) and enhanced (6-inch) pavement markings, focusing on the benefits (such as crash reduction and improved lane-keeping), costs and current maintenance practices.
• Surveyed Minnesota counties to learn about their current practices and management approaches for pavement markings.
• Reviewed existing County Road Safety Plan (CRSP) methodology to learn about research and data used to rank at-risk road segments and identify CRSP improvement strategies, specifically the range of pavement markings that CRSPs recommended.
Researchers were then able to develop a prioritization approach and a decision-making tool that incorporated both past research and local state of the practice. In addition to producing a final report describing task results, they developed a brochure explaining the approach, the tool and implementation steps.
“This innovative tool will help local agencies make pavement marking decisions under tight budget constraints, where the question is always how to best allot funds for competing needs. This tool clarifies the problems and helps prioritize the possible solutions,” said David Veneziano, LTAP Safety Circuit Rider, Iowa State University Institute for Transportation.
What Did We Learn?
The literature search revealed limited research addressing traditional pavement marking use and effectiveness on local roadways. Pavement markings produce safety benefits, including reduced crash rates, but showed no real effects on vehicle speed, indicating that pavement markings may not alter driver behavior. Only limited efforts were identified in the literature aimed at investigating the prioritization and management of pavement markings.
The survey of local Minnesota agencies revealed that most counties use centerline and/or edge lines, which may be the result of MnDOT State-Aid Operation Rules. Some counties mark all their roads; most use 4-inch latex paint or epoxy markings. Repainting schedules depend upon road age, marking condition and county budgets.
A review of Minnesota counties’ CRSPs showed they included pavement marking recommendations. The CRSPs recommended, on average, 109 miles of pavement markings in every county. Applying one linear foot of centerline costs about 5 cents; 100 miles of centerline cost $26,400. Because of the extent of these recommendations, researchers directly incorporated the methods and directives from the CRSPs into their prioritization approach and tool.
The spreadsheet tool produced through this project allows users to enter road site characteristics such as pavement condition, road width, the CRSP rating and traffic volume, as well as the age of extant markings, costs, durability and the potential for crash reduction. Pavement marking options include centerline and/or edge lines, high visibility markings and enhanced durability materials. The tool uses factor weights that assign a relative importance to each criterion for any potential marking approach compared to other alternatives. The result is a performance rating score for each marking alternative. Thus, the tool assists not only in identifying the physical aspects of a road segment, it also incorporates the agency’s preferences, priorities and budget through a priority-weighting feature that generates the cost or cost range for a marking project.
Recommendations for further research include conducting a follow-up survey of users
of the new spreadsheet tool to facilitate future modifications, creating databases of roadway characteristics to simplify agencies’ use of the tool, and performing additional research on the safety and other effects of pavement markings. Researchers also encouraged agencies to keep in mind a proposed national retroreflectivity rule for the Manual on Uniform Traffic Control Devices that could affect pavement marking practices on low-volume roads. This rule has not yet been finalized or implemented.
Data from a new system for tracking work zone intrusions may be used to change work zone design and policies, reducing the risk of injury and death from intrusion crashes.
MnDOT and the Local Road Research Board engaged researchers to develop a user-friendly system that allows highway crews to quickly record instances of motorists’ intrusion into work zones, using a laptop, tablet or paper.
“This collaboration resulted in a fast, efficient and easy-to-use system because crews and supervisors let us know throughout the process exactly what they needed to consistently report work zone intrusions,” said Nichole Morris, Director, University of Minnesota HumanFIRST Laboratory.
What Was Our Goal?
The goal of this research project was to develop and test an efficient, comprehensive and user-friendly reporting system for intrusions into work zones. It was essential for the system to be accepted by highway workers. The information collected from the system, which was modeled after the existing MNCrash report, would then be used to examine risk factors to reduce intrusions and danger to workers. Safety data would be relayed back to workers and to MnDOT managers, providing an empirical basis for design changes to work zones, as well as future policy recommendations to the state government.
“To reduce work zone intrusions and make work zones safer, we need to track and analyze the intrusions. This reporting system will generate the data we need to make smart changes and possibly to influence legislative policy,” said Todd Haglin, Emergency Management and Safety Manager, MnDOT Office of Administration.
What Did We Do?
To design a usable system for reporting work zone intrusions, research designers had to:
Understand the characteristics of the typical system user (in this case, the work zone supervisors and crew).
Develop common or typical intrusion scenarios to realistically test the system.
Conduct iterative testing with typical users (supervisors and crew members) and incorporate revisions based on test results.
The research team interviewed work zone supervisors from rural and urban truck station locations across the state: in Baxter, St. Cloud and Duluth and at Cedar Avenue near Minneapolis-St. Paul. Researchers sought to learn what crews and supervisors considered an intrusion and what they thought should be reportable elements of the intrusion, such as the work zone layout, weather, location, time, visibility, road conditions and maneuvers of the intruding vehicle.
Researchers used information gathered from the interviews to develop four typical intrusion scenarios—which were reviewed and revised by MnDOT supervisors—and used these scenarios to test the prototype reporting interface. Then they conducted usability tests with these scenarios and with actual intrusions that crews had experienced. Users suggested changes to the report format throughout the process.
Crews and supervisors collaborated with researchers during three rounds of testing, revising the reporting interface after each round. An online beta version had been supplemented with a paper version. Both versions were revised through this iterative design process.
What Did We Learn?
This design approach allowed the research team to produce a report interface incorporating the very specific needs of the work zone crews and supervisors:
The third major revision split the report decision flow into two options—a shorter report and a comprehensive report—based on whether the intrusion presented a risk to the crew. Without this revision, intrusions that workers considered minor were not likely to be reported.
Researchers surveyed users of the system with each revision. Supervisors liked the drop-down menus, the comprehensiveness of the system and its ease of use. They rated the final revision as good in terms of usability, ease of use and time to completion (five to six minutes on average).
The final design version was tested using a laptop, tablet and paper. Multiple reporting options made it more likely that workers and supervisors would quickly report data about a work zone intrusion before details were forgotten.
Supervisors and workers involved in the design process gave high marks to the final version of the reporting system. The design is considered complete. Researchers had created the interface as a free-standing program, using the University of Minnesota’s digital resources to build and evaluate their design. For this reporting system to be made vailable for use by MnDOT and other agency workers, MnDOT must engage MNIT, the state’s information technology professionals, to determine where the system will reside and to integrate it into the state’s existing computer platform.
In a recently completed pilot study, researchers developed maps for two Minnesota counties that rank the failure potential of every slope using a geographic information system (GIS)-based model.
“GIS mapping has been applied to very small watersheds. The two counties in this study are huge areas in comparison. We used a physics-based approach that shows engineers where slope failure is likely to occur,” said Omid Mohseni, Senior Water Resources Manager, Barr Engineering Company.
What Was Our Goal?
The goal of this study was to determine if slope failure models could be developed to help counties anticipate where failures may occur. Researchers used publicly available data, research findings and geotechnical theory to develop failure models that could then be mapped with GIS in two topographically dissimilar Minnesota counties. These maps would identify slopes susceptible to failure so that county highway departments could develop preventive strategies for protecting roadways from potential lope failure or prepare appropriate failure response plans.
What Did We Do?
Researchers began with a literature review of studies about the causes of slope failure, predictive approaches and mapping. They were particularly interested in research related to potential failure mechanisms, algorithms used for predicting failures and slope-failure susceptibility mapping.
Then investigators collected data on known slope failures in Carlton County in eastern Minnesota and Sibley County in south central Minnesota to identify failure-risk factors not found in the literature. Researchers reviewed various statewide data sets, identifying topographic, hydrologic and soils information that could be used in GIS-based modeling. Next, they developed a GIS-based slope-failure model by incorporating the available data with geotechnical theory and probability factors from hydrologic data, and writing computer code to allow the data to be input into mapping software.
Researchers tested the software on known failure sites to refine soil parameter selection and failure models. The refined models and software were then used to identify and map slope failure risks in Carlton and Sibley counties.
What Did We Learn?
After analyzing the literature and the failure and geotechnical data, researchers identified the following key causal factors in slope failure: slope angle, soil type and geology, vegetation, land use and drainage characteristics, soil moisture, and rainfall intensity and duration.
Researchers then developed mapping models for the two counties using three key data sets. The first was data from 3-meter resolution, high-quality lidar, which measures distances with laser range finders and reflected light, available through Minnesota’s Department of Natural Resources website. The team augmented this data with U.S. Department of Agriculture soils survey data, and with National Oceanic and Atmospheric Administration and National Weather Service hydrologic data for precipitation and storm duration information.
Based on research in geotechnical theory, researchers developed algorithms for anticipating failure and built these into the lidar-based topographic mapping model. They also developed input parameters based on the failure factors and established output parameters representing five levels of failure susceptibility: very low, low, moderate, high and very high.
After testing the GIS-based model against a slope along County Highway 210 in Carlton County, researchers confirmed that failure potential correlated well with documented or observed slope failure. The team further validated the model by applying it to several small areas in the adjacent Carver and Sibley counties, finding similarly effective correlation with identifiable failure sites.
Independent geotechnical experts examined the modeling software and further refined geotechnical, soil and hydrologic elements. Finally, the team developed maps of Carlton and Sibley counties that assigned failure susceptibility levels to slopes in the two counties. Viewing maps through the software remains the most useful way to examine slopes, although large-format maps are available.
“If county engineers have higher slopes adjacent to roadways, they can use this basic tool to predict slope failures and then hire a geotechnical consultant to investigate the site.” – Tim Becker, Public Works Director, Sibley County
With additional funding, mapping could be extended to every county in Minnesota to further refine failure modeling. Maps may also be useful in identifying structures such as roadways, ecological features, transmission lines and pipelines, bridges and culverts that may be threatened by slope failure susceptibility. Potential risks could be used to prioritize slope treatment plans.
Pavement marking performance metrics from a new study will help Minnesota local agencies save time and money by choosing longer-lasting pavement marking products.
Researchers developed pavement marking performance metrics for Minnesota local agencies to use as a guide to make better pavement marking product decisions. The metrics were developed based on an analysis of survey data collected from Minnesota local agencies and MnDOT pavement marking data mined from the National Transportation Product Evaluation Program (NTPEP). Findings showed differences in product performance with regard to retroreflectivity and service life, which were impacted by variables such as road surface type, year of application, traffic volume and type of pavement marking.
“There would be great potential savings in using pavement marking products with a longer service life. Mining NTPEP data to analyze product performance has not been done before and should contribute substantially to this goal,” said Omar Smadi, Director, Iowa State University Center for Transportation Research and Education.
What Was Our Goal?
The goal of this research was to develop pavement marking performance metrics for Minnesota local agencies to use as a guide when choosing the most durable and cost-effective products. Researchers developed the pavement marking performance metrics, specifically for retroreflectivity and service life, by analyzing existing MnDOT data mined from NTPEP. They also used the findings to make recommendations for future pavement marking research to support local agency needs.
What Did We Do?
Researchers designed and conducted a survey to assess pavement marking products used by local agencies in the state. Then they extracted 2010 and 2013 MnDOT pavement marking data from NTPEP to analyze the performance of products that survey respondents identified as commonly used.
NTPEP data included products tested at two different sites and applied on different road surfaces. Researchers analyzed performance with regard to retroreflectivity and deterioration or longevity of the materials under various conditions, such as road surface type, year of application, traffic volume and type of pavement marking. Based on results from the analysis, researchers developed performance metrics for Minnesota local agencies to use as a guide for choosing particular pavement marking product types.
What Did We Learn?
From the survey results, researchers learned that the majority of Minnesota local agencies use either latex or epoxy as their primary pavement marking material. However, epoxy and tape outperformed latex at all levels of conditions and provided a service life of three years or more.
A few survey respondents also reported grooving as a method that seemed to extend the service life of latex paint markings. Researchers were unable to investigate the impact of grooving, however, since MnDOT grooving data was not accessible.
From the NTPEP data analysis, researchers concluded the following:
White markings had significantly higher initial retroreflectivity and slower deterioration than yellow markings.
Road surface type does not significantly impact retroreflectivity throughout its service life.
Epoxy has higher retroreflectivity than latex materials.
As expected, markings on wheel zones deteriorated faster, reducing retroreflectivity over time.
Deterioration values of markings varied among different test sites, which may be attributed to differences in average annual daily traffic (AADT) values (10,000 in 2010 versus 37,000 in 2013) or installation practices.
“The findings from this research will be beneficial for Minnesota local agencies in determining which pavement marking materials are most effective,” said Kate Miner, then-Scott County Traffic Manager.
Although the product performance metrics data will help Minnesota local agencies make better pavement marking product decisions in less time, researchers recommend developing a guidebook to make the information more usable. Adding grooving data to the guidebook would also be beneficial to investigate the potential impact grooving provides in extending the service life of pavement markings.
Researchers also recommend testing the same products evaluated in this research on low-volume local roads and on challenging surface types. MnDOT NTPEP data only included products that were tested on high-volume freeways.
Lane-departure crashes on curves make up a significant portion of fatal crashes on rural Minnesota roads. To improve safety, solutions are needed to help drivers identify upcoming curves and inform them of a safe speed for navigating the curve.
“Traditionally there are two ways to do this: with either static signage or with dynamic warning signs,” says Brian Davis, a research fellow in the U of M’s Department of Mechanical Engineering. “However, while signing curves can help, static signage is often disregarded by drivers, and it is not required for roads with low average daily traffic. Dynamic speed signs are very costly, which can be difficult to justify, especially for rural roads with low traffic volumes.”
In a recent project led by Davis on behalf of MnDOT and the Minnesota Local Road Research Board, researchers developed a method of achieving dynamic curve warnings while avoiding costly infrastructure-based solutions. To do so, they used in-vehicle technology to display dynamic curve-speed warnings to the driver based on the driver’s real-time behavior and position relative to the curve. The system uses a smartphone app located in the vehicle to provide the driver with visual and auditory warnings when approaching a potentially hazardous curve at an unsafe speed.
“Highway curves [make up] 19 percent of the total mileage of the paved St. Louis County highway system, yet these curves account for 47 percent of all severe road departure crashes,” says Victor Lund, traffic engineer with St. Louis County. “In-vehicle warnings will be a critical strategy to reduce these crashes.”
To begin their study, researchers designed and tested prototype visual and auditory warning designs to ensure they were non-distracting and effective. This portion of the study included decisions about the best way to visually display the warnings and how and when audio messages should be used. “To create the optimal user experience, we looked at everything from how to order the audio information and when the message should play to the best length for the warning message,” says Nichole Morris, director of the U’s HumanFIRST Lab and co-investigator of the study.
Next, a controlled field test was conducted to determine whether the system helped reduce curve speeds, pinpoint the best timing for the warnings in relation to the curves, and gather user feedback about the system’s usefulness and trustworthiness. The study was conducted with 24 drivers using the test track at the Minnesota Highway Safety and Research Center in St. Cloud, Minnesota. The selected course allowed drivers to get up to highway speeds and then travel through curves of different radii, enabling researchers to learn how sensitive drivers are to the position of the warnings.
Based on the study results, the system shows both feasibility and promise. “Our in-vehicle dynamic curve warning system was well-liked and trusted by the participants,” Davis says. “We saw an 8 to 10 percent decrease in curve speed when participants were using the system.”
The project was funded by MnDOT and the Minnesota Local Road Research Board.
Many local agencies in Minnesota lack funding to construct and maintain all the bridges in their roadway network. One way to lower costs is to reduce the number of bridges.
In Minnesota, some township bridges are on roads with low usage that have alternative accesses for nearby residents, but local officials are reluctant to remove the bridges.
To identify possible changes to how redundant and low-use bridges are identified and removed in Minnesota, the Local Road Research Board conducted a transportation research synthesis, “Local Bridge Removal Policies and Programs,” that explores how other states make bridge removal decisions.
Fifteen state DOTs responded to a survey about their processes, with varying levels of state oversight identified for bridge removal decisions. Researchers also examined funding and incentives offered by some DOTs to local agencies for bridge removal, as well as criteria for considering bridge removal.
A literature search of bridge design manuals, inspection manuals and bridge programs was also conducted to identify related policies and programs.
Read the TRS to learn more about the various bridge removal policies and procedures in place in Minnesota and other states.
To mark Earth Day 2016, MnDOT Research Services is taking a glance at five stellar examples of current research projects at MnDOT that involve pollution control, wetland mitigation, road salt reduction and new ways of recycling pavement.
Soil carried away in stormwater runoff from road construction sites can pollute lakes and rivers.
Stormwater settling ponds provide a place for this sediment to settle before the water is discharged into local bodies of water. However, since stormwater ponds have limited space, a mechanism is needed to remove clean water from the pond to prevent the overflow of sediment-laden water.
MnDOT-funded researchers designed temporary stormwater ponds with floating head skimmers that can remove clean water from the surface of the settling pond, using gravity to discharge water into a ditch or receiving body.
The study, which was completed in spring 2014, identified five methods for “skimming” stormwater ponds that can improve a pond’s effectiveness by 10 percent. MnDOT researchers also created designs for temporary stormwater ponds on construction sites with the capacity to remove approximately 80 percent of suspended solids.
These designs will help contractors meet federal requirements for stormwater pond dewatering. Researchers also determined how often a pond’s deadpool must be cleaned, based on watershed size and pool dimensions.
Stormwater can pick up chemicals and sediments that pollute rivers and streams. Roadside drainage ditches, also known as swales, lessen this effect by absorbing water. But until recently, MnDOT didn’t know how to quantify this effect and incorporate it into pollution control mitigation measures.
In a study completed in fall 2014, researchers evaluated five Minnesota swales, measuring how well water flows through soil at up to 20 locations within each swale.
A key finding: grassed swales are significantly better at absorbing water than expected, which may reduce the need for other, more expensive stormwater management practices, such as ponds or infiltration basins.
This could save MnDOT and counties significant right-of-way and construction costs currently expended on more expensive stormwater management techniques.
Road salt is used for de-icing roadways during winter months, but can have a negative impact on the environment.
This research, which was just approved for funding through the Minnesota Local Road Research Board in December 2015, will investigate the reduction in road salt application during winter months that can be attained with permeable pavements, while still providing for acceptable road safety.
Some initial investigations (see previous study) suggest that road salt application can be substantially reduced, even eliminated, with permeable pavement systems. The proposed research will investigate this hypothesis more thoroughly, and further document the reduction in road salt application that can be expected with permeable pavement.
Road construction in northeast Minnesota often causes wetland impacts that require expensive mitigation. However, borrow areas excavated for road construction material can be developed into wetland mitigation sites if hydric vegetation, hydric soils and adequate hydrology are provided. Fourteen wetland mitigation sites were constructed north of Virginia, Minnesota along the U.S. Trunk Highway 53 reconstruction project corridor and evaluated for wetland. The sites were established with the goal of mitigating for project impacts to seasonally flooded basin, fresh meadow, shallow marsh, shrub swamp, wooded swamp, and bog wetlands. All but one of the sites consistently meet wetland hydrology criteria.
The sites contain a variety of plant communities dominated by wet meadow, sedge meadow, and shallow marsh. Floristic Quality Assessment (FQA) condition categories for the sites range from “Poor” to “Exceptional.”
According to the research report published in March 2016, these sites have shown the potential for creating mitigation wetlands in abandoned borrow pits in conjunction with highway construction. Adaptive management, particularly water level regulation, early invasive species control, tree planting, and continued long-term annual monitoring can make mitigation sites like these successful options for wetland mitigation credit.
MnDOT already extends the lives of some old concrete highways by paving over them with asphalt instead of tearing them up. Now MnDOT hopes to add a third life for these old concrete roads by using a process called cold in-place recycling to re-use that existing asphalt pavement when it reaches the end of its life.
Cold in-place recycling (CIR) uses existing pavements, without heat, to create a new layer of pavement. It involves the same process of cold- central plant mix recycling (which is being employed by MnDOT for the first time on two shoulder repair projects this year), but it is done on the road itself by a train of equipment. It literally recycles an old road while making a new road.
CIR has been in use in Minnesota for 20 years, but only with hot-mix asphalt (HMA) over gravel roads. The purpose of a new study, which was approved for funding in April 2016, is to validate Iowa’s promising new practice using CIR on bituminous over concrete.
In this research project (see proposal), MnDOT will use cold-in-place recycling to replace the asphalt pavement on a concrete road and then evaluate it for several years, comparing it also with control sections.
Along with the potential of a better service life, the cost of CIR is much lower than new hot mix asphalt (HMA). Therefore, a 20-percent to 30-percent price reduction per project may be realized.