Confluence Retirement

In an effort to consolidate USGS hosted Wikis, myUSGS’ Confluence service is scheduled for retirement on January 27th, 2023. The official USGS Wiki and collaboration space is now SharePoint. Please migrate existing spaces and content to the SharePoint platform and remove it from Confluence at your earliest convenience. If you need any additional information or have any concerns about this change, please contact myusgs@usgs.gov. Thank you for your prompt attention to this matter.
Child pages
  • Pinedale Anticline Data Management System (PADMS) Operator Manual

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: spelling/grammar updates

...

PADMS is an application used by the Bureau of Land Management (BLM), the Pinedale Anticline Project Office (PAPO), and energy companies to track and document disturbance and reclamation activities associated with natural gas operations on the Pinedale Anticline in NW Wyoming. Operators can view all data in the application but can only edit their own data. Agency managers have the ability to look at and edit all data. The application allows querying of the data entered to provide useful information to all users.

...

When a PAPO user logs in to PADMS, the first page displayed is the PADMS Entry Page. This is the page users will employ to navigate to the individual operator pages and reporting component.

The following figure is the PADMS Entry Page. The following sections describe each of the primary four components.

...

The reports component is comprised of "canned" and "ad-hoc" reports. Canned Reports is a report that has the criteria pre-selected so that when the link is selected, the report runs automatically with minimal additional information required.

...

  • Presence of Noxious Weeds displays the type of noxious weeds present per location: select Presence of Noxious Weeks link from the Frequently Used Reports section to retrieve this report
  • Presence of Undesirable Species displays the types of undesirable species present per location: select Presence of Undesirable Species link from the Frequently Used Reports section to retrieve this report
  • Seeding Method Used dispays displays the type of seeding method used per location: select the Seending Seeding Method Used link from the Frequently Used Reports section, and
    • refine the report as necessary by specifying an operator, location type, and/or seeding method
    • select the display format
    • use Sort By and Ordered fields to sort the report
    • select the Run Report button to produce the report
    • Select the Reset Form button to display the Ad-Hoc Report selection page with more selection criteria
  • Archived Locations displalys displays all the the locations that have been archived: select the Archived Locations link from the Frequently Used Reports section to retrieve this report
  • All Data Report displays all the the operators and the data they've entered: select the All Data link from the Frequently Used Reports  section to retrieve this report

...

  • Select the Ad-Hoc link from the Frequently Used Reports section
  • Refine the report results by selecting specific criteria
    • Report Title to name the report
    • Scope includes a specific operator and/or location type
    • Spatial Reports refines locations with specific spatial data, e.g. Search for locations only having disturbances with no reclamation
    • Status Reports refines locations with specific status report data, e.g. locations with a specific status or has no qualitative data
    • Output Modes default is On-screen list, but may be sorted using the Sort By and Ordered fields
    • Noxious or Undesirable Weed Species will display locations that have the specified weed(s) present
    • Seeding Method specifies a particular seeding method
    • Pre-ROD specifies locations that were established before the ROD was created
    • Federal Surface Site shows either federal surfance surface sites or non-federal surface sites
  • Select Run Report to produce the report
  • Select Reset Form to display the Ad-Hoc Reports selection page again

...

  • Home directs the user back to the PADMS Entry Page
  • Reporting directs the user to the Ad-Hoc selection page
  • Species List displays a complete list of the species entered into the application
  • Ecological Site Description displays a complete list of ecological site descriptions Ecological Site Descriptions (ESD) entered into the application
  • Modify Search displays a map containing all the locations in the report's results list
    • NOTE: this option only appears when not looking at the results on a map
  • Regular Report displays the report's results in a table format
    • NOTE: this option only appears when not looking at the results in the table format
  • Export As allows the report to be exported in the following formats
    • PDF outputs the displayed report in this format
    • XLS outputs the displayed report in this format
    • SHP zips the spatial data for all locations listed in the report's results list
    • CSV outputs the dislayed displayed report in a comma-separate file

...

Downloads

Downloads found on the PADMS Entry Page contain every operator in the PADMS application and the data they’ve entered.

...

The Printable Map button captures the map with the selected criteria displayed and allows the user to print the map. On the print page, the map is displayed along with a map legend below it which indicates what criteria is displayed. The user can zoom in and out on the map before printing.

Return to Table of Contents

Map Controls

  • Zoom in/out by using the vertical gray sliding bar in the upper left corner of the map
  • Change the background by selecting Map, Aerial, or Terrain from the upper right corner of the map
  • Pan the area by clicking the left mouse button and dragging
  • For additional information about a spatial feature, select a specific disturbance or reclamation area, or reference point by zooming in then clicking on the polygon. This will cause a pop-up box to appear with more information regarding the specific spatial feature.

...

Operator Summary Page

From the PADMS Entry Page, select an operator from the Operators list to navigate to the Operator Summary Page.

...

The Operator Map functions the same as the map found on the PADMS Entry Page. However, the spatial data displayed on the Operator Map is specific to the operator, and the layers can be turned on or off by selecting the check box in the Map Controls box.

...

The Operator Summary Downloads section is similar to Downloads on the PADMS Entry Page. However, the Operator Summary Downloads section only contains information pertaining to the specific operator selected.

...

Return to Table of Contents

Editing a Location

The Locatin Location Edit Tools are found at the end of each row. The edit tools do not appear if you are not the operator for these locations.

...

Operator Main Menu

From the PADMS Entry Page, select an operator to navigate to the Operator Summary Page.

...

Location Entry Page

From the PADMS Entry Page, select an operator to navigate to the Operator Summary Page. Then Select the name of a location in the Location Summary Table.

...

The BLM Comments section displays comments that only BLM managers may enter per location. These comments are used to provide more detailed information on the location. 

...

Anchor
AddNewLocation
AddNewLocation
Adding and Editing a Location

From the PADMS Entry Page select an operator from the Operators list, which will navigate to the Operator Summary Page.

...

  • Enter the name of the location and select the location type from the drop down menu
    • NOTE: if Mat Pad is checked, seeding date fields are not required in the qualitative reports. If Pre-Rod Pad and Federal Surface Site are both cheked checked as Yes then the disturbance and reclamation acreage are not counted in the operator summaries.
  • Select Create to save the location, or select Cancel to terminate the "add new location" process
    • NOTE: A location entered as a Reference Point will populate the Linked Reference Point field for the Frequency and Line-point Intercept data entry page

...

  • From the Operator Summary Page select Upload Spatial Reports. This link is used to batch upload spatial data, and detailed instructions for uploading a batch is in the Batch Uploads section.
  • Select a file to upload, and the system will "read" the data. If there are locations that do NOT exist in the application but are found in the uploaded file, the user will be able to create locations.

...

Editing a location is done from the Operator Summary Page. From the PADMS Entry Page, select an operator from the Operators list to navigate to the Operator Summary Page.

...

  • Qualitative Status Reports are NOT uploaded or used for Reference Points
  • Because Reference Location is a required field in the Frequency and Line-point Intercept status reports, a Reference Point must exist in the application before it can be entered into these data forms. If the Reference Point does not exist in the application, an error will be displayed to the user indicating the Reference Point doesn’t exist.
  • When using the batch upload feature to upload Frequency and Line-point Intercept data for a Reference Point, the user must enter the name of the Reference Point in both the Site Name and the Reference Location fields.
  • Reference Points have no spatial data associated with them. The user only needs to enter the latitude and longitude coordinates for the point.
  • Reference Points appear as orange circles on the map
  • Reference Points have an Ecological Site Description (ESD) associated with them. The ESD determines how many sample points must be taken in the Frequency data form for forbs and shrubs.

...

There are two places from which Spatial Reports can be accessed.

  • From the PADMS Entry Page the user selects an operator from the Operators list to navigate to the Operator Summary Page. Select the Date in any of the Status Reports fields for the particular location.
  • From the PADMS Entry Page, select an operator  to navigate to the Operator Summary Page. Select the name of the location to navigate to the Location Entry Page. Select Status Reports from the Navigation box on the left side of the screen.

...

Uploading an Individual Spatial Report

From the PADMS Entry Page, select and operator to navigate to the Operator Summary Page. Select the Name of a location in the Location Summary Table.

...

  • If spatial data hasn’t been entered for the location, the user can select the Add a Spatial Report link found in the right corner of the Location Entry Page.
  • Browse and select the zip file for upload
    • NOTE: once Sumbit Submit is selected it may takea  take a few moments for hte the application to upload the data and verify that it contains no errors
  • If there are multiple SHP files included in the zip file the user will need to select which SHP needs to be uploaded into the system
  • Once the file has been read into the application, the user must then enter a Collection Date and select whether a polygon represents a disturbance or reclamation. . If the new reclamation polygon is known to be smaller than the previous reclamation polygon, select Yes to the corresponding question to allow the polygon to be uploaded without issue.
  • Select Save, or select cancel to stop the process, or go back to the list of SHP files to pick a different one

...

Editing and Deleting an Individual Spatial Report

From the PADMS Entry Page, select an operator from the Operators list to navigate to the Operators list to navigate to the Operator Summary Page. The user can navigate to an individual spatial report for a specific location by one of two links.

...

Uploading, Editing, and Deleting Individual Photographs

From the PADMS Entry Page, select an operator from the Operators list to navigate to the Operator Summary Page. Select the name of the location to navigate to the Location Entry Page

Return to Table of Contents

Uploading

...

Photographs

From the Location Entry Page, the user can use three different links to upload individual photo collection.

...

Editing and Deleting Uploaded Photographs

Start from the PADMS Entry Page and select an operator from the Operators list to navigate to the Operator Summary Page. Select the name of the location to navigate to the Location Entry Page.

...

Uploading, Editing, and Deleting Individual Status Reports

From the PADMS Entry Page select an operator from the Operators list, which will navigate to the Operator Summary Page. Select the name of the location to navigate to the Location Entry Page. Select the Status Report link found in the Navigation box on the left side of the screen.

...

Status Reports

Please see the Data Dictionaries section of the manual which provides the definitions for each field contained within the data forms.

...

Entering, Editing, and Deleting Status Reports

From the PADMS Entry Page, select an operator from the Operators list to navigate to the Operator Summary Page. Select the name of a location to navigate to the Location Entry Page.

...

Editing and Deleting an Existing Status Report

From the PADMS Entry Page select an operator from the Operators list to navigate to the Operator Summary Page. Select the date in any of the  Status Reports fields for the particular location. Or, from the PADMS Entry Page select an operator from the Operators list to navigate to the Operator Summary Page. Select the Name of the location to navigate to the Location Entry Page. Then select Status Reports from the Navigation box on the left side of the screen. 

...

Return to Table of Contents

Anchor
PADMSbatches
PADMSbatches
Batch Uploads

From the PADMS Entry Page, select an operator from the Operators list to navigate to the Operator Summary Page.

...

Uploading Batch Photograph Files

Start from the PADMS Entry Page and selet select an operator from the Operators list to navigate to the Operator Summary Page.

...

Downloading Data Forms

Start at the PADMS Entry Page.

  • The user must be logged into the PADMS application
  • Select the Status Report Files (xls) found in the Reports, Downloads & Interactive Maps section under the Downloads heading
  • This link will direct the user to the PADMS Data Templates. The user can select the data form to download by clicking on the data form name

...

Return to Table of Contents

Frequency Batch Upload

Frequency File Naming Convention

It is recommended that each Frequency data form be named according to what has been entered into the Site Name field within the data form. E.g: The text in the Site Name field is ANT 2-6; name the frequency form ANT_2-6.xls

NOTE: Do NOT leave any spaces in the file name, use an underscore (_) for spaces in a name. There is no naming convention for the name of the zip file.

Return to Table of Contents

Uploading Batch Frequency Files

Start from the PADMS Entry Page and select an operator from the Operators list to navigate to the Operator Summary Page.

  • Select the Upload Status Reports link in the gray main menu at the top of the page
  • Use the Browse button to the right of the Frequency Status Reports (zip file) file upload box to search your computer for a zipped LPI file to upload
  • Select the Submit Frequency Reports button
  • Once the zip file has been successfully uploaded, the user will be brought back to the Upload Status Reports page and a blue box will appear indicating the upload was successful

Return to Table of Contents

Line-point Intercept Batch Upload

Line-point Intercept File Naming Convention

It is recommended that each Line-point Intercept data form be named according to what has been entered into the Site field within the data form. E.g: The text in the Site field is ANT 2-6; name the frequency form ANT_2-6.xls

NOTE: Do NOT leave any spaces in the file name, use an underscore ( _ ) for spaces in a name. There is no naming convention for the name of the zip file.

Return to Table of Contents

Uploading Batch Line-point Intercept Files

Start from the PADMS Entry Page and select an operator from the Operators list to navigate to the Operator Summary Page.

  • Select the Upload Status Reports link in the gray main menu at the top of the page
  • Use the Browse button to the right of the LPI Status Reports (zip file) file upload box to search your computer for a zipped Line-point Intercept file to upload
  • Select the Submit Intercept Reports button
  • Once the zip file has been successfully uploaded, the user will be brought back to the Upload Status Reports page and a blue box will appear indicating the upload was successful

Return to Table of Contents

Qualitative Batch Upload

Qualitative File Naming Convention

It is recommended that each Qualitative data form be named according to what has been entered into the Site Name field within the data form. E.G: The text in the Site Name field is ANT 2-6; name the frequency form ANT_2-6.xls

NOTE: Do NOT leave any spaces in the file name, use an underscore ( _ ) for spaces in a name. There is no naming convention for the name of the zip file.

Return to Table of Contents

Uploading Batch Qualitative Files

Start from the PADMS Entry Page and select an operator from the Operators list to navigate to the Operator Summary Page.

  • Select the Upload Status Reports link in the gray main menu at the top of the page
  • Use the Browse button to the right of the Qualitative Status Workbook file upload box to search your computer for an Excel Qualitative file to upload
  • Select the Submit Qualitative Reports button
  • Once the zip file has been successfully uploaded, the user will be brought back to the Upload Status Reports page and a blue box will appear indicating the upload was successful

Return to Table of Contents

Batch Upload Error Messages and Guidelines

Errors and Messages Encountered on he Frequency Form

All error messages will have the file name that the error is found in at the end of the message.

NOTE: If the location is a reference point, enter the reference point name in BOTH the Site and Reference Location field EXACTLY as it is entered into the application. Any data entered for the quadrats that come after column AY will be dropped from the batch upload and WILL NOT be entered into the application.

"Files must be a zip file"

  • Verify the file being uploaded is a zip file

“Site Name not found at row: <row #>”

  • Verify that there is data in the Site Name field in the data form
  • Verify that the Site Name exists in the Location Summary Table; if not use the Add New Location feature to add it
  • Verify that the Site Name is spelled exactly as it appears in the application
    • Make sure spaces are in the appropriate places
    • Make sure periods (.) are used when appropriate. E.g. If the correct name is ANT 2-6 then there MUST be a space between ANT and 2.

Edit the location name in the application by selecting the pencil icon located to the right, at the end of the row in the Location Summary Table. Make sure there isn’t a space at the end of the location name.

“Collection Date not found at row: <row #>”

Multiple Line-point Intercept status reports can be uploaded for the same location on the same date as long as the transect number is different. The definition of a duplicate Line-Point Intercept form is when the Site Name, Collection Date, and Transect # are the same between 2 or more status reports.

  • Verify that there are no duplicate Line-point Intercept forms within the zip file being uploaded
    • This error appears when the Site Name, Collection Date, and Transect # are the exact same for 2 or more forms.
      E.g. LPI1 and LPI2 both have the following data entered:
      Site Name = ANT-24
      Collection Date = 06/30/2011
      Transect # = N12
    • Because of this data being the same in two different files, a duplicate collection date error was displayed for the LPI2 file.
    • NOTE: If there are multiple forms within the same zip file that are duplicates, the batch upload feature will accept the first file it encounters and will display the duplicate collection date for all subsequent duplicate forms.
    • Verify that the Site Name, Collection Date, and Transect # are correct. If an error is found correct it. If no correction is necessary and the information in the 3 fields are correct then delete one of the duplicate forms
  • Verify that there are no other Line-Point Intercept status reports entered into the application for the location listed in the Site Name field of the form that also have the same data entered in the Site Name, Collection Date, and Transect # fields
    • When the duplicates are found in the application and in the zip file, the user must delete one the status report from the application or delete the form from the zip file

“Observer not found at row: <row #>”

  • Verify that there is data in the Observer field in the data form

“Transect Number not found at row: <row #>”

  • Verify that there is data in the Transect Number field in the data form

“Data Source not found at row: <row #>”

  • Verify that there is data in the Data Source field in the data form

“Recorder not found at row: <row #>”

  • Verify that there is data in the Recorder field in the data form

“Reference Location not found at row: <row #>”

  • Verify that there is data in the Reference Location field in the data form
  • Verify that the name entered in the Reference Location is spelled exactly as it appears in the application
    • Make sure spaces are in the appropriate places
    • Make sure periods (.) are used when appropriate. E.g. If the correct name is ANT 2-6 then there MUST be a space between ANT and 2.
  • Edit the location name in the application by selecting the pencil icon located to the right, at the end of the row in the Location Summary Table. Make sure there isn’t a space at the end of the location name.

“Operator not found at row: <row #>”

  • Verify that there is data in the Operator field in the data form
  • Verify that the name is spelled correctly in the Operator field in the data form

“Duplicate species found at row: <row #>”

  • Verify that there’s only one entry for a species in the data form

“Minimum number of quadrats not met or invalid data at row: <row #>”

The Frequency data form has sample sizes based on the type of Ecological Site Description that is associated with the Reference Location entered in the data form. Please see Reference Points for more information.

  • Verify that all necessary quadrats have data entered
  • Verify that the quadrats only contain a 1 or 0 (zero)

Return to Table of Contents

Errors and Messages Encountered on the Line-point Intercept Form

All error messages will have the file name that the error is found in at the end of the message.

NOTE: If the location is a reference point, enter the reference point name in BOTH the Site and Reference Location field EXACTLY as it is entered into the application.

“File must be a zip file”

  • Verify that the file being uploaded is a zip file

“Operator not found at row: <row #>”

  • Verify that there is data in the Operator field in the data form
  • Verify that the name is spelled correctly in the Operator field in the data form

“Observer not found at row: <row #>”

  • Verify that there is data in the Observer field in the data form

“Data Source not found at row: <row #>”

  • Verify that there is data in the Data Source field in the data form

“Site not found at row: <row #>”

  • Verify that there is data in the Site field in the data form
  • Verify that the Site exists in the Location Summary Table; if not use the Add New Location feature to add it
  • Verify that the Site is spelled exactly as it appears in the application
    • Make sure spaces are in the appropriate places
    • Make sure periods (.) are used when appropriate E.g. If the correct name is ANT 2-6 then there MUST be a space between ANT and 2.
    • Edit the location name in the application by selecting the pencil icon located to the right, at the end of the row in the Location Summary Table. Make sure there isn’t a space at the end of the location name.

“Transect Number not found at row: <row #>”

  • Verify that there is data in the Transect # field in the data form

“Recorder not found at row: <row #>”

  • Verify that there is data in the Recorder field in the data form

“Reference Location invalid at row: <row #>” or “Reference Location <reference location entered in the file> invalid at row: <row #>”

  • Verify that there is data in the Reference Location field in the data form
  • Verify that the name entered in the Reference Location is spelled exactly as it appears in the application
    • Make sure spaces are in the appropriate places
    • Make sure periods (.) are used when appropriate E.g. If the correct name is ANT 2-6 then there MUST be a space between ANT and 2.
    • Edit the location name in the application by selecting the pencil icon located to the right, at the end of the row in the Location Summary Table. Make sure there isn’t a space at the end of the location name.

“Direction invalid at row: <row #>”

  • Verify that there is data in the Direction field in the data form
  • Verify that the data entered in the Direction field is numeric between 0 – 359. NO alpha characters are accepted in this field

“Collection Date not found at row: <row #>”

  • Verify that there is a date entered in the Collection Date field in the data form

“Duplicate Collection Date <day, date, and time>”

Multiple Line-point Intercept status reports can be uploaded for the same location on the same date as long as the transect number is different. The definition of a duplicate Line-Point Intercept form is when the Site Name, Collection Date, and Transect # are the same between 2 or more status reports.

  • Verify that there are no duplicate Line-point Intercept forms within the zip file being uploaded.
    • This error appears when the Site Name, Collection Date, and Transect # are the exact same for 2 or more forms. E.g. LPI1 and LPI2 both have the following data entered:
      Site Name = ANT-24
      Collection Date = 06/30/2011
      Transect # = N12
    • Because of data being the same in two different files, a duplicate collection date error was displayed for the LPI2 file.
    • NOTE: If there are multiple forms within the same zip file that are duplicates, the batch upload feature will accept the first file it encounters and will display the duplicate collection date for all subsequent duplicate forms.
  • Verify that the Site Name, Collection Date, and Transect # are correct. If an error is found correct it. If no correction is necessary and the information in the 3 fields are correct then delete one of the duplicate forms.
  • Verify that there are no other Line-Point Intercept status reports entered into the application for the location listed in the Site Name field of the form that also have the same data entered in the Site Name, Collection Date, and Transect # fields.
  • When the duplicates are found in the application and in the zip file, the user must delete either the status report from the application or delete the form from the zip file.

“Invalid Species, duplicate species, or invalid Soil Surface found at row: <row #>”
There are many rules for entering data into the Top Canopy, Lower Canopy Layers, and Soil Surface fields. Please carefully read all bullet points to ensure the data is entered correctly.

  • Verify that the Top Canopy and Soil Surface fields have data entered.
  • Verify that all species codes are valid. Check the USGS Plant Database at http://plants.usda.gov/java
  • Verify that there are NO duplicate species found in the Top Canopy and Lower Canopy Layers fields
  • Verify that the codes L and WL are only found in the Lower Canopy Layers fields
  • Verify that the codes R, BR, LC, S, EL, and D are only found in the Soil Surface field
  • Verify that NONE is only found in the Top Canopy field
  • Verify that points 1 – 50 and 51 – 100 appear in rows 15 – 64. If they do not, the data form is corrupted and new form will need to be filled out and uploaded.

Errors and Messages Encountered on the Qualitative Form

“The qualitative spreadsheet you are trying to upload has the wrong number of columns (it should have 26).” 

  • Download a new Qualitative data form from the Entry Page, this ensures the data form is the most up-to-date version
  • Data should only go to column Z; verify there’s no data in columns AA and beyond

“An Excel file (with the extensions .xls or .xlsx) must be selected"

  • Verify that the file being uploaded is an .xls or .xlsx file

“Site <Site Name entered in the data form> is a Reference Point. Qualitative status is not allowed: <row #>”

  • Verify that the name entered in the Site Name field is NOT a reference point by looking up the name in the Location Summary Table
  • Check the Type field to make sure the location is NOT a reference point
    • If the location is a reference point, it must be deleted from the Qualitative data form.

“Missing Operator at row: <row #>”

  • Verify that there is data in the Operator field in the data form

“Location name not found at row: <row #>” 

  • Verify that there is data in the Site Name field in the data form
  • Verify that the Site Name exists in the Location Summary Table; if not use the Add New Location feature to add it
  • Verify that the Site Name is spelled exactly as it appears in the application
    • Make sure spaces are in the appropriate places
    • Make sure periods (.) are used when appropriate E.g. If the correct name is ANT 2-6 then there MUST be a space between ANT and 2.
  • Edit the location name in the application by selecting the pencil icon located to the right, at the end of the row in the Location Summary Table
  • Make sure there isn’t a space at the end of the location name

“Collection Date missing at row: <row #>” 

  • Verify that there is data in the Collection Date field in the data form

“Duplicate Collection Date at row: <row #>”

A Qualitative status report with the same date and transect number exists in the application for the specified location.

  • Check the specified location in the Location Summary Table to verify that the date listed under the Last Qual. column is NOT the same as what is entered in the file
    • E.g. When uploading a qualitative data form, a “Duplicate Collection Date at row: 46” is received. The location name in row 46 is CAB 35-1. Go to the application and look up CAB 35-1 in the Location Summary Table. Once this location is found, check the Last Qual. column and see if the date listed is the same as the date listed in row 46. If it is, either the status report in the application should be deleted or the row in the data form should be deleted.

“Data Source missing at row: <row #>” 

  • Verify that there is data in the Data Source field in the data form

“Topsoil Storage record not found at row: <row #>” 

  • Verify that there is data in the Topsoil Storage field in the data form

“Months of topsoil storage is max of 3 digits at row: <row #>”

  • The range for this field is 0 – 999
  • Verify that the number entered in the Months of Topsoil Storage is within range

“Months of topsoil storage is missing at row: <row #>” 

  • Verify that there is data in the Months of Topsoil Storage field in the data form

“Months of topsoil storage is invalid at row: <row #>” 

  • Verify that only numeric data is entered in the Months of Topsoil Storage field in the data form

“Seeding Method is invalid at row: <row #>”

  • Verify that there is data in the Seeding Method field in the data form

“If Seeding Method is Other, a Seeding Method Description must be entered at row: <row #>” 

  • Verify that Seeding Method (column H) contains “Other”
  • If this is true verify there is data in the Other Seeding Method field in the data form

“Date Seeded must be less than Collection Date at row: <row #>” 

  • Verify that the Collection Date field contains data
  • Verify that the date entered in the Date Seeded field is earlier / prior to the date entered in the Collection Date field in the data form

“Date Seeded not valid at row: <row #>” 

  • Verify that there is data in the Date Seeded field in the data form

“Seed Mix is invalid at row: <row #>” 

  • Verify that there is data in the Seed Mix field in the data form

“Soil Amendment missing at row: <row #>” 

  • Verify that there is data in the Soil Amendment field in the data form

“Amendment Date must be less than Collection Date at row: <row #>” 

  • Verify that the Collection Date field contains data
  • Verify that the date entered in the Date of Amendment Application field is earlier / prior to the date entered in the Collection Date field in the data form

“Soil Amendment Date invalid at row: <row #>” 

  • Verify that the Soil Amendment (column L) contains “Yes”
  • If this is true verify there is a date entered in the Date of Amendment Application field in the data form

“Missing Seed Germination Apparent data at row: <row #>” 

  • Verify that there is data in the Is seed germination apparent field in the data form

“Missing Area free of Undesirable Materials data at row: <row #>” 

  • Verify that there is data in the Is the area free of undesirable materials… field in the data form

“Invalid Soil Stable data at row: <row #>” 

  • Verify that there is data in the Is the soil stable with no indications of subsidence… field in the data form

“Missing noxious weed data at row: <row #>”

  • Verify that there is data in the Are noxious and undesirable weed absent field in the data form
  • Verify that the Are noxious and undesirable weed absent (column V) contains “No”
  • If this is true verify the comment field (column W) contains at least one species symbols /codes 

“Invalid Noxious Weeds List at row: <row #>” 

  • Verify that the data contained in column W is a species code
  • Verify that the data contained in column W are separated by commas (,) if there are multiple species codes entered

“Missing Reproductive Capability data at row: <row #>” 

  • Verify that there is data in the Is there evidence of good reproductive capability field in the data form

Return to Table of Contents

Anchor
PADMSDictionaries
PADMSDictionaries
Data Dictionaries

Quantitative Data Dictionary – Frequency

Site Name – The name of the well pad, road, pipeline, equipment area, etc.
Collection Date – The date the data was collected
Quadrat Size – The size (within a frame) of a quadrat used to gather data (Should be ½*1 meter, as of May 2011)
Observer – The individual who observers or ‘calls-out’ the data
Transect # – The number of a transect for a site (e.g., 1 of 1, 1 of 3, etc.)
Data Source – The company/entity who provides the data (e.g., name of a contractor business PAPO, etc.)
Recorder – The individual who records/writes the observed/called-out data
Reference Location – The name of the reference location associated with a site
Operator – The name of the operator
Plant Species Symbol – The USDA Plants Database symbol for each species that occurs on a location
Numbered Columns (e.g., 1, 2, 3, etc.) – The quadrat number along a transect. A ‘0’ or ‘1’ is entered to indicate if a species is absent, or present, respectively, within a quadrat.

Return to Table of Contents

Quantitative Data Dictionary – Line-point Intercept

Operator – The name of the operator
Observer – The individual who observers or ‘calls-out’ the data
Data Source – The company/entity who provides the data (e.g., name of a contractor business PAPO, etc.)
Site – The name of the well pad, road, pipeline, equipment area, etc.
Transect # – The number of a transect for a site (e.g., 1 of 1, 1 of 3, etc.)
Recorder – The individual who records/writes the observed/called-out data
Reference Location – The name of the reference location associated with a site
Direction – The direction of a transect (numeric value)
Collection Date – The date the data was collected
Top Canopy – The first species the pin flag intercepts, if none, record NONE*
Lower Canopy Layers (Code 1 – 3) – The 2nd, 3rd, and 4th species the pin flag intercepts, or herbaceous litter (L), woody litter (WL) (> 5 MM, ~ ¼” diameter).*
Soil Surface – The last item (e.g., species, duff [D], rock fragment [R], etc.) the pin flag intercepts on the ground

*If a species is intercepted in the top canopy and a lower canopy, it is ONLY recorded in the top canopy. Similarly, if a species is intercepted in more than one of the lower canopy levels (i.e., code 1 – 3), it is only recorded in the first Code where it intercepts. In other words, if a species is intercepted more than once in the top canopy, and any of the three lower canopy layers, it is recorded only in the first layer it intercepts.

Return to Table of Contents

Qualitative Data Dictionary

Operator – The name of the operator
Site Name – The name of the well pad, road, pipeline, equipment area, etc.
Collection Date – The date the data was collected
Observer – The individual who observers or ‘calls-out’ the data
Data Source – The company/entity who provides the data (e.g., name of a contractor business PAPO, etc.)
Topsoil Storage – Depth and/or method topsoil is stored (e.g., stockpile [> 3 feet], stockpile [< 3 feet], Direct Haul, etc.)
Months of Topsoil Storage – The number of months the topsoil was stored
Seeding Method – The method(s) used to seed a location. If more than one method report the other method(s) in the ‘Other Seeding Method’ column
Other Seeding Method – The method used if ‘Other’ is selected in the column ‘Seeding Method’
Date Seeded – The last date a location was seeded
Seed Mix – The name of the seed mix used to reseed a location (e.g., Loamy Soil, Temporary reclamation, etc.)
Soil Amendment – Any addition to surface soils (e.g., nutrients, organic matter, etc.) immediately before or after seeding, or during seeding
Date of Amendment Application – The last date a soil amendment was added to the soil of a location. If amendments were added to the soil of a location on more than one date, report the additional dates in the ‘Soil Amendment Comments’ column
Soil Amendment Comments – Additional comments relevant to soil amendments, such as additional dates amendments were added, observations (e.g., weather following application, success, concerns, etc.) associated with an application
Is seed germination apparent? Seeds have germinated, seedlings are emerging
Is the area free of undesirable materials? Examples: trash, construction material, etc.
Is the soil stable with no indications of subsidence, slumping and/or significant erosion? Rills > 2 inches, accelerated erosion is obvious, and soils are not being held by plants on site, sheet flow, head cutting in drainages, slopes occurring on or adjacent to reclaimed areas
Are noxious or undesirable weeds absent?

Noxious Weeds – Federal, state, and county listed noxious weeds (e.g., perennial pepperweed, Canada thistle, black henbane, etc.)
Undesirable Weeds – Weeds listed as noxious by adjacent counties, or other undesirable species (e.g., common mullein [Teton County], cheatgrass, halogeton, etc.)
Is there evidence of good reproductive capability? Seed production is evident for all life forms (i.e., grasses, shrubs, and forbs). Amount of tillers, rhizomes, flowers, and/or seed stalks are comparable to the reference site.

Return to Table of Contents

Examples of Completed Data Forms

Completed Frequency Data Form

Completed Frequency Data FormImage Added

Return to Table of Contents

Frequency Data Formats Accepted Per Field

Required Fields
Site Name: Alphanumeric
Transect Number: Alphanumeric
Reference Location: Alphanumeric
Collection Date: mm/dd/yyyy, will not accept any date prior to 01/01/1990
Data Source: Alphanumeric
Operator: Alphanumeric
Observer: Alphanumeric
Recorder: Alphanumeric
Plant Species Symbol: Alphanumeric, only species symbols accepted
Quadrats 1 – 50: Numeric range 0 – 1 0 = Absent 1 = Present

Optional Field
Comments: Alphanumeric

Return to Table of Contents

Completed Line-point Intercept Form

Completed Line-point Intercept FormImage Added

Return to Table of Contents

Line-point Intercept Data Formats Accepted Per Field

Required Fields
Operator: Alphanumeric
Observer: Alphanumeric
Data Source: Alphanumeric
Site: Alphanumeric
Transect #: Alphanumeric
Recorder: Alphanumeric
Reference Location: Alphanumeric
Direction: Numeric range 0 - 359
Collection Date: mm/dd/yyyy, will not accept any date prior to 01/01/1990
Top Canopy: Alphanumeric, only species codes and “NONE” accepted
Soil Surface: Alphanumeric, only species and soil surface codes accepted
Soil Surface Codes:

  • BR = Bedrock
  • D = Duff
  • EL = Embedded Litter
  • LC = Lichen
  • M = Moss
  • R = Rock Fragment
  • S = Soil

Optional Fields
Lower Canopy Layers (Code 1-3): Alphanumeric, only species and layer codes accepted
Layer Codes:

  • L = Herbaceous Litter
  • WL = Woody Litter

Notes: Alphanumeric

Return to Table of Contents

Completed Qualitative Data Form

Completed Qualitative Data FormImage Added

Close-up Columns A-JImage Added

Close-up Columns K-UImage Added

Close-up Colmns V-ZImage Added

Return to Table of Contents

Qualitative Data Formats Accepted Per Field

Required Fields:
Operator: Alpha drop down list
Drop down list:

  • Anschutz
  • Linn
  • QEP Energy Company
  • SWEPI LP
  • Ultra
  • USQE
  • Yates

Site Name: Alphanumeric
Collection Date: mm/dd/yyyy, will not accept any date prior to 01/01/1990
Data Source: Alphanumeric
Topsoil Storage: Alphanumeric drop down list
Drop down list:

  • Stockpile (> 3 ft)
  • Stockpile (< 3 ft)
  • Direct Haul
  • None

Months of Topsoil Storage: Numeric range 0 – 999
Seeding Method: Alpha drop down list
Drop down list:

  • Broadcast
  • Drill
  • Other

Other Seeding Method: Alphanumeric, only required when Other selected for Seeding Method
Date Seeded: mm/dd/yyyy, will not accept any date prior to 01/01/1990
Seed Mix: Alpha drop down list
Drop down list:

  • Cover Crops
  • Loamy Soil
  • Playas & Other Alkaline Areas
  • Sagebrush-dominated w/ Alkaline Soils
  • Sagebrush-dominated w/ Sandy Soils
  • Saltbush Communities
  • Temporary Reclamation
  • Other


Soil Amendment: Alpha drop down list
Drop down list:

  • Yes
  • No
  • Unknown

Date of Amendment Application: mm/dd/yyyy, will not accept any date prior to 01/01/1990 and is only required when Yes is selected for Soil Amendment
“Is seed germination apparent?”: Alpha – only “Yes” or “No” is accepted
“Is the soil stable…”: Alpha – only “Yes” or “No” is accepted
“Are noxious or undesirable…”: Alpha – only “Yes” or “No” is accepted
Comments: If above question is answered with No then comment is required. Only comma separated species symbols are accepted.
“Is there evidence of good…”: Alpha – only “Yes” or “No” is accepted

Optional Fields
Observer: Alphanumeric
Soil Amendment Comments: Alphanumeric
General Comment: Alphanumeric
The Comment fields for the following questions are optional:

  • Is seed germination apparent?
  • Is the area free of undesirable materials (trash, construction materials, liquids, etc.)?
  • Is the soil stable with no indications of subsidence, slumping and /or significant erosion?
  • Is there evidence of good reproductive capability?

Return to Table of Contents