Skip to content
English
  • There are no suggestions because the search field is empty.

Adding Sample Points in the User Interface

Summary

This guide explains how to add sample points directly in the ENFOS user interface (UI). Sample points must exist in ENFOS before you can upload field or lab data to them. Adding a point in the UI is the best option when you need to create points one at a time. To create many points at once, see the Importing Sample Points article.

Before You Begin

  • Sample point names must be unique. Aliases are available if a name is used differently elsewhere (for example, on a Chain of Custody).
  • Confirm whether data is managed at the site (level 17) or the AOC (level 20). This is set by the data node assignment in Administration > Settings.

Step-by-Step Instructions

  1. Navigate to the site or AOC level in the hierarchy (depending on data node assignment in Administration > Settings).
  2. Navigate to the Scientific Data Module and select Sample Points. A list of existing sample points appears in the window.
  3. Select the Sample Point Type from the drop down menu and click Add Sample Point.
  4. Fill in all required fields. Required fields are marked with an asterisk (*).
    1. Note that Aliases can be added as an optional field when adding a new sample point. They can also be added at any time to an existing sample point.
  5. Once the fields are populated, click Save at the bottom of the screen. The added sample point is added to the sample point list for the site or AOC.

Tips and Best Practices

  • Aliases: An alias lets you import lab and/or field data under a different name while still associating it with the correct sample point. Multiple aliases can be added as comma separated values. For example, if ENFOS has "MW-01" but the incoming data uses "MW1", adding "MW1" as an alias lets ENFOS match that data to sample point MW-01 and reduces errors and fix ups.
  • Z elevations: Z elevations can be updated over time, and ENFOS maintains a history of the values. Changes are date constrained, so each Z elevation is tied to the date it applies to. Groundwater elevation calculations use the Z elevation with the associated date.
  • Naming conventions: Keep sample point names clean and consistent. There is no need to build the sampling date or depth into the name, because the Field Sample Name and Lab Sample Name fields tied to each sample point capture that detail when lab data is imported. For example, use MW-1 as the sample point name with MW-1-20250324 as the field sample name, or SB-1 as the sample point name with SB-1-2" as the field sample name. Standardizing your naming approach across the site (level 17) or AOC (level 20) makes points easier to find and helps reduce errors.

Common Questions

Why can I not upload data to a sample point? The sample point must exist in ENFOS before any field or lab data can be loaded to it. Confirm the point has been created at the correct site or AOC node, then import the data again.

The lab or field data uses a different name than the sample point in ENFOS. What do I do? Add that name as an alias on the sample point. The alias lets ENFOS associate the incoming data with the correct point without renaming the point, which reduces errors and fix ups during EDD processing.

Do I need to include the sampling date or depth in the sample point name? No. Keep the sample point name simple and reuse it over time. The date or depth belongs in the Field Sample Name or Lab Sample Name fields in the lab data EDD, which are associated with the sample point.

Can I change a sample point's Z elevation later? Yes. Z elevations can be updated, and ENFOS keeps a dated history. Because the values are date constrained, groundwater elevation calculations use the Z elevation that applies to the relevant date.