Waste Cleanup Responsible Party Sites - Open

Florida Department of Environmental Protection, Division of Waste Management, Waste Cleanup Program 20100224 Waste Cleanup Responsible Party Sites - Open - October 2020 vector digital data Tallahassee, FL Florida Department of Environmental Protection State of Florida http://geodata.dep.state.fl.us/ This data set reflects OPEN Waste Cleanup (Responsible Party) sites. Cleanup of the site as tracked by the District Waste Cleanup Section remains to be done, a cleanup phase is progressing, or the site is subject to a monitoring plan. This set does not include sites awaiting action as a result of a case referral, e.g., to EPA or State Cleanup/Superfund. Sites that have completed remediation and are awaiting a copy of a county clerk "filed" stamp for recording of any institutional controls are still considered OPEN. Sites where EPA has assumed the role of lead agency but the site is not on the National Priorities List are still overseen by the district are included in the list of OPEN sites. To compile programmatic information associated with waste cleanup sites at all stages of cleanup until final site rehabilitation completion is approved or until referred to and accepted by other program areas such as the EPA, State Cleanup/Superfund, petroleum, or drycleaning solvent cleanup programs. This layer is intended to supersede previous layers associated with COMET and CAP/RAP for viewing waste cleanup (CU) sites. The waste cleanup (WCU) program was established to implement risk-based corrective action (RBCA) provisions of Section 376.30701(2), F.S. for sites where contaminants have been released or discharged into the environment and legal responsibility for site rehabilitation exists pursuant to other provisions of chapter 376 or 403 of the Florida Statutes. WCU site rehabilitation may be conducted voluntarily or pursuant to the department's enforcement authority and generally follow the provisions of 62-780 F.A.C. Contaminated Site Cleanup Criteria, as promulgated on December 27, 2007; or under enforcement orders with comparable requirements. District office staff oversee WCU site remediation conducted by responsible parties. 20100224 20201001 publication date Complete As needed -87.406970 -79.886577 30.978332 24.520743 ISO 19115 Topic Category COMET waste contaminated site cleanup CAP/RAP contaminant of concern environment 62-780 Responsible Party environmental monitoring and modeling risk-based corrective action Global RCBA waste cleanup None Florida None Because a variety of sources and methods were used to derive information for this data, the quality of the linework may vary accordingly. This data is intended to be used for general locational representation and should not be considered appropriate for legal and/or cadastral purposes. Florida Department of Environmental Protection, Division of Waste Management, Waste Cleanup Program Chris Williams GIS & ICR Coordinator mailing and physical

2600 Blair Stone Rd

Tallahassee FL 32399-2400 US (850) 245-8758 Christopher.A.Williams@dep.state.fl.us Email is preferred. Please include your name, organization, question or description of data requested, date data is needed, and brief description of how the data will be used. FDEP District Office Waste Cleanup Staff, COMET Data System Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595 FDEP Waste Cleanup Program: https://floridadep.gov/waste 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 0 onLine Spatial and Attribute Information This GIS layer was based on query used to create the GIS view for COMET and modified it to filter just for OPEN WCU sites. Also includes some other relevant fields that staff and management use to routinely view and filter data. Query language follows: /* Name: WCU_COMET_GEOMETRY_VW.SQL Version: 1 Function: Creates the GEOM.WCU_COMET_GEOMETRY_VW Oracle Spatial view. Dependencies: DIFF.T_LOCATION_COMET@FDEP COMET.SITES@ORAPROD COMET.ACTIVITIES@ORAPROD COMET.PROJECTS@ORAPROD COMET. PROJECT_SITES@ORAPROD GEOM account on ORAPROD Oracle SQL*Plus Oracle Spatial Existing FDEP Albers custom projection in MDSYS.CS_SRS Programmer: Eric W Brockwell DEP/BIS/GIS (GEOM.COMET_GEOMETRY_VW) Proposed new view by Lissie Bartlett DWM/BWC/PTSS adaped from GEOM.COMET_GEOMETRY_VW and Donna Gorton's sql statement for COMET.ACTIVITY_SITE_REPORTS_VW to show open, inactive, and closed WCU "responsible party" sites. Date: 09/28/05 (GEOM.COMET_GEOMETRY_VW) Revision History: 09/28/05 - Original coding. ewb (GEOM.COMET_GEOMETRY_VW) 2/24/10 - proposed modification E. Bartlett (lb) (GEOM.WCU_COMET_GEOMETRY_VW) 03/29/10 - Changed objectid to be rownum instead of site_id. April Williford 10/28/10 - Changed datum to dcd_datum_id coming from comet.sites and added data elements. E. Bartlett (lb) 11/8/10 - Added required and recommended data elements for consistency with FDEP GIS Location Data Standard STD-09061811.1.0. E. Bartlett (lb) 11/10/10 - Updated field list and alias names, cleaned up comments E. Bartlett (lb) */ -- Create a view with geometry column for COMET setting invalid coords to 0,0 create or replace force view wcu_comet_geometry_vw as -- lb: renamed query and added fields to the select statement, changed table references to be more descriptive select proj.oc2_office_id district, sit.site_id, proj.name project_name, proj.project_id project_id, proj.sc3_status_id status, proj.user_id project_mgr, act.ogc_number, act.date_initiated ISDR_date, act.completion_notes contaminants, act.pats_number offsiteCOC, act.condition_number priority_score, --*** Show for OPEN sites only *** sit.address_1 address, sit.city, sit.zip5, sit.zip4, sit.cc_county_id county_id, sit.dcd_datum_id datum_id, sit.cmcd_method_id method_id, sit.feature, --project mgr notes on feature mapped in coordinates sit.ooic_object_of_interest_id object_of_interest, sit.ppc_point_proximity_id proximity_to_object, sit.lat_dd, sit.lat_mm, sit.lat_ss, sit.long_dd, sit.long_mm, sit.long_ss, -- *** Additional fields proposed by E Bartlett to match FDEP GIS Location Data Standard STD-09061811.1.0 sit.gis_albx, sit.gis_alby, sit.collect_username, sit.collect_affiliation, sit.collect_prac_program_area_id collect_program_id, sit.determination_date collect_date, sit.map_source, sit.map_source_scale, sit.interpolation_scale, sit.cac1_coordinate_accuracy_id coordinate_accuracy_id, sit.verify_cmcd_method_id verify_method_id, sit.verifier_username, sit.verifier_affiliation, sit.verifying_prac_program_area_id verifying_program_id, sit.verification_date, rownum as objectid, -- the following code was from original query - changed table references from b. to sit. CASE when sit.long_dd < 78 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.long_dd > 88 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.long_dd is NULL THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.long_mm < 0 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.long_mm >= 60 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.long_mm is NULL THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.long_ss < 0 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.long_ss >= 60 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.long_ss is NULL THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.lat_dd < 23 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.lat_dd > 32 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.lat_dd is NULL THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.lat_mm < 0 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.lat_mm >= 60 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.lat_mm is NULL THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.lat_ss < 0 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.lat_ss >= 60 THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) when sit.lat_ss is NULL THEN MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL) ELSE mdsys.sdo_cs.transform( -- transform from lat/long to albers mdsys.sdo_geometry ( -- create the lat/long geometry 2001, -- 2D point feature decode(SIT.DCD_DATUM_ID, 'NAD27',8260, 'CAC',8213, 'NAD83',8265, 'HARN',8265, 'HGPN',8265, -- unfortunately some schemas have -- this invalid code! 'HPGN',8265, 'WGS84',8307, NULL, 8265, 8265), -- cover the datums we are likely to find -- assume HPGN as NAD83 until Oracle Spatial handles HPGN -- at 9i Oracle Spatial treats NAD83 and WGS84 the same mdsys.sdo_point_type -- make a point from the lat/long ( -(abs(NVL(sit.long_dd,0)) + (NVL(sit.long_mm,0)/60) + (NVL(sit.long_ss,0)/3600)), (abs(NVL(sit.lat_dd,0)) + (NVL(sit.lat_mm,0)/60) + (NVL(sit.lat_ss,0)/3600)), null), null, -- no element info array null ), -- no ordinate array 1000001 ) END geometry -- transform to the fdep albers srid --lb: continue revised sql statement for waste cleanup relationships from comet.activities act, comet.projects proj, comet.project_sites ps2, comet.sites sit where proj.project_id = act.proj_project_id AND ps2.proj_project_id = proj.project_id AND ps2.sit_site_id = sit.site_id AND act.cpac_program_area_id='CU' AND act.ac5_activity_code_id='ISDR' order by district, project_name; FDEP not complete Florida Department of Environmental Protection, Division of Waste Management, Bureau of Waste Cleanup Elizabeth Bartlett Engineer IV mailing and physical

2600 Blair Stone Rd MS4535

Tallahassee FL 32399-2400 US 850-245-7501 elizabeth.bartlett@dep.state.fl.us Email is preferred. Please include your name, organization, question or description of data requested, date data is needed, and brief description of how the data will be used. Layer based on the updated query provided by Lissie Bartlett (DWM) was inserted in ArcSDE, and published in DataCatalog, DataMiner and MapDirect. FDEP 20101208 Updated layer with new field DOCUMENTS containing to documents stored in the agency's document management system. Florida Department of Environmental Protection (FDEP) OTIS/GIS Section 20170308 This dataset was downloaded by the GeoPlan Center on 10/1/2020 from the FDEP website (http://geodata.dep.state.fl.us/). The data was received as a geodatabase and was in the following projection: NAD_1983_2011_Florida_GDL_Albers. The dataset was projected to NAD_1983_HARN_Florida_GDL_Albers using the NAD_1983_HARN_To_NAD_1983_2011 transformation. This dataset is updated daily. Contact the FDEP for the most recent data. - Added the field DESCRIPT based on PROJECT_NA. - Added fields LAT_DD_1, LONG_DD_1, MGRS, and GOOGLEMAP. LAT_DD_1 and LONG_DD_1 were calculated using the calculate geometry command and selecting decimal degrees as the units. MGRS was calculated using the Convert Coordinate Notation tool and selecting Output coordinate Format as MGRS. The GOOGLEMAP field was calculated by concatenating: "https://www.google.com/maps/place/" & [MGRS]. - Added the field FGDLAQDATE based on date downloaded from source. - Upcased all text in the attribute table except for DOCUMENTS field. - Data set was renamed wcu_open_oct20 from WCU_RP_OPEN_SITES_SP Notes: Changes as of April 2017 New fields: DOCUMENTS GeoPlan 20201001 Vector Entity point 930 NAD 1983 HARN Florida GDL Albers 24.0 31.5 -84.0 24.0 400000.0 0.0 coordinate pair 0.0001 0.0001 meter D North American 1983 HARN GRS 1980 6378137.0 298.257222101 WCU_OPEN_OCT20 WCU_OPEN_OCT20.DBF FDEP OBJECTID Internal feature number. Esri Sequential unique whole numbers that are automatically generated. Shape Feature geometry. ESRI Coordinates defining the features. DISTRICT FDEP District COMET.PROJECTS.OC2_OFFICE_ID SD South District SED Southeast District SWD Southwest District CD Central District NED Northeast District NWD Northwest District SITE_ID COMET Site ID (OCULUS ID uses "COM_" prefix) COMET.SITES.SITE_ID PROJECT_NA Name of project FDEP PROJECT_ID Project ID - ID number assigned by COMET to track multiple projects under a single COMET Site ID COMET.PROJECTS.PROJECT_ID STATUS Site Status - OPEN, CLOSED, or INACTIVE COMET.PROJECTS.SC3_STATUS_ID PROJECT_MG Project manager FDEP OGC_NUMBER OGC Case Number if a Consent Order has been executed for the contaminated site. For projects wtih multiple OGC #s, will list only most recent OGC # COMET.ACTIVITIES.OGC_NUMBER ISDR_DATE Date for "Initial Data Received on New Potential Contamination Site" All COMET projects with known contamination should have an ISDR activity code where contamination is confirmed through use of a field screening instrument or lab analytical determination. COMET.ACTIVITIES.DATE_INITIATED where AC5_ACTIVITY_CODE_ID="ISDR" CONTAMINAN Contaminant FDEP OFFSITECOC Designation of "Offsite" contamination impacts to soil, sediment, ground or surface water that is documented off the source property. COMET.ACTIVITIES.PATS_NUMBER where AC5_ACTIVITY_CODE_ID="ISDR" Y Yes, there is documentation that contamination above applicable standards or criteria exists 'offsite'. U Unknown, documentation does not exist, or exists but is inconclusive, as to whether contamination above applicable standards or criteria extends offsite N No, the best available evidence (such as completed SAR) demonstrates that contamination above applicable standards or criteria DOES NOT extend offsite. PRIORITY_S Priority score FDEP ADDRESS Site Street Address COMET.SITES.ADDRESS_1 CITY City where site is located COMET.SITES.CITY ZIP5 5-digit Zip Code COMET.SITES.ZIP5 ZIP4 4-digit Zip Code suffix COMET.SITES.ZIP4 COUNTY_ID 2-digit ID for county where site is located COMET.SITES.CC_COUNTY_ID DATUM_ID Datum - the horizontal reference for measuring locations on the Earth's surface. COMET.SITES.DCD_DATUM_ID NAD83 North American Datum of 1983 FDEP GIS Location Data Standard STD-09061811.1.0 NAD27 North American Datum of 1927 FDEP GIS Location Data Standard STD-09061811.1.0 HARN High Accuracy Reference Network FDEP GIS Location Data Standard STD-09061811.1.0 HPGN High Precision GIS Network / High Precision Geodetic Reference FDEP GIS Location Data Standard STD-09061811.1.0 CAC Cape Canaveral FDEP GIS Location Data Standard STD-09061811.1.0 WGS84 Geodetic Survey of 1984 FDEP GIS Location Data Standard STD-09061811.1.0 METHOD_ID Method - The method or mechanism used to derive the measurements. COMET.SITES.CMCD_METHOD_ID WGPS GPS with Wide-Area Augmentation Service Correction FDEP GIS Location Data Standard STD-09061811.1.0 CALC Calculated by GIS Software FDEP GIS Location Data Standard STD-09061811.1.0 ADDM Address Matching FDEP GIS Location Data Standard STD-09061811.1.0 AGPS Autonomous GPS FDEP GIS Location Data Standard STD-09061811.1.0 DPHO Digital Aerial Photography With Ground Control FDEP GIS Location Data Standard STD-09061811.1.0 GGPS Geodetic Quality GPS FDEP GIS Location Data Standard STD-09061811.1.0 DGPS Differentially Corrected GPS FDEP GIS Location Data Standard STD-09061811.1.0 CSUR Cadastral Survey FDEP GIS Location Data Standard STD-09061811.1.0 LORN LORAN-C Navigational Device FDEP GIS Location Data Standard STD-09061811.1.0 MMAP Manual Map Interpolation FDEP GIS Location Data Standard STD-09061811.1.0 ZIP2 ZIP Code + 2 Segment Centroid FDEP GIS Location Data Standard STD-09061811.1.0 ZIP4 ZIP Code + 4 Segment Centroid FDEP GIS Location Data Standard STD-09061811.1.0 DMAP Digital Map Interpolation FDEP GIS Location Data Standard STD-09061811.1.0 UNKN Unknown Method FDEP GIS Location Data Standard STD-09061811.1.0 OTHR A Method Not Listed FDEP GIS Location Data Standard STD-09061811.1.0 SATI Satellite Imagery With Ground Control FDEP GIS Location Data Standard STD-09061811.1.0 ZIPC Zip Code Centroid FDEP GIS Location Data Standard STD-09061811.1.0 MPHO Manual Aerial Photography With Ground Control FDEP GIS Location Data Standard STD-09061811.1.0 FEATURE Feature - project manager notes on selected feature to be mapped COMET.SITES.FEATURE OBJECT_OF_ Object of interest FDEP PROXIMITY_ Proximity to object FDEP LAT_DD Latitude - Degree COMET.SITES.LAT_DD LAT_MM Latitude - minutes COMET.SITES.LAT_MM LAT_SS Latitude - seconds COMET.SITES.LAT_SS LONG_DD Longitude - degrees COMET.SITES.LONG_DD LONG_MM Longitude - minutes COMET.SITES.LONG_MM LONG_SS Longitude - seconds COMET.SITES.LONG_SS GIS_ALBX The X-coordinate is the decimal degree Longitude based on FDEP Albers projection COMET.SITES.GIS_ALBX GIS_ALBY The Y-coordinate is the decimal degree Latitude based on FDEP Albers projection COMET.SITES.GIS_ALBY COLLECT_US Collect username FDEP COLLECT_AF Collect affiliation FDEP COLLECT_PR Collect program ID FDEP COLLECT_DA Collect date FDEP MAP_SOURCE If the measurement was derived from a map, the name of the map series that was used. MAP_SOUR_1 The scale of the source map INTERPOLAT Interpolation scale FDEP COORDINATE Coordinate accuracy ID FDEP VERIFY_MET Verify method ID FDEP VERIFIER_U Verifier username FDEP VERIFIER_A Verifier affiliation FDEP VERIFYING_ Verifying program ID FDEP VERIFICATI Verification date FDEP DOCUMENTS FDEP Document link to DEP nexus LAT_DD_1 Latitude in decimal degrees. Esri LONG_DD_1 Longitude in decimal degrees. Esri MGRS Military Grid Reference System (MGRS) Coordinate of the Facility. The MGRS is the geocoordinate standard used by NATO militaries for locating points on the earth. The MGRS provides a means to represent any location on the surface of the Earth using an alphanumeric string. Hierarchical references are based on the Universal Transverse Mercator (UTM) coordinate system. The MGRS is used for the entire earth. http://mgrs-data.org/ GeoPlan GOOGLEMAP Webpage hyperlink to location in Google Maps. GeoPlan DESCRIPT FGDL added field based on PROJECT_NA GeoPlan FGDLAQDATE FGDL field added based on date downloaded from source GeoPlan AUTOID Sites and Projects SITE = For the purposes of tracking in COMET, a contaminated "site" is generally the contiguous lands (property) associated with known contamination area(s). However, if a "site" is a very large parcel that contains multiple contamination locations each of which is being independently assessed and remediated, these individual contamination "sites" may have unique individual Site and Project records if that is needed to facilitate the management of the cleanup efforts. This definition of site should not be confused with the formal Chapter 62-780 definition of site (which tracks the statutory definition). Chapter 62-780 defines "site" as follows: 62-780.200 (42): "Site" refers to the definition for "contaminated site". 62-780.200 (13): "Contaminated site" means any contiguous land, sediment, surface water, or groundwater area that contains contaminants that may be harmful to human health or the environment. 62-780.200 (11): "Contaminated" or "contamination" means the presence of free product or any contaminant in surface water, groundwater, soil, sediment, or upon the land, in concentrations that exceed the applicable CTLs specified in Chapter 62-777, F.A.C., or water quality standards in Chapters 62-302, 62-520, or 62-550, F.A.C., or in concentrations that may result in contaminated sediment. Each cleanup area (COMET Site) as defined above should have a separate project in Comet. Comet requires that each new Project have a Site record attached to it upon creation. Unless there is an over whelming reason to use an existing Comet "Site" record which is shared by other program areas, WCU staff should normally create a new Site record in Comet for each WCU project created. This new Site record should have appropriate Lat/Long data entered and any DC alternate ID;'s added, if needed. This "one-to-one" linkage between WCU's Project and Site record is needed to allow the lat/long coordinates entered into the site record for each WCU project as well as it's DC status to be used to produce both the Statewide and District reports. Project Status Codes These codes are used to provide a quick reference as to whether the project is currently being managed by the district (OPEN), is temporarily managed by some other entity (INACTIVE) or has been cleaned up or permanently transferred to another entity (CLOSED) Note: All activity codes and data entry identified below must be entered as "CU" program code activities in the Comet system to be included in the WCU program database reports and program evaluations. OPEN = District staff has been assigned to manage and track the progress of a potentially contaminated site. Cleanup of the site as tracked by the District Waste Cleanup Section remains to be done, a cleanup phase is progressing or the site is subject to a monitoring plan. It does not include sites awaiting action as a result of a case referral, e.g., to EPA ("CRE") or State Cleanup/Superfund ("CRSC"). Sites that have completed the remediation and are awaiting a copy of a county clerk "filed" stamp for recording of institutional controls are still considered "OPEN". Sites where EPA has assumed the role of lead agency but the site is not on the National Priorities List are still overseen by the district and should be kept OPEN in COMET. CLOSED = Case file has been closed by the District Waste Cleanup Section. All cleanup phases, including long term monitoring have been accomplished or are no longer the responsibility of the District. Cases referred to, and accepted by, other program areas, e.g., the EPA, State Cleanup/Superfund programs, petroleum programs, drycleaning solvent cleanup program should be CLOSED. A case file may or may not be "deactivated" on the OGC database. There may be long-term deed restrictions or engineering controls placed on a site that has been "CLOSED" in Comet. Any such controls are tracked in the Institutional Control Registry. INACTIVE = Case should be placed in this status while awaiting action as a result of determining eligibility for program cleanup in either Dry Cleaning or Petroleum or CERCLA screening. Sites placed in this status may return to Waste Cleanup after the program cleanup or evaluation is completed to resolved any outstanding issues, When a case is returned to the District Waste Cleanup Section from one of the reviewing program noted above, the status should be changed to "OPEN". Priority Score The field labeled "COND #" on the ISDR activity code detail screen will be used to contain the informal and non binding "score" or risk evaluation number resulting from the use of the document inserted below. The score should normally be a number between 1 and 35. The score sheet is attached to this document as Appendix A. "Offsite" Contamination The field labeled "PERMIT #" on the ISDR activity code detail screen will be used to document whether any contamination from the source property has been documented on any other property (ies). These "offsite" impacts may be soil, sediment, ground or surface water contamination that is present of the property owned or under the control of the RP responsible for the contamination being addressed. The term "offsite" is a bit of a misnomer given the 62-780 definition of site and is used here to indicate contamination that is documented off the source property. The determination of whether or not contamination is "offsite" is based upon the current property configuration. Therefore if a large parcel is subsequently subdivided such that the contamination is now present on more than one of the new, smaller parcels, then that contamination is now "offsite". Conversely, if contamination is spread over more than one parcel and these individual parcels are consolidated into a single, larger parcel that completely encompasses the extent of contamination, then that contamination is no longer "offsite". In some special cases there may not be an archetypal "source property" due to a release from a third party. Perhaps the most common example of this would be a vehicular accident in which contaminants are discharged in the right of way. For the purposes of the notice requirements in Chapter 62-780 and tracking in COMET, such incidents should only be considered as "offsite" if the contamination spreads to any surrounding property. Presumably the owner of the property upon which the discharge occurred is notified that their property is now contaminated and can pursue the appropriate legal remedies. Database Values for the PERMIT # Field Y - Yes, there is documentation that contamination above applicable standards or criteria exists "offsite". N - No, the best available evidence (such as a completed SAR) demonstrates that contamination above applicable standards or criteria DOES NOT extend offsite. U - Unknown, documentation does not exist, or exists but is inconclusive, as to whether contamination above applicable standards or criteria extends offsite. Contaminant Identification The category of contaminants under assessment or remediation at each site should be identified in the field labeled "Completion Comments" on the ISDR activity code detail screen in Comet. Contaminant Categories could include: Metals, VOCs, PAHs, SVOCs, Inorganics, BTEX, Methane, [or any others the group wants to identify - suggest we keep the list short, and consistent, since we are going to be doing text parsing to make anything in the field usable in a report.] Waste Cleanup COMET Guidance, updated 6/28/2008 Florida Geographic Data Library (FGDL) mailing

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 US Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html Technical Support: http://www.fgdl.org/fgdlfeed.html Web site: http://www.fgdl.org FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html DOWNLOADABLE DATA 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 20201120 Florida Department of Environmental Protection (FDEP) OTIS/GIS Section Chris Williams GIS & ICR Coordinator mailing and physical

2600 Blair Stone Rd

Tallahassee FL 32399-2400 US (850) 245-8758 GIS.Librarian@dep.state.fl.us FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 local time