Exhibit 3c NISIMS_25_User_Guide.pdf

NISIMS 2.5 USER GUIDE

INSTRUCTIONAL GUIDANCE FOR THE NATIONAL INVASIVE SPECIES

INFORMATION MANAGEMENT SYSTEM (NISIMS) WORKFLOW

SECOND EDITION

Updated: 2/21/2017

TABLE OF CONTENTS

Introduction

How to Use this Guide

Different Audiences

Navigating the Guide

Supplemental Resources

Background

What is NISIMS?

Why is NISIMS Important?

How does NISIMS Affect Me?

Workflow Overview

National SDE

State SDE Replicas

Local Geodatabases

Check-outs

Setup

Desktop

System Requirements

Setting Up ArcGIS

Mobile Devices

OS and Hardware Requirements

Software Requirements

Adding Data to NISIMS Lookup Tables

NISIMS LU Tables

Outbound Data Steps

SDE Default Replica to Local GDB

NISIMS GDB Concepts

How to Create a NISIMS GDB

Custom Lookup Table Lists

Custom Lookup Table Concepts

How to Create Custom Lookup Table Lists

Check-outs

Important Check-out Concepts

Mobile Device Check-outs

Desktop Check-outs

Data Collection

Business Rules and Tips

All Layers

Infestations

Treatments

Survey Polygons and Survey lines

Photo Points

Initial Steps

Opening ArcPad

Activating the GPS Receiver

Collecting Features

Choosing Basic Parameters

Capturing Features

Filling out Attributes

Closing ArcPad

Additional Tools

Copy Geometry

Inbound Data Steps

Checking Data into Parent GDB

From Mobile Device

From Desktop to GDB

NISIMS Geoprocessing (GP)

When to Perform NISIMS GP

Initiating NISIMS GP Manually

Upload to SDE

Summary

Additional Web Resources

Introduction >> How to Use this Guide 1

INTRODUCTION

HOW TO USE THIS GUIDE

Before you jump into this user manual, read some tips below on how to use it.

DIFFERENT AUDIENCES

NISIMS is a complex system whose user base grows every year, as does the diversity of its user roles and backgrounds.

VARYING ROLES

The NISIMS workflow involves a variety of users- field data collectors, crew leads, GIS specialists, SDE administrators, and there often exists an overlap of roles. Therefore, depending on your responsibilities, certain parts of this guide may not be relevant to you.

As a very general guideline that does not factor in overlap of NISIMS roles (i.e. someone who collects data and also transfers it into the database), here is the breakdown of sections based on user relevance:

All new users should read the background and workflow overview to get an understanding of the system.

Field-only users will be concerned with setting up mobile devices if you are responsible for configuring your own device, and data collection.

GIS users can first focus on desktop setup, followed by outbound and inbound data steps.

VARYING ACCESS LEVELS

NISIMS users now include both BLM and non-BLM parties. While we kept this guide as generic as possible, certain steps in the workflow may only be possible and applicable to BLM users due to network access constraints.

These BLM-only sections are denoted by a green BLM logo:

NAVIGATING THE GUIDE

This user guide is organized into a very logical, hierarchical outline, and visualizing its structure can be beneficial to understanding primary concepts and how they are related.

VIEWING THE OUTLINE IN A PDF

If you viewing this document as a PDF in Adobe Reader, you may turn on the outline via View > Show/Hide > Navigation

Panes > Bookmarks:

Introduction >> How to Use this Guide 2

This should cause the outline to appear in the Bookmarks pane on the left side of the screen, and you may click the + signs to expand each section:

VIEWING THE OUTLINE IN AN MS WORD DOCUMENT

If you are reading this guide in Microsoft Word, click the View tab on the ribbon and make sure Navigation Pane is checked:

Introduction >> Supplemental Resources 3

This will display the Navigation Pane in the left-hand panel, where you may click to expand a section:

SUPPLEMENTAL RESOURCES

In addition to this guide, there are a couple of websites with an abundance of NISIMS instructional materials:

BLM users may visit the NISIMS SharePoint site at http://teamspace/projects/nisims.

Non-BLM users may visit the public NISIMS homepage at http://www.blm.gov/wo/st/en/prog/more/weeds/nisims.html.

BACKGROUND

Before you begin learning how to use NISIMS, take a minute to read what it’s all about.

WHAT IS NISIMS?

The National Invasive Species Information Management System (NISIMS) is a standardized, spatially-enabled BLM database containing location, treatment, and monitoring data relevant to invasive species. Currently the system pertains to invasive plants, but future versions will incorporate additional taxa including birds, fish, and algae.

NISIMS is the first BLM system with tools to collect field data and seamlessly integrate it into a centralized geospatial database. A primary benefit of this is facilitated data sharing and reporting at regional, state and national levels.

The structure of NISIMS is based on the BLM’s Enterprise Geographic Information System (EGIS) architecture and

Geospatial Services Strategic Plan, which the BLM approved nationally in 2003 and 2008, respectively.

http://teamspace/projects/nisims http://www.blm.gov/wo/st/en/prog/more/weeds/nisims.html

Introduction >> Workflow Overview 4

WHY IS NISIMS IMPORTANT?

Invasive species create a huge variety of environmental and economic problems. Consider this excerpt from the FWS website (http://www.fws.gov/invasives/faq.html#q2):

The introduction of invasive species can have a dramatic effect on our natural resources, human health, and economy.

When non-native species are introduced into an ecosystem in which they did not evolve their populations sometimes explode in numbers. The reason for this is that in a natural or native community, species evolve together into an ecosystem with many checks and balances that limit the population growth of any one species. These checks and balances include such things as: predators, herbivores, diseases, parasites, other organisms competing for the same resources and limiting environmental factors. These checks and balances form the complex web of life that makes up an ecosystem and in which a native species competes for survival. However, when an organism is introduced into an ecosystem in which it did not evolve naturally, it no longer has those limits and its numbers can sometimes dramatically increase. The unnaturally large population numbers can then have severe impacts.

NISIMS has been established to map and document such impacts, and to ultimately use this data to create and implement strategic plans and budgets for mitigating them.

HOW DOES NISIMS AFFECT ME?

As a member of a national effort against invasive species, it is your responsibility to map and document infestations and treatments. NISIMS will reduce redundant data entry and make data collection and reporting of invasive species more efficient. It is designed to collect infestation and treatment data in a standardized format. This will enable better reporting, more accurate data and better representation of the efforts being made against invasive species by the Bureau.

WORKFLOW OVERVIEW

Although NISIMS is a complex system, its general workflow can be understood by describing its four primary types of data storage:

1. National SDE

2. State SDE replicas

3. Local file geodatabases (GDBs)

4. Mobile check-outs

NATIONAL SDE

Housed at the BLM National Operations Center, the national SDE (Spatial Database Engine) is an enterprise database containing the master set of NISIMS data and lookup tables (i.e. plant species, herbicides), which are updated weekly. Most users never access the national SDE directly except in a read-only capacity when viewing data and generating reports via the NISIMS web portal.

http://www.fws.gov/invasives/faq.html#q2

Introduction >> Workflow Overview 5

STATE SDE REPLICAS

State SDE replicas are essentially subsets of the national SDE but are hosted by and contain data specific to each state (or group of states, such as Montana and the Dakotas). To maintain currency, a weekly automated two-way synchronization occurs between replicas and the national SDE. Therefore, data added to replicas is pushed into the national SDE, and changes made to national lookup tables are pushed to state replicas.

Most users may view but not modify a replica’s master version (referred to as Default), but can create edit versions that allow for input or modification of records safely outside Default. Once changes to an edit version are finalized, state SDE administrators will post and reconcile them with Default.

In addition to editing purposes, replicas serve as the source and destination of local geodatabases, discussed next.

LOCAL GEODATABASES

Local file geodatabases (GDBs) are smaller, user-generated spatial databases derived from their replica’s Default version at a state-level extent in ArcMap. Their main NISIMS role is middleman between field data and state SDE replicas but, unlike

SDE, may be used offline. GDBs are both the source of mobile check-outs used in data collection and the destination of this data when it is “checked in”. Once a reasonable amount of data has been added (generally monthly) and geoprocessing is complete, the GDB is uploaded into an SDE edit version and then posted to Default by an administrator.

CHECK-OUTS

Derived from GDBs in ArcMap at a project-level extent, check-outs are the most common storage container for new NISIMS data. Once data collection in a check-out is complete, the data is checked back into its parent GDB and the check-out itself is deleted in order to prevent accidental subsequent check-in of the same data.

COLLECTION METHODS IN CHECK-OUTS

Data within a check-out may be generated several ways:

GPS data collection is the most common method, whereby users map new data in the field using handheld GPS devices equipped with ArcPad software and custom tools to streamline a variety of tasks.

On-screen digitizing involves tapping (or clicking, in ArcPad Desktop) to create new features. Although only practical in conjunction with a background reference layer, digitizing is often useful for creating NISIMS data obtained from non-NISIMS sources such as contractors, partners, or legacy records.

Coordinate entry is based on manually entering known x/y coordinates of point features. As with digitizing, this method is only practical for reasonable amounts of data.

DATA FROM NON-NISIMS SOURCES

For legacy data (older data relevant to but not in the exact format as NISIMS) or contractor/partner data, data creation steps vary by scenario. For a larger number of records, the process may incorporate a custom method in ArcMap, or digitizing within a check-out in ArcPad Desktop for a small number of records. Note that the latter is generally the preferred

Setup >> Desktop 6 method of migrating data into NISIMS since custom ArcPad forms perform automated tasks that would otherwise be manual (i.e. creating unique IDs for new features).

For those migrating non-NISIMS data into the system, work with a BLM GIS specialist for assistance. Data dictionaries and object model diagrams of the NISIMS database are very useful for this process and can be found at http://www.blm.gov/wo/st/en/prog/more/weeds/nisims.html. Additionally, short videos describing the general approach to this task can be found on the NISIMS Vimeo channel at http://vimeo.com/channels/nisims.

SETUP

If your role in NISIMS involves any desktop tasks, there are several hardware and software items that may be required before using the system. Additional help can be found on the NISIMS public website at http://www.blm.gov/wo/st/en/prog/more/weeds/nisims/What_Contractors_and_Partners_Need_and_How_to_Get_it.ht ml

DESKTOP

If you are strictly a field user and someone else is configuring your desktop computer for you, skip to mobile device setup.

For those installing software onto mobile devices and/or performing GIS tasks, read the relevant sections below.

SYSTEM REQUIREMENTS

Depending on your role in NISIMS, certain software may be required for device connectivity and GIS tasks.

WINDOWS MOBILE DEVICE CENTER

If you are responsible for setting up mobile devices, then your PC must have Windows Mobile Device Center (WMDC). This software enables communication between your mobile device and PC, which allows applications to be installed on the device via your computer. BLM users requiring this software must submit a Help Desk ticket if it is not presently installed.

ARCGIS

If you are involved in GIS tasks such as creating check-outs or editing geodatabases, read the applicable requirements below. For BLM Citrix users, some or all of these may already be available to you (if not, submit a Help Desk ticket). BLM local users require administrative privileges to install software on a PC, so you must submit a Help Desk ticket as well.

ALL GIS USERS

Adobe Acrobat Reader to view PDF reports

Citrix ICA Client 12.1 if using ArcGIS in Citrix. It is important that the version is 12.1 since this ensures proper connectivity with mobile devices.

http://www.blm.gov/wo/st/en/prog/more/weeds/nisims.html http://vimeo.com/channels/nisims http://www.blm.gov/wo/st/en/prog/more/weeds/nisims/What_Contractors_and_Partners_Need_and_How_to_Get_it.html http://www.blm.gov/wo/st/en/prog/more/weeds/nisims/What_Contractors_and_Partners_Need_and_How_to_Get_it.html

Setup >> Desktop 7

ARCGIS 10.1 AND 10.2 USERS

ArcGIS Desktop 10.1 SP1 or 10.2 SP1 to perform GIS tasks.

S1 ArcPad Data Manager 4.01.07 to streamline GIS data management tasks. Download (all users):

http://www.blm.gov/pgdata/etc/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.94530.File.da t/S1_ESRI_Desktop_Applications_4_03_04_ArcGIS.zip

ArcPad 10 SP1 Desktop Extension to allow data to be prepared for ArcPad. BLM users may download here:

http://teamspace/projects/nisims/HelpInstall/ArcPadSetup_1001.zip.

Python Report Lab 2.6 for Python 2.7 to ensure functionality of custom tools (PRL is auto-installed with S1 Data

Manager 3.0+). BLM users may download here: http://teamspace/projects/nisims/HelpInstall/reportlab-2.6.win32-py2.7.zip.

SETTING UP ARCGIS

For those NOT performing ArcMap tasks, skip to mobile device setup. For everyone else, read the relevant sections below and note that each step is required one time only as the settings will be retained by ArcGIS.

CONNECT TO NISIMS SDE

For those working with NISIMS SDE to create or upload GDBs or edit SDE data, you must first establish a connection with your state’s SDE replica. Since most contractors and partners lack access to the BLM network, this section will not likely apply to you.

How you create your NISIMS database connection will depend on which state you operate in since each state manages its own user edit accounts. This connection will be stored in your user profile and made available each time you open ArcGIS.

To request a database edit account for your state, please contact:

California: Gary Walter

Idaho: Jon Norred

Montana: Michelle Johnson

New Mexico: Al Sandoval

Oregon: Jay Stevens

Utah: Marcel Martinez

NHS (NOC Hosted States): John Reitsma

Once you receive your database connection properties, refer to the document relevant to your state below:

California: http://teamspace/projects/nisims/Help/Creating_DB_Connection_CA.docx

Idaho: http://teamspace/projects/nisims/Help/Creating_DB_Connection_ID.docx

Montana: http://teamspace/projects/nisims/Help/Creating_DB_Connection_MT.docx

New Mexico: http://teamspace/projects/nisims/Help/Creating_DB_Connection_NM.docx

Oregon: http://teamspace/projects/nisims/Help/Creating_DB_Connection_ORWA.docx

Utah: http://teamspace/projects/nisims/Help/Creating_DB_Connection_Utah.docx

NHS: http://teamspace/projects/nisims/Help/Creating_DB_Connection_NOC_hosted_State.docx http://www.blm.gov/pgdata/etc/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.94530.File.dat/S1_ESRI_Desktop_Applications_4_03_04_ArcGIS.zip http://www.blm.gov/pgdata/etc/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.94530.File.dat/S1_ESRI_Desktop_Applications_4_03_04_ArcGIS.zip http://teamspace/projects/nisims/HelpInstall/ArcPadSetup_1001.zip http://teamspace/projects/nisims/HelpInstall/reportlab-2.6.win32-py2.7.zip http://teamspace/projects/nisims/HelpInstall/reportlab-2.6.win32-py2.7.zip http://teamspace/projects/nisims/Help/Creating_DB_Connection_CA.docx http://teamspace/projects/nisims/Help/Creating_DB_Connection_ID.docx http://teamspace/projects/nisims/Help/Creating_DB_Connection_MT.docx http://teamspace/projects/nisims/Help/Creating_DB_Connection_NM.docx http://teamspace/projects/nisims/Help/Creating_DB_Connection_ORWA.docx http://teamspace/projects/nisims/Help/Creating_DB_Connection_Utah.docx http://teamspace/projects/nisims/Help/Creating_DB_Connection_NOC_hosted_State.docx

Setup >> Desktop 8

VERIFY EXTENSIONS

Extensions are add-ons that enable additional functionality in a program, two of which are required in ArcMap when using

NISIMS. Follow these steps to enable the extensions:

1. Launch ArcMap. Exact steps vary, but for BLM personnel it is often through Citrix, while non-BLM users with local

ArcGIS licenses (aka on your computer) will likely click Start > All Programs > ArcGIS > ArcMap <your version #>.

2. Once ArcMap starts, the “Getting Started” dialog appears. Normally you may want to open an existing map, but since this is our first time and we want to start with a blank map, click Cancel:

3. You should now be looking at a blank map in ArcMap. To view a list of currently available extensions, click the

Customize menu, then Extensions:

Setup >> Desktop 9

4. The only extension we need is ArcPad Data Manager, so make sure the box is checked.

5. Close the Extensions dialog.

ENABLE S1 DATA MANAGER TOOLBAR

Many NISIMS GIS tasks require the S1 ArcPad Data Manager Toolbar (S1APDM), which is a custom set of SDE/GDB/mobile data management tools developed by Service 1 st to simplify integration between databases and field data.

To see a list of all available toolbars, click the Customize menu, then Toolbars. Scroll down to S1 ArcPad Data Manager

Version <your version #> and make sure there is a checkmark to its left. If not, check it now:

SET WORKING DIRECTORY

Your S1 Working Directory is an intermediate storage location for data check-outs which, as with all other steps in this

“Setting Up ArcGIS” section, needs only to be set once. To do so:

1. Click the Set Working Directory on the S1APDM toolbar:

Setup >> Mobile Devices 10

2. The “Set S1 ArcPad Data Manager Preferences” dialog appears, but its options vary by user:

BLM users’ working directory is on a server whose path depends on state and field office, so choose the appropriate options.

Since non-BLM users lack access to the BLM network, you must set your working directory by clicking Browse and then navigating to a desired local folder. Coordinate with your BLM point of contact for assistance with this step if needed.

3. Click OK to save the changes.

MOBILE DEVICES

Although NISIMS field collection devices vary, they share some common requirements and basic setup steps.

OS AND HARDWARE REQUIREMENTS

Most mobile devices purchased within the last few years will meet the minimum operating system (OS) and hardware requirements, but it is important to verify them on your device before proceeding.

OPERATING SYSTEM

To collect NISIMS field data, you must use a mobile device with an operating system (OS) supported by ArcPad:

Windows Mobile is the most common OS since it ships with the most popular devices, made by Trimble. Supported versions include version 5 and above.

Windows 7 and 8 are also supported and are generally found in tablets, but laptops can be used as well if they are paired with a USB or Bluetooth GPS device.

MEMORY CARD

Memory/storage cards (usually SD or Micro SD, depending on device) are a required item serving several purposes:

Additional storage: most modern cards have considerable storage capacity and, since NISIMS check-outs require minimal space, you should have plenty of room left for reference data and other projects.

Portability: the portable nature of storage cards facilitates transfer between individuals. For example, a field collector lacking GIS access can simply have a GIS user create a check-out for them on a storage card.

Desktop integration: storage cards are essential to the data check-in process in that they are visible in any desktop environment (unlike devices using WMDC with Citrix) when used in conjunction with the USB Toggle (see below for details).

Setup >> Adding Data to NISIMS Lookup Tables 11

INTEGRATED GPS

To collect GPS data in a disconnected environment, your mobile device must be equipped with integrated GPS. This means that it does not rely on cellular signals or Wi-fi to locate your position. Any device designed specifically for GPS data collection (i.e. Trimble devices) will automatically have integrated GPS, but multi-purpose devices such as tablets often do not. So, do a little research before purchasing a tablet to use in the field!

SOFTWARE REQUIREMENTS

Several pieces of software are required in order to collect NISIMS data:

ArcPad 10 SP1: a lightweight ArcGIS for the field. You will likely use ArcPad for all data collection as it is designed to integrate seamlessly NISIMS.

S1 ArcPad Toolbar v3.80 or later: set of tools that simplify ArcPad tasks. Not just for NISIMS, this toolbar was designed by Service 1 st to streamline many steps involved in feature creation, selection, and navigation.

S1 USB Toggle: a means to switch between WMDC and USB Mass Storage Mode. By default, your device connects to PCs through WMDC and its entire hard drive is visible to the PC. The USB Toggle, however, allows just your storage card to be visible and therefore becomes accessible in any desktop environment (including Citrix). Detailed information and usage instructions can be found here:

http://www.blm.gov/pgdata/etc/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.38104.File.da t/S1%20USB%20Toggle_Public.pdf

To simplify installation of these items, use the S1 Mobile Installer. This custom Service 1 st package automatically deploys and configures the necessary software onto mobile devices. You may download the installer here:

http://www.blm.gov/pgdata/etc/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.39304.File.dat/S1_ESR

I_Mobile_Applications_3_80_12.zip

Detailed written instructions on the installer can be found at:

http://www.blm.gov/pgdata/etc/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.63021.File.dat/S1_Arc

Pad_Mobile_Installer_3_8-HowTo.pdf

For supplemental assistance, watch the setup videos on the NISIMS Vimeo channel:

Part 1: http://vimeo.com/channels/nisims/62401975

Part 2: http://vimeo.com/channels/nisims/62403071

ADDING DATA TO NISIMS LOOKUP TABLES

Before you begin collecting data in the field, you will need to ensure that your specific project names, Pesticide Use

Proposal numbers (PUPs), Biological Control Agent Release Proposal numbers (BCARPs), and person/organization information are in the NISIMS database. By adding this information prior to collecting data in the field, this will ensure that the specific data you need will be available to you in the customized lookup tables that are used when collecting data.

Contractors or partners lacking BLM network access will need someone to perform this step for them.

http://www.blm.gov/pgdata/etc/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.38104.File.dat/S1%20USB%20Toggle_Public.pdf http://www.blm.gov/pgdata/etc/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.38104.File.dat/S1%20USB%20Toggle_Public.pdf http://www.blm.gov/pgdata/etc/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.63021.File.dat/S1_ArcPad_Mobile_Installer_3_8-HowTo.pdf http://www.blm.gov/pgdata/etc/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.63021.File.dat/S1_ArcPad_Mobile_Installer_3_8-HowTo.pdf http://vimeo.com/channels/nisims/62401975 http://vimeo.com/channels/nisims/62403071

Setup >> Adding Data to NISIMS Lookup Tables 12

NISIMS LU TABLES

To request an update to the NISIMS database tables, BLM employees will need to navigate to the NISIMS SharePoint Site.

Click on the DB Table Updates icon.

Scroll to the bottom of the page and click on the Add Document button. A new form will open up in Microsoft InfoPath.

Select the appropriate Requesting Office and choose the Request Type. The information on the bottom portion of the form will change based on the Request Type selected. After filling out the required fields in the form, click on Submit Request.

http://teamspace/projects/nisims/Pages/Home.aspx

Outbound Data Steps >> SDE Default Replica to Local GDB 13

Requests are updated every Friday afternoon to the National NISIMS Database. Individual states should see the changes reflected in their states Database the following Monday. Be sure to plan ahead and submit the information on the

SharePoint site prior to creating your local GDB.

Note: The DB Table Updates form does not allow requests for chemical components, adjuvants, or species. To request additions of such items, BLM personnel must contact their state weed lead directly.

OUTBOUND DATA STEPS

To get from SDE to a local geodatabase (GDB) and eventually to mobile devices, NISIMS data goes through several stages. If you need a recap on the different stages, refer to the Workflow Overview.

SDE DEFAULT REPLICA TO LOCAL GDB

Before you can start creating mobile check-outs, you first need a GDB to work with. Contractors or partners lacking BLM network access will need someone to perform this step for them.

NISIMS GDB CONCEPTS

KEY NISIMS GDB CHARACTERISTICS

Below are a handful of important characteristics relevant to NISIMS geodatabases.

Schema only: For the most part, a NISIMS GDB is just an empty schema of its parent SDE. That is, although there is no editable data in a new GDB, its structural properties such as field names, data types, and domains match those of the SDE database from which it originated.

Repeated use: Once a GDB is created, you can continue to use it to make check-outs. There are two scenarios, however, when you might want to create new GDBs. If either of them apply to you and you do end up creating a new

GDB, it may be wise to check all your data into your existing GDB and upload it to SDE before using the new GDB so that you are only dealing with one GDB.

o SDE lookup table updates- changes to the master lookup tables in SDE do not get pushed down to local GDBs dynamically, so the only way to have the most current lookup tables is to create a new GDB. For example, if you request via SharePoint to have a new project name added to the master tables, you would need to create a fresh GDB once your request has been processed. Otherwise the new project name will not be an option to include in pick-lists.

o Viewing infestation from others’ GDBs- if you need to view new infestation records collected in a different GDB by others in your field office or district, you will need to create a new GDB to see their additions (providing they have been uploaded into SDE already). The reason for this is again due to the fact that changes made in SDE are not automatically pushed down to existing GDBs. So, if your co-worker uploads their GDB into SDE, their newest infestations will not appear in your WeedInfestationReference layer unless you create a fresh GDB.

State extent: GDBs are created at the geographic extent of your state. Whatever reference data falls in that extent when creating the GDB in ArcMap will end up in your GDB. Even if you are only collecting data in a small area, it is

Outbound Data Steps >> SDE Default Replica to Local GDB 14 still highly recommended that the GDB be created at your state’s extent because some of the reference layers such as county and field office are used for performing automatic attribute calculations in a future geoprocessing step.

Sharing GDBs: Depending on your role in NISIMS, you may be responsible for generating GDBs for others. If this is the case, it is important to define and understand what types of GDB sharing are acceptable:

o Multiple users sharing a single GDB, such as one stored in a shared network directory, is acceptable.

o Making copies of a GDB, such as to give to a contractor who lacks network access required to make their own, is NOT acceptable. The reason is because if data is collected in two or more identical GDBs, there will be conflicts during upload to SDE since records from each GDB are viewed as the same data and there is no way to resolve the differences. To avoid this when handing over a GDB on a USB drive, simply cut the GDB (instead of copying it). That way there will only be one unique copy of that GDB in existence and therefore no potential for conflicts during upload to SDE.

WHAT’S IN A NISIMS GDB?

At first glance when you create a new GDB, the number of items that appear in ArcMap’s table of contents may seem overwhelming and confusing. Fortunately they can be broken down into a few groups.

NISIMS GDB FEATURE CLASSES

A feature class is a container for spatial data. Feature classes in a NISIMS GDB can be broken down into several categories.

REFERENCE FEATURE DATASET

In GIS, a feature dataset is a container for feature classes. In the case of NISIMS, the only feature dataset is called Reference and contains feature classes used as background reference and for automated calculation purposes. They are maintained by other data stewards and are therefore not something you will edit. Note that they are not automatically updated in your

GDB, only in SDE, so your GDB’s reference layers are only guaranteed to be current at the time of download from SDE.

Outbound Data Steps >> SDE Default Replica to Local GDB 15

WEED INFESTATION REFERENCE

Another reference layer in its own right, albeit outside the feature dataset and not derived from SDE, WeedInfestationReference is a read-only feature class containing all weed infestations present in your map extent when a

GDB is created. This layer is a simplified version of the primary infestation feature class, WeedInfestationLocation, and is included as a shapefile in check-outs in order to provide basic information about infestations collected in the past.

FEATURE CLASSES ENDING IN ‘PT’, ‘LN’, OR ‘PG’

Layers ending in one of these two-letter suffixes serve as intermediate, temporary storage containers between check-outs and the GDB feature classes in which data is more permanently stored. When you first check your data back into a GDB, this is where it ends up.

As far as naming conventions go, their names should look familiar to data collectors as they match those of the layers in an

ArcPad check-out.

In terms of data editing, it is recommended that, when possible, post-field editing is performed on these layers in ArcMap instead of on the permanent feature classes. Reason being, the data in these intermediate layers is still in its original geometry as the features have not yet been buffered into polygons by the NISIMS geoprocessing (GP) step.

Also note that after GP has been performed, the data in these intermediate layers is automatically deleted, so don’t panic if you see it missing! Instead, look for it in the permanent feature classes.

Outbound Data Steps >> SDE Default Replica to Local GDB 16

FEATURE CLASSES ENDING IN ‘LOCATION’

These are the more permanent layers mentioned above. Their names are derived from the SDE feature classes from which they originated, and they contain only polygons (except for PhotoLocation, which always retains its point geometry). These layers are the destination of your new data once NISIMS GP has been run, after which they may be uploaded directly into an SDE version. If you perform any edits on these feature classes, you may need to run NISIMS GP again before uploading.

NISIMS GDB TABLES

In addition to feature classes, a NISIMS GDB also contains a variety of tables which can be grouped in several categories.

LOOKUP TABLES

Tables whose names begin with LU are lookup tables that store the comprehensive set of values used to create your custom pick-lists as well as a variety of other attributes you will not see in the field. These read-only tables originate from those in SDE and, just like the reference layers in the feature dataset are not dynamically kept current in your GDB. Should you require a more current set of lookup tables (such as when a request to include a new project name has been processed), you must create a new GDB from SDE.

Outbound Data Steps >> SDE Default Replica to Local GDB 17

TEMPORARY DESTINATIONS OF TABLE DATA

Tables ending in PT, LN, and PG are tabular counterparts to the feature classes with corresponding names and, as with the feature classes, will automatically be removed of their records after NISIMS GP is run.

These tables contain fields that correspond to those of their respective external data collection forms (the ones with colored backgrounds, except for photo points), plus some auto-generated ID fields. If edits must be made to values filled out in the external forms during data collection, this must be done in these tables prior to NISIMS GP since the records will be deleted after this step, as mentioned above.

PERMANENT DESTINATIONS OF TABLE DATA

Tables in the screenshot above are essentially the permanent destination of all tables mentioned in the previous section, plus some additional fields not found on data collection forms. These tables are populated during NISIMS GP and have corresponding equivalents in SDE.

ALL OTHER TABLES

The remaining tables are beyond the scope of this guide, but more information can be found online:

The data dictionary is a spreadsheet providing detailed information about all fields in NISIMS feature classes and tables. All users may download it here:

http://www.blm.gov/style/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.2099.File.dat/NISIM

S_25_Data Dictionary.pdf

The entity relationship diagram describes how NISIMS feature classes and tables are related to each other. It can be downloaded here:

Outbound Data Steps >> SDE Default Replica to Local GDB 18 http://www.blm.gov/style/medialib/blm/wo/Planning_and_Renewable_Resources/nisims.Par.63905.File.dat/NISI

MS_25_Entity_Rel_Diagram.pdf

HOW TO CREATE A NISIMS GDB

ADD SDE DATA TO ARCMAP

This step assumes you have already connected to your state’s NISIMS SDE replica. To start making a new GDB, you must first add to ArcMap the source data from which the GDB originates, which is your state’s (or state group) SDE replica. You should not have to repeat this step if you save your map project (mxd).

1. Start ArcMap. This process varies by user and state, so consult a GIS specialist if you are unsure how to start ArcMap.

2. Cancel the welcome screen that appears since we want to start with a blank map:

3. To add data to the map, click the Add Data button:

4. Navigate to your NISIMS SDE connection. This varies by user, but is often in the Database Connections of the Look in drop-down menu.

5. To see the contents of the database, double-click its container:

Outbound Data Steps >> SDE Default Replica to Local GDB 19

6. We need everything except the relationship classes, but it’s easier to simply select every item. To do, click the first item (yours may vary from the screenshot) then hold the Shift key on your keyboard and press the End key. If you did it right, you should be able to scroll left and see every item selected:

7. Click the Add button to add the selected items to ArcMap.

8. Because you selected all items in the database, including relationship classes, you will receive a warning popup since

ArcMap cannot display relationship classes. Simply click OK and you will be taken to the map:

CREATE LOCAL GDB FROM SDE

Now that SDE data is present in your map, you can use it to generate a local geodatabase (GDB).

1. As mentioned in the NISIMS GDB Concepts, NISIMS GDBs are intended to be used at state-level geographic extents. So, first make sure your state layer is turned on in the table of contents, and turn off any layers that may be obscuring it in the map:

Outbound Data Steps >> SDE Default Replica to Local GDB 20

2. Zoom to your state using the Zoom tool or whichever zoom method you prefer. The extent doesn’t have to be perfect, but the idea is just to encompass the entire state so that all features from reference layers (i.e. County, Owner, etc.) that fall within its boundaries are included.

3. As with most steps involving S1 Data Manager tools, you must be in List By Source view so that map layers are arranged in the table of contents based on their their actual file location. This allows you to indicate to the S1 tools which database you are working with. To verify that you are in this view, make sure the List By Source icon is activated in the table of contents: .

4. The S1 tools need to know which SDE database you are working with, so click your SDE name in the table of contents (yours may differ from the screenshot):

5. Click Download Schema From SDE Default button on S1 Data Manager toolbar:

6. You are presented with a dialog box asking you to specify the directory location where the GDB will be stored (if you are wondering why the other options are disabled, it is to preserve the standardized NISIMS GDB naming convention and database type on which the S1 Tools rely). Click to browse to a directory.

Outbound Data Steps >> SDE Default Replica to Local GDB 21

7. The location where your GDB will live is up to you and will therefore vary by user. It should be somewhere in which you have write privileges and will remember the location. If you already have a folder in mind then browse to that location, otherwise browse to a directory in which you have write privileges and (optionally) create a folder that will help you stay organized., then click OK.

8. Click to close the Browse For Folder dialog.

9. Click again to initiate the SDE-to-GDB export.

10. Soon you should receive a confirmation prompt indicating a successful export. Click OK to close it:

Outbound Data Steps >> Custom Lookup Table Lists 22

11. Since you will likely be working with this ArcMap project (mxd) again, it is not a bad idea to save the map if you have not yet done so. Click File > Save, then navigate to a familiar directory in which you have write access, and assign the map a descriptive name.

Nice work! You now have your very own NISIMS local GDB, whose contents should now be present in the table of contents.

CUSTOM LOOKUP TABLE LISTS

This step allows you to filter the hundreds of records in the master lookup tables into custom lists relevant to your own data collection. The lists are then used to populate drop-down menus in your data forms for several attributes:

Chemical component

Adjuvant component

Project name

Species treated

Person/organization name

Pesticide Use Proposal Number

Biological Control Species

CUSTOM LOOKUP TABLE CONCEPTS

Before creating your first list, there are a few concepts to understand:

Number of items: For the custom list tool to work, each list must contain at least one value regardless of its applicability to your data collection. For example, even if you are not performing chemical treatments, you must still select a value for the chemical component list. The value can be anything, so long as there is one. However, be sure to avoid adding every item as this may cause your device to freeze up.

Repeated use: Once the lists are created, you may continue to use them throughout the field season.

Requesting additions: If you need a person/organization, project names, or Proposal Numbers added to the master lookup tables, which are updated weekly, BLM employees may follow the steps outlined in the Adding Data to NISIMS LU Tables section of this document.

Request early: While not always possible, it is recommended that NISIMS users browse through the available lookup table values prior to the field season to confirm whether or not the necessary values are present. This alleviates the need to create a new GDB after data collection has already begun (remember, data is not automatically pushed down from SDE to GDBs).

Outbound Data Steps >> Custom Lookup Table Lists 23

Modifications: If you need to modify any of your custom lists, you may do so at any time through the same initial process used to create the lists.

HOW TO CREATE CUSTOM LOOKUP TABLE LISTS

The process of creating custom pick-lists is relatively straightforward:

1. Verify that you are in List By Source view in ArcMap’s Table of contents (this should be the case by default). This view lists all layers in your map based on their actual file location:

2. The custom list tool needs a GDB to work with, so click your GDB path to highlight it (this will differ from screenshot):

3. The pick-list tool is located on the S1 ArcPad Data Manager toolbar. To initiate it, click the first drop-down menu and then Create BLM NISIMS Lookup Tables:

4. Prior to each pick-list customization, you will see the following popup. Click Start to proceed:

Outbound Data Steps >> Custom Lookup Table Lists 24

5. The Chemical Component list is the first to be customized, and the process to do so is the identical for the other four pick-lists. First click a desired item in the Master List on the left, and then click the button to add it to your User

List on the right:

6. After adding as many items as needed (again, do not add all items), click Save Preferences to complete this form.

7. You should receive a confirmation that the list was successfully populated (followed by a similar message, if you are modifying an existing list, about files being overwritten). Click OK to close the message/s:

Outbound Data Steps >> Check-outs 25

8. At the popup that appears, click Next>>> to proceed to customize the next list:

9. Repeat steps 5-8 on the remaining lists and remember that each list must have at least one value regardless of whether or not you will be using it.

CHECK-OUTS

Check-outs are basically subsets of geodatabases used for collecting new data. They are “checked out” of their parent GDB and “checked in” to the same GDB after data collection.

IMPORTANT CHECK-OUT CONCEPTS

Before creating check-outs, there are some useful concepts to understand about them.

KEY CHARACTERISTICS OF CHECK-OUTS

Project extent: Unlike GDBs, check-outs are created in ArcMap at a project-level view extent rather than state-level. Reason being, larger extents often mean more WeedInfestationReference features, which leads to larger file sizes and eventually poor performance if not complete inability to collect data on handheld devices due to system limitations.

Schema only: The check-out layers in which you will collect data represent only the schema of the parent GDB.

That is, they are essentially a skeleton of the GDB- field names and data types are the same, but there is no actual data present. The rationale for a schema-only check-out is to promote efficiency (checking out actual data takes much longer) and to ensure that existing data is edited only in ArcMap. T

Existing infestations: The only layer in a check-out containing any NISIMS data is WeedInfestationReference. This read-only shapefile contains non-editable infestation features (and a simplified set of attributes) present in the map extent during check-out. The GDB source layer is updated with new infestations when NISIMS GP is run.

Device-agnostic: Check-outs can be used in ArcPad on a mobile device or desktop, the latter being more common when digitizing is most applicable. The subtle variations between creating a check-out for the two platforms are discussed below.

Layer properties: Changes to a layer’s properties (i.e. labels, symbology, definition queries, etc.) in ArcMap will be preserved in the check-out, which opens up considerable options for customizing your map’s appearance. This applies to both NISIMS and non-NISIMS layers.

Outbound Data Steps >> Check-outs 26

CHECK-OUT FILE MANAGEMENT CONCEPTS

Single-GDB compatibility: Data must always be checked back into the GDB from which it originated, and it is not possible to check it into a different GDB.

Automatic deletion: Once data has been successfully checked back into its parent GDB, the check-out folder is automatically deleted to prevent subsequent check-in of the same data. When you are ready to collect more data, simply create a new check-out.

One unique copy: As with GDBs, there can be only a single unique instance of a check-out since complications will arise if data is checked in from an original check-out and a copy of it. In other words, do not make copies of check-out folders! If you need multiple check-outs, either for yourself or for other users, you must repeat the check-out process for each particular instance.

Folder contents: A check-out folder consists of a variety of files, none of which you should touch! Some files are databases, others are scripts, and modifying or deleting any of them may result in problems.

Short lifespan: For the same reason, check-outs are suited for only a week or two of data collection. This is a rough guideline, but it is best to avoid using the same check-out for an extended period (i.e. an entire field season) since system memory issues can occur. To eliminate the potential for this, you may store multiple check-outs for different project areas and/or different timeframes on your device’s memory card.

MOBILE DEVICE CHECK-OUTS

The majority of check-outs are created for use with mobile devices, discussed in this section.

ROUTINE REQUIREMENTS

Before creating a check-out on a mobile device, there are a few things to confirm:

Memory card: A storage card, usually SD or microSD, must be present.

Power: Your device must be powered on during check-out. The process varies by make and model, so consult your owner’s manual if needed.

ArcPad closed: ArcPad (or any GPS software for that matter) must be closed prior to data transfer to avoid problems caused when both the mobile device and ArcMap attempt to access files simultaneously.

USB cable: Securely connect your device to your PC using the supplied USB cable.

USB Mass Storage Mode: To ensure your device’s visibility in any desktop environment, it must be set to USB

Mass Storage Mode. If you want to verify that your device is in this mode, you may open My Computer or

Windows Explorer and confirm that a removable disk is present. The name, size, and letter drive will vary, but here is a general example of what you might see:

If a removable disk is not present, this may be due to one of several reasons:

Outbound Data Steps >> Check-outs 27 o You are not in mass storage mode. Open USB Toggle and check which mode you are in.

o Your USB cable is not securely connected. Make sure both ends are snugly inserted into their ports, and try a different cable and/or port if you are still experiencing issues.

o Your device is missing a memory card. Turn the device off and check the card slot (steps vary by device).

o A memory card is present but not seated properly. To eliminate this possibility:

1. Turn the device off.

2. Remove the card (steps vary by device).

3. Blow in the card slot to remove any dust.

4. Wipe the terminal contacts with a small amount of rubbing alcohol, if available.

5. Wait for the alcohol to dry, then put the card back in and turn on the device.

HOW TO CREATE MOBILE CHECK-OUTS

Once you have verified the required items, follow these steps to create a check-out for your mobile device:

1. Although optional, it helps to have some reference layers turned on during this step. You may either toggle the existing NISIMS reference layers (i.e. County, Field Office) or add your own. The online basemaps available via Add

Basemap… (in the Add Data drop-down menu) are particularly useful, so feel free to experiment:

2. Since check-outs are intended to be used at project-level geographic extents, you must zoom to your general area of data collection using the Zoom tool or whichever zoom method you prefer. The extent doesn’t have to be perfect since you may still collect data outside this area once the check-out is created, but the idea is just to encompass the approximate area in which data will be collected.

Remember that a large extent can lead to an excessive number of WeedInfestationReference features. Although there is no magic number in terms of scale or amount of features that causes this, if you are zoomed into a reasonably-sized project area with a normal amount of features then it should not be an issue.

If you want to see whether problems occur right off the bat, try opening your check-out on a mobile device prior to field collection and maybe creating (and then deleting) a test feature or two. While this is not a 100% guarantee of problem-free fieldwork, you will at least know your check-out is functioning properly at the onset of collection.

If, however, you begin experiencing memory errors or performance issues in ArcPad, try creating a new check-out with fewer features. Do this either by A) zooming in closer to reduce the number of features in the extent, or B) creating a Definition Query on the WeedInfestationReference layer. Consult a GIS specialist or the built-in ArcMap help for assistance.

Outbound Data Steps >> Check-outs 28

3. As with creating pick-lists, you must indicate which GDB will be used in creating the check-out. So, first verify that you are in List By Source view in ArcMap’s table of contents (this should be the case by default). This view lists all layers in your map based on their actual file location:

4. To specify which GDB will be used to make the check-out, click its path in the table of contents (yours will differ from the screenshot):

5. Click the Check Out to ArcPad button on the S1 ArcPad Data Manager toolbar to initiate the check-out process:

6. You will occasionally receive a message the first time you perform a NISIMS check-out, as the system downloads essential files from the web to your Windows profile that are used in the checkout process. From time to time, these files are updated and new versions are posted to the web. The S1 Data Manager checks for updates at each check-out and, if your profile needs to be updated, you will see the message while the files are downloading.

7. If you have not yet saved your map, you will be prompted to do so now. Navigate to your desired folder (locations vary), assign the map a descriptive name, then click Save. This step simplifies the NISIMS desktop workflow since you can simply open this map whenever you need to check data in or out of the same GDB.