<< Click to Display Table of Contents >> Navigation:  Vapor Intrusion Module > EQuIS Vapor Intrusion Format

Format Name: EQuIS_Vapor_Intrusion

File Name: EQuIS_Vapor_Intrusion.zip

Source: Available for the EarthSoft Primary Point of Contact (POC) on the EarthSoft Community Center (ECC) Downloads Dashboard in the Products\Vapor Intrusion folder.

Export(s): Yes (see section below)

Enum File: EQuIS_Vapor_Intrusion-enum.xml

 

Description: The EQuIS_Vapor_Intrusion Format is used to load vapor intrusion (VI) data into an EQuIS database. This format can load current and historical datasets. The EQuIS_Vapor_Intrusion Format also contains an Export File that can be used to export vapor intrusion data from the database.

 

Installation Instructions: This format requires the EQuIS Vapor Intrusion Schema (schema.Vapor.xme) applied to the EQuIS database.

•Download the EQuIS_Vapor_Intrusion format from the EarthSoft Community Center and unblock the *.zip file.

•For Enterprise and Professional usage of the export, this format should be published to the database. The export will be available for selection as a report once it has been published.

 

Prerequisites: Prior to using the EQuIS_Vapor_Intrusion format, it is recommended that the VI_ReferenceValueEDD_Example.xls file provided on the ECC is loaded to the database via the VI-refvals.zip format (see the Setup Reference Values for EQuIS Vapor Intrusion Module article. This file contains enumeration values that must be stored as reference values in the database before they can be used in an EDD. Using enumeration values prior to loading them as reference values will result in an error on Commit. The file also contains additional reference values that may be helpful when first establishing a VI workflow.

 

Overview: The EQuIS_Vapor_Intrusion format contains 1 grouping of 14 sections intended for the import of vapor intrusion data. The format sections are designed for the import of data related to buildings, locations, and samples. There are also sections intended for the population of file and geography data. Records in these sections can be associated to records in the VI_Sample_Parameter section by way of the object_euid field.

 

Limitations/Assumptions: The checks and mappings in any EDD format involve assumptions. The following are limitations and assumptions for the EQuIS_Vapor_Intrusion format.

VI_Building_Address

•Within this section, there is a default mapping of ‘BUILDING’ to DT_SUBFACILITY.SUBFACILITY_TYPE. A record must be present in RT_SUBFACILITY_TYPE where SUBFACILITY_TYPE = ‘BUILDING’ or an error will occur on commit.

•VI_Building_Address.subfacility_code maps to DT_SUBFACILITY.PARENT_SUBFACILITY_CODE. If the value in this field is not already in DT_SUBFACILITY.SUBFACILITY_CODE, an error will occur on commit.

•When the county field is populated, the associated state value must match the value stored in the RT_COUNTY.STATE_CODE field in the database where county = RT_COUNTY.COUNTY_CODE.

VI_Building_Inspection

•The enumeration values used in the foundation_wall_material and foundation_floor_material fields must exist in  RT_MATERIAL.MATERIAL_NAME or an error will occur on commit.

VI_Building_Parameter

•The param_unit field is configured to pull a list of valid values from RT_UNIT.UNIT_CODE. However, the selected value must also exist in the ‘param_unit’ enumeration or a “Value not found in list” error will occur.

VI_TestResultsQC

•VI_TestResultsQC.prep_date cannot precede VI_Sample.sample_start_date and must be before VI_TestResultsQC.analysis_date.

•VI_TestResultsQC.result_value cannot be zero if detect flag = 'Y' unless one of the radiological fields is populated (minimum_detectable_conc, counting_error, uncertainty, or critical_value).

•VI_TestResultsQC.cas_rn cannot be the same for two sample records both of which have a reportable_result value of 'Yes' unless the lab_anl_method_name values are different.

VI_Locations

•When both the loc_county_code and loc_state_code fields are populated, the value in the loc_state_code field must match the RT_COUNTY.STATE_CODE value in the database where loc_county_code = RT_COUNTY.COUNTY_CODE or an error will occur on Commit.

•The horz_accuracy_unit field is configured to pull a list of valid values from RT_UNIT.UNIT_CODE. However, the selected value must also exist in the ‘accuracy_unit’ enumeration or a “Value not found in list” error will occur.  

VI_TestResultsQC

•The prep_date field is required when the prep_method field is populated.

VI_COC_Analysis

•New COC records can be associated with existing DT_SPM_CONTRACT_MAG table records by way of the spm_contract_mag_id field. The value populated in this field must already exist in the DT_SPM_CONTRACT_MAG table or an error will occur on Commit.

•New COC records can be associated with existing DT_SPM_CONTRACT_METHOD table records by way of the spm_contract_method_id field. The value populated in this field must already exist in the DT_SPM_CONTRACT_METHOD table or an error will occur on Commit.

VI_Files

•The object_euid field is optional in this section. If you wish to associate a file record to either a DT_GEOGRAPHY or DT_SAMPLE_PARAMETER record, the local euid from the VI_Geography or VI_Sample_Parameter sections, respectively, should be populated in the VI_Files.object_euid field.

VI_Geography

•The object_euid field is required in this section and should be populated with the local EUID from the VI_Sample_Parameter section of the format. New DT_GEOGRAPHY table records that reference existing records in the DT_SAMPLE_PARAMETER table can be added with the EQuIS_Vapor_Intrusion format by populating sys_sample_code, measurement_date, and param_code for an existing DT_SAMPLE_PARAMTER record. VI_Geography.object_euid must match the VI_Sample_Parameter.euid value in the EDD.

 

 

EQuIS Table Mappings:

 

 

Exports: The data returned will be automatically filtered by the facility to which the user is connected, as well as by the parameters selected prior to running the report. See the Exports from Professional EDP article for more information about running exports.