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
  • White River Field Office Data Management system (WRDMS) Operator Manual
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Introduction

The White River Field Office Data Management System (WRDMS) is an application used by the White River Field Office and energy companies to track and document disturbance and reclamation activities associated with oil and gas operations in the Mesa Verde Play area by utilizing a buffering and the threshold concept. Operators have the ability to look at all data entered into the application but are only allowed to edit their own data. Agency managers have the ability to view as well as edit all data. The application allows querying of the data entered to provide useful information to all users.

When fully deployed, WRDMS information will be visible to the public through the web interface.

For Additional Help with WRDMS:

Email the WRDMS help desk at: Ryan Snyder rlsnyder@blm.gov

How to Log In To the System

Go to: https://my.usgs.gov/wrfo/

Log in with your username and password. If you do not already have a user account, select "Request New Account" and follow the steps provided. Ryan Snyder will be the USGS Sponsor for external user requests.

Change or Forgot Your Password

Please contact Ryan Snyder at  rlsnyder@blm.gov

USGS utilizes my.usgs.gov for centralized user management for all applications hosted on the USGS site. Therefore, usernames and passwords are managed by the USGS User Profile store at https://my.usgs.gov. As a result, users are forwarded to this system to enter their authentication credentials. The myUSGS site has a team who helps with password resets and access questions. The WRDMS Application allows myUSGS to determine if a user is authorized and authenticated and does not store any user profile information.

Disable the Security Information Pop-up

If you receive the following alert while using the application (only seen in Internet Explore),
select Yes.

Error Message using Explorer

Return to Table of Contents

WRDMS Entry Page

Navigate to the WRDMS Entry Page (https://my.usgs.gov/wrfo/).

This is the page users will employ to navigate to the individual operator pages and reporting component.

WRDMS Landing Page

Return to Table of Contents

Operators Section 1.

The Well Pad Operators section (1.) is in the lower right corner of the WRDMS Entry Page.

Because WRDMS has numerous operators, the Operators section provides a list of the five most used operators while allowing the ability to search for all operators in the application. Each name in the list is a link, and when selected, will navigate to that particular operator’s page. This is the link used when an operator would like to add or edit data.

If the operator name doesn’t appear in the operator list then a user can type the name of the operator into the Find box to select the correct operator and navigate to the operator page. E.g. If an Exxon / XTO user logs in and select “Exxon/XTO” from the operator list, this user will be able to edit data. IF an Exxon/XTO user logs in and selects “WR Delux Drilling” from the operator list, this user will only be able to view WR Delux Drilling's data.

Return to Table of Contents

Reports, Downloads, and Interactive Maps Section 2.

The Reports, Downloads, & Interactive Maps section (2.) is in the lower left corner of the WRDMS Entry Page.

Frequently Used Reports

There are two options for reports. 

All Data is a "canned" report where all the criteria is pre-selected. When the link is clicked, it displays all of the operators and the data they have entered. 

Ad-Hoc reports allows the user to select specific criteria to query in the application. Ad-hoc reports provide much more criteria to select and query from when designing a report. The query form looks like this:

Ad-hoc report query form

To generate an ad-hoc report:

  • Select  Ad-hoc link from the Frequently Used Reports section
  • Select specific criteria to refine the report results
    • Report Title field is used to name the report
    • Scope selects the specific operator and/or location type
    • Spatial Reports searches locations with specific spatial data, E.g. Search for locations only having disturbance with no reclamation
    • Status Reports searches locations with specific status report data, E.g. Search for locations with a specific status or has no qualitative data
    • Output modes chooses the outpuf of the report; default is on-screen list (HTML), but reports can also be sorted by using the Sort By and Ordered fields
    • Weed Status selects the type of weed querying, and the choices are Noxious and Undesirable.
    • Noxious or Undesirable Weed Species will display locations that have the specified weed species present
    • Seeding Method selects a specific seeding method
  • Select the Run Report button to produce the report, or select the Reset Form button to display the ad-hoc report selection page again

Return to Table of Contents

Report Main Menu

After a report runs, the main menu bar at the top of the page changes and allows the user more options. The options available in the Report Main Menu are listed below and follow the menu order from left to right.

  • Home directs the user back to the WRDMS Entry Page
  • Reporting directs the user to the Ad-Hoc selection page
  • Modify Search directs the user to the Ad-Hoc selection page
  • Map Report displays a map containing all the locations in the report’s results list
  • Acrobat Reader (PDF) outputs the displayed report in PDF format
  • Microsoft Excel (XLS) outputs the displayed report in Excel format
  • ESRI Shapefile (SHP) zips all of the spatial data for all locations listed in the report’s results list
  • Comma-separated (CSV) outputs the displayed report in a comma-separated file

Return to Table of Contents

WRDMS Map Section 3.

The WRDMS Map displays the Mesa Verde Play boundary, disturbance and reclamation areas, and buffered areas around disturbances.

By default all the layers are turned off; checking the box to the left of the layer name will allow the layer to display in the map. The user can also select a specific location type along with the spatial layer. Once all criteria have been selected, click the Refresh Map button to display the new criteria.

For more information on the location types, the user can click the “click for definitions” link.

The Print 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.

Map Controls

  • Zoom in/out by using the 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.

Return to Table of Contents

Lease Holder/Operator Unit Section 4.

The Lease Holder/Operator Unit section is in the middle column of the lower half of the WRDMS Entry Page.

Because WRDMS has numerous lease holders and operator units, the Lease Holder/Operator Unit section provides a list of the 5 most used lease holders/operator units while allowing the ability to search for all lease holders/operator units in the application. Each name in the list is a link, and when selected, will navigate to that particular lease holder’s page.

If the lease holder name doesn’t appear in the list then a user can type the name of the lease holder into the Find box to select the correct lease holder and navigate to the lease holder page. E.g. If an EXXON MOBIL CORP user logs in and selects “EXXON MOBIL CORP” from the lease holder/operator unit list, this user will be able to edit data. If an EXXON MOBIL CORP user logs in and selects “ANNE W PHILLIPS TR” from the operator list, this user will only be able to view ANNE W PHILLIPS TR’s data.

Return to Table of Contents

Mesa Verde Status Summary Section 5.

The Mesa Verde Status Summary is located in the top right corner of the WRDMS Entry Page.

The chart shows a summary of all developments in the Mesa Verde Area. It displays the different statuses each oil and gas feature can be in, the number of features currently in that status, and the total number of unreclaimed acres occupied by those features. The user can hover over each one of the statuses to get the description of that status.

Return to Table of Contents

Reclamation Status Summary Section 6.

The Reclamation Status Summary chart is below the Mes aVerde Status Summary section on the right side of the  WRDMS Entry Page. The chart displays the statuses of reclamation, the number of features that have initiated that status, the total number of acres initiated in that status, the number of features meeting required standards in that status, and the total number of acres that have met the required standards for that reclamation status. The user can hover the mouse over each of the statuses to get its description.

Return to Table of Contents

Lease Holder/Operator Unit

From the  the WRDMS Entry Page, select a lease holder from the Lease Holder/Operator Unit list, or search for a lease holder using the find box to navigate to the Lease/Unit Operator summary Page.

The Lease/Operator Summary Page displays uploaded data specific to the lease holder selected from the Lease Holder section on the Entry Page. This page provides a detailed view of the lease holder’s thresholds and status of uploaded locations.

Return to Table of Contents

Lease Holder/Operator Unit Map & Downloads Section 1.

The Lease / Operator Map functions the same as the map found on the WRDMS Entry Page; however, the spatial data displayed on the Lease / Operator Map is specific to the lease holder chosen from the the WRDMS Entry Page.

For more information on the location types, the user can select the click for definitions link in the Map Controls box.

The Downloads section contains data downloads or information specific to the selected lease holder.

Return to Table of Contents

Lease/Unit Summary Section 2.

The Lease/Unit Summary section in the top right corner of hte page exhibits a chart that quantifies the number of locations that have a specific status (e.g. Production) and cumulatively the amount of unreclaimed acres of those statuses.

For more information on each status, hovering the mouse over a status will display a pop-up box with a status definition.

Return to Table of Contents

Reclamation Status Summary Section 3.

The Reclamation Status Summary chart is located below the Lease/Unit Summary on the right side of the page. It displays the selected lease holder’s statuses of reclamation, the number of features that have initiated that status, the total number of acres initiated in that status, the number of features meeting required standards in that status, and the total number of acres that have met the required standards for that reclamation status. The user can hover over each of the statuses to get its description.

Return to Table of Contents

Threshold Tracking Section 4.

The Threshold Tracking table is located below the Lease/Operator Map on the left side of the page.

The WRDMS application utilizes the threshold and buffering concept to encourage operators to cluster drill as well as move the well to the production status quickly.

Return to Table of Contents

Buffering of Disturbance Polygons

When a disturbance polygon is uploaded into the application (uploads are covered in a different section), a “buffer” polygon is created. This buffer is 200 meters extending from the perimeter of the disturbance polygon. This 200 meter buffer is calculated for each disturbance polygon, regardless of disturbance type (well pad, facility, pipeline, etc.)

Example of Buffer

As part of the upload process, calculations are made to identify the “potential” buffered disturbance acres that may be added to the specific lease. These calculations are made for each range type (Summer Range, Winter Range, etc.). The calculations take into account overlap between buffer areas so that the same acreage is not counted multiple times. In GIS terms, the disturbance buffers are “dissolved” into one polygon per range type.

The message on the planning page indicates that the disturbances have the potential for adding “X” number of acres to the threshold limit. This indicates the maximum the disturbances would add to the limit; however, because the disturbance buffers are not added to the threshold limits until specific actions are taken (i.e. construction begins). It’s possible that a disturbance may be in a “planned” phase for a period of time and not contribute to the threshold limit.

Return to Table of Contents

Threshold Calculations

Threshold calculations are made for each leaseholder / range type combination. For each combination there is an acute disturbance calculation and a collective disturbance calculation. Depending on the status of the disturbance either the 200 meter buffer and corresponding area or the actual disturbance area is used in calculating the total disturbed area.

NOTE: If the disturbance is planned it is not included in the calculations.

The 200 meter buffer is used when the following conditions are met:

  • Pad status is: Construction, Drilling, Completion
  • Pad status is: Production and Interim Reclamation is not yet approved or the trips to the site is > 7 per week

These disturbance criteria above are what make up the Acute threshold disturbance limit.

The actual disturbance footprint is used when the following conditions are met:

  • Pad status is production
    •  Reclamation status is Interim or Final Reclamation approved by the BLM AND
    • Trips to the site is < 7 per week
  • Pad status is Abandoned

These disturbances are added to the Acute disturbance acres to form the Collective disturbance limit.

Return to Table of Contents

Current Threshold Calculations

Summer Range and Winter Range Acute disturbances:Max of 10% of the lease/range type area

Summer Range and Winder Range Collective disturbances:

Max of 20% of the lease/range type area

Severe Winter Range, Winter Concentration Areas, Severe Winter Range/Winter Concentration area Acute disturbances:Max of 5% of the lease/range type area
Severe Winter Range, Winter Concentration Areas, Severe Winter Range/Winter Concentration area Collective disturbances:Max of 10% of the lease range type area

Return to Table of Contents

Lease/Operator Location Summary Table Section 5.

The Lease/Operator Location Summary Table is located at the bottom of the page. It displays the most recent date the data was collected for each location of the specific lease holder. Locations can be filtered by selecting a specific location type, and options for location types are All, Well Pad, Road, Pipeline, Other, Facility, and Powerline.

The user can navigate to a specific location’s page by clicking on a location’s name. By clicking on a collection date, the user will be directed to the specific report. E.g. If the user selects the date in the “Last Spatial” column for pad101, the user will be directed to the
spatial report for that date and location.

Return to Table of Contents

Operator Summary Page

From the  WRDMS Entry Page, select an operator from the Operator List or search for an operator using the Find box. Either option will navigate to the Operator Summary Page.

The Operator Summary Page displays uploaded data specific to the operator selected. This page provides a more detailed view of the operator’s activities and status of uploaded locations.

Operator Summary Page elements

Return to Table of Contents

Operator Map Section 1.

The Operator Map functions the same as the map found on the WRDMS Entry Page; however, the spatial data displayed on the Operator Map is specific to the operator chosen.

For more information on the location types, the user can select the click for definitions link in the Map Controls box. As well, the user may turn on or off different map layer features from the Map Controls.

The Downloads section is below the Map Controls box, and contains downloads for information specific only to this operator.

Return to Table of Contents

Operator Summary Section 2.

The Operator Summary section is in the top right corner of the page and exhibits a chart that quantifies the number of locations that have a specific status (e.g. Production) and cumulatively the amount of un-reclaimed acres of these statuses.

Return to Table of Contents

Operator Location Summary Table Section 3.

The Location Summary Table displays the most recent date the data was collected for each location. The user can navigate to a specific location’s page by clicking on a location’s name. By clicking on a collection date, the user will be directed to the specific report.

E.g. If the user selects the date in the “Last Spatial” column for “AAAAA”, the user will be directed to the spatial report for that date and location.

The Listing drop down menu, located above the Location Summary Table, allows the user to specify the types of locations to view. If an operator has a large number of pads, selecting a specific type of location can significantly reduce the locations listed in the table and provide a more manageable list to view.

The location details may be edited by clicking on the pencil icon on the right end of the location row.

Location Summary table

Return to Table of Contents

Reclamation Status Summary Section 4.

The Reclamation Status Summary chart is located to the right of the map and below the Operator Summary box. It displays only the operator’s statuses of reclamation, the number of features that have initiated that status, the total number of acres initiated in that status, the number of features meeting required standards in that status, and the total number of acres that have met the required standards for that reclamation status. The user can hover the mouse over each of the statuses to get its description.

Return to Table of Contents

Operator Summary Main Menu

From the  WRDMS Entry Pageselect an operator from the Operators list or search for an operator using the Find box to navigate to the Operator Summary Page.

The main menu across the top of the Operator Summary Page contains all of the necessary links to navigate the site and perform data entry activities. From this menu the user can:

  • Navigate to the WRDMS Entry Page by selecting Home
  • Navigate to the reports page by selecting Reporting
  • Add a new location by selecting New Location
  • Batch upload spatial data by selecting Upload Spatial Reports
  • Batch upload photographs by selecting Upload Photographs
  • Batch upload qualitative and quantitative data by selecting Upload Status Reports
  • Search for a location using the Location Search box
    • As the user types, a list auto-populates of locations based on the first few letters entered
  • Add Modify Authorized User for "Operator Name" - Once a user has been added to myUSGS and has been added to the correct WRFO community role, their email address can then be entered on this page to allow edit access to the specified operator page.

Return to Table of Contents

Location Entry Page

From the  WRDMS Entry Pageselect an operator from the Operators list or search for an operator using the Find box to navigate to the Operator Summary Page. Then select the name of a location in the Location Summary Table.

The Location Entry Page is a detailed view of the activities for a specific location. This page displays the spatial, photographs, documents, qualitative and quantitative data that have been uploaded into the application.

This page allows the user to edit data already entered into the application one record at a time as opposed to a batch upload. This is advantageous in the event data was erroneously entered for one or two specific fields of a report. Instead of performing a batch upload to replace all data the user selects the location with the incorrect data and fixes the specific fields.

Location Entry Page

Return to Table of Contents

Navigation Section 1.

The Navigation box provides links to all the different activities performed on a pad and allows you to easily advance to the next or the previous location. The available links are:

  • Summary: directs the user to the Location Entry Page
  • Status Reports: Navigates to the page that houses uploaded quantitative and qualitative data.
  • Spatial Reports: Navigates to the page that houses uploaded spatial data.
  • Photographs: Directs to the page that houses uploaded pictures.
  • Downloads: ESRI Shapefile contains all spatial data ever uploaded for the specific location. Microsoft Excel contains all LPI and Belt Transect data uploaded for the location

Return to Table of Contents

Location Status Section 2.

On the Location Entry Page, the Location Status box displays the location type, range site, status, reclamation status, latest spatial report, the amount of disturbed acres, the amount of reclaimed acres, +/- 8 trips to the pad per week, and a link to the BMP (Best Management Practices) answers. The location name, type, and range site can be edited by using the Pencil icon found in the upper right corner of the box.

The Status, Reclamation Status, and number of trips to the pad per week can be edited by clicking on the linked status (e.g. "construction"). BPM Answers can be edited by clicking the Show/Edit BMP Answers link. The BMP answers must be complete before the location's status can be changed to "production".

Return to Table of Contents

Latest Belt Transect Section 3.

The Belft Transect area displays the most recent status report (Line-point Intercept, Qualitative) as well as the most recent belt transect that have been uploaded for a specific location. If there have been no status reports uploaded, the box for Status Reports will not be displayed and instead only the Belt Transect (Section 3) will display below the Location Status  (Section 2) box.

Return to Table of Contents

Location Map Section 4.

The map displayed on the Location Entry Page presents the spatial data that has been uploaded for the specified site. A legend is displayed to describe each graphic on the map.

Return to Table of Contents

Most Recent Documents Section 5.

The Most Recent Documents is located below the map, and this section displays the most current documents that have been uploaded to the location. Select the blue link to the right of the document title to view the document.

Return to Table of Contents

Most Recent Photographs Section 6.

The Most Recent Photographs area is located below the Most Recent Documents section, and it  displays the most current photo collection that has been uploaded for the location. Each picture has edit tools in the upper left corner. The pencil icon allows the individual picture to be edited, and the red x allows the individual picture to be deleted.

Return to Table of Contents

Pad History Section 7.

The box for the Pad History is located at the bottom of the Location Entry Page, below the Latest Belt Transect section. This is where events that happen to this location are recorded. The events include status change, new data uploads, etc...

Return to Table of Contents

Adding and Editing a Location

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page.

Adding a New Location

There are two different links that can be used to add a new location to the application.

Link 1

From the Operator Summary Page, select the New Location link in the main menu bar across the top of the page.

  • Enter the name of the location and select the location type and range site descriptions from the
    drop down menus
    • Note: it's recommended that the naming conventions are consistent for all locations

Adding new location information

  • Select Create to create and save the location, or select Cancel to terminate the process.

Return to Table of Contents

Link 2

From the Operator Summary Page, select the Upload Spatial Reports link. This link is used to upload spatial data (please see Batch Uploads section for detailed instructions). After selecting this link, a file can be chosen to upload.

  • Select a file to upload: 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 prompted to allow the application to automatically create
    locations

Add location through files

Return to Table of Contents

Editing a Location

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page. The location edit tool is the pencil icon found at the end of each row in the Location Summary Table on the Operator Summary Page. This tool is used to edit the name, location type, and range site description.

Note: only managers can delete spatial data.

Once the appropriate changes are made, the user can select the Save button to save the changes or select the Cancel button to stop the edit process and discard changes.

Return to Table of Contents

Changing the Ownership of a Pad

When a pad has changed ownership, the current operator of the pad needs to initiate the change. Below are the steps to follow to accomplish this.

  • On the Location Entry Page select the pencil icon in the upper right corner of the Location Status box
  • Check the Request Pad Ownership Transfer check box
  • Choose the new operator from the Change operator to drop down list
  • Click Save
  • Once Save is selected the following message will appear. From this screen, the user can select
    the Back to Operator button to return to the Operator Summary Page

transfer request message

Return to Table of Contents

Uploading Individual Spatial Reports

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page. Select the Date in the Last Spatial field for the particular location. Or, from the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page. Select the Name of the location to navigate to the Location Entry Page.Select Spatial Reports from the Navigation box on the left side of the screen.

Spatial Reports

All spatial reports that have been uploaded into the application will appear in the box with the heading Spatial Reports. The report that is highlighted in red will appear on the right side of the screen.

If a spatial report doesn’t yet exist for a location, in place of the Spatial Reports Box there will be text indicating no spatial reports exist and provides a link for the user to add one.

Spatial Reports Box

  • Green polygons represent reclamation acreage
  • Blue polygons represent disturbed acreage

Return to Table of Contents

Spatial Data Rules

Following is a list of rules for uploading spatial polygons into the application. These rules are also included in the Spatial Template found on the WRDMS Entry Page.

General Shapefile Construction

  • Shapefile submissions must be zipped (a .zip file) and contain valid DBF, SHP, SHX, and PRJ files
  • The PRJ file must contain legitimate projection information. The system will attempt to automatically transform the spatial data found in your shapefile to the system's internal projection, Web Mercator (EPSG:3857). This process may have varying degrees of accuracy and you should use the preview map to verify that the system has completed the transformation properly. To ensure maximum accuracy, use NAD-27, NAD-83, or WGS-84 for your projection's datum. Area calculations are determined by transforming to EPSG:26913 during the upload process.
  • Empty Spatial Templates are provided for WGS-84 Geographic, and NAD-83 UTM13N
  • Disturbances and reclaimed spatial submissions must consist of a single polygon or multipolygon feature
  • All polygons and multipolygons must conform to the OpenGIS Simple Features Specification for SQL
  •  The implications of this are:
    •  The shell and holes of all polygons cannot self-intersect.
    •  Holes can touch the shell or another hole at a single point only. This means that holes cannot intersect one another at multiple points or in a line segment
    • Polygon interiors must be connected (this is implied by the previous statement)
    • There is no requirement that a point where a hole touches the shell be a vertex
    • The element Polygons in a MultiPolygon may touch at only a finite number of points (e.g. they may not touch in a line segment)
    • The interiors of the element Polygons in a MultiPolygon must be disjoint (e.g. they may not cross).

Return to Table of Contents

Associating Shapefile Records with Distured Areas

  • The system will allow users to associate one and only one record in a shapefile to a disturbance. All disturbed areas associated with a pad must be dissolved into a multipolygon record before submission.
  • If an area consists of multiple polygons (pad, equipment area, road), then these polygons must be made into a single multipolygon feature in the shapefile that conforms to the geometry 41 White River Data Management System Operator’s Manual – Version 1.5.3 (05/26/15) standards outlined above. Generally, polygons (except for pipelines) are not allowed to intersect more than 5% of the disturbance surface area. NOTE: The intersection constraint is for pad disturbance and reclamation areas, the buffer area associated with a disturbance can overlap other features.
  • The disturbance feature must represent the total disturbance area of the pad/location, including any areas that have been reclaimed.
  • A collection date must be supplied with the disturbance multipolygon.
  • The disturbance area can not overlap any disturbance areas for other features.

Return to Table of Contents

Associating Shapefile Records with Reclaimed Areas

  • The reclamation feature for the pad/location must be a subset of the current disturbance feature. In other words, it must be completely contained by the disturbance feature.
  • The system will allow users to associate one and only one record in a shapefile to the reclamation area. All reclaimed areas associated with a disturbance must be dissolved into a multipolygon record before submission.
  • The reclamation feature must represent the total reclaimed area of the pad/location, including any areas that areas that have been reclaimed in different timeframes.

Return to Table of Contents

Multiple Pads in the Same Shapefile

NOTE: The shapefile can contain other fields but these will NOT be imported.

  • If a shapefile contains multiple pads, roads, pipelines, and other features, it can be batch uploaded as long as it follows these rules:
    • Features can be uploaded if they do not already exist in the system but only if this is specified during the upload. Otherwise, the feature name (pad name, road name, etc) must already exist in the system, and the shapefile's use of that name must be identical to the one the system stores
    • If the system has a pad named SHB 1-31, the shapefile must name that pad SHB 1-31. Names like "shb1-31", "shb/cor 1-31", and "shb1a-31b" do not match up and will be rejected.
  • The Shapefile Data Dictionary (the attributes in the dbf) must conform to the following:
    • Name (Character(254)) -- The name of the feature. If this is a Well Pad, this should be the Pad name. If this is a pipeline, this should represent the beginning and end point of the pipeline. This will be unique for an operator.
    • FeatType (Character(254)) -- This is the type of feature. Allowed Entries: Well Pad, Road, Pipeline, Other.
    • CollDate (Date or Character(254)) -- Date the data was collected; this should represent the date of the observation, not processing. Format = MM/DD/YYYY.
    • DistType (Character(20)) -- Allowed Entries: disturbance or reclamation

Return to Table of Contents

Uploading Spatial Data

Spatial reports can be entered individually using two different methods.

Method 1

  • If spatial data has not 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

Add a Spatial Report link location

  • Select the Browse button and select the zip file for upload
    • NOTE: Once Submit is selected it may take a few moments for 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 by selecting the radio button next to the file name
  • Once the file has been read into the application, the shapefile is displayed on the left with the attribute data displayed on the right. The user can review the spatial and attribute data to ensure it is correct.
  • Select Save. The user can also cancel the spatial upload or go back to the list of SHP files to pick a different file.
  • Once the upload is complete a blue message will appear on the following screen indicating if the
    upload was successful

Return to Table of Contents

Method 2

From the Location Entry Page, select the Add Spatial Report link from the main menu bar across the top of the page, and follow the steps found in Method 1 above, starting at the second bullet point.

Return to Table of Contents

Uploading, Editing and Deleting Individual Photographs

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page. Select the Name of the location to navigate the Location Entry Page.

Uploading Photographs

There are three places from the Location Entry Page that the user can use to upload individual photo collections.

Places to upload individual photos

Link 1 and 2

Links 1 and 2 will take the user to the Add Photograph page for the specific location. Link 3 has an interim page that will be illustrated later.

Required Photo Fields

  • Enter the required data into the Add Photograph form
    • NOTE: Collection Date, Direction and Image are required. Accepted image formats are JPG, GIF, and PNG.
  • Use the Browse button to search your computer for a photo to upload
  • Select Save to complete the Add Photograph process or select Cancel to stop the process
  • Once the photo is uploaded, the user will be returned to the Location Entry Page. If the
    uploaded photo is the most recent it will appear in the Most Recent Photographs area on the
    Location Entry Page

If more photos need uploaded, select the blue Add Photograph link in the upper right corner of the
Most Recent Photographs section of the page.

By selecting the Photographs link on the Location Entry Page, the user can view all the photo records that have been uploaded for the location.

Photos are grouped in 30 day intervals by Collection Date. The most recent photo record is highlighted
red in the Photograph Groups section of the page, and the photos are also displayed on the right. The user can select
the Magnifying Glass icon next to other records to view the photos in the Selected Photographs area.

Return to Table of Contents

Link 3

If the location has no photos, selecting link 3 (highlighted above) will bring the user to the following page:

Link to uploading individual photos opt 3

Once the user selects the blue add one text, the page will direct to the Add Photograph Page. Follow the steps listed under Link 1 and 2 above.

Return to Table of Contents

Editing and Deleting Uploaded Photographs

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page. Select the Name of the location to navigate the Location Entry Page.

The most current photos can be edited and deleted from the Location Entry Page. To edit or delete older photos, the user must select the Photographs link from the Navigation box located on the left side of the page.

Return to Table of Contents

Edit and Delete Most Recent Photographs

From the Location Entry Page, use the icons found in the upper left corner of each photo to edit or delete the photo.

  • Use the X icon to delete the selected photo
  • Use the Pencil icon to edit the photo information including direction, collection date, etc.

Return to Table of Contents

Edit and Delete Photographs

To edit any photo regardless of the collection date, select the Photographs link from the Navigation Box located on the left side of the Location Entry Page.

Photos are grouped into collections based on the collections date entered and edit tools can be found in the upper left corner of each photo. If more photos need to be added, the blue Add Photograph link is found in the upper right corner of the Selected Photograph box.

Editing photo properties

To edit photos one at a time:

  • Select the Pencil icon in the upper left corner of the photo
  • The edit screen will appear
  • All fields can be changed except for Location.
  • Select Update to save the changes, or select Cancel to terminate the edit process

To delete photos one at a time:

  • Select the red X icon found in the left corner of each photo
  • Once selected, the user will be asked to verify if they want to delete the selected photo
  • Select Yes to complete the delete process, or No to cancel the delete process

Return to Table of Contents

Uploading, Editing and Deleting Individual Status Reports

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page. Select the Name of the location to navigate the Location Entry Page. Select the Status Report link found in the Navigation box on the left side of the screen.

Return to Table of Contents

Status Reports

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

From the Location Entry Page, the Status Reports link is found in the Navigation box on the left side of the screen. This link directs the user to the page that houses all of the status reports that have been uploaded into the system.

There are two different Status Reports a user must enter for each location

  • Line-point Intercept (LPI)
  • Belt Transect

Return to Table of Contents

Status Reports Box

All status reports that have been uploaded into the application will appear in the box with the heading Status Reports. The report that is highlighted in red will appear on the right side of the screen.

If a status report doesn't yet exist for a location, in place of the Status Reports box will be a text indicating no status reports exist. A link is provided for the user to add a status report.

Return to Table of Contents

Status Report Edit Tools

Edit tools are found in the top right corner of the selected status report.

  • The magnifying glass allows the user to view a different status report
  • The X will delete a status report
  • The pencil icon allows the user to edit a status report
  • The lock indictes a manager, such as a user with the BLM, has entered the status report. These reports are not editable by operators

Return to Table of Contents

Editing and Deleting Status Reports

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page. Select the Name of the location to navigate the Location Entry Page.

Data Entry Error Message

If any required fields are left blank or the wrong data format is entered, a red error box will appear indicating the errors that have been encountered with the submission of a Status Report.

Data Entry Error Message

Return to Table of Contents

Editing an Existing Line-point Intercept Report

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 Top Canopy and Soil Surface fields have data entered
  • Verify that all species codes are valid. Check the USDA Plant Database at: http://plants.usds.gov/java
  • Verify there are NO duplicate species found in the Top Canopy and Lower Canopy Layers fields
  • Verify the codes L and WL are only found in the Lower Canopy Layers fields
  • Verify the codes R, BR, LC, S, M, EL, and D are only found in the Soil Surface field
  • Verify NONE is only found in the Top Canopy field
    • To add more than one LPI Report to a location the Transect Number must be different for each report.
      E.g. Location CAB-31 can have multiple LPI Reports if there are no duplicate Collection Dates. If there are multiple LPI Reports with the same Collection Date then the Transect Numbers must be different.

Keeping the above rules in mind, these are the steps for editing and deleting status reports.

  1. Use the pencil icon to add/edit species that have been encountered along the transect. In all of the species selection pop up boxes, the user can either select the species by activating the drop down menu using the down arrow to the right of the field or start typing in the species name. The species list will auto-populate based on what the user types in this field.
    1. Top Canopy – this field must be filled out with either a species code or the word “NONE”. Selecting the pencil icon in the top canopy filed will activate the Upper Canopy Selection pop up box. The user can select a species from the drop down menu or select the NONE button to fill in the top canopy field.
    2. Lower Canopy Layers – up to 3 species codes can be entered for this layer. Duplicate species codes amongst the Lower Canopy Layers and the Top Canopy is NOT allowed: each column must contain a unique entry. Selecting the pencil icon in the lower canopy fields will activate the Lower Canopy Selection pop up box. The user can select from the Species field or the Layer field. If a species is selected from the Species field, the user must select the Add Species button to add the species to the form. The Layer field contains codes specific to the Lower Canopy Layers fields. If a code is selected from this field, the user must select the Add Layer button to add the code to the form.
    3. Soil Surface – this field can contain a species code or a code specific to the soil surface. A species code entered in the Top Canopy or the Lower Canopy Layers fields are allowed to be entered in the Soil Surface field. In this case duplicate species codes are permitted. Selecting the pencil icon in the Soil Surface fields will activate the Soil Surface Selection pop up box. The user can select from the Species field or the Soil Surface field. If a species is selected from the Species field, the user must select the Add Species button to add the species to the form. The Soil Surface field contains codes specific to the Soil Surface field. If a code is selected from this field, the user must select the Add Soil Surface button to add the code to the form.
  2. After all data has been entered, select the Save button to save the data or select Cancel button to stop the process. NOTE: ALL 150 points must contain data or an error indicating "the  highlighted fields need to be corrected" will occur. When data is missing from a point, the field will be outlined in red.

Return to Table of Contents

Deleting an Existing Status Report

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page. Select the Date in the Status Report column in the Location Summary Table for any location.

OR

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page. Select the Name of the location to navigate the Location Entry Page. Select Status Reports from the Navigation box on the left side of the screen.

To edit or delete an existing Status Report, the user can use the edit tools found to the right at the end
of each row. Each row contains its own status report, and it does not need to be highlighted in red in order to edit.

  • Select the magnifying glass  to view a different status report
  • Select the red "X" to delete a status report, which will generate a confirmation page to delete the specified record
    • Select Yes to confirm deletion, or select No to cancel the delete process
  • Select the pencil icon to edit a status report
    • After making the necessary edits, select Save to keep the changes, or Cancel to undo the changes
  • The lock indicates a manager, such as a user with the BLM, has entered the status report. The reports cannot be edited by operators.

Return to Table of Contents

Batch Uploads

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page.

Spatial Data Batch Uploads

The following is a list of rules to know in order to upload spatial polygons into the application. These rules are also included in the Spatial Template found on the WRDMS Entry Page.

General Shapefile Construction

  • Shapefile submissions must be zipped (a .zip file) and contain valid DBF, SHP, SHX, and PRJ files
  • The PRJ file must contain legitimate projection information. The system will attempt to automatically transform the spatial data found in your shapefile to the system's internal projection, Web Mercator (EPSG:3857). This process may have varying degrees of accuracy and you should use the preview map to verify that the system has completed the transformation properly. To ensure maximum accuracy, use NAD-27, NAD-83, or WGS-84 for your projection's datum. Area calculations are determined by transforming to EPSG:26913 during the upload process.
  • Empty Spatial Templates are provided for WGS-84 Geographic, and NAD-83 UTM13N.
  • Disturbances and reclaimed spatial submissions must consist of a single polygon or multipolygon feature
  • All polygons and multipolygons must conform to the OpenGIS Simple Features Specification for SQL, and the implications of this are:
    • The shell and holes of all polygons cannot self-intersect
    • Holes can touch the shell or another hole at a single point only. This means that holes cannot intersect one another at multiple points or in a line segment
    • Polygon interiors must be connected (this is implied by the previous statement)
    • There is no requirement that a point where a hole touches the shell be a vertex
    • The element Polygons in a MultiPolygon may touch at only a finite number of points (e.g. they may not touch in a line segment)
    • The interiors of the element Polygons in a MultiPolygon must be disjoint (e.g. they may not
      cross)

Return to Table of Contents

Associating Shapefile Records with Disturbed Areas

  • The system will allow users to associate one and only one record in a shapefile to a disturbance. All disturbed areas associated with a pad must be dissolved into a multipolygon record before submission
  • If an area consists of multiple polygons (pad, equipment area, road), then these polygons must be made into a single multipolygon feature in the shapefile that conforms to the geometry standards outlined above. Generally, polygons (except for pipelines) are not allowed to intersect more than 5% of the disturbance surface area. NOTE: The intersection constraint is for pad disturbance and reclamation areas, the buffer area associated with a disturbance can overlap other features
  • The disturbance feature must represent the total disturbance area of the pad/location, including any areas that have been reclaimed
  • A collection date must be supplied with the disturbance multipolygon
  • The disturbance area cannot overlap any disturbance areas for other features.

Return to Table of Contents

Associating Shapefile Records with Reclaimed Areas

  • The reclamation feature for the pad/location must be a subset of the current disturbance feature. In other words, it must be completely contained by the disturbance feature
  • The system will allow users to associate one and only one record in a shapefile to the reclamation area. All reclaimed areas associated with a disturbance must be dissolved into a multipolygon record before submission
  • The reclamation feature must represent the total reclaimed area of the pad/location, including any areas that areas that have been reclaimed in different timeframes

Return to Table of Contents

Multiple Pads in the Same Shapefile

If a shapefile contains multiple pads, roads, pipelines, and other features, it can be batch uploaded as long as it follows these rules:

  • Features can be uploaded if they do not already exist in the system but only if this is specified during the upload. Otherwise, the feature name (pad name, road name, etc) must already exist in the system, and the shapefile's use of that name must be identical to the one the system stores
  • If the system has a pad named SHB 1-31, the shapefile must name that pad SHB 1-31. Names like "shb1-31", "shb/cor 1-31", and "shb1a-31b" do not match up and will be rejected

The Shapefile Data Dictionary (the attributes in the dbf) must conform to the following:

  • Name (Character(254)) -- The name of the feature. If this is a Well Pad, this should be the Pad name. If this is a pipeline, this should represent the beginning and end point of the pipeline. This will be unique for an operator
  • FeatType (Character(254)) -- This is the type of feature. Allowed Entries: Well Pad, Road, Pipeline, Other
  • CollDate (Date or Character(254)) -- Date the data was collected; this should represent the date of the observation, not processing. Format = MM/DD/YYYY
  • DistType (Character(20)) -- Allowed Entries: disturbance or reclamation

NOTE: The shapefile can contain other fields but these will NOT be imported.

Return to Table of Contents

Uploading Batch Spatial Files

  • Select the Upload Spatial Reports link in the main menu across the top of the page
  • Use the Browse button to search your computer for a zipped spatial file to upload


  • Select the Submit button after the zip file has been selected
  • Select the SHP file to upload (if necessary) and select the Submit button
    • NOTE:  the zip file can contain multiple SHP files, if it does, one must be selected
  • The following page will display the locations that are contained within the selected SHP. The Status column found at the beginning of the table indicates whether errors or warnings associated with the location exist. If there are no errors the status is displayed as OK. If the location doesn’t yet exist in the application, select Yes to the Add locations if they don’t
    already exist question found at the top of the screen. This will create the new location and upload the corresponding shapefile(s).
    • E.g. If Demo Pad doesn’t exist, by selecting Yes, the process will create a location named Demo
      Pad. The following graphic is an explanation of the error status. 
    • NOTE: Yes is selected for the Add locations if they don’t already exist. This has changed
      the status of the entries to Error and OK respectively.

  • Only records in a shapefile that have a status of Warning or OK will be uploaded when the Save button is selected. Once all locations have the appropriate statuses, select the Save button.
  • After the upload has completed successfully, the user will be brought to the Operator Summary Page. Above the map will be a blue box indicating the upload was successful.

Return to Table of Contents

Photograph Batch Uploads

Naming Conventions

Ensure the photos are named as <location name>_<direction as N, S, E, W, Close-up>

  • Directions choices are: N = North, S = South, E = East, W = West, O = Other, Close-up
  • Example: North facing picture of CAN 1-25 would be named CAN_1-25_N
    • NOTE: do NOT leave any spaces in the photograph name, use an underscore for spaces in the name.
    • There is no naming convention for the name of the zip file

Return to Table of Contents

Uploading Batch Photograph Files

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page.

  • Select the Upload Photographs link in the main menu at the top of the page
  • Use the Browse button to search your computer for a zipped photo file to upload
  • Select the Submit button
  • A dialog box will appear with a list of photos that are contained in the zip file. If there are any errors found with a photo, it will be indicated in the Status column
    • NOTE: the collection date is required. Image formats accepted include JPG, GIF, PNG
    • If there are any photos with errors, only the cancel button is displayed at the bottom of the page. All errors must be fixed before an upload can successfully complete
  • Once all photos have a status of ok, select the save button to save the photos, or cancel to terminate the process without saving the photos
  • The user will be brought to the Operator Summary Page after the photos have uploaded successfully. A blue box will appear above the map indicating the upload was successful.

Return to Table of Contents

Downloading Data Forms

Start on the  WRDMS Entry Page.

  • Log into the WRDMS application
  • Select the Belt Transect or LPI Template found in the Reports, Downloads & Interactive Maps section under the Downloads  heading in the lower left section of the page
  • Selecting these links allows the forms to be saved. Once the name of the data form has been selected, a gray pop up box appears that allows either saving or opening the file.

Return to Table of Contents

Line-point Intercept Batch Upload

Line-point Intercept File Naming Convention

Each Line-point Intercept (LPI) data form needs to 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 LPI form ANT_2-6.xls

NOTE: Do NOT leave any spaces in the file name; use an underscore (_) for spaces in the name.

There is no naming convention for zip files.

Return to Table of Contents

Uploading Batch Line-point Intercept Files

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page.

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

Return to Table of Contents

Belt Transect Batch Upload

Belt Transect File Naming Convention

Each Belt Transect data form should be named according to what has been entered into the location field within the data form. E.g. The text in the location field is ANT 2-6; name for the Belt Transect form ANT_2-6.xls

NOTE: Do NOT leave any spaces in the file name; use and underscore (_) for spaces in the name.

There is no naming convention for the zip file.

Return to Table of Contents

 Uploading Belt Transect Files

From the  WRDMS Entry Pageselect an operator from the Operators list, or search for an operator using the Find box to navigate to the Operator Summary Page.

  • Select the Upload Status Reports link in the main menu at the top of the page
  • Use the Browse button to the right of the Belt Transect Reports (zip file) file upload box to search your computer for a zipped Belt Transect file to upload
  • Select Submit Belt Transect Reports button
  • When the zip file is successfully finished uploading, you will be brought back to the Upload Status Reports page and a blue box will indicate the upload was successful

Return to Table of Contents

Batch Error Messages and Guidelines

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

Errors and Messages Encountered on the Line-point Intercept Batch Upload

"Files 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
  • Verify there are no extra spaces before, after or in the middle of the name

"Observer not found at row: <row #>"

  • Verify that there is data is the Observer 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 the Site name is spelled exactly as it appears in the application
  • Make sure that spaces are in the appropriate places
  • Make sure periods (.) are used when appropriate
  • 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

"Direction invalid at row: <row #>"

  • Verify that there's data in the Direction field in the data form
  • Verify that the data entered in the Direction field is numeric between 0 and 359. NO alpa 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 stats reports can be uploaded for the same location on the same date as long as the transect numbers are different. The definition of a duplicate line-point intercept form is when the Site Name, Collection Date, and Transect # are the same between two or more status reports.

  • Verify there are no duplicate LPI forms within the zip file being uploaded
    • E.g. LPI1 and LPI2 both have the following data entered: site name = ANT-24, collection date = 06/30/2011, transect # = N12
    • NOTE: if there are multiple forms within the same zip file that 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 the Site Name, Collection Date, and Transect # are correct. If an error is found then correct it. If no correction is necessary and the information in the 3 fields are correct then delete one of the duplicate forms
  • Verify there are no other LPI 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 duplicates are found in the application and the zip file, you 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. Carefully read all the 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 USDA Plant Database at https://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, M, 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 – 75 and 76 – 150 appear in rows 15 – 89. If they do not, the data form is corrupted and a new form will need to be downloaded, filled out, and uploaded

Return to Table of Contents

Errors and Messages Encountered on the Belt Transect Batch Upload

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

"File must be a zip file"

  • Verify that the file being uploaded is a zip file

"Observer of Recorder not found at row <row #>"

  • Verify that there’s data in the Observer and Recorder data fields on the data form

"Location 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

"Transect Number or Transect Direction not Found at Row: <row #>"

  • Verify that there is data in the L – P Transect Number field in the data form
  • Verify that there is data in the Transect Direction field in the data form

"Valid Date not Found at Row: <row #>"

  • Verify that there is a date entered in the Date 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

"Duplicate Collection Date <day, date and time>"

Multiple belt transect status reports can be uploaded for the same location on the same date as long as the transect numbers are different. The definition of a duplicate belt transect form is when the Location, Date, and L – P transect number are the same between 2 or more belt transect status reports.

  • Verify that there are no duplicate LPI forms within the zip file being uploaded
    • E.g. BeltTransect1 and BeltTransect2 both have the following data entered:
      Location = ANT-24
      Date = 06/30/2011
      L – P Transect Number = N12
    • 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 date error for all subsequent duplicate forms
  • Verify that the Location, Date, and L – P Transect Number 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 belt transect status reports entered into the application for the location listed in the Location field of the form that also have the same data entered in the Location, Date, and L – P Transect Number 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 <species code> found at row: <row #>"

Return to Table of Contents

Data Dictionaries

Line-Point Intercept Data Dictionary

Operator –  The name of the operator
Observer – The individual who observes or “calls out” the data
Data Source – The company who provides the data (e.g. name of a contractor, business, 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
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 is encountered, 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), etc. (>5 MM, ~1/4” diameter)*

*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 of intercept.

Return to Table of Contents

Belt Transect Data Dictionary

Observer – The individual who observes or “calls out” the data
Location – The name of the well pad, road, pipeline, equipment area, etc.
L - P Transect Number – The line-point intercept transect number for a site (e.g. 1 of 1, 1 of 3, etc.)
Recorder – The individual who records / writes the observed/ called out data
Operator – The name of the operator
Transect Direction – The direction of a transect (numeric value)
Date – The date the data was collected
Species Code – The code of the species encountered
Individual Tally – Individual tick marks for every time the same species is encountered
Individual Count – The sum of the individual tally marks as a numeric value

Return to Table of Contents

Examples: Completed Data Forms

Completed Line-Point Intercept Form

Completed Line-point intercept form

Completed Line-point Intercept Form part 2

Return to Table of Contents

Line-point Intercept Data Formats Accepter per Field

Required Fields:

Operator: Alphanumeric

Observer: Alphanumeric

Site: Alphanumeric

Transect #: Alphanumeric

Recorder: Alphanumeric

Direction: Numeric range 0 – 359

Collection Date: mm/dd/yyy, 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
    • EL = Embedded Litter
    • LC = Biological Crust
    • D = Duff
    • M = Moss
    • R = Rock Fragment
    • S = Soil

Optional Fields:

Data Source: Alphanumeric

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 Belt Transect Data Form


Completed Belt Transect Form

Return to Table of Contents

Belt Transect Data Formats Accepter per Field

Required Fields

Observer: Alphanumeric

Location: Alphanumeric

L – P Transect Number: Alphanumeric

Recorder: Alphanumeric

Operator: Alphanumeric

Transect Direction: Numeric range 0 - 359

Date: mm/dd/yyyy, will not accept any date prior to 01/01/1990

Optional Fields

Species Code: Alphanumeric, only species codes accepted

Individual Tally: Alphanumeric

Individual Count: Numeric

Return to Table of Contents


  • No labels