Water Level - Action Level Exceedance

<< Click to Display Table of Contents >>

 >EQuIS Library > Reports > EarthSoft Standard Reports > Action Level Reports >

Water Level - Action Level Exceedance

Report Name: Water Level - Action Level Exceedance

 

Report Type: Standard

 

Description: The Water Level - Action Level Exceedance (WLALE) Report generates an Excel export of the results of the Water Level II Report (WLII), action level information if action level parameters are selected and/or charts if the "Plot Water Level" parameter is selected. The report compares a numerical field of WLII, e.g. exact_elev etc., against the applicable action levels, when action level(s) input is included.

 

For chart layout options, select Plot/Plot group type of "one worksheet with separate charts for each location " to access the “Plot\The number of plots per print page:” and the “Chart Layout/Layout” input parameters. Layout1 includes a legend at top and no axis titles.

 

The Plot/Series chart type options apply to the water level series. The action levels are plotted as red line series.

 

The Logo file name input is for including a logo image in the upper-left header of each worksheet of the Excel export. If the input logo file (default demo name - artp_logo.jpg) is uploaded to DT_FILE, the logo will be in the Excel output file.

 

Action Level Data Preparation

 

The Water Level - Action Level Exceedance Report accommodates various action level configurations, as described below. Users may implement any one or each of these. Since the data structure is flexible and EQuIS does not enforce any single approach, a careful consideration of naming conventions and related best practices is highly recommended.

 

Action level data can be prepared in either DT_ACTION_LEVEL (DT_AL) and DT_ACTION_LEVEL_PARAMETER (DT_ALP) or DT_ACTION_LEVEL_LOOKUP (DT_ALL).

 

Note: The comparison_operator and euid of DT_ALL are required to be populated and cannot be empty by schema when DT_ALL is edited. The two fields are not used by this report. Therefore, in preparing action level data or editing DT_ALL for the report, populate comparison_operator with anything but null, and euid with distinct integers which will be auto-corrected when the table is saved.

 

After a water level variable, e.g. exact_elev, is defined, one or more action level codes for the water level at a location can be prepared. If an action level code is prepared in DT_AL/ALP, a single seasonal action level can be created for all locations.  

 

A basic action level code can be prepared in either DT_AL/ALP or DT_ALL tables, but should not be in both tables.  

 

If an action level code is prepared in DT_ALL, it can have various types of action levels such as general type (applied to all locations), location-specific type, seasonal type (applied to all locations), and location-seasonal type. Also, one or more seasonal action levels of the action level code can be created.  

 

When an action level code includes different types of action levels, the following rules apply.  

 

1.For non-seasonal action levels, location-specific overwrites non-location-specific action levels. In other words, when both location-specific and non-location-specific action levels are provided for a location, the report ignores the latter.

2.location-season-specific overwrites season-specific action levels. In other words, when both locational season-specific and seasonal only action levels are provided for a location, the report ignores the latter.

3.Seasonal overwrites non-seasonal, for the seasonal duration specified. In other words, when both seasonal and non-seasonal are provided, the report will apply the seasonal for its specified time period and ignore the non-seasonal of the same time period.

 

If an action level is overwritten, its warning level is also ignored.

 

If, accidently, an action level code is present in both DT_AL/ALP and DT_ALL tables but its seasonal data do not match, the report gives an information message and does not run.

 

The table below illustrates how these rules apply, with seasonal and locational action levels overwriting more basic action levels when included in the same action level code.

 

Action Level Type

Data Table

Basic

Seasonal

Locational

Seasonal and Locational

DT_ACTION_LEVEL (DT_AL)

DT_ACTION_LEVEL_PARAMETER (DT_ALP)

DT_ACTION_LEVEL_LOOKUP (DT_ALL)

 

 

 

 

Basic (non-locational and non-seasonal) action levels

Locational or seasonal action levels of an action_level_code.

If overlapping data are present, these action levels will be applied over the  basic action levels.  

Seasonal and locational action levels of an action_level_code.  

If overlapping data are present, these action levels will overwrite the more basic action levels.

Grey fill indicates this data table is not used for this action level variation.

                                                    Types of Action Levels and Overlapping Rules

 

A. Basic (not locational and not seasonal) Action Levels  

 

A basic action level code can be prepared in either DT_AL/ALP or DT_ALL tables (see table above) but should not be in both tables. If, accidently, an action level code is present in both DT_AL/ALP and DT_ALL tables but its data do not match, the report gives an information message and does not run.  

 

Preparing basic action levels in DT_AL and DT_ALP:

Required: param_code = exact_level or other numeric fields of the results of WLII  

    action_level_code      

    action_level

    unit

Optional: warning_level  

 

Or preparing basic action levels in DT_ALL

Required: param_code = exact_level, or other numeric fields of the results of WLII

    lookup_source = action_level_code

    comparison_id = "ANY"

    lookup_method="non-seasonal"

    action_level  

    action_level_unit

    Others required but not used by this report: comparison_operator and euid (see Note box above)

Optional: warning_level

 

B. Locational Action Levels  

 

Preparing DT_ALL:  

Required: param_code = exact_level or other numeric fields of the results of WLII

    lookup_source = action_level_code

    comparison_id = sys_loc_code

    lookup_method="any string" and not used by this scenario

    action_level

    action_level_unit

    Others required but not used by this report: comparison_operator and euid (see Note box above)

Optional: warning_level

 

C. Location-Specific Seasonal Action Levels

 

Preparing DT_ALL:

Required: param_code = exact_level or other numeric fields of the results of WLII

    lookup_source = action_level_code

    comparison_id = sys_loc_code

    lookup_method indicates how action levels change over time and may be any of the following date formats. The date formats are case sensitive. The hyphen
    is used as a separator; do not use an underscore else certain report functionality may be lost.  

1.yyyy

2.MM

3.MM-MM

4.MMdd-MMdd

5.yyyyMM

6.yyyyMMdd-yyyyMMdd

    and its corresponding value in comparison_value = (4 digits) year, (2 digits) month, ... or (less than 19 digits) date range, e.g. 2010, 02, 20100101-20100330
    etc., which must match the format defined in lookup_method.

    action_level

    action_level_unit

    Others required but not used by this report: comparison_operator and euid (see Note box above)

Optional: warning_level

 

D. Seasonal (general or non-locational) Action Levels

 

A seasonal action level code can be prepared in either DT_AL/ALP or DT_ALL tables (see table above) but should not be in both tables. If, accidently, an action level code is present in both DT_AL/ALP and DT_ALL tables, but its seasonal data do not match, the report gives info message and does not run.

 

Preparing DT_AL and DT_ALP:

Required: param_code = exact_level or other numeric fields of the results of WLII  

    action_level_code      

    action_level

    Unit

    DT_AL.season_start_month, or season_start_day. Note that if only season_start_month and no season_end_month are populated, the report assumes
    season_end_month is the end day of the season_start_month.  

Optional: warning_level, DT_AL.season_end_month/season_end_day  

 

Or preparing DT_ALL:

Required: the parameters are the ones in C above except:

    lookup_method =MM-MM or MMdd-MMdd

    comparison_id = “ANY”

 

Note that WLALE processes DT_ACTION_LEVEL_LOOKUP data without using the advanced action level API (i.e. no reliance on the object EarthSoft.ActionLevels.Library.105851.dll)).

 

Report Dependencies: This report depends on the Water Level II Report (EarthSoft.Reports.Library.64102.dll).

 

Note for Enterprise Use: Since this report depends on the WLII Report, enabling it in Enterprise requires storing the EarthSoft.Reports.Library.64102.dll in the Enterprise bin folder (typically at C:\Program Files\EarthSoft\Enterprise\bin).

 

File Name: EarthSoft.Reports.Library.52702.dll

Contact support@earthsoft.com for a direct file link.

 

Language: English

 

Input Parameters: A selection made to customize the output of a report. Note the Additional Fields parameter may be customized as explained here.

 

Input Parameters

Input Parameter Screenshot

Output Columns

Water Level

Location





Individual(s)




Group(s)



Water Level





Date Range





Start Date




End Date



Tasks




Reported Value




Calculation




Elevation




Depth



*Water Level

Approval Code(s):



*ebatch




*Water Level

User-estimated product density:



*sigfigs


defaults to 6


*Water Level

Default Specific Gravity:

defaults to 0.8


Additional Fields



Action Level

Action Level(s)




Comparison

Operator



Use Action Level Units




Max Decimals for unit conversion




Output exceedance rows only



Plot

Plot water level




Plot group type




The number of plots per print page




Series chart type:




Add trendline

Type




Display equation




Display R-Squared Value



Chart Layout

Layout




Layout2

Chart Title:




Left Y Axis Title:




X Axis Title:




Legend Position:


Chart Action Level

Action Levels



Adjust X axis min/max

Days less than minimum date:




Days more than maximum date:



X axis date format




Logo file name:



wl_ale_input

 

 

 

 

FACILITY_ID

FACILITY_CODE

SYS_LOC_CODE

LOC_NAME

LOC_GROUP

LOC_REPORT_ORDER MEASUREMENT_DATE

REFERENCE_ELEV

WATER_LEVEL

EXACT_ELEV

MEASURED_DEPTH_OF_WELL

DEPTH_UNIT

BATCH_NUMBER

TECHNICIAN

DRY_INDICATOR_YN

MEASUREMENT_METHOD

DIP_OR_ELEVATION

REMARK

EQUIPMENT_CODE

LNAPL_CAS_RN

LNAPL_DEPTH

LNAPL_THICKNESS

LNAPL_DENSITY

WATER_DEPTH

DNAPL_CAS_RN

DNAPL_DEPTH

DNAPL_THICKNESS

TASK_CODE

APPROVAL_CODE

X_COORD

Y_COORD

LONGITUDE

LATITUDE

* indicates hidden parameter

 

Tables:        DT_WATER_LEVEL, DT_WELL, RT_ANALYTE_DETAIL, DT_LOCATION, RT_GROUP, RT_GROUP_MEMBER, DT_FACILITY, DT_MEASURE_DATUM, RT_UNIT, RT_UNIT_CONVERSION_FACTOR, VW_LOCATION, DT_ACTION_LEVEL, DT_ACTION_LEVEL_PARAMETER, DT_ACTION_LEVEL_LOOKUP

 

Optional other tables, if Additional Fields are selected:

 

DT_WELL

DT_DRILL_ACTIVITY

DT_FACILITY

DT_LOCATION

DT_MEASURE_DATUM

DT_TASK

DT_WATER_LEVEL

VW_LOCATION

DT_WELL

DT_WELL_SEGMENT

 

Database Type: SQL

 

Database Schema: Standard (no custom or add-on schemas required)

 

Database Version: EQuIS 7+

 

Data Requirements: N/A

 

Output Type: Report Grid with options for Excel and CrossTab

 

Example Output: View the following example.

 

wale_example_output