Statewide coverage of Water Assurance Compliance System (WACS) Solid Waste Facilities
To compile facility specific information on Solid Waste Management facilities statewide and monitor their potential to impact ground water.
The Solid Waste Program regulates (permitting, compliance, enforcement) the design, construction, operation and maintenance of Solid Waste Facilities. It ensures the proper closure and long-term monitoring and maintenance of those facilities which have concluded useful production, or which are otherwise required by rule to be closed. The program also administers financial responsibility requirements designed to guarantee that owners/operators have the financial ability to properly close and manage the Solid Waste Facilities
publication date
The locational data point of each is provided by the responsible party and reviewed by the Florida Department of Environmental Protection (FDEP) agency staff. FDEP makes no representations of any kind, including, but not limited to, the warranties of merchantability or fitness for a particular use, nor are any such warranties to be implied with respect to the digital data layers furnished hereunder. FDEP assumes no responsibility to maintain them in any manner or form. By using data provided herein, the user acknowledges that terms and conditions have been read and that the user is bound by these criteria.
2600 Blairstone Road
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.
Data was compiled by the Districts and Tallahassee Solid Waste GIS Coordinator
GeoPlan relied on the integrity of the attribute information within the original data.
Layer was created in ArcGIS 9.2.
Layer has not been completed
Accuracy of this layer is intend for displaying the general location of these facilities. Layer need revision since the Object of Interest Code was added
Vertical measurements not included in data set yet.
Spatial and Attribute Information
Features were digitized by looking the 1994, 1999 2004 Digital Ortho Quads on the screen. The department used flat maps, micro fish, and the application to find GIS locations.
2600 Blairstone Road
Please, email it is preferred. Include your name, organization, date data is needed, and brief description of what the data will be used for
Layer updated with the revised script as requested by Lee Martin and Casey Taylor:
CREATE OR REPLACE VIEW waste_facs_pt_geometry_vw (
facility_id,
facility_name,
facility_type,
facility_status,
status_date,
object_of_interest,
class,
class_status,
ownership,
address,
city,
zip5,
zip4,
district,
office,
county_id,
county,
proximity_id,
lat_dd,
lat_mm,
lat_ss,
long_dd,
long_mm,
long_ss,
datum_id,
coordinate_method_id,
accuracy_level,
accuracy,
qa_status,
collector_user_name,
collect_date,
verifier_user_name,
verification_date,
verify_method_id,
geometry,
objectid )
AS
SELECT
wf.wacs_facility_id facility_id,
wf.name facility_name,
(select Initcap(description) from wacs.wacs_facility_type_codes
where wacs_facility_type_id = wf.wftc_wacs_facility_type_id) facility_type,
(select Initcap(description) from wacs.facility_status_codes
where facility_STATUS_ID = wf.fsc3_facility_status_id) facility_status,
wf.facility_status_date,
(Select Initcap(Name) from FDM.object_of_interest_codes
where object_of_interest_id = gl.oic_object_of_interest_id) object_of_interest,
decode(gl.oic_object_of_interest_id,
'DISPS',(select description
from wacs.facility_class_type_codes, wacs.solid_waste_landfills sl
where sl.solid_waste_landfill_id = gl.swl_solid_waste_landfill_id
and facility_class_type_id = sl.fctc_facility_class_type_id) ,
'PROCE',(select description
from wacs.facility_class_type_codes, wacs.solid_waste_processings sp
where sp.solid_waste_processing_id = gl.swp_solid_waste_processing_id
and facility_class_type_id = sp.fctc_facility_class_type_id),null) class_type,
decode(gl.oic_object_of_interest_id,
'DISPS',(select Initcap(description)
from wacs.facility_status_codes, wacs.solid_waste_landfills sl
where sl.solid_waste_landfill_id = gl.swl_solid_waste_landfill_id
and facility_status_id = sl.fsc3_facility_status_id),
'PROCE',(select Initcap(description)
from wacs.facility_status_codes, wacs.solid_waste_processings sp
where sp.solid_waste_processing_id = gl.swp_solid_waste_processing_id
and facility_status_id = sp.fsc3_facility_status_id),null) class_status,
(select Initcap(description) from wacs.wacs_ownership_type_codes
where WACS_ownership_type_ID = wf.wotc_wacs_ownership_type_id ) owner_type,
wf.address,
Initcap(wf.city),
wf.zip5,
wf.zip4,
wf.dis_district_abbreviation district,
(select Initcap(Name) from fdm.office_codes oc
where oc.office_id = wf.oc2_office_id
and oc.ddc_dep_district_id = wf.dis_district_abbreviation),
wf.cc_county_id county_id,
(select Initcap(Name) from BIS_LIB.county_codes
where county_id = wf.cc_county_id),
(select description from fdm.proximity_codes
where gl.PC2_proximity_id = proximity_id),
gl.lat_dd_nbr,gl.lat_mm_nbr,gl.lat_ss_nbr,gl.long_dd_nbr,gl.long_mm_nbr,gl.long_ss_nbr,
gl.DC4_DATUM_ID,
(select description from fdm.coordinate_method_codes
where CMC2_COORDINATE_METHOD_ID = COORDINATE_METHOD_ID),
gl.CALC_COORD_ACCURACY_LEVEL_ID,
(select Range_begin||' - '||Range_end||' meters' from BIS_LIB.coordinate_accuracy_codes
where coordinate_accuracy_id = gl.CALC_COORD_ACCURACY_LEVEL_ID),
Initcap(gl.VSC1_VERIFICATION_STATUS_ID),
/* Fields following this comment will be needed by DQD. */
gl.COLLECTOR_USER_NAME,
gl.COLLECT_DATE,
gl.VERIFIER_USER_NAME,
gl.VERIFICATION_DATE,
gl.CMC2_VERIFIED_COORD_METHOD_ID,
CASE when long_dd_nbr < 78 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when long_dd_nbr > 88 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when long_dd_nbr is NULL THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when long_mm_nbr < 0 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when long_mm_nbr >= 60 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when long_mm_nbr is NULL THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when long_ss_nbr < 0 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when long_ss_nbr >= 60 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when long_ss_nbr is NULL THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when lat_dd_nbr < 23 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when lat_dd_nbr > 32 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when lat_dd_nbr is NULL THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when lat_mm_nbr < 0 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when lat_mm_nbr >= 60 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when lat_mm_nbr is NULL THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when lat_ss_nbr < 0 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when lat_ss_nbr >= 60 THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
when lat_ss_nbr is NULL THEN
MDSYS.SDO_GEOMETRY(2001, 1000001, MDSYS.SDO_POINT_TYPE(0, 0, NULL), NULL, NULL)
ELSE
mdsys.sdo_cs.transform( -- trasnform from lat/long to albers
mdsys.sdo_geometry ( -- create the lat/long geometry
2001, -- 2D point feature
decode(dc4_datum_id,
'NAD27', 8260,
'NAD83', 8265,
'WGS84', 8307,
'HARN', 8265,
NULL, 8265,
8265), -- cover the datums we are likely to find
mdsys.sdo_point_type( -- make a point from the lat/long
( -(abs(NVL(long_dd_nbr,0)) + (NVL(long_mm_nbr,0)/60)
+ (NVL(long_ss_nbr,0)/3600)) ),
(abs(NVL(lat_dd_nbr,0)) + (NVL(lat_mm_nbr,0)/60)
+ (NVL(lat_ss_nbr,0)/3600)),
null),
null, -- no element info array
null ), -- no ordinate array
1000001 ) END geometry, -- transform to the fdep albers srid
rownum
FROM wacs.wacs_facilities wf,
wacs.wacs_geographic_locations gl
WHERE wf.wftc_wacs_facility_type_id in (3)
AND gl.oic_object_of_interest_id IN ('FACIL' , 'DISPS' , 'PROCE')
AND wf.wacs_facility_id not in
-- new exclude query per Lee Martin 10-24-11
(
SELECT distinct wf1_wacs_facility_id from wacs.FAC_WASTES_HANDLED fwh
WHERE fwh.WTC_WASTE_TYPE_ID = 161
union
select distinct wf1_wacs_facility_id from wacs.solid_waste_landfills
where fctc_facility_class_type_id = 530 or fsc3_facility_status_id = 'M'
union
select distinct wf1_wacs_facility_id from wacs.solid_waste_processings
where fctc_facility_class_type_id = 530 or fsc3_facility_status_id = 'M'
)
AND wf.wacs_facility_id = gl.wf1_wacs_facility_id
AND GL.WACS_GEO.SDO_GTYPE IN (2001)
Order by facility_id, facility_status
Added 2 new fields DOCUMENTS and REPORTS. These fields contain document links to DepNexus and links to a reporting application respectively.
This dataset was downloaded by the GeoPlan Center on 1/2/2019 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_HARN_Florida_GDL_Albers. - Added a DESCRIPT field based on CLASS - 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 FGDLAQDATE field based on date downloaded from source - Upcased all records in the table except for DOCUMENTSand REPORTS fields. - Updated metadata ground condition to reflect changes apparent in the data as noted in the COLLECT_DA field (12/26/2018) - Changed name of data set from WASTE_FACS_PT_SP to sldwst_dec18
Dataset copied.
Internal feature number.
ESRI
Feature geometry.
ESRI
Facility ID
Facility name
Facility type
Facility status
Date associated with facility status field
The Object of Interest (the thing regulated, permitted, or tracked). While the BIS Applications group will maintain the Object of Interest code table, the program area will be responsible for determining the taxonomy of codes needed to support their applications and business decisions.
Class or type of site. For example: landfill, tire disposal, yard trash, etc.
Class status
Type of ownership
Site address
City where site is located
5-Digit zip
4-Digit zip
Florida Department of Environmental Protection district where site is located
Central District
North East District
North West District
South East District
South West District
South District
District office
County ID. 1-67
Florida county where site is located
Description of proximity of point to actual feature being represented
Latitude - Degrees location identifier
Latitude - Minutes location identifier
Latitude - Seconds location identifier
Longitude - Degrees location identifier
Longitude - Minutes location identifier
Longitude - Seconds location identifier
Datum Identifier
High Precision GIS Network / High Precision Geodetic Reference
North American Datum of 1927
North American Datum of 1983
World Geodetic Survey of 1984
Method by which coordinates were acquired
Coordinate accuracy level codes
+/-0.01 meter
0.02 to 1.0 meter
1.1 meter to 10 meters
10 meters to 20 meters
20 meters to 50 meters
> 50 meters
Accuracy level
CSUR - Cadastral or Land Survey
GGPS - Geodetic Quality C/A Code and Carrier Phase GPS
DGPS - Differentially Corrected C/A Code Phase GPS
WGPS - C/A Code Phase GPS with Wide-Area Augmentation Service Correction
DPHO - Digital Aerial Photography
AGPS - Autonomous C/A Code Phase GPS
DMAP - Digital Map Interpolation
CALC - Calculated by GIS Software
LORN - LORAN-C Navigational Device
ADDM - Address Matching / Precision Mapping
MPHO - Manual Aerial Photography With Ground Control
MMAP Manual Map Interpolation
SATI - Satellite Imagery
ZIP2 - ZIP Code + 2 Segment Centroid
ZIP4 - ZIP Code +4 Segment Centroid
ZIPC - ZIP Code Centroid
Other or unknown
Reviewing status
The name of the person taking the measurement
The date and time on which the measurement was taken
Person or FDEP program verifying info
Date of verification
Method of verification
Digital Aerial Photography With Ground Control
Links to documents in the DepNexus repository
Link to facility reports
Latitude in decimal degrees.
Esri
Longitude in decimal degrees.
Esri
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
Webpage hyperlink to location in Google Maps.
GeoPlan
FGDL added field based on CLASS
GeoPlan
FGDL added field based on date downloaded from source
GeoPlan
Unique ID added by GeoPlan
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
http://ca.dep.state.fl.us/imf?focus=solidwaste
2600 Blairstone Road
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.