<< Click to Display Table of Contents >> Navigation:  EQuIS Library > Formats > Oil_Gas_Baseline_EQEDD Format

Format Name: Oil_Gas_Baseline_EQEDD

File Name: Oil_Gas_Baseline_EQEDD.zip

Source: Available for the EarthSoft Primary Point of Contact (POC) on the EarthSoft Community Center Downloads dashboard from the All Items > Formats folder.

Export(s): Yes (see section below)

Enumeration File: Oil_Gas_Baseline_EQEDD-enum.xml

 

Description: The Oil_Gas_Baseline_EQEDD format is a modification of the standard EQEDD format and is intended for loading fracking-specific data. This format includes a variety of exports that can be used for reporting purposes.

 

Installation Instructions: The Oil_Gas_Baseline_EQEDD format is available as part of a format package (Oil_Gas_Baseline_EQEDD_FormatPackage.zip) file on the EarthSoft Community Center. To access the format, download the Oil_Gas_Baseline_EQEDD format package, unblock the *.zip file, and extract the contents. The extracted contents of the format package will include the Oil_Gas_Baseline_EQEDD.zip format file alongside a ReadMe text file, an example reference value EDD, an example remap set, an example field results EDD, and an example lab results EDD.

 

Overview: The Oil_Gas_Baseline_EQEDD format contains the following sections:  

•Field

•DataProvider_v1 – Creates record(s) in the RT_COMPANY table.

•Task_v1 – Creates record(s) in the DT_TASK table.

•Subfacilities_v1 – Creates record(s) in the DT_SUBFACILITY table.

•Location_v1 – Creates record(s) in the DT_LOCATION, DT_COORDINATE, DT_MEASURE_DATUM, DT_WELL, and DT_WELL_SEGMENT tables.

•LocationParameter_v1 – Creates record(s) in the DT_LOCATION_PARAMETER table.

•Survey_Info_v1 – Creates record(s) in the DT_LOCATION_PARAMETER table regarding site surveys.

•DrillActvility_v1 – Creates record(s) in the DT_DRILL_ACTIVITY table.

•Lithology_v1 – Creates record(s) in the DT_LITHOLOGY table.

•Well_v1 – Creates record(s) in the DT_well and DT_MEASURE_DATUM tables.

•WellConstruction_v1 – Creates record(s) in the DT_WELL_SEGMENT table.

•GeoSample_v1 – Creates record(s) in the DT_SAMPLE, DT_STATIC_PROPS, and DT_ATTERBERG tables.

•WaterLevel_v1 – Creates record(s) in the DT_WATER_LEVEL table.

•WaterTable_v1 – Creates record(s) in the DT_WATER_TABLE table.

•DownholePoint_v1 – Creates record(s) in the DT_DOWNHOLE_POINT_DATA table.

•ExtractionInjectionWells_v1 – Creates record(s) in the DT_PUMP_RATE table.

•Equipment_v1 – Creates record(s) in the DT_EQUIPMENT table.

•Purge_v1 – Creates record(s) in the DT_PURGE table.

•BasicResults_v1 – Creates record(s) in the DT_BASIC_RESULT table.

•FieldSample_v1 – Creates record(s) in the DT_FIELD_SAMPLE, DT_SAMPLE, DT_STATIC_PROPS, DT_CHAIN_OF_CUSTODY, and DT_SDG tables.

•SampleParameter_v1 – Creates record(s) in the DT_SAMPLE_PARAMETER table.

•FieldResults_v1 – Creates record(s) in the DT_RESULT and DT_TEST TABLES for field samples.

•WaterLevel_Purge – Creates record(s) in the DT_PURGE and DT_WATER tables.

•COC_v1 – Creates record(s) in the DT_CHAIN_OF_CUSTODY table.

•Lab

•LabSample_v1 – Creates record(s) in the DT_SAMPLE table for lab samples.

•TestResultsQC_v1 – Creates record(s) in the DT_RESULT table for lab and lab QC samples.

•TestBatch_v1 – Creates record(s) in the DT_TEST_BATCH table.

•Files

•Creates record(s) in the DT_FILE table.

 

 

Oil_Gas_Baseline_EQEDD vs. EQEDD

 

The following additions are found in the Oil_Gas_Baseline_EQEDD format that distinguishes this format from the standard EQEDD format:

 

 

 

 

 

Limitations/Assumptions: The checks and mappings in any EDD format involve assumptions. Here is a list of those assumptions and limitations for the Oil_Gas_Baseline_EQEDD format:

•The following reference values must exist in the database prior to import:

•DataProvider_v1

•The data_provider must exist in the RT_COMPANY table as COMPANY_CODE.

•The company_type must exist in the RT_COMPANY table as COMPANY_TYPE.

•Subfacilities_v1

•The subfacility_type must exist in the RT_SUBFACILITY_TYPE table as SUBFACILITY_TYPE.

•The state must exist in the RT_STATE table as STATE_CODE.

•The parent_subfacility_code must exist in the DT_SUBFACILITY table as SUBFACILITY_CODE.

•Location_v1

•The elev_unit, horz_accuracy_unit, elev_accuracy_unit, depth_unit, and datum_unit must exist in the RT_UNIT table as UNIT_CODE.

•The horz_collect_method_code must exist in the RT_COORD_HORZ_METHOD table as HORZ_COLLECT_METHOD_CODE.

•The elev_collect_method_code must exist in the RT_COORD_ELEV_METHOD table as ELEV_COLLECT_METHOD_CODE.

•The elev_datum_code must exist in the RT_COORD_ELEV_DATUM table as ELEV_DATUM_CODE.

•The subcontractor_name_code must exist in the RT_COMPANY table as COMPANY_CODE.

•The geometric_type_code must exist in the RT_COORD_GEOMETRIC_TYPE table as GEOMETRIC_TYPE_CODE.

•The loc_type must exist in the RT_LOCATION_TYPE table as LOCATION_TYPE_CODE.

•The loc_state_code must exist in the RT_STATE table as STATE_CODE.

•The loc_major_basin must exist in the RT_BASIN table as BASIN_CODE.

•The county_code must exist in the RT_COUNTY table as COUNTY_CODE (with correlating STATE_CODE).

•The horz_datum_code must exist in the RT_COORD_HORZ_DATUM table as HORZ_DATUM_CODE.

•The data_provider must exist in the RT_COMPANY table as COMPANY_CODE.

•LocationParameter_v1

•The parameter_code must exist in the RT_LOCATION_PARAM_TYPE table as PARAM_CODE.

•The parameter_unit must exist in the RT_UNIT table as UNIT_CODE.

•Survey_Info_v1

•The task_code must exist in the DT_TASK table as TASK_CODE.

•The coll_point_desc, age_of_water_supply, treatment_yn, treatment_type, gas_well_operator, gas_well_unit_name, gas_well_permit_num, water_source_date, and treatment_samp_loc must all exist in the DT_LOCATION_PARAMETER table as param_code.

•DrillActivity_v1

•The diameter_unit must exist in the RT_UNIT table as unit_code.

•The drilling_subcontractor must exist in the RT_COMPANY table as COMPANY_CODE.

•Lithology_v1

•The material_type must exist in the RT_MATERIAL table as MATERIAL_NAME.

•Well_v1

•The datum_unit, depth_unit, stickup_unit, pump_unit and sump_unit must exist in the RT_UNIT table as UNIT_CODE.

•The datum_collection_method_unit_code must exist in the RT_COORD_ELEV_METHOD table as ELEV_COLLECT_METHOD_CODE.

•The construct_contractor must exist in the RT_COMPANY table as COMPANY_CODE.

•WellConstruction_v1

•The depth_unit, diameter_unit, thickness_unit, and slot_size_unit must exist in the RT_UNIT table as UNIT_CODE.

•GeoSample_v1

•The K_unit, density_unit and organic_carbon_unit must exist in the RT_UNIT table as UNIT_CODE.

•WaterLevel_v1

•The depth_unit must exist in the RT_UNIT table as UNIT_CODE.

•The lnapl_cas_rn and dnapl_cas_rn must exist in the RT_ANALYTE table as CAS_RN.

•WaterTable_v1

•The capped_pressure_unit and temperature_unit must exist in the RT_UNIT table as UNIT_CODE.

•DownholdPoint_v1

•The param_unit must exist in the RT_UNIT table as UNIT_CODE.

•The param must exist in the RT_DOWNHOLE_POINT_PARAM_TYPE table as PARAM.

•ExtractionInjectionWells_v1

•The pump_rate_unit and design_rate_unit must exist in the RT_UNIT table as UNIT_CODE.

•Equipment_v1

•The equipment_type must exist in the RT_EQUIPMENT_TYPE as EQUIPMENT_TYPE.

•The size_unit must exist in the RT_UNIT table as UNIT_CODE.

•Purge_v1

•The depth_unit, purge_vol_unit, and purge_rate_unit must exist in the RT_UNIT table as UNIT_CODE.

•BasicResults_v1

•The field_parameter must exist in the RT_ANALYTE table as CAS_RN.

•The depth_unit and result_unit must exist in the RT_UNIT table as UNIT_CODE.

•FieldSample_v1

•The sample_matrix_code must exist in the RT_MATRIX table as MATRIX_CODE.

•The sample_type_code must exist in the RT_SAMPLE_TYPE table as SAMPLE_TYPE_CODE.

•The depth_unit must exist in the RT_UNIT table as UNIT_CODE.

•The sampling_company_code must exist in the RT_COMPANY table as COMPANY_CODE.

•The geologic_unit_code must exist in the RT_GEOLOGIC_UNIT table as GEOLOGIC_UNIT_CODE.

•SampleParameter_v1

•The param_code must exist in the RT_SAMPLE_PARAM_TYPE table as PARAM_CODE.

•The param_unit must exist in the RT_UNIT table as UNIT_CODE.

•FieldResults_v1

•The data_provider and sampling_company_code must exist in the RT_COMPANY table as COMPANY_CODE.

•The cas_rn must exist in the RT_ANALYTE table as CAS_RN.

•The sample_matrix_code must exist in the RT_MATRIX table as MATRIX_CODE.

•The qualifier must exist in the RT_QUALIFIER table as QUALIFIER.

•WaterLevel_Purge

•The controller must exist in the DT_EQUIPMENT table as EQUIPMENT_CODE.

•The depth_unit, diameter_unit, purge_vol_unit, and purge_rate_unit must exist in the RT_UNIT table as UNIT_CODE.

•The measurement_method must exist in the RT_LOOKUP table as LOOKUP_CODE.

•The lnapl_cas_rn and dnapl_cas_rn must exist in the RT_ANALYTE table as CAS_RN.

•COC_v1

•The shipping_company must exist in the RT_COMPANY table as COMPANY_CODE.

•LabSample_v1

•The sample_matrix_code must exist in the RT_MATRIX table as MATRIX_CODE.

•The sample_type_code must exist in the RT_SAMPLE_TYPE table as SAMPLE_TYPE_CODE.

•The depth_unit must exist in the RT_UNIT table as UNIT_CODE.

•TestResultsQC_v1

•The sys_sample_code must exist in the DT_SAMPLE or in the LabSample_v1 section.

•The lab_anl_method_name must exist in the RT_ANALYTIC_METHOD table as ANALYTIC_METHOD.

•The total_or_dissolved must exist in the RT_FRACTION table as FRACTION.

•The test_type must exist in the RT_TEST_TYPE table as TEST_TYPE.

•The lab_matrix_code must exist in the RT_MATRIX table as MATRIX_CODE.

•The prep_method must exist in the RT_PREP_METHOD table as PREP_METHOD.

•The lab_name_code must exist in the RT_COMPANY table as COMPANY_CODE.

•The subsample_amount_unit, final_volume_unit, result_unit, and detection_limit_unit must exist in the RT_UNIT table as UNIT_CODE.

•The preservative must exist in the RT_PRESERVATIVE table as PRESERVATIVE.

•The cas_rn must exist in the RT_ANALYTE table as CAS_RN.

•The result_type_code must exist in the RT_RESULT_TYPE table as RESULT_TYPE_CODE.

•The interpreted_qualifiers must exist in the RT_QUALIFIER table as QUALIFIER.

•TestBatch_v1

•The lab_anl_method_name must exist in the RT_ANALYTIC_METHOD table as ANALYTIC_METHOD.

•The total_or_dissovled must exist in the RT_FRACTION table as FRACTION.

•The test_type must exist in the RT_TEST_TYPE table as TEST_TYPE.

•The test_type_batch must exist in the RT_TEST_BATCH_TYPE as TEST_BATCH_TYPE.

•Files_v1

•The file_type must exist in the RT_FILE_TYPE table as FILE_TYPE.

•Test Alternate Key (TAK) fields available in the format: SAMPLE_ID, ANALYTIC_METHOD, ANALYSIS_DATE, FRACTION, COLUMN_NUMBER, and TEST_TYPE.  The IDENTIFIER field does not exist in the Oil_Gas_Baseline_EQEDD format. If “Identifier” is toggled in the database test-level key fields, an error message will appear for DT_TEST upon the Create step.

•All sections containing the sys_loc_code column will function as explained below:

•If the sys_loc_code field is populated, the format will check against the Location_v1 section to see if this data exists.

•If the Location_v1 section of the format file is empty, the sys_loc_code fields will check the database to see if the locations exist (Professional EDP Only).

•If the location does not exist in the database or the Location_v1 section, an error will occur on the commit stage.

•All default mappings in the EDD description pre-exist in the EQuIS tables. These values are used as a reference to properly map data to the corresponding tables and an error will occur if the reference is not found.

•TestBatch_v1 must have corresponding records in the LabSample_v1 and TestResultsQC_v1 sections.

•Files_v1.place_type must equal “sys_loc_code” and Files_v1.place_code must equal the sys_loc_code value associated with the file.

•LabQC EDD export – TestResultsQC_v1.analysis_location equal “LB” for this section to populate.  

•Location EDD export – DT_FACILITY.IDENTIFIER must equal "PRIMARY" and DT_FACILITY.COORD_TYPE_CODE must equal "LAT LONG" for this export to generate correctly.

•When generating the Field Sample EDD export, FieldSample_v1 must have the following filter applied: sample_source = “FIELD”.

•If well or well segment data are imported through the Location_v1 section of the format, be aware that the default value for well depth unit and well segment depth unit is ‘ft’.

 

For custom checks and additional default mappings, please see the EDD Description file for the Oil_Gas_Baseline_EQEDD format.

 

 

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.