U.S. Department of Transportation
Federal Highway Administration
1200 New Jersey Avenue, SE
Washington, DC 20590
202-366-4000
Federal Highway Administration Research and Technology
Coordinating, Developing, and Delivering Highway Transportation Innovations
TECHNICAL REPORT |
This report is an archived publication and may contain dated technical, contact, and link information |
|
Publication Number: FHWA-HRT-17-036 Date: March 2018 |
Publication Number: FHWA-HRT-17-036 Date: March 2018 |
This appendix provides the 2007 grant recipients and how they addressed the individual steps of the Eco-Logical approach.
2007 Grant Recipient | Step 1: Collaboration |
Step 2: Eco Status |
Step 3: Develop REF |
Step 4: Assess REF |
Step 5: Prioritize |
Step 6: Crediting |
Step 7: Agreements |
Step 8: Implement |
Step 9: Update REF |
---|---|---|---|---|---|---|---|---|---|
CAPCOG(63) | Partnered with regional and local stakeholders. | Eco-Logical grant expanded on a previous Greenprint plan to include three more counties and integrated GIS and other data for these counties. | Integrated data into a GIS model/ REF. | Met with stakeholders to inform regional conservation priorities in REF. | Prioritized conservation opportunity areas in a region with a quickly growing population. | — | — | — | — |
H-GAC(65) | Partnered with stakeholders to map resources and also performed outreach to get more partners to use the mapping tool.(10) | Defined resources to be included in the mapping tool. | Created a GIS-based product to identify environmental resource priority areas. | Prioritized conservation needs based on resource type. | — | — | — | — | Updated the Eco-Logical tool. |
LOSRC(66) | Worked with various stakeholders to create resource maps and encouraged local government to use the maps. | Compiled various information to create maps and green infrastructure framework. | Developed resource assessments and a Regional Green Infrastructure map using State and local GIS data and national spatial data integration tools. | Used maps and tools to assess possible development patterns in LRTP and also as baseline data for GroWNC, an HUD Sustainable Communities Grant. | — | — | — | — | — |
MARC(67) | Worked with existing partners and formed new relationships with State and Federal agencies. | Identified strategies for integrating environmental data earlier into transportation planning processes. | Incorporated an action plan into LRTP and revised project selection criteria.(3) | — | — | — | — | — | — |
NCTCOG(70) | Worked with partners and improved relationship with resource agencies. | Used regional data to develop 10 base maps and 1 composite map of resource priorities by watershed.(12) | Utilized a watershed-scale approach to integrate regional conservation data and infrastructure planning into an REF dataset.(12) Developed 10 base maps and 1 composite map of resource priorities by watershed. | Worked with partner agencies to refine the priority weightings assigned to different criteria in the REF methodology. | — | — | — | — | Update the REF every 4–5 yr. |
TJPDC(74) | Coordinated 33 stake-holders in a facilitated engagement process to build consensus for the Free Bridge Area Congestion Relief Project.(97) | Finalized a Green Infrastructure Study that compiled existing natural resource data from 12 data layers.(71) | Created an REF for the six locality region. | Developed tools that use the REF to assess the impacts of transportation projects on natural resources. | — | — | — | — | — |
TCRPC(75) | Developed partnerships and collaborated with regional stakeholders. | Gathered environmental, transportation, and other data to create GIS maps. | Created GIS maps. | Considered various strategies in plan for improving environmental/ conservation outcomes and transportation planning. | Determined regional priorities and strategies for land use and infrastructure development. | — | — | — | — |
—No data were collected/steps were not completed.
—No data were collected/steps were not completed.
2007 Grant Recipient | Step 1: Collaboration |
Step 2: Eco Status |
Step 3: Develop REF |
Step 4: Assess REF |
Step 5: Prioritize |
Step 6: Crediting |
Step 7: Agreements |
Step 8: Implement |
Step 9: Update REF |
---|---|---|---|---|---|---|---|---|---|
Chicago Department of Transportation(80) | Partnered with local and regional entities on the creation of the guidelines.(79) | Integrated data and plans on sustainable streetscapes. | — | — | Prioritized sustainable streetscapes and used quantitative measures to justify the principles. | — | — | Created sustainable streets guidelines and a demonstration project.(79,78) | — |
Envision Utah(81) | Partnered with multiple stakeholders on visioning process for the Jordan River. | Created maps and identified priorities as part of creating the Jordan River Blue Print Plan.(81) | Combined map analyses to create regional vision for the Jordan River. | — | Identified priorities in plan and created a commission to oversee implementation. | — | — | Implemented projects with better understanding of impacts due to the Blue Print Plan. | — |
NHA(83) | Convened interagency workgroup as part of the project. | Defined resources to be included in the mapping tool. | Developed a GIS-based wildlife connectivity framework to evaluate the impact of transportation projects on wildlife species. | Used tools to look at impacts of transportation projects on wildlife species. | — | — | — | — | — |
NCDENR(86) | Worked with NCDOT and other stakeholders throughout grant process. | Provided data on upland and non-riparian wetland habitats that enhance the State Wildlife Action Plan.(84) Digitized cultural resource features to demonstrate their role in the State’s ecosystems. Integrated data into a comprehensive statewide conservation planning tool.(85) | Integrated data into a GIS-based CPT that is available to the public.(85) | Used the data created for the tool to help identify high-priority, unfragmented wildlife habitats based on occurrence data for indicator species and digital aerial photography. MPOs/regional planning organizations, NCDOT, and other agencies can use these data. | — | — | — | — | — |
OSU(58) | Worked with partners to consolidate disparate data; partnerships continued as OSU showed agencies how to use REF. | Compiled data from various places into an internal database to serve as the basis for maps and the REF. | Established an REF to identify conservation priority areas in Oregon and compile these data across the State.(58) | Identified priority conservation areas as part of the REF development; agencies use this information when evaluating impacts of transportation projects. | — | — | — | — | — |
TCSWCD(87) | Worked with various partners to develop an REF. | Collected natural resource and transportation data to populate an online mapping tool for the REF, which was created for use by NYSDOT.(87) | Created an REF for NYSDOT. | Worked with stakeholders to identify priority areas for keystone species and other key conservation areas. | Worked with Upper Susquehanna Coalition so that USC could administer the ILF program. | Assisted developing the ILF, Program which has helped implement the REF. | Improved working relationships with State agencies to make it possible to streamline funding mechanisms. | — | Update the REF every 4–5 yr. |
USEPA Region 6.(88) | Coordinated with six States that are included in REAP. | Gathered environmental data and characterized priority areas for conservation. | Developed a REAP that uses a GIS analysis to classify land on the basis of its ecological significance. | — | — | — | — | — | — |
—No data were collected/steps were not completed.
2013 SHRP2 Recipient | Step 1: Collaboration |
Step 2: Eco Status |
Step 3: Develop REF |
Step 4: Assess REF |
Step 5: Prioritize |
Step 6: Crediting |
Step 7: Agreements |
Step 8: Implement |
Step 9: Update REF |
---|---|---|---|---|---|---|---|---|---|
ARC(5) | Worked with internal and external partners to identify information priorities for developing the Proctor Creek REF. | Analyzed fiscal, economic, and environmental impacts of implementing REF for PCED. | Adapted regional REF for more detailed, local area for Proctor Creek. | Used REF data to create draft maps and decision criteria for inclusion in ARC’s future regional transportation plans. | — | — | — | — | — |
CA-MPO (part of TJDPC)(5) | Worked with stakeholder committee to identify and screen project alternatives for the Free Bridge Area Congestion Relief Project.(97) | Collected data for REF as part of TJDPC’s 2007 Eco-Logical grant project. | Created and updated REF for TJPDC’s 2007 grant project. | Piloted use of REF in evaluating proposed alternatives at the planning phase of project development for the Free Bridge Area Congestion Relief Project.(97) Incorporated REF into a weighted ranking system to evaluate impacts of seven proposed project alternatives. Each project alternative was assigned a score that quantified its environmental impact. | — | — | — | — | Developed REF under 2007 grant updated under 2013 IAP. |
NCTCOG(5) | Worked with 18 stakeholders to identify priority watershed and potential mitigation areas. | Updated REF with current information to ensure it reflects regional conservation priorities. | Developed with previous 2007 grant. | Applied the REF to a pilot corridor, the Loop 9 Southeast Corridor, to determine the feasibility of using the REF for corridor-level conservation and mitigation. | — | — | — | — | Gathered information on priority areas to update REF. |
PPACOG(5) | Worked with stakeholder group and committee to identify conservation and mitigation targets. | Gathered data on transportation projects and potential impacts on conservation and mitigation areas. | Developed a spatial database with a list of mitigation targets and associated acreage.(99) | Developed a Conservation Value Summary and related conservation ranking for proposed transportation projects.(99) | — | — | — | — | Updated existing REF to reflect new data developed since SHRP2 C18 project ended.(100) |
—No data were collected/steps were not completed.
—No data were collected/steps were not completed.
—No data were collected/steps were not completed.
—No data were collected/steps were not completed.