This dataset contains mitigation bank and in-lieu fee program sites in Florida from the US Army Corps of Engineers Regulatory In-lieu Fee and Bank Information Tracking System (RIBITS). A mitigation bank is a site where resources (e.g., wetlands, streams, riparian areas) are restored, established, enhanced, and/or preserved for the purpose of providing compensatory mitigation for impacts authorized by Department of the Army permits. The U.S. Army Corps of Engineers regulates resources like wetlands and streams under Section 404 of the Clean Water Act and in some cases Section 10 of the Rivers and Harbors Act. The measure of aquatic functions is based on the resources restored, established, enhanced, or preserved. An in-lieu fee program involves the restoration, establishment, enhancement, and/or preservation through funds paid to a governmental or non-profit natural resources management program sponsor to satisfy compensatory mitigation requirements under Department of the Army permits. Funds are often received by the in-lieu fee program sponsor prior to undertaking compensatory mitigation projects. In lieu fee programs can involve multiple mitigation project sites.
RIBITS (Regulatory In lieu fee and Bank Information Tracking System) was developed by the U.S. Army Corps of Engineers with support from the Environmental Protection Agency, the U.S. Fish and Wildlife Service, the Federal Highway Administration, and NOAA Fisheries to provide better information on mitigation and conservation banking and in-lieu fee programs across the country. RIBITS allows users to access information on the types and numbers of mitigation and conservation bank and in-lieu fee program sites, associated documents, mitigation credit availability, service areas, as well information on national and local policies and procedures that affect mitigation and conservation bank and in-lieu fee program development and operation.
A mitigation bank is an aquatic resource area that has been restored, created, enhanced, or (in exceptional circumstances) preserved, which is then set aside to compensate for future impacts to aquatic resources for development activities. A mitigation bank may be created when a government agency, a corporation, or a nonprofit organization undertakes such activities under a formal agreement with a regulatory agency. The value of a bank is determined by quantifying the functions or area restored or created in terms of "credits." Benefits of Mitigation Banking: * Banking can provide more cost-effective mitigation and reduce uncertainty and delays for qualified projects, especially when the project is associated with a comprehensive planning effort. * Successful mitigation can be ensured since the aquatic resource can be functional in advance of project impacts. * Banking eliminates the temporal losses of aquatic resource functions that typically occur when mitigation is initiated during or after the development impacts occur * Consolidation of numerous small, isolated or fragmented mitigation projects into a single large parcel may have greater ecological benefit. * A mitigation bank can bring scientific and planning expertise and financial resources together, thereby increasing the likelihood of success in a way not practical for individual mitigation efforts.
publication date
None.
441 G Street NW
U.S. Army Corps of Engineers
GeoPlan relied on the integrity of the attribute information within the original data.
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
GeoPlan Center Process Steps: Mitigation bank and ILF site data was downloaded from RIBITS on 11/8/2019. Download Instructions: 1. https://ribits.usace.army.mil/ 2. MENU > Banks & ILF Sites 3. Actions > Select Columns: Add all columns to "Display in Report" window 4. Actions > Filter: State Abbrev List contains 'FL' 5. Actions > Download: As CSV 6. After making the selections above, download Footprint KML file from the Google Map window. Downloaded Files: - banks_and_ilf_sites.csv (168 records) - RIBITS_BANKS_ILF_KML_footprint.kmz (156 records) Latitude/longitude data from "banks_and_ilf_sites.csv" was mapped and exported as a shapefile and "RIBITS_BANKS_ILF_KML_footprint.kmz" was converted from a kmz file to a shapefile. Both datasets were mapped in the GCS_WGS_84 (EPSG: 4326) projection and then reprojected to FGDL Albers NAD83 HARN (EPSG: 3087). Next, "banks_and_ilf_sites" was joined to "RIBITS_BANKS_ILF_KML_footprint" via the BANK_ID field. The resulting table join was exported to shapefile. Twelve sites had no footprint (polygon) spatial data, and thus were not included in the final dataset: * HATCHINEHA RANCH CONSERVATION BANK PHASE 2 (BANK ID 3526) * HATCHINEHA RANCH MB (BANK ID 1040) * HEATHER ISLAND MB (BANK ID 290) * ILF KEYS ENVIRONMENTAL RESTORATION FUND (BANK ID 2120) * ILF-KRF-BAHIA HONDA PROJECT A (BANK ID 3573) * ILF-KRF-CRANE POINT HAMMOCK (BANK ID 3385) * MARION MB (BANK ID 4438) * NATURAL RESOURCE MB (BANK ID 3272) * OSPREY UNIT MB (BANK ID 3061) * PEPPER RANCH PRESERVE CONSERVATION BANK (BANK ID 5375) * RG RESERVE MB (BANK ID 277) * TWIN OAKS MB (BANK ID 3553) Field lengths of existing fields were shortened and fields were upcased. The following fields were added to the table: - URL field populated based on the following field calculation: "https://ribits.usace.army.mil/ribits_apex/f?p=107:10:12127777969408::NO::P10_BANK_ID:" & [BANK_ID] & ":" - DESCRIPT field populated based on NAME. - FGDLAQDATE field populated based on the date the dataset was downloaded from the source. Finally, the file was renamed ribits_2019.shp.
Dataset copied.
Internal feature number.
ESRI
Feature geometry.
ESRI
[Name] Not defined by source.
USACE
[Bank Name] Not defined by source.
USACE
[Bank ID] Not defined by source.
USACE
URL web address providing general information about the site.
GeoPlan
[Status] Not defined by source.
USACE
[Year Established] Not defined by source.
USACE
[Bank Type] Not defined by source.
USACE
[Credit Type] Not defined by source.
USACE
[Total Acres] Not defined by source.
USACE
[X] Not defined by source.
USACE
[Y] Not defined by source.
USACE
[Has Footprint] Not defined by source.
USACE
[District List] Not defined by source.
USACE
[NOAA Fisheries Region List] Not defined by source.
USACE
[Field Office] Not defined by source.
USACE
[County List] Not defined by source.
USACE
[Is USACE] Not defined by source.
USACE
[Is FWS] Not defined by source.
USACE
[Is NMFS] Not defined by source.
USACE
[Is Conservation] Not defined by source.
USACE
[Is DOT] Not defined by source.
USACE
[Is ILF] Not defined by source.
USACE
[Is 404] Not defined by source.
USACE
[Is NRDA] Not defined by source.
USACE
GeoPlan added field based on NAME.
GeoPlan
GeoPlan added field based on date downloaded from source.
GeoPlan
Unique ID added by GeoPlan
GeoPlan
Area in meters
GeoPlan
Perimeter 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
441 G Street NW