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.

...

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)

...

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 onbeyond

“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 o
    • 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 . column is not 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
    90 Pinedale Anticline Data Management System Operators Manual – Version 3.2.3 (09/29/2014)

“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. 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