NoxiousWeedUserGuide.pdf

PDF 295 KB Posted Apr 6, 2015

Attached to: FPRD - Noxious Weed Treatment Services Federal contract opportunity
Solicitation number: AG-65T0-S-15-0021
Issued by: Department of Agriculture Forest Service R2-Rocky Mountain Region

About this file

From the source

Noxious Weed User Guide

View the file

Other files for this federal contract opportunity

Other files attached to FPRD - Noxious Weed Treatment Services, newest first.
File	Type	Posted
2015_PreQuoteMeetingMinutes_4152015.docx	DOCX document	Apr 15, 2015
SF30ModificationAmendment.rtf	RTF text file	Apr 9, 2015
EditingNoxiousWeedGeodatabase.pdf	PDF	Apr 6, 2015
NebraskaNoxiousWeedFieldSheets.pdf	PDF	Apr 6, 2015
NebraskaNoxiousWeedGPSUserGuide.pdf	PDF	Apr 6, 2015
2015_Contract_TreatmentArea_Map2.pdf	PDF	Apr 6, 2015
2015_Contract_TreatmentArea_Map3.pdf	PDF	Apr 6, 2015
RFQAG65T0S150021FPRDNoxiousWeedSpraying.docx	DOCX document	Apr 6, 2015
2015_Contract_TreatmentArea_Map1.pdf	PDF	Apr 6, 2015
SF1449RFQAG65T0S150021FPRRDNoxiousWeeds.pdf	PDF	Apr 6, 2015

On GovTribe

Work with this file on GovTribe

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

NOXIOUS	WEEDS	USER	GUIDE
Nebraska	National	Forests	and	Grasslands
January	1,	2013

INTRODUCTION

The

Forest

Service

has

been

performing

invasive

plants

inventories,

and

treating

invasive

plants

(Noxious

Weeds)

for

than

years.

Much

that

data

has

been

loaded

into

the

nox_weeds

geodatabase.

This

database

allows

tracking

noxious

weed

infestations

and

treatment

logical

manner.

The

Nebraska

National

Forests

and

Grasslands

Range

team

and

GIS

has

developed

comprehensive

Noxious

Weed

Form

and

Geodatabase

collect

all

the

necessary

data

for

National

Applications,

and

local

use.

When

current

and

future

collectors

noxious

weed

data

head

for

the

field,

they

need

mindful

the

preceding

history

data,

and

the

time

and

effort

devoted

the

data.

Collection

noxious

weed

data

should

done

careful

manner

insure

continuity

existing

data.

must

collected

using

the

best

spatial

techniques

available,

and

all

mandatory

items

the

form

must

completed.

Both

agencies

are

required

report

this

data

higher

level,

but

its

primary

use

track

and

treat

invasive

plants

locally.

The

noxious

weeds

inventory

for

the

Nebraska

National

Forests

and

Grasslands

made

single

polygon

feature

class

which

contains

data

for

both

inventories

and

treatments.

times

points

and

lines

are

used

collect

the

data

the

field

and

those

are

converted

polygons

the

office

using

buffer

radius

width.

All

the

data

stored

geodatabase

(nox_weeds)

one

simple

polygon

feature

class

with

data

attached.

This

simple

“shape‐file

design”

allows

easy

data

from

GPS

units

with

data

dictionaries.

BASIC

RULES

The

following

rules

must

followed

when

collecting

invasive

plant

(noxious

weed)

data:

1. There

always

one

GIS

polygon

for

each

treatment

inventory.

Polygons

are

not

collected

without

data

and

data

not

collected

without

polygons

(in

the

field

polygon

may

represented

point

line

that

buffered

later

the

office)

2. Treatment

information

always

includes

inventory

information

(Both

page

and

the

form,

EXHIBIT

3. Monitoring

decision

that

requires

comparing

the

information

for

one

polygon

with

the

information

stored

for

the

associated

parent

polygon.

There

not

separate

feature

class

for

monitoring.

4. GIS

identities

(SITE

ID’s)

must

unique

within

the

entire

set

polygons.

5. Point

and

line

data

collected

the

field

must

converted

polygon

data

(buffered

with

the

radius

width

entered)

prior

into

the

master

database

and

all

required

data

items

must

completed.

6. Inventory

polygons

are

queried

using

inventory

date.

Treatment

polygons

are

queried

using

treatment

date.

Treatment

polygons

have

both

inventory

and

treatment

information

and

are

counted

both

inventory

and

treatment

for

reporting

purposes.

The

reason

that

treatments

include

the

inventory

record

for

potential

monitoring

purposes

–

i.e.

what

was

treated.

DATA

COLLECTION

Spatial

data

can

collected

many

ways,

but

for

this

system

GPS

features

must

collected

with

associated

spatial

data

that

are

generated

shape‐files

ready

load

into

the

GeoDataBase.

shape

file

stores

both

the

features

(points,

lines

polygons)

and

the

data

associated

with

them.

There

one‐to‐one

relationship

between

each

feature

and

its

data

attributes.

The

preferred

method

data

entry

Trimble

GPS

unit

with

associated

data

dictionary.

For

non‐contract

data

only,

the

paper

form

may

used

association

with

GPS

features.

Using

the

paper

form

will

require

entering

that

data

into

the

access

data

base

found

here

after

the

GPS

data

has

been

collected.

http://fsweb.sanjuan.r2.fs.fed.us/Range/invasives_form_for_garmin.zip http://fsweb.sanjuan.r2.fs.fed.us/Range/invasives_form_instructions.pdf

The

paper

field

form

shown

EXHIBIT

displays

the

information

that

must

collected.

All

the

data

the

first

page

the

form

required

for

inventories

with

the

exception

that

the

sub‐

activity

called

monitoring,

which

only

required

when

specified.

All

the

data

both

page

and

page

the

form

are

required

for

treatments,

with

the

exception

that

the

sub‐activity

called

monitoring

only

mandatory

when

specified.

Refer

EXHIBIT

for

the

shapefile

GeoDataBase

feature

class

specifications

required

for

electronic

submission.

Data

dictionaries

used

for

data

collection

must

contain

the

fields

corresponding

the

paper

form

with

these

specifications

for

field

size

and

type.

Refer

EXHIBIT

for

legal

codes

used

when

completing

the

Noxious

Weed

data

form.

These

are

the

GeoDataBase

“domains”.

When

using

the

GeoDataBase

directly

the

user

selects

from

these

lists

when

entering

data.

The

GPS

data

dictionaries

setup

must

also

use

these

same

codes.

Proper

completion

the

field

electronic

paper

form

requires

thorough

knowledge

and

understanding

this

user

guide.

REQUIREMENTS	FOR	NOXIOUS	WEED	INVENTORY
The	following	items	are	required	in	order	to	perform	noxious	weed	inventories:

1. Map

any

polygons

specifically

monitored

with

associated

SITE

IDs.

Monitoring

these

specified

polygons

requires

completion

the

monitoring

sub‐activity

information;

monitoring

flag

Y(es),

parent

type

completed.

2. One

hundred

foot

tape

for

radius

determination.

3. Weber’s

plant

guide

(COLORADO

FLORA:

WESTERN

SLOPE)

and

Noxious

Weed

Plant

guides.

4. Hand

lens

for

keying

plants.

5. Trimble

GPS

unit

with

data

dictionary

for

data

entry

alternative

method

specified

such

paper

form.

6. Computer

with

hardware

capacity

run

GIS

software

and

convert

GPS

data

into

shapefiles.

7. ArcView

ArcGis

software

(ESRI)

for

aggregating

exported

GPS

files

into

shape

files.

8. Complete

knowledge

and

understanding

the

requirements

this

user

guide.

9. Ability

identify

noxious

weeds,

determine

dominant

species,

analyze

trends

and

organize

and

enter electronic data. Knowledge of GPS and accuracy standards.

Refer to EXHIBIT 4 for general information pertaining to GPS.

INVENTORIES

AND

TREATMENTS

The

system

will

allow

inventory

record

without

treatment.

However

treatments

also

provide

inventory

information.

Every

inventory

must

have

associated

inventory

date.

Every

treatment

must

have

associated

treatment

date.

The

total

number

inventory

records/polygons

the

result

query

where

inventory

date

exists.

The

total

number

treatment

records/polygons

the

result

query

where

treatment

date

exists.

USE

THE

MONITORING

SUBSYSTEM

This

system

has

the

capability

monitor

invasive

plant

polygons

determine

the

increase

decrease

size

the

infestation

area,

and

the

changing

cover

percents

well

the

effectiveness

treatment.

First

decision

monitor

must

made.

When

polygon

intended

for

monitoring,

the

sub‐activity

for

monitoring

must

coded

YES.

addition,

the

parent

polygon

SITE_ID

must

coded

the

parent

polygon

field.

This

way

differences

can

compared

examining

the

parent

and

follow‐up

polygons

well

the

differences

data

collected.

polygon

monitored

the

spatial

accuracy

its

location

becomes

important.

For

example,

roughly

drawn

polygons

are

usually

inadequate

for

the

purpose

monitoring.

The

Forest

Service

will

designate

polygons

monitored

the

supplemental

specifications.

When

monitoring

existing

polygon,

new

inventory

treatment

conducted

and

all

the

required

fields

are

completed.

new

polygon

created

association

with

the

inventory

inventory/treatment

record.

When

monitoring

required,

shape

file

with

the

polygons

and

data

monitored

will

used

background

file

the

GPS

unit.

LOADING GPS DATA INTO THE MASTER GEODATABASE

FIELD CREW AND CONTRACTOR REQUIREMENTS

This

GeoDataBase

system

designed

that

data

may

easily

loaded

from

shape

files

that

are

generated

from

Trimble

GPS

unit

with

data

dictionary.

The

field

person

needs

concerned

with

the

GPS

unit

used

collect

the

data

and

that

the

proper

data

dictionaries

are

place

(obtained

from

the

GIS

team).

They

must

fully

read

and

understand

this

user

guide

and

complete

all

required

data

items

and

spatial

features.

Both

inventory

and

treatment

shapefiles

will

loaded

copy

the

master

GeoDataBase

for

that

year

work

was

done.

When

the

paper

form

used

(non‐contract

data

collection),

shape

file

also

required

for

the

GIS

features.

For

this

method

data

collection

the

tabular

data

must

entered

using

the

access

database

referenced

under

the

DATA

COLLECTION

heading.

This

would

apply

Garmin

GPS

users.

When

the

spatial

data

and

tabular

data

are

separate

critical

that

the

SITE

field

completed

and

1:1

between

the

spatial

and

tabular

data.

GARMIN GPS UNIT

setup

for

use

with

Garmin

other

GPS

units

available.

This

the

recommended

alternative.

However,

the

separate

spatial

and

tabular

access

database

method

may

also

used.

either,

Garmin

users

will

deliver

merged

shapefile

with

corresponding

tabular

data

electronic

format

district

person

for

inclusion

copy

the

master

Geodatabase.

DISTRCIT TEAM REQUIREMENTS

Points

and

lines

shape‐file

data

will

first

buffered

the

entered

radius

width

prior

into

the

GeoDataBase.

All

new

data

first

loaded

into

empty

GeoDB

schema.

Once

verified

clean

re‐loaded

into

the

master

using

the

ArcCatalog

simple

data

loader

via

the

GIS

personnel.

This

loader

will

add

all

the

new

polygons

with

their

attached

data.

For

those

polygons

without

field

SITE

ID,

one

will

generated

using

ArcMap,

but

only

before

the

data

has

been

loaded

into

the

master.

critical

that

existing

SITE

ID’s

are

not

changed

since

they

could

“parent

polygons”.

Various

checks

will

made

the

integrity

the

data

including

checking

for

unique

id,

correct

legal

codes,

and

existing

parent

polygons.

The

district

personnel

will

contact

the

data

collector

the

data

not

clean

see

the

problems

can

corrected.

the

data

unacceptable

will

rejected

and

returned.

GIS TEAM REQUIREMENTS

The

GIS

team

member

updates

the

master

GeoDataBase

which

resides

Oracle

ArcSde.

After

the

data

for

fiscal

year

finalized

added

the

Master

Geodatabase

using

the

ArcCatalog

simple

data

loader.

backup

copy

the

ArcSde

master

the

form

Access

Database

(MDB)

stored

the

server.

See

Exhibit

for

some

notes

maintaining

the

master

GeoDataBase.

EXHIBIT 1 – NNF FIELD SHEET

Page 1 of 2, Version 9.0 01/01/2013

(Page 1 – Complete for both surveys and treatments)

NOXIOUS WEED INVENTORY SITE_ID __ __ __ __ __ __ __ __ __ __ __ __ __

DISTRICT YEAR SURVEYOR Opt Char

CODE INITIALS

LOCATION: District: BRD BN SRM PRRD ONG FRRD WRD FPNG Agency: PVT STATE USFS

INVENTORY DATE ___________________ (Ex. 04/21/2005)

PROJECT NAME_______________________________________________

SITE DESCRIPTION Riparian Roadside Upland Other

GIS Polygon Type -Check one: Survey______ Treatment ______ (There is one and only one polygon; treatment or survey created corresponding to this form)

SURVEYOR or APPLICATOR 1 (License #) _______________________________ ( ) SURVEYOR or APPLICATOR 2 (License #) _______________________________ ( )

SubActivity -Check one: Monitoring __ (Yes) __ (No) For Monitoring = Yes: Parent Polygon SITE ID __ __ __ __ __ __ __ __ __ __

Select One: POINT____POLYGON_____LINE _____

RADIUS/WIDTH in Feet for Point or Line__________ (For lines, enter the width inventoried/treated on ONLY ONE SIDE of a line or road, even though both sides are inventoried/treated. Points and Lines will be converted to polygons for the final database, and the RADIUS/WIDTH field will be used to buffer the points and lines).

Canopy Cover: Trace < 1% Low 1 – 5% Moderate 5 – 25% High 25 – 100%

PLANT CODE: __________ (Enter the Species code for the primary target invasive species)

ASSOCIATED SPECIES 1 ____________ ASSOCIATED SPECIES 2 ___________

TREND: Decreasing ______ Stable _______ Increasing _____ SOURCE SCALE (Ex. 24000): _____________ only needed if using paper map and drawing site

MAPSOURCE: Aerial Photos___Topo map_____Travel Maps___GPS___Other_______

INFESTATION CAUSES: 1 for primary, 2 for secondary – only include 2 causes./ ___Slash Pile ___Timber Plantation ___Road/Trail ___Dispersed Rec Site ___Reservoir ___Stock Trail ___Developed Rec Site ___Timber Sale ___Corral ___Range Improvement ___Wildlife ___Utility Corridor ___Livestock ___ Fire ___Wind Other__________________

COMMENTS (Additional information specific to the particular survey or treatment)

EXHIBIT 1 – NNF FIELD SHEET

Page 1 of 2, Version 9.0 01/01/2013

(Page 2 – Complete this page in addition to page 1 for treatments only)

TREATMENT [Check One]

HERBICIDE

BIO CONTROLS

MECHANICAL

TREATMENT DATE & TIME ___________________ (Ex. 04/21/2005 1145

TREATMENT CATEGORY (Check One) ___Weed Crew ___Fire Crew ___Dawes County ___Contractor ___Recreation Crew ___Landowner ___Sioux County ___Fall River County ___ ___ ___ ___Custer County ___ Other_____________________________________________________

Complete the Information for herbicide, biological or chemical treatment below depending on which box was checked above

CHEMICAL TREATMENT

% Solution Per gallon CHECK ONE Herbicide 1 (prod1appl) Rate Pints Ounces Pounds

Herbicide 2 (prod2appl) Rate Pints Ounces Pounds

Herbicide 3 (prod3appl) Rate Pints Ounces Pounds

Temperature ____ Wind Direction ____ Wind speed ____

Application Rate _________________ Total Application Amount Applied for the Feature_______ (Use .1 minimum) Units for Application Rate and Amount (Gallons or Pounds) – circle one

BIOLOGICAL TREATMENT

Insect Release 1 Total Released Insect Release 2 Total Released

MECHANICAL TREATMENT (Check on) ___Pres. Burning ___Grubbing ___Shading ___Seed Head Removal ___Mowing ___Fertilization ___Seeding ___Tilling ___Mulching ___Clipping ___Hand Pullng ___ Other_____________________________________________________

EXHIBIT 2 – GEODATABASE FEATURE CLASS ITEMS

FIELD	NAME	DATA	TYPE
INFESTATION_ID	TEXT
LOCATION	TEXT
INVENTORY_DATE	DATE
MONITORING	TEXT
PARENTPOLY	TEXT
PROJECT	TEXT
SITE_DESCR	TEXT
PERSON1	TEXT
APPLICATOR1	TEXT
PERSON2	TEXT
APPLICATOR2	TEXT
RADWIDTH	DATE
GROSS_AC	DOUBLE
NET_ACRES	DOUBLE
COVER_CLASS_CODE	TEXT
PLANT_CODE	TEXT
ASSOC_SPECIES_1	TEXT
ASSOC_SPECIES_2	TEXT
TREND	TEXT
MAPSOURCE	TEXT
MAPSCALE	TEXT
INFACUSE1	TEXT
INFCAUSE2	TEXT
TREATTYPE	TEXT
TREATDATE	DATE
TREATTIME	DATE
TREATCAT	TEXT
PROD1APPL	TEXT
PROD1RATE	DOUBLE
PROD1UNITS	TEXT
PROD2APPL	TEXT
PROD2RATE	DOUBLE
PROD2UNITS	TEXT
PROD3APPL	TEXT
PROD3RATE	DOUBLE
PROD3UNITS	TEXT
APPLRATE	LONG	INTEGER
APPLAMT	DOUBLE
APPLUNITS	TEXT
WINDSPEED	TEXT
WINDDIRECT	TEXT
TEMP	DOUBLE
INSECT1	TEXT
INSECT1TOT	LONG	INTEGER
INSECT2	TEXT
INSECT2TOT	LONG	INTEGER
MECHMETH	TEXT
GENERAL_COMMENTS	TEXT
ERRORCHECK	TEXT

EXHIBIT 3 – LEGAL CODES FOR FIELDS

The

following

lists

legal

codes

for

each

the

noxious

weed

data

fields.

These

are

the

only

acceptable

values

for

the

specified

columns.

These

codes

are

enforced

using

“domains”

ArcGIS.

Only

these

codes

may

entered.

Any

change

coding

must

cleared

the

primary

developer

this

geodatabase.

Note

that

the

listed

here

may

not

up‐to‐date.

Check

against

the

GeoDataBase

domain

for

possible

added

persons,

chemicals,

plants.

Page 1 (Inventories and Treatments)

Page 1 of the Nebraska Noxious weed form is always completed for both inventories and treatments.

SITE_ID (REQUIRED)

The

only

absolute

requirement

for

SITE

IDs

that

they

unique

within

the

treatment

records

and

also

unique

within

the

survey

records.

For

electronic

data,

the

SITE

will

generated

after

the

blank

copy

the

master

GeoDataBase.

When

using

the

paper

form,

may

desirable

enter

SITE

and

so,

the

following

naming

scheme

used:

Digits

1‐6:

NFC

designator

code

(e.g.

020701

for

Bessey

and

Samuel

McKelvie)

Digits

7‐8:

Last

digits

Fiscal

Year

that

initial

feature

established.

Digits

9‐10:

Surveyor’s

initials

for

original

GIS

feature.

Digits

11‐13:

sequential

number

for

each

surveyor

starting

with

the

number

for

new

fiscal

year.

Forest

Service

Fiscal

Years

start

October

When

switching

from

polygons

points

lines,

visa

versa,

this

sequence

number

must

incremented.

PROJECT_NAME (REQUIRED)

Enter

the

name

the

project

for

particular

survey

such

“Missionary

Fire”.

This

must

entered

consistently

order

query

out

the

data

for

particular

project.

When

Using

project

funds

enter

the

following

the

Project

Name

field:

“KV

Timber

Sale

name”.

For

example

“KV

Lucy

Timber

Sale”,

not

“KV

Lucy

Timber

Sale

Unit

#1”

When using the forest‐wide KV funds enter the following in the Project Name field:

“KV Forest Wide”

SURVEYOR AND/OR APPLICATOR 1 AND 2 (AT LEAST ONE NAME IS REQUIRED)

For

inventory

only

records

minimum

one

person

and

maximum

two

who

are

responsible

for

the

data

collection

must

entered.

For

inventory/treatment

record

two

people

who

are

responsible

for

the

inventory

and

treatment.

one

did

the

inventory

and

the

other

the

treatment

record

the

person

who

did

the

inventory

first.

CODE	Description
Brent	Lakin	Brent	Lakin
Claude	Plumb	Claude	Plumb
Curt	Nixon	Curt	Nixon
Dan	Chrisp	Dan	Chrisp
Dan	Ruterbories	Dan	Ruterbories
Jacob	Novotny	Jacob	Novotny
Jens	Johnson	Jens	Johnson
Jerry	Mack	Jerry	Mack
Kelly	Stover	Kelly	Stover
Lora	O'Rourke	Lora	O'Rourke
Other	Other
Richard	Red	Cloud	Richard	Red	Cloud
Robert	Hodorff	Robert	Hodorff
Sarlyn	Morse	Sarlyn	Morse
Shelly	Gerhart	Shelly	Gerhart
Kelsey	Amos	Kelsey	Amos

Michael	Croxan	Michael	Croxan
Timothy	Griffin	Timothy	Griffin
Megan	Mortellaro	Megan	Mortellaro
Courtney	Humphrey	Courtney	Humphrey
Janessa	Chew	Janessa	Chew
Carol	Erickson	Carol	Erickson
Kelly	Fuoss	Kelly	Fuoss
Ryan	Cumbow	Ryan	Cumbow
Tonya	Weisbeck	Tonya	Weisbeck
Ruben	Mares	Ruben	Mares
John	Hess	John	Hess
Cole	Julson	Cole	Julson
Michael	Small	Michael	Small
Jeremy	Noteboom	Jeremy	Noteboom
Cory	Ferguson	Cory	Ferguson
Clint	Phillips	Clint	Phillips
Wyatt	Kirwan	Wyatt	Kirwan
Lori	Jeffrey	Lori	Jeffrey
Norman	Eisenbraun	Norman	Eisenbraun
Leo	Stangle	Leo	Stangle
Brian	Graves	Brian	Graves
Susanna	Wempe	Susanna	Wempe
Nina	Steinmetz	Nina	Steinmetz
Richard	Strehlow	Richard	Strehlow
Jessica	Warner	Jessica	Warner
Dale	Molitor	Dale	Molitor
Robert	Novotny	Robert	Novotny
Michael	Erk	Michael	Erk
Teresa	Harris	Teresa	Harris
Leslie	StewartPhelps	Leslie	Stewart‐Phelps
Elisha	Patten	Elisha	Patten
Pat	Deaver	Pat	Deaver
Lindsey	Glock	Lindsey	Glock
Unknown	Unknown	Unknown	Unknown

The above list is updated frequently. Check with your invasive plant coordinator.

LOCATION (REQUIRED) THIS IS USED FOR THE FACTS ID / SUID AND OWNERSHIP

Code	Description
BRD	Bessey
SRM	Samuel	R	McKelvie
PRRD	Pine	Ridge
ONG	Oglala
FRRD	Fall	River
WRD	Wall
FPNG	Fort	Pierre

INVENTORY DATE (REQUIRED)

Enter the inventory date. Enter the date using the sample format of 07/02/2003.

SUB‐ACTIVITY MONITORING (REQUIRED WHEN SPECIFIED)

Code	Description
Y	Monitoring	Record
N	Not	Monitoring	Record

PARENT POLYGON (REQUIRED FOR MONITORING ACTIVITIES)

this

survey

treatment

has

been

designated

for

monitoring

(monitoring

Y),

then

the

parent

polygon

type

must

completed,

and

the

exact

SITE_ID

the

parent

polygon

must

entered

this

field.

POINT, POLYGON, OR LINE (RADIUS / WIDTH IS REQUIRED FOR NON‐POLYGONS)

the

survey

treatment

based

point

line

field

SITE

feature,

the

radius

width

(in

feet)

must

entered

order

buffer

the

feature

polygon

the

office

prior

the

master

GeoDataBase.

The

feature

type

must

checked

the

form.

The

different

feature

types

would

different

data

dictionaries

when

using

GPS

unit

capable

supporting

data

dictionary.

RADIUS/WIDTH (REQUIRED IF NOT A POLYGON)

point

checked,

enter

the

radius

the

weed

patch

feet.

the

radius

100

feet

greater,

polygon

should

used

for

the

feature

and

not

point.

For

line

feature,

the

field

describes

one

side

the

centerline

inventoried

treated

line,

feet.

the

feature

road,

the

road

width

not

included,

and

the

field

describes

the

width

one

side

the

inventoried

treated

road.

Leave

this

field

blank

for

polygons.

This

information

will

left

the

master

database

after

buffering

polygons

metadata

item.

This

field

must

entered

for

all

GPS

points

and

lines

order

create

polygon

GIS.

This

value

must

converted

meters

for

the

buffer

operation.

Example

Line

Feature:

you

inventoried

treated

feet

each

side

road,

the

width

entered

would

feet

(include

only

one

side

the

road,

and

not

include

the

width

the

road).

CANOPY COVER (REQUIRED)		Choose	the	canopy	cover	percent	using	the	Greater	Yellowstone	method
of	all	noxious	weeds	as	a	number	between	0	and	100.

Code	Description
T	0	–	1%
L	1.1	–	5.0%
M	5.1	–	25.0%
H	25.1	–	100%

INVASIVE SPECIES (REQUIRED) – ENTER THE MOST DOMINANT SPECIES IN THE PLANT CODE FIELD. ENTER THE NEXT 2

SPECIES IN ORDER OF DOMINANCE IF THEY EXIST IN THE ASSOCIATED SPECIES FIELDS

Code	Description	Code	Description
ARAB3	absinth	wormwood	PEHA	African	rue
HYNI	black	henbane	SONI	black	nightshade
CHTE2	blue	mustard	SAOF4	bouncingbet
CIVU	bull	thistle	ALMA12	camelthorn
CIAR4	Canada	thistle	CIIN	chicory
CLOR	Chinese	clematis	MASA	coast	tarweed
ARMI2	common	burdock	CRVU2	common	crupina
SEVU	common	groundsel	VETH	common	mullein
HYPE	common	St.	Johnswort	TAVU	common	tansy
DIFU2	common	teasel	ANAR6	corn	chamomile
DILA4	cutleaf	teasel	EUCY2	cypress	spurge
LIDAD	Dalmatian	toadflax	HEMA3	dame's	rocket
CEDI3	diffuse	knapweed	BRTE	downy	brome
ISTI	Dyer's	woad	MYSP2	Eurasian	watermilfoi
COAR4	field	bindweed	DESO2	flixweed
SAMO5	giant	salvinia	SEVI4	green	foxtail
SOPH	hairy	nightshade	HAGL	halogeton
CADR	hoary	cress	CYOF	houndstongue
HYDRI	hydrilla	SOHA	Johnsongrass
AECY	jointed	goatgrass	KOSC	kochia
EUES	leafy	spurge	CEPR2	meadow	knapweed
SAAE	Mediterranean	sage	TACA8	medusahead
VEBL	moth	mullein	MAGL2	mountain	tarweed

CANU4	musk	thistle	EUMY2	myrtle	spurge
NONE	No	Invasive	Species	HIAU	orange	hawkweed
OTHER	Other	‐	Enter	in	Comments	LEVU	oxeye	daisy
LELA2	perennial	pepperweed	SOAR2	perennial	sowthistle
CAAC	plumeless	thistle	COMA2	poison	hemlock
TRTE	puncture	vine	LYSA2	purple	loosestrife
ELRE3	quackgrass	ERCI6	redstem	filaree
CHJU	rush	skeletonweed	ACRE3	Russian	knapweed
SATR12	Russian	thistle	ELAN	Russian‐olive
TARA	saltcedar	MAPE2	scentless	false	mayweed
ONAC	Scotch	thistle	LECU	sericea	lespedeza
CABU2	shepherd's	purse	CEBI2	spotted	knapweed
ANCR2	spurred	anoda	CETR8	squarrose	knapweed
ANCO2	stinking	chamomile	PORE5	sulfur	cinquefoil
SPSA3	swainsonpea	SEJA	tansy	ragwort
ABTH	velvetleaf	HITR	Venice	mallow
CACA19	wild	caraway	SIAR4	wild	mustard
AVFA	wild	oat	PAMI2	wild	proso	millet
PEGL2	yellow	foxtail	CYES	yellow	nutsedge
CESO3	yellow	star‐thistle	LIVU2	yellow	toadflax
COVA2	crown	vetch	BRIN2	smooth	brome
FAVU	sickleweed

The above list is updated frequently. Check with your invasive plant coordinator.

TREND (REQUIRED)

Code		Description
INC	Increasing
DEC	Decreasing
STB	Stable

SCALE OF THE DATA SOURCE (REQUIRED)

Code		Description
5000	1:5000
10000	1:10000
15840	1:15840
24000	1:24000
40000	1:40000
80000	1:80000
100000	1:100000
126720	1:126720
NONE	Not	Applicable	(GPS)
OTHER	Other		(Enter	in	Comments)

MAP SOURCE (REQUIRED)

Code	Description
TOPO	Topographic	map
PHOTO	Aerial	Photo
GPS	GPS	locations
GPS1	GPS	Garmin
GPS2	GPS	Trimble
GPS3	GPS	ArcPad
ORTHO	Orthophoto
VMAP	Visitor	Map
OTHER	Other		(Enter	in	Comments)
TVLMGT	Travel	Management	Map
ANEC	Anecdotal	Data
HIST	Historical	Map

INFESTATION CAUSES (REQUIRED)

Code	Description
TIMS	Timber	Sale
RIPA	Riparian	Area
CORR	Corral
LIVES	Livestock
TIMP	Timber	Plantation
RES	Reservoir
RGIM	Range	Improvement
RDTR	Road/Trail
STTR	Stock/Trail
WILD	Wildlife
DVREC	Developed	Rec	Site
UTIL	Utility	Corridor
FIRE	Fire
WIND	Wind
OTHER	Other	‐	Enter	in	Comments
DSREC	Dispersed	Rec	Site
SLASH	Slash	Pile
UNKNO	Unknown

COMMENTS (REQUIRED AS SPECIFIED)

240

characters

commentary

may

entered.

Comments

are

especially

important

for

significant

information

that

does

not

apply

the

required

fields.

Page 2 (Treatments Only)

TREATMENT TYPE (REQUIRED FOR TREATMENTS)

Code		Description
HERB	Herbicide	Treatment
MECH	Mechanical	Treatment
BIOL	Biological	Agent

TREATMENT DATE (REQUIRED FOR TREATMENTS)

Enter the treatment date. Enter the date using the sample format of 07/02/2003.

TREATMENT CATEGORY (REQUIRED FOR TREATMENTS)

Code		Description			Code		Description
WC	Weed	Crew	CONTRT	Contractor
OTHER	Other			FC		Fire	Crew
RC	Recreation	Crew		LNDWNR	Landowner
DCNTY	Dawes	County		SCNTY		Sioux	County
FRCNTY	Fall	River		CCNTY		Custer	County

Complete	the	information	for	herbicide,	biological,	or	chemical	treatment	based	on
which	treatment	was	selected.

HERBICIDES (REQUIRED FOR CHEMICAL TREATMENTS)

Code	Description	Code	Description
Arsenal	Arsenal	Banvel	Banvel
Carbaryl	Carbaryl	Curtail	Curtail
Escort	Escort	Garlon	3A	Garlon	3A
Garlon	4	Garlon	4	Grazon	P&D	Grazon	P&D
Habitat	Habitat	Milestone	Milestone
Other	Other	‐	Enter	in	Comments	Overdrive	Overdrive
Plateau	Plateau	Redeem	R&P	Redeem	R&P

Roundup	Ultra	Roundup	Ultra	Sahara	DG	Sahara	DG
Spike	20P	Spike	20P	Telar	Telar
Tordon	22K	Tordon	22K	Transline	Transline
Velpar	L	Velpar	L	Veteran	Veteran
Aquastar	Aquastar	Cimarron	Plus	Cimarron	Plus
Paramount	Paramount	Rodeo	Rodeo
Metcel	Metcel	2,4‐D	2,4‐D
2,4‐D	Ester	2,4‐D	Ester	Telar	XP	Telar	XP
Escort	XP	Escort	XP	Glyphomax	Plus	Glyphomax	Plus
Outpost	Outpost	Patriot	Patriot
Platoon	Platoon	Metcel	VMF	Metcel	VMF
Chaparral	Chaparral

The above list is updated frequently. Check with your invasive plant coordinator.

herbicides

may

reported

along

with

the

required

rates

per

acre

and

units

measure.

This

information

required

whenever

the

treatment

chemical.

Note

additives

such

oil

the

comments

section.

PER ACRE RATE (REQUIRED FOR CHEMICAL TREATMENTS)

The herbicide rate (prod1rate) must be reported as per acre and not total.

UNIT OF MEASURE (REQUIRED FOR CHEMICAL TREATMENTS)

Code		Description
oz	Dry	Ounces
pt	Pints
lb	Pounds
lo	Liquid	Ounces

WIND SPEED (REQUIRED FOR CHEMICAL TREATMENTS)

Code		Description
1	<	5	mph
2	5‐10	mph
3	>	10	mph

Code the wind speed for chemical treatments

APPLICATION RATE (REQUIRED FOR CHEMICALS)

Code the application rate per acre of the mixture. For example code 160 for 160 gallons/acre.

TOTAL APPLICATION AMOUNT (REQUIRED FOR CHEMICALS)

Code

the

total

amount

applied

the

formulated

product(s),

adjuvants,

AND

carrier

for

the

entire

polygon

when

using

chemical

treatments.

Thus

gallons

tank

mix

Tordon

22K,

2,4‐D,

and

water

applied,

entered

the

APPLAMT

field.

And

gallons

3:1

mix

JLB

Oil

and

Garlon4

applied,

entered

the

APPLAMT

field.

APPLICATION UNITS

Code the application units used for the mix per acre as GAL (for gallons) or LBS (for pounds)

INSECT RELEASE 1 AND 2 (REQUIRED FOR BIOLOGICAL TREATMENTS)

Code		Description
CALU	Calophasia	lunula	(defoliating	moth)
CARU	Cassida	rubiginosas	(defoliating	beetle)
CELI	Ceutorhynchus	Litura	(crown	/	root	weevi
LAPL	Larinus	planus	(seed	head	weevil)
MEJA	Mecinus	janthinus	(stem	boring	weevil)
OTHER	Other	(write	in	comments)

RHCO	Rhinocyllus	conicus	(seed	head	weevil)
TRHO	Trichosirocalus	horridus	(crown/rood	wee
URCA	Urophora	cardui	(stem	gall	fly)
HALI	Hadroplontus	litura	(stem	mining	weevil)

The species of insect released must be recorded for biological treatments.

TOTAL RELEASED (REQUIRED FOR BIOLOGICAL TREATMENTS)

Enter the total number of insects released

MECHANICAL TREATMENT (REQUIRED FOR MECHANICAL TREATMENTS)

Code		Description
Clip	Clipping
Fert	Fertilization
Grub	Grubbing
Pull	Hand	pulling
Mow	Mowing
Mulch	Mulching
Other	Other
Burn	Prescribed	Burning
Rem	Seed	head	removal
Seed	Seeding
Shade	Shading
Till	Tilling

ENTRY

ORDER

FOR

MULTIPLE

HERBICIDES

The

detailed

data

the

Geodatabase

grouped

for

reporting

the

FACTS

system.

For

example

there

could

Tordon

22K

2,4‐D

and

there

could

2,4‐D

Tordon

22K

which

were

the

same

treatment

but

would

grouped

into

two

separate

rows

the

report.

order

for

there

fewer

groups

enter

into

FACTS

the

following

recommended

for

herbicide

treatments.

Tordon	22K/2,4‐D
Tordon	22K/Escort/2,4‐D

The

default

convention

for

entry

order

multiple

chemicals

should

Tordon,

followed

the

second

herbicide,

and

third

alphabetical

order.

2,4‐D

herbicides

should

named

last.

Where

Tordon

not

used,

then

list

the

herbicides

used

alphabetical

order

(with

the

exception

2,4‐D

which

always

listed

last).

Following

are

some

examples:

Tordon	22K/2,4‐D
Tordon	22K/Escort/2,4‐D
Tordon	22K/Escort/Telar
Tordon	22K/Excort/2,4‐D

EXHIBIT 4 – GPS DISCUSSION AND STANDARDS

the

past,

noxious

weed

infestations

were

plotted

paper

mylar

maps

manually,

and

either

scanned

into

the

electronic

format,

on‐screen

digitized

using

DRG’s

(topographic

maps)

background.

Hard

copy

maps

can

refer

topo

maps

visitor

maps,

long

the

drawn

features

are

distinguishable

the

source

map

scale

(note

that

SCALE

attribute).

GPS

will

yield

accurate

result

some

cases,

but

discussion

the

advantages

and

disadvantages

different

types

GPS

data

appropriate.

The

Forest

Service

often

use

Trimble

GPS

units,

because

they

come

with

their

own

software

(Pathfinder

Office)

which

can

differentially

correct

raw

data

improve

its

accuracy

and

export

the

data

shape

files.

Additionally,

the

Trimble

GPS

units

have

the

capability

storing

the

Data

Dictionary

and

the

Data

associated

with

the

Noxious

Weeds

Inventory

form

from

above.

This

means

that

the

tabular

data

stored

with

the

spatial

data

and

makes

incorporation

into

GIS

efficient.

The

Garmin

GPS

units

cost

less

than

the

Trimble,

but

lack

the

ability

differentially

correct

store

tabular

data

with

spatial

data.

The

only

way

import

Garmin

GPS

data

into

GIS

using

GIS

extensions.

Hard

copy

map

features

and

Garmin

GPS

data

need

accompanied

completely

filled

out

Noxious

Weed

Inventory

Form

which

must

then

entered

into

empty

copy

the

GeoDataBase

manually.

GPS

can

excellent

tool

use

acquiring

spatial

data.

The

following

excerpt

from

the

document

GPS

GIS:

Procedural

Handbook

version

7.0.

For

detailed

information

about

getting

GPS

data

into

GIS,

refer

San

Juan

intranet.

There

are

variety

GPS

receivers

available

the

forest

that

can

collect

data,

but

important

understand

their

capabilities

and

limitations.

also

important

keep

your

data

needs

(including

type

data)

mind

when

selecting

unit.

Trimble

units

are

specifically

designed

collect

and

store

spatial

information.

Garmin

units

are

primarily

designed

navigation

tools.

lot

can

depend

what

you

want

use

the

data

for

that

may

govern

which

GPS

tool

use,

but

keep

mind

the

final

product.

GIS

uses

the

best

data

available

(which

may

not

very

good).

Rule

thumb,

Garbage

Out.

collecting

data,

don't

short

yourself

getting

the

best

data

possible.

Currently,

the

Nebraska

GIS

recommends

the

use

Trimble

(or

equivalent)

GPS

units

for

data

collection

when

units

are

available.

These

units

provide

higher

quality

data

and

interface

with

GIS

very

well.

However,

understood

that

cost

and

availability

can

deterring

factor

and

more,

less

expensive

Garmin

handheld

units

are

available

users

the

forest.

Any

GPS

data

going

into

GIS

layers,

regardless

source,

should

“clean”

(edited)

possible.

When

exporting

data

from

the

trimble

for

invasive

plants

sure

use

code

and

not

attribute

value.

GPS Standards defined

o GPS	standard	for	GIS	(draft)	WO
o FGDC	part	3	Geospatial	Positioning	Accuracy
o FSH	2409.12	Timber	cruise	Handbook

o Metadata

GPS	(Region	2)
o PDOP	Mask		6.0	(using	the	default	setting)	Recommended

NOTE:

Difficult

satellite

coverage

may

need

use

higher

number.

o SNR/CNR

Mask

4.0

(using

the

default

setting)

o This

dictates

that

satellite’s

signal

will

not

used

below

this

value.

o Elev

Mask

degrees

o Min

Satellites

(unit

will

collect

mode)

Export Coordinate System

o System	UTM
o Zone	13	North
o Datum	NAD83	(Conus)	CORS96	(preferred)

EXHIBIT 4 – GPS DISCUSSION AND STANDARDS

o or	NAD83	(Conus)
o Units			Meters
o Altitude		MSL

Export Units

o Distance	Meters
o Area		Square	Meters
o Velocity	Meters	per	Second

Perceived accuracy vs. Required accuracy.

o NMAS	40ft	(12.2m)
o NSSDA	13.9m
o FGDC	10m
o GPS	design	accuracy	<	15m
o LAAS,	WAAS	for	airport/aircraft	requires	5	satellites.

GENERAL FEATURES

1. Trimble: 8‐12 channel (including GeoXT, GeoXM, Geo Explorer 1,2,3, ProXL, ProXR, Allegro Datalogger)

Cost:	$$‐$$$
Accuracy:

a. Uncorrected	data	without	Selective	Availability:		5‐15	meters.
b. Differential	Correction	(DGPS):		1‐5	meters
c. Wide	Area	Augmentation	System	(WAAS)	capable	receivers:		1‐3	meters

Refer	to	the	document	K:\res\gisteam\gps_notes\waas_faq.pdf	for	a	detailed
description	of	WAAS.

d.	Carrier	Phase:	Submeter
Features:

a. Data

Dictionary

–

record

attributes

greater

detail.

Can

designed

match

existing

GIS

layer

attribute

fields.

b. Postprocessing	–	GPS	files	can	be	differentially	corrected	and	edited.
c. Can	average	multiple	positions	per	point	to	yield	a	more	accurate	point.
d. Memory	storage	–	generally	can	accommodate	large	amounts	of	data.
e. Ideal	for	Point,	Line	and	Polygon	data.

Software: Pathfinder Office (Active Sync/Lassen PC for the Allegro)

2.		Garmin:	8‐12	channel
Cost:	$
Accuracy:

a. Uncorrected	data	without	Selective	Availability:		15	meters.
b. Garmin	under	trees	20‐40m
c. DGPS	(must	have	beacon	receiver,	antenna	and	within	range	of	a	beacon

transmitter):		3‐5	meters
d. Wide	Area	Augmentation	System	(WAAS)	capable	receivers:	<	3	meters

	Features:
a. Designed	and	excellent	for	navigation.
b. Works	very	well	with	collecting	points.
c. Small,	lightweight.

Software:

Several

extensions

available

for

downloading

Arcview

(DNR

Garmin

the

best).

Line

Polygon

data

will

require

lot

editing.

EXHIBIT 5 – INVASIVE PLANTS GIS MAINTENANCE

EXTRACTING A SCHEMA FROM THE MASTER GEODATABASE FOR CURRENT WORK ONLY

Data

for

each

fiscal

year

collected

new

empty

GeoDataBase.

Once

that

complete

and

edited

loaded

into

the

master

GeoDataBase.

The

following

describes

how

create

new

empty

GeoDataBase

for

the

fiscal

year.

Add

the

distributed

geodatabase

toolbar

ARCMAP

using

tools,

customize

and

checking

distributed

geodatabase.

Add the master GeoDb NoxiousWeeds feature class to ArcMap using the +.

Click the button on the distributed geodatabase toolbar to “Extract Data”

Select the checkbox for schema only. Do not check Reuse schema or show advanced options

Navigate

the