IB-OR-2003-110-Interagency Species Management System Spatial Data Cleanup
United States
Department of
Agriculture
Forest Service
R-6
R-5
OR/WA
CA
United States
Department of
Interior
Bureau of Land
Management
Reply Refer To:1950(FS)/1736PFP (BLM) (OR-935) P
Date: March 2, 2003
EMS TRANSMISSION
FS-Memorandum
BLM-Information Bulletin No. OR-2003-110
Forest Service Forest Supervisors within the Area of the Northwest Forest Plan and Bureau of Land
To:
Management District Managers (Coos Bay, Eugene, Lakeview, Medford, Roseburg, Salem) and Field
Managers (Klamath Falls and Tillamook, OR. and Arcata, Redding and Ukiah, CA.)
Subject:
Interagency Species Management System Spatial Data Cleanup
Due Date: 04/30/2003
Program Area: Survey and Manage Program, Interagency Species Management System (ISMS)
Purpose: This Information Bulletin (IB) provides direction for the proper spatial data entry of Survey and Manage
data into the ISMS database and cleanup of spatial data already entered.
Action: A high level of data quality is necessary to support both field unit and regional interagency level analyses for
Bureau of Land Management (BLM) and Forest Service (FS) activities. The BLM and FS are moving away from
ArcView 3.x to ArcGIS, and the ISMS database will be changed to meet those new requirements. The spatial data in
ISMS must be of high enough quality to migrate into the ArcSDE program being adopted by the BLM and FS.
ISMS users will need to follow the ISMS standards, rules, and guidelines as well as the ISMS User’s Guide and ISMS
Training Guide. These documents outline the spatial framework and criteria for spatial data entered into ISMS. The
most recent versions are available on the ISMS web page (http://isms.r6.fs.fed.us), including the March 2003 update to
the ISMS standards, rules, and guidelines with clarifications for spatial data entry on General Surveys.
ISMS standards state that all sites in ISMS must have an associated General Survey, and that all General Survey and
Species Locations must each be linked to a polygon. A General Survey must have one, and only one, polygon.
Species Locations too must have one, and only one, polygon. Also, all polygons in ISMS must be a minimum of 9m
radius. Polygons should be free of errors such as slivers.
All spatial data will need to be cleaned up to meet these data quality criteria. See the attachments for a summary list
of spatial errors found in the February 2003 ISMS Corporate Shapefiles. The lists of individual records with errors
sorted by administrative unit are available at http://isms.r6.fs.fed.us/ corp_data.htm.
2
Timeframe: The next ISMS Corporate Shapefile theme gathering is scheduled for April 30, 2003. All cleanup should
be done prior to April 30, 2003, and the fixed data submitted as part of the theme gathering.
Coordination: ISMS has several levels of data stewards identified (see IB NO OR-2003-037 available at
http://web.or.blm.gov/records/ib/2003/ib-or-2003-037.htm). At the field office level, the data stewards coordinate the
program management, training, and quality assurance. The ISMS Regional Data Stewards are also available to answer
questions that the local data stewards are unable to answer.
Contact:
ISMS Regional Data Stewards:
IB-OR-2003-110-Interagency Species Management System Spatial Data Cleanup
Kelli Van Norman ([email protected]; 503-326-4325) and Stephanie Sprague ([email protected];
503-326-4327).
/s/ Terry D. Brumley
TERRY BRUMLEY
Interagency Survey and Manage Program Manager
Authenticated by
Mary O'Leary
Management Assistant
4 Attachments
1 – Flora General Survey (srvflr) Summary List of Errors Compiled from the February 7, 2003, Corporate
Shapefile (2pp)
2 – Flora Summary List of Errors Compiled from the February 7, 2003, Corporate Shapefile (2pp)
3 – Fauna General Survey (srvfna) Summary List of Errors Compiled from the February 7, 2003, Corporate
Shapefile (3pp)
4 – Fauna Summary List of Errors Compiled from the February 7, 2003, Corporate Shapefile (2pp)
3
BLM Distribution
WO-230 (Room 204LS)-1
CA-330 (Paul Roush, Jeanne McFarland)-2
CA-920 (Richard Grabowski, Donna Reynolds, Leroy
Mohorich)-3
CA-930 (Carl Rountree)-1
OR-010 (Lucile Housley)-1
OR-930 (Ed Shepard)-1
OR-931 (Judy Nelson, Joan Seevers)-2
OR-932 (Janis VanWyhe)-1
OR-935 (NancyDuncan, Paul Hohenlohe, Russell Holmes,
Rob Huff, Neal Middlebrook, Bruce Rittenhouse)-6
cc:
Forest Service-R5
KathyAnderson, Paula Crumpton
Forest Service – R6
Terry Brumley, Kathleen Cushman
Chiska Derr, Judy Harpel, Richard
Helliwell, Carol Hughes, Peggy Kain, Linda Geiser, Pat
Ormsbee, Deb Quintana-Coyer, Roger Sandquist
PNW
Brian Biswell, Tina Dreisbach, Randy Molina, Dede Olson,
Nan Vance
FWS
Jay Watson, Laura Finley, Barbara Amidon, Paul Phifer,
Steve Morey
FLORA GENERAL SURVEY (SRVFLR) SUMMARY LIST OF ERRORS COMPILED FROM THE
FEBRUARY 7, 2003 CORPORATE SHAPEFILE
See http://isms.r6.fs.fed.us/ corp_data.htm for a more detailed listing of errors by LOC_CN and LOC_ID for each
administrative unit. The ISMS ArcView Query Extension contains the tools to run and create this and other spatial
error reports. The extension is available for downloading at http://isms.r6.fs.fed.us/utils/default.htm.
Multi-Part Polygons
There should be no multi-part polygons. A multi-part polygon is a feature that is composed of more than one physical
part but only references one set of attributes in the attribute table. Records with small polygon slivers may also show
up as multi-part polygons.
IB-OR-2003-110-Interagency Species Management System Spatial Data Cleanup
Total # of srvflr multi-part polygon errors: 961
Data Source Code
BLMOR010FL
BLMOR080FL
BLMOR090FL
BLMOR100FL
BLMOR110FL
BLMOR120FL
FS0505FL
FS0508FL
FS0510FL
FS0514FL
FS0601FL
FS0603FL
FS0605FL
FS0609FL
FS0610FL
FS0611FL
FS0615FL
FS0617FL
FS0618FL
FS0620FL
Number of Multi-Part
Polygon Errors
1
7
42
32
553
40
6
20
5
150
3
8
17
3
2
5
39
3
10
15
Polygon Size
The following records fail to meet the minimum polygon size (9 meter radius) for ISMS polygons as documented in
the ISMS Standards and Guidelines.
Total # of srvflr polygon size errors: 8
Data Source Code
BLMOR090FL
BLMOR110FL
FS0514FL
FS0601FL
FS0615FL
Number of Polygon
Size Errors
3
2
1
1
1
Attachment 1-1
Duplicate Records
The following records are duplicate LOC_CN’s that have a different polygon in the corporate shapefile. This
commonly occurs when one user edits the polygon of an existing record and then fails to remove that polygon from
his/her co-worker’s shapefile. During the theme gathering process both polygons end up in the final shapefile.
Total # of srvflr duplicate record errors: 4
Data Source Code
FS0603FL
FS0611FL
Number of Duplicate
Record Errors
2
2
IB-OR-2003-110-Interagency Species Management System Spatial Data Cleanup
Invalid LOC_ID
The following records have a LOC_ID value in the shapefile that does not match the LOC_ID value for the
corresponding oracle record. This commonly happens when a LOC_ID is modified in the Oracle forms, but the user
fails to re-link the record to the corresponding shape.
Total # of srvflr invalid LOC_ID errors: 44
Data Source Code
BLMOR010FL
BLMOR090FL
BLMOR110FL
FS0510FL
FS0514FL
FS0603FL
FS0615FL
FS0618FL
Number of Invalid
LOC_ID Errors
1
3
9
1
17
2
5
6
Attachment 1-2
FLORA SUMMARY LIST OF ERRORS COMPILED FROM THE
FEBRUARY 7, 2003 CORPORATE SHAPEFILE
See http://isms.r6.fs.fed.us/ corp_data.htm for a more detailed listing of errors by LOC_CN and LOC_ID for each
administrative unit. The ISMS ArcView Query Extension contains the tools to run and create this and other spatial
error reports. The extension is available for downloading at http://isms.r6.fs.fed.us/utils/default.htm.
Multi-Part Polygons
There should be no multi-part polygons. A multi-part polygon is a feature that is composed of more than one physical
part but only references one set of attributes in the attribute table. Records with small polygon slivers may also show
up as multi-part polygons.
Total # of flora multi-part polygon errors: 138
Data Source Code
BLMOR090FL
BLMOR110FL
BLMOR120FL
FS0505FL
FS0603FL
FS0605FL
FS0610FL
FS0611FL
FS0615FL
FS0617FL
FS0618FL
FS0620FL
Number of Multi-Part
Polygon Errors
1
49
28
1
1
2
4
20
10
1
4
17
IB-OR-2003-110-Interagency Species Management System Spatial Data Cleanup
Polygon Size
The following records fail to meet the minimum polygon size (9 meter radius) for ISMS polygons as documented in
the ISMS Standards and Guidelines.
Total # of flora polygon size errors: 30
Data Source Code
BLMOR110FL
BLMOR120FL
FS0505FL
FS0514FL
FS0609FL
FS0611FL
FS0615FL
Number of Polygon
Size Errors
11
10
1
4
1
2
1
Attachment 2-1
Duplicate Records
The following records are duplicate LOC_CN’s that have a different polygon in the corporate shapefile. This
commonly occurs when one user edits the polygon of an existing record and then fails to remove that polygon from
his/her co-worker’s shapefile. During the theme gathering process both polygons end up in the final shapefile.
Total # of flora duplicate record errors: 27
Data Source Code
BLMOR010FL
FS0606FL
FS0610FL
FS0611FL
FS0620FL
Number of Duplicate
Record Errors
2
5
16
2
2
Invalid LOC_ID
The following records have a LOC_ID value in the shapefile that does not match the LOC_ID value for the
corresponding oracle record. This commonly happens when a LOC_ID is modified in the Oracle forms, but the user
fails to re-link the record to the corresponding shape.
Total # of flora invalid LOC_ID errors: 196
Data Source Code
BLMCA330FL
BLMOR010FL
BLMOR080FL
BLMOR120FL
Number of Invalid
LOC_ID Errors
39
6
41
5
IB-OR-2003-110-Interagency Species Management System Spatial Data Cleanup
FS0505FL
FS0510FL
FS0608FL
FS0610FL
FS0611FL
FS0615FL
FS0620FL
FUNGI_TLFL
4
3
1
11
32
51
2
1
Attachment 2-2
FAUNA GENERAL SURVEY (SRVFNA) SUMMARY LIST OF ERRORS COMPILED FROM THE
FEBRUARY 7, 2003 CORPORATE SHAPEFILE
See http://isms.r6.fs.fed.us/ corp_data.htm for a more detailed listing of errors by LOC_CN and LOC_ID for each
administrative unit. The ISMS ArcView Query Extension contains the tools to run and create this and other spatial
error reports. The extension is available for downloading at http://isms.r6.fs.fed.us/utils/default.htm.
Multi-Part Polygons
There should be no multi-part polygons. A multi-part polygon is a feature that is composed of more than one physical
part but only references one set of attributes in the attribute table. Records with small polygon slivers may also show
up as multi-part polygons.
Total # of srvfna multi-part polygon errors: 318
Data Source Code
BLMOR080FA
BLMOR090FA
BLMOR100FA
BLMOR110FA
BLMOR120FA
FS0505FA
FS0510FA
FS0514FA
FS0601FA
FS0603FA
FS0605FA
FS0608FA
FS0609FA
FS0611FA
FS0615FA
FS0617FA
FS0618FA
FS0620FA
Number of Multi-Part
Polygon Errors
10
1
6
49
27
19
1
121
1
15
12
5
3
6
14
18
5
5
IB-OR-2003-110-Interagency Species Management System Spatial Data Cleanup
Attachment 3-1
Polygon Size
The following records fail to meet the minimum polygon size (9 meter radius) for ISMS polygons as documented in
the ISMS Standards and Guidelines.
Total # of srvfna polygon size errors: 61
Data Source Code
BLMOR080FA
BLMOR090FA
BLMOR100FA
BLMOR110FA
BLMOR120FA
FS0514FA
FS0605FA
FS0606FA
FS0609FA
FS0615FA
FS0620FA
Number of Polygon
Size Errors
1
7
4
6
8
1
3
27
1
2
2
Duplicate Records
The following records are duplicate LOC_CN’s that have a different polygon in the corporate shapefile. This
commonly occurs when one user edits the polygon of an existing record and then fails to remove that polygon from
his/her co-worker’s shapefile. During the theme gathering process both polygons end up in the final shapefile.
Total # of srvfna duplicate record errors: 95
Data Source Code
BLMOR080FA
BLMOR100FA
FS0510FA
FS0601FA
FS0603FA
Number of Duplicate
Record Errors
80
4
5
2
4
Attachment 3-2
Invalid LOC_ID
The following records have a LOC_ID value in the shapefile that does not match the LOC_ID value for the
corresponding oracle record. This commonly happens when a LOC_ID is modified in the Oracle forms, but the user
fails to re-link the record to the corresponding shape.
Total # of srvfna invalid LOC_ID errors: 104
IB-OR-2003-110-Interagency Species Management System Spatial Data Cleanup
Data Source Code
BLMOR080FA
BLMOR100FA
BLMOR110FA
BLMOR120FA
FS0510FA
FS0514FA
FS0618FA
Number of Invalid
LOC_ID Errors
1
3
9
1
3
85
2
Attachment 3-3
FAUNA SUMMARY LIST OF ERRORS COMPILED FROM THE
FEBRUARY 7, 2003 CORPORATE SHAPEFILE
See http://isms.r6.fs.fed.us/ corp_data.htm for a more detailed listing of errors by LOC_CN and LOC_ID for each
administrative unit. The ISMS ArcView Query Extension contains the tools to run and create this and other spatial
error reports. The extension is available for downloading at http://isms.r6.fs.fed.us/utils/default.htm.
Multi-Part Polygons
There should be no multi-part polygons. A multi-part polygon is a feature that is composed of more than one physical
part but only references one set of attributes in the attribute table. Records with small polygon slivers may also show
up as multi-part polygons.
Total # of fauna multi-part polygon errors: 11
Data Source Code
BLMOR110FA
BLMOR120FA
FS0620FA
Number of Multi-Part
Polygon Errors
9
1
1
Polygon Size
The following records fail to meet the minimum polygon size (9 meter radius) for ISMS polygons as documented in
the ISMS Standards and Guidelines.
Total # of fauna polygon size errors: 2296
Data Source Code
BLMOR110FA
BLMOR120FA
FS0510FA
FS0514FA
FS0601FA
FS0620FA
FS06FA
Number of Polygon
Size Errors
2263
1
1
3
25
3
1
IB-OR-2003-110-Interagency Species Management System Spatial Data Cleanup
Attachment 4-1
Duplicate Records
The following records are duplicate LOC_CN’s that have a different polygon in the corporate shapefile. This
commonly occurs when one user edits the polygon of an existing record and then fails to remove that polygon from
his/her co-worker’s shapefile. During the theme gathering process both polygons end up in the final shapefile.
Total # of fauna duplicate record errors: 2
Data Source Code
FS0611FA
Number of Duplicate
Record Errors
2
Invalid LOC_ID
The following records have a LOC_ID value in the shapefile that does not match the LOC_ID value for the
corresponding oracle record. This commonly happens when a LOC_ID is modified in the Oracle forms, but the user
fails to re-link the record to the corresponding shape.
Total # of fauna invalid LOC_ID errors: 571
Data Source Code
BLMOR010FA
BLMOR080FA
BLMOR090FA
BLMOR100FA
BLMOR110FA
BLMOR120FA
FS0514FA
FS0610FA
FS0611FA
FS0615FA
FS0617FA
Number of Invalid
LOC_ID Errors
2
8
373
83
1
1
33
44
6
10
11
Attachment 4-2