Transcript Trails_Integration_and_Standards_July2010.PPT

Integrating and Standardizing
Trails Data for West Virginia
Evan Fedorko
13 July 2010
1
Outline
•
•
•
•
•
•
Background
GIS Data Preparation
GIS Data Compilation
Database Integration
Gap Analysis
Recommendations
2
Project Deliverables
• A spatial database of trail lines and attributes integrated
with the WV State Trail Coordinator's (WVSTC) tabular
database of trail information. This dataset was
constructed utilizing the Federal Interagency Trail Data
Standard.
• A gap analysis describing where no spatial data exists for
trails.
• A final report, which includes recommended standards
and best practices for integration of data in the future
and long term maintenance.
• A statewide trail map.
3
Benefits
• Consolidates WVDOT Trail Coordinator’s
knowledge into one DB and allows for spatial
queries along side existing tabular reports
• Framework layer for future trail outreach,
management, tourism applications, etc.
4
Study Area
5
Data
• Started with ~35 datasets.
• Utilized datasets and summary metadata to
reduce that down to a dozen datasets.
• Necessary to address some basic questions:
Source Dataset
State Trail Plan
Trails of WMAs
CVI Trails
Monongahela National
Forest Trails
State Forest Trails
Canaan Valley NWR Ski
Trails
Canaan Valley NWR Public
Use Trails
Hatfield-McCoy Trails
Source Agency
NPS
Year
2002
Area of Coverage
Statewide
WVDNR
2005
Wildlife Mgmt. Areas
CVI
2007
CVI Property
USFS
2009
Monongahela National Forest
WVDNR
2001
State Forests
USFWS
2006
Canaan Valley NWR
USFWS
2006
Canaan Valley NWR
RTI
2008
Mercer County
2007
Six small areas across six counties
Mercer County and parts of adjacent
counties
CVI
Unk.
Tucker County
NPS
2007
New River Gorge Area
NPS
2007
Bluestone River area
– In cases where multiple versions of datasets are
available, which version is the most current?
– In areas where datasets overlap, which dataset is the
authoritative source?
– Is it possible to address scale issues as datasets are
compiled?
Trails of Mercer County
Misc. Trails of Tucker
County
New River Gorge Trails
Bluestone National Scenic
River Area Trails
6
Data Preparation
• Once we have the source data, we need to
carefully prepare that data for merging.
• This required a county by county, dataset by
dataset review and extensive manual editing.
• Several minor errors fixed at this step, but
mostly we repaired overlap:
7
Overlap
8
Data Prep.; Attributes
• Data Model is based on the Federal
Interagency Trail Standard (FITS) - why use this
standard?
– Well vetted
– Designed for use across agencies
– Well documented
• Through the addition and extension of
attributes, we customize the model to fit our
situation.
9
Data Model
FEDERAL FIELD
Data Source Agency
GIS FIELD
FORMAT
NOTES
dataAgency
FIELD
DEFINITION
FIELD
LENGTH
Text
10
Date of Last Data Used sourceDate
to Update
updated
Date of Last Update
YYYYMM
date
6
YYYYMM
date
6
Dataset link (if
available)
Source Dataset
TRAIL NAME
TRAIL NUMBER
TRAIL STATUS
TRAIL LENGTH
http://….
weblink
50
miles
Text
Text
Text
Text
Number
50
50
10
10
XXX.X
SHARED SYSTEM
TRAIL SURFACE
ADMIN ORG
MANAGING ORG
CONGRESSIONAL
DISTRICT
COUNTY
JURISDICTION
MUNICIPALITY
STATE
TRAIL SYSTEM
ROAD SYSTEM
LAND USE PLAN
dataLink
sourceDataset
trailName
trailNumber
trailStatus
trailLength
sharedSystem
Text
30
trailSurface
adminOrg
manageOrg
Text
Text
Text
30
30
30
congress
Number
XX
county
jurisdic
municip
state
Text
Text
Text
Text
20
30
30
4
trailSystem
Text
30
roadSystem
landUsePlan
Text
Text
30
50
FEDERAL FIELD
PRIMARY TRAIL
MAINTAINER
TRAIL CLASS
hiking allowed
bicycles allowed
horses allowed
xc ski allowed
backpacking allowed
Interpretive Trail
fitness trail
AMERICAN DISABILITY
ACT COMPLIANT
water trail
MOTORIZED
suitable for atvs
suitable for OHVs
suitable for dirt bikes
PROHIBITED USE
ACCESSIBILITY STATUS
HISTORIC
SIGNIFICANCE
NATIONAL TRAIL
DESIGNATION
RIGHTS-OF-WAY
SPECIAL MGMT AREA
TRAIL CONDITION
GIS FIELD
FORMAT
FIELD
FIELD
NOTES DEFINITION LENGTH
maintainer
Text
30
trailClass
Text
10
hike
y/n
Text
4
bike
y/n
Text
4
horse
xcski
backpack
interp
fitness
y/n
y/n
y/n
y/n
y/n
Text
Text
Text
Text
Text
4
4
4
4
4
ada
y/n
Text
4
water
motorized
atv
y/n
y/n
y/n
Text
Text
Text
4
4
4
ohv
y/n
Text
4
dirtbike
y/n
prohibUse
accessStatus
Text
Text
Text
4
30
10
historic
y/n
Text
4
nationalTrail y/n
Text
4
rightsOfWay
mgmtArea
condition
Text
Text
Text
30
50
10
10
Source Attributes
• Attributes of spatial datasets needed to be
conflated to new data model.
• Example:
DNR - WMAs
WVDNR
1/1/2007
4/28/2010
http://www.wvgis.wvu.edu/data/dataset.php?ID=298
Trails of WV WMA's
NAME
LENGTH (units?)
SURFACE
yes
LOCCODE (codes…?)
Crosswalk Method
Calculate
Calculate
Calculate
Calculate
Calculate
Crosswalk
Crosswalk
Crosswalk
Crosswalk
Crosswalk
New Attributes
dataAgency
sourceDate
updated
dataLink
sourceDataset
TRAIL NAME
TRAIL LENGTH
TRAIL SURFACE
MOTORIZED PROHIBITED
SPECIAL MGMT AREA
• Repeated for each dataset. This helped to
automate some parts of merging.
11
Data Merge
• Initial dataset merge is accomplished via the
merge tool in ArcGIS-Arc Toolbox
• Pre-prepared field maps make this relatively
pain free
• Topological editing follows
12
Topological Editing
Inter-dataset connection issues
13
Misc. Geometric Errors
14
Scale Issues
• Two “symptoms” of scale issues – multiname/multi-system trails and visual
alignment.
• Scale address later, in the gap analysis section.
15
Multi-system Trails
• Problem addressed via a feature of the data
model: the attribute called “sharedSystem.”
16
Database Integration
• WVDOT Trail Coordinator maintains a tabular
database of WV trails.
• That data is unique and needs to be preserved
–we harmonize that information with spatial
data and track it via attributes in each table
17
Tabular to GIS Comparison
• Principal purpose is to crosswalk WVSTC
attributes into the compiled spatial database
• Secondarily this process will feed the gap
analysis.
• We use four attributes in the comparison
process, also completed (more or less) on a
county by county manual basis.
TABULAR
inGIS
Description
1 or 0. Indicates whether the record has a corresponding record in the GIS
database. A 0 in this field indicates a probable data gap.
1 or 0. Indicates whether the record has been reviewed and compared to the
checked GIS database. At the end of the cross walk process, all records should have a
value of 1 for this attribute.
GIS
inDB
1 or 0. This value indicates that the record corresponds to a record in the
WVSTC's trail database and that the information in that database record has
been conflated to the GIS record(s).
1 or 0. This field indicates that the record has been reviewed and compared to
the WVSTC's database. Cases where this value is attributed with a "1" and the
checked inDB record is attributed with a "0" indicates that the trail in question is
adjacent to or in the same land area as a trail in the DB and is clearly absent
from the WVSTC's database. This is a probable gap.
18
“Results”
• Record to record comparison gives a peek at
data gaps.
Total Records
Database
1005
GIS
1321
inDB
-372
inGIS
369
--
Percentage
37%
28%
• Interpret with caveats!
19
Caveats
• Not all trails are "identifiable" in the GIS. There are many
areas GIS data exists and a corresponding record most likely
exists in the database, but due to the lack of identifying
attributes in the GIS, no "match" can be made. Many of these
records are marked with a 1 in the checked field and a 0 in the
inDB field. We were able to mark these as checked due to the
fact that the database contained other records within the
management area, so we can be sure that the WVSTC is aware
of trails in the area (example: Kanawha State Forest).
20
Caveats (2)
• During the course of the analysis we noted many trails in the
DB that were attributed as being in one county but were in
fact located in another county. We made the necessary
change in the database and cross walked information where
possible, but undoubtedly some of these were missed,
resulting in mistakes in the crosswalk.
• Approximately 24% of the lines in the GIS database were not
checked against the WVSTC's database. Many of these trails
(~50%) are unnamed or ambiguously named making any
cross checking difficult. Some of these records fall within
public land areas that are not included in the WVSTC's
database (example: Hughes River Wildlife Management Area).
21
Caveats (3)
• The WVSTC's database includes several roads (example:
Thomas Mountain Road, within Seneca State Forest). No road
lines are presently included in the GIS trails database.
• No water trails are included in the GIS database at this time.
22
Gap Analysis
• We cover 5 types of identifiable gaps.
23
Known Omissions and Mismatches
• We included no GIS data for the George Washington or
Jefferson National Forests.
• Almost no GIS data is available for municipal trails, including
city and county parks.
• Most trails listed in the WVSTC's database as being on private
land have no GIS data.
• The GIS data includes 309 individual trails for the Hatfield and
McCoy Trails system. The WVSTC’s database, however,
includes only two records for each of the six areas.
• No water trails are included in the GIS dataset at this time.
24
County Gaps
• Seven counties contain no trail lines and
should be considered counties with no data
coverage: Calhoun, Clay, Gilmer, Hancock,
Pleasants, Tyler and Wayne.
• Nine additional counties contain only low
resolution lines: Berkeley, Brooke, Doddridge,
Hardy, Harrison, Jefferson, Marion, Morgan,
and Putnam
25
Public Lands
• We examined four public land types: state
forests, wildlife management areas, state
parks and National Park Service land and
determined coverage of trail data.
Total
136
All
GIS
56
Data
Perc. 41.18%
WMAs
86
SFs
9
SPs
39
NPS
2
33
7
14
2
38.37%
77.78% 35.90% 100.00%
26
Scale
• Scale “gaps” refer to problems related to data
that is included but is of such insufficient scale
that a gap results.
• Some repairs were made to poor scale data,
but the work is incomplete.
27
Multiple System Trails
• Many long trails utilize existing roads and trails
and, therefore, are more difficult to attribute.
Gaps in these trails, as exemplified by the
poor scale data that fills in space and the
empty “sharedSystem” attribute entail a gap.
• The completeness of these is not known,
though two trails appear to be well filled out.
28
Recommendations
• We break recommendations into three
categories:
– Content
– Maintenance and Updates
– Validation and Outreach
29
Content
• Critically examine and discuss the data model and make
changes as needed.
• Compile and include lines for water trails.
• Compile and include lines for WV trails in the George
Washington and Jefferson National Forests.
• There are several instances of GIS data for certain public lands
(ex: state forests and state parks) containing insufficient
attributes to compare and crosswalk with WVSTC's database.
We believe that further research, using published trail maps
and other resources, will allow this data to be improved.
30
Content (2)
• Lines for major rail trails can be improved through either the
acquisition of new lines from stakeholders or through
digitizing.
• Unprocessed road line data from the 2003 SAMB project may
be a useful source for some trail lines, rail trails and former
logging roads, in particular. This should be explored.
• Using gap analysis results and the inGIS attribute of the
WVSTC's database, contact pertinent parties and attempt to
collect GIS data for trails in those areas. Of particular concern
are municipal trails.
• Consider adding other ancillary features such as trail heads,
parking areas and waypoints for trail intersections.
31
Maintenance and Updates
• Utilize gap analysis and overall mission
interests to target specific areas for data
improvement.
• Test update process and protocols and modify
best practices as needed.
32
Validation and Outreach
• Consider development of a volunteer geographic information
portal to confirm and collect trail information from non-GIS
users.
• Publish downloadable version of the database for public use.
• Provide subsets of newly compiled and attributed datasets to
relevant stakeholders (ie, provide the Monongahela National
Forest Trails to MNF personnel) and encourage maintenance
of the data in that format.
• Distribute draft of trail standard and report to trail
stakeholders for review and comments.
• Identify GIS personnel within the WV Department of
Transportation to provide technical support to the State Trail
33
Coordinator.
Questions?
• Thank you for your time!
34