Parcel environmental engineering-control status
What physical engineering controls are officially recorded for contamination or remediation at or near this parcel, and what type, implementation or effective date, current or lifted status, and termination date are reported?
The data that answers it
Ranked by fit · best firstNJDEP’s parcel-addressable remediation layer reports engineering-control status, including ongoing or lifted states, an engineering-control date, remediation case and site identity, parcel references, and remedial-action-permit context. Preserve the raw status, date, parcel references, case status, and source vintage; registry status does not establish remedy effectiveness, physical condition, compliance, causation, or liability.
ADEQ’s public queryable DEUR/VEMUR layer exposes distinct raw USE_RESTRICTION values for “DEUR - Engineering Control” and “VEMUR - Engineering Control,” together with site status, recorded and closed dates, remediation and document identifiers, address, coordinates, and document links. It identifies officially recorded engineering-control presence and type at a site without proving effectiveness or physical condition.
NYSDEC’s queryable remediation-site data exposes control_type, control_code, programme and site identity, project phase, and actual or planned project completion date. Rows explicitly carrying control_type='ENG' establish recorded engineering-control presence and associated programme/project timing. Project completion date is not automatically the control implementation, operating, lift, or termination date.
The ISRA Source reports raw engineering-control status and implementation date with case/site identity, parcel references, case status, permit context, and source vintage.
Florida’s public queryable control-boundary layer provides site identity and address, polygon geometry, boundary control identity, an explicit BOUNDARY_ENGINEERING_CONTROLS field, begin and end dates, and mechanism effective dates. Only records with explicit engineering-control evidence support this link; full-registry membership alone does not prove an engineering control, and generic dates must not be recast as implementation or lift dates without record-level support.
The re-evaluation Source reports raw engineering-control status and implementation date for identified open confirmed-contaminated cases, with parcel and permit context.
The Known Contaminated Sites layer reports engineering-control status and date for identified geocoded sites with case status, remedial classification, and source vintage.
The Source reports raw ENG_CONTROL status and EC_DATE engineering-control implementation timing for parcel-reachable identified closed cases, with case status, remedial-action-permit context, and source vintage. It does not support an inferred current, lifted, or termination state when no such raw value is reported.
The public DC LUST layer has case-level ENG_CONTROL_TYPE and ENG_CONTROL_DATE fields, together with engineering-control manufacturer/product and parcel-reachable address and coordinate fields. It supports officially recorded engineering-control type and associated date for populated records, but exposes no control-specific current/lifted status or termination date.
The official closure-determination layer reports paving or cap maintenance, building-slab maintenance, vapor-barrier presence or requirement, vapor-system presence or requirement, future-construction and excavation-soil requirements, groundwater-encounter requirements, operations/maintenance/inspection plans, and long-term monitoring requirements. The determination issue date pins when those controls or requirements were reported, but the schema does not provide control-specific implementation, lift, or termination dates.
The statewide governmental full-file extract contains one record per recorded institutional or engineering control and exposes control_type and control_detail with remediation programme, corrective-action status, filed date, site identity, address, and coordinates. Raw engineering-control values establish recorded physical-control presence and type at a geocoded remediation site; they do not prove performance, condition, or continuing effectiveness.
ADEQ records raw land-use restriction values including 'DEUR (EC)' with restriction-recorded date, site identity, site status, acceptance date, and closure date.
Show 4 more sources+−
Live grouped results show HW rows with control_type='ENG'; this supports coarse recorded engineering-control presence, not physical subtype or control-specific lifecycle dates.
The site-aggregated NFR product reports whether any NFR letter identifies an engineered barrier and distinguishes asphalt, concrete, building slab, three- or ten-foot clean soil, alternate, and other barrier types. This directly supplies officially recorded engineering-control presence and type. The earliest/latest NFR dates bound the site's determination history but cannot be assigned as a control-specific implementation or effective date when several letters exist; the product does not establish present operation, lifted status, or termination date.
Live grouped results show VCP rows with control_type='ENG'; this supports coarse recorded engineering-control presence, not physical subtype or control-specific lifecycle dates.
The verified Virginia VRP/UECA statewide full-file export identifies remediation sites carrying an engineered remedy through the normalized engineering_control_present field. It supports engineering-control presence, but not control subtype, implementation date, operating status, or lift date; unsupported lifecycle values remain unknown and the export vintage and site-match method must be retained.
Related questions
Under Parcel environmental contamination and remediation statusNeed Parcel environmental engineering-control status answered at scale?
We will test these sources on your own records, show you match and fill rates, then handle the contract, security review, and delivery into your stack.