Common use of Technical Specifications for Deliverables Clause in Contracts

Technical Specifications for Deliverables. (1) Sampling and monitoring data must be submitted in standard Regional Electronic Data Deliverable (EDD) format prescribed in the Removal Work Plan. Other delivery methods may be allowed if electronic direct submission presents a significant burden or as technology changes. (2) Spatial data, including spatially-referenced data and geospatial data, must be submitted: (a) in the ESRI File Geodatabase format; and (b) as unprojected geographic coordinates in decimal degree format using North American Datum 1983 (NAD83) or World Geodetic System 1984 (WGS84) as the datum. If applicable, submissions should include the collection method(s). Projected coordinates may optionally be included but must be documented. Spatial data should be accompanied by metadata, and such metadata should be compliant with the Federal Geographic Data Committee (FGDC) Content Standard for Digital Geospatial Metadata and its EPA profile, the EPA Geospatial Metadata Technical Specification. An add-on metadata editor for ESRI software, the EPA Metadata Editor (EME), complies with these FGDC and EPA metadata requirements and is available at ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatial/epa-metadata- editor. (3) Each file must include an attribute name for each site unit or sub- unit submitted. Consult ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatial/geospatial-policies-and- standards for any further available guidance on attribute identification and naming. (4) Spatial data submitted by Purchaser does not, and is not intended to, define the boundaries of the Site.

Technical Specifications for Deliverables. (1) Sampling and monitoring data must should be submitted in standard Regional Electronic Data Deliverable (EDD) format prescribed in the Removal Work Planformat. Other delivery methods may be allowed if electronic direct submission presents a significant burden or as technology changes. (2) Spatial data, including spatially▇▇▇▇▇▇▇▇▇-referenced data ▇▇▇▇▇▇▇▇▇▇.▇▇▇▇ and geospatial data, must be submittedshould besubmitted: (a) in the ESRI File Geodatabase format; :, and (b) as unprojected geographic coordinates in decimal degree format using North American Datum 1983 (NAD83) or World Geodetic System 1984 (WGS84) as the datum. If applicable,, submissions should include the collection method(smelhod(s). Projected coordinates may optionally be included but must be documented. Spatial data should be accompanied be.accompanied by metadata, and such metadata should be compliant with the Federal Geographic Data Committee (FGDC) Content Standard for Tor Digital Geospatial Metadata and its EPA profile, the EPA Geospatial Metadata Technical Specification. An add-on metadata editor for ESRI software, ▇▇▇▇ ▇▇▇▇▇▇▇▇. the EPA Metadata Editor (EME), complies with these FGDC and EPA metadata requirements and is available at ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatialhUps://www.epa..uoy/geospatial/epa-metadata- metadcna: editor. (3) Each file must include an attribute name for each site unit or sub- sub­ unit submitted. .. Consult ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatial/geospatial▇▇▇▇▇▇▇▇▇▇▇/▇▇▇▇▇▇▇▇▇▇-policies▇▇▇▇▇▇▇▇-and- ▇▇▇▇▇ standards for any further available furlher availabie guidance on attribute identification and naming. (4) Spatial data submitted by Purchaser Respondent does not, . and is not intended to, define the boundaries of the Site.

Technical Specifications for Deliverables. (1) Sampling and monitoring data must should be submitted in standard Regional Electronic Data Deliverable (EDD) format prescribed in the Removal Work Planformat. Other delivery methods may be allowed if electronic direct submission presents a significant burden or as technology changes. (2) Spatial data, including spatially-referenced data and geospatial data, must should be submitted: (a) in the ESRI File Geodatabase format; and (b) as unprojected geographic coordinates in decimal degree format using North American Datum 1983 (NAD83) or World Geodetic System 1984 (WGS84) as the datum. If applicable, submissions should include the collection method(s). Projected coordinates may optionally be included but must be documented. Spatial data should be accompanied by metadata, and such metadata should be compliant with the Federal Geographic Data Committee (FGDC) Content Standard for Digital Geospatial Metadata and its EPA profile, the EPA Geospatial Metadata Technical Specification. An add-on metadata editor for ESRI software, the EPA Metadata Editor (EME), complies with these FGDC and EPA metadata requirements and is available at ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatial/epa-metadata- editor. (3) Each file must include an attribute name for each site unit or sub- unit submitted. Consult ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatial/geospatial-policies-and- standards for any further available guidance on attribute identification and naming. (4) Spatial data submitted by Purchaser Respondents does not, and is not intended to, define the boundaries of the Site.

Technical Specifications for Deliverables. (1) Sampling and monitoring data must should be submitted in standard Regional Electronic Data Deliverable (EDD) format prescribed in the Removal Work Planformat. Other delivery methods may be allowed if electronic direct submission presents a significant burden or as technology changes. (2) Spatial data, including spatially-referenced data and geospatial data, must should be submitted: (a) in the ESRI ESRl.File Geodatabase format; and (b) as unprojected geographic coordinates in decimal degree format using North American .American Datum 1983 (NAD83) or World Geodetic System 1984 (WGS84) as the datum. If applicable, submissions should submissions.should include the collection method(s). Projected coordinates may optionally be included but must be documented. Spatial data should be accompanied by metadata, and such metadata should be , compliant with the Federal Geographic Data Committee (FGDC) Content Standard for Digital Geospatial Metadata and its EPA profile, the EPA Geospatial Metadata Technical Specification. An .An add-on metadata editor for ESRI ESRl software, the EPA Metadata Editor (EME), complies with these FGDC and EPA metadata requirements and is available at ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇▇/geospatial/epa^VgeospatiaEepa-metadata- editor. (3) Each file must include an attribute name for each site unit or sub- unit submitted. Consult Co t su U ▇▇▇▇▇://▇▇▇▇-▇▇.▇▇▇.▇▇▇/geospatial/geospatial-policies-and- standards for any further available guidance on attribute identification and naming.. ■ (4) Spatial data submitted by Purchaser Respondent does not, and is not intended to, define the boundaries of the Site.

Technical Specifications for Deliverables. (1) Sampling and monitoring data must should be submitted in standard Regional regional Electronic Data Deliverable (EDD) format prescribed in the Removal Work Planformat. Other delivery methods may be allowed if electronic direct submission presents a significant burden or as technology changes. (2) Spatial data, including spatially-spatially referenced data and geospatial data, must should be submitted: (ai) in the ESRI File Geodatabase format; and (bii) as unprojected geographic coordinates in decimal degree format using North American Datum 1983 (NAD83) or World Geodetic System 1984 (WGS84) as the datum. If applicable, submissions should include the collection method(s). Projected coordinates may optionally be included but must be documented. Spatial data should be accompanied by metadata, and such metadata should be compliant with the Federal Geographic Data Committee (FGDC) Content Standard for Digital Geospatial Metadata and its EPA profile, the EPA Geospatial Metadata Technical Specification. An add-on metadata editor for ESRI software, the EPA Metadata Editor (EME), complies with these FGDC and EPA metadata requirements and is available at ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatial/epa-metadata- editor./EME/. (3) Each file must include an attribute name for each site unit or sub- sub-unit submitted. Consult ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/geospatial/geospatial-policiespolicies- and-and- standards for any further available guidance on attribute identification and naming. (4) Spatial data submitted by Purchaser Respondent does not, and is not intended to, define the boundaries of the Site.