Invasive Species Science Team Meeting

1
Invasive SpeciesScience Team Meeting

• John L. Schnase
• NASA Goddard Space Flight Center
• Greenbelt, Maryland
• Thomas J. Stohlgren
• USGS National Institute of Invasive Species
  Science
• Fort Collins, Colorado
• 9 July 2003

2
Agenda

• Wednesday, 9 July 03
• NASA Status Report (ESTO/CT Milestones, F,O1, C
  G Carbon Years 2 3)
• USGS Status Report (ESTO/CT Milestones, F,O1, C
  G Carbon Years 2 3)
• NASA HQ Report (Program Plans, NASA/USDA, )
• -----
• Big Problem (Priorities, issues, strategies,
  )
• MSU Collaboration (Opportunities, overlaps, )
• REASoN CAN (Initial project overview, HQ
  guidance )
• Thursday, 10 July 03
• Big Problem (Discussion, next steps, task
  assignments)
• MSU Collaboration (Discussion, next steps, task
  assignments)
• REASoN CAN (Discussion, next steps, task
  assignments)

3
NASA Status Report

• John Schnase
• NASA Goddard Space Flight Center

4
Invasive SpeciesA Top Environmental Issue of the
21st Century

• Economic Costs
• 137 Billion / Yr
• (Pimentel, et al. 1999 NISRC Management Plan,
  2001)
• Environmental Costs
• Decreased biodiversity, ecological services, etc.
• Human-Health Costs
• West Nile Virus, Malaria, etc.
• Agricultural Costs
• Crop pathogens, hoof-and-mouth, mad cow disease

• Notorious examples include
• Dutch elm disease, chestnut blight, and purple
  loosestrife in the northeast kudzu, Brazilian
  peppertree, water hyacinth, nutria, and fire ants
  in the southeast zebra mussels, leafy spurge,
  and Asian long-horn beetles in the Midwest salt
  cedar, Russian olive, and Africanized bees in the
  southwest yellow star thistle, European wild
  oats, oak wilt disease, Asian clams, and white
  pine blister rust in California cheatgrass,
  various knapweeds and thistles in the Great
  Basin whirling disease of salmonids in the
  northwest hundreds of invasive species from
  microbes to mammals in Hawaii and the brown tree
  snake in Guam.
• As many as 50,000 now,hundreds new each year ...

5
Federal Government Response

• National Invasive Species Council (EO 13122 -
  1999)
• Co-Chaired by Departments of Agriculture,
  Commerce, and Interior
• USGS has a lead role in dealing with invasive
  species science in natural and semi-natural areas
• Responsible for measurement, management, and
  control on all Department of Interior and
  adjacent lands ...

6
USGS National Institute of Invasive Species
Science
USGS Biological Resources Division (BRD)
laboratory Located at USGSs Ft. Collins Science
Center New facilities opened Aug 02 Director,
Tom Stohlgren Many current / future partners ...
Grand Challenge Biodiversity and Ecosystem
Functioning with special emphasis on invasive
species ... NRC Committee on Grand Challenges
in Environmental Sciences, 2001
Needed A National Center For Biological
Invasions Don Schmitz and Dan
Simberloff Issues in Science and Technology,
Summer 2001
7
USGS Science / Client Needs

• On-demand, predictive landscape- and
  regional-scale models and maps for biological
  invasions
• Pick any point, land management unit, county,
  state, or region and determine the current
  invasion, and vulnerability to future invasion by
  species.
• Pick any species or group of species, and get
  current distributions, potential distributions,
  potential rates of change, and levels of
  uncertainty.
• Data integration and sharing
• Comprehensive information on control efforts and
  cost. Share early detection data, control
  strategies, local expertise. Help public and
  private land managers.

8
National Invasive Species Forecasting System
(ISFS)

• NASA / USGS Partnership
• Chip Groat, Kathie Olsen early promoters
• Goal Develop an operational DSS capability for
  USGS DOI
• Research topic adopted by YO
• Carbon Cycle Science Applications Program
• Predicting Regional-Scale Exotic Plant Invasions
  in Grand Staircase-Escalante National Monument
  (NASA YS/YO NRA - Schnase, Smith, Stohlgren)
• ESTO/Computational Technologies Program
• Biotic Prediction Building the Computational
  Technology Infrastructure for Public Health and
  Environmental Forecasting (NASA YS CAN -
  Schnase, Smith, Stohlgren)
• Ref. EOM Article / NRC Report /
  http//ct.gsfc.nasa.gov/milestones.schnase.html

9
C Objectives

• Adapt a suite of multi-phase, multi-scale early
  detection and monitoring protocols to use new
  types of EOS and commercial data
• Extend a suite of predictive models to enable
  their use in regional-scale assessments of
  invasive species patterns and vulnerable habitats
• Integrate science and technology results into a
  community-developed, high-resolution,
  regional-scale application system for invasive
  species management in Utahs Grand
  Staircase-Escalante National Monument
• Make the resulting application system broadly
  available through the USGS National Biological
  Information Infrastructure program
• Evaluate its potential as an operational system
  for managing all Department of Interior lands.

10
CT Objectives

• Create a high-performance, parallel
  implementation of the PlantDiversity modeling
  code for invasive species
• Document the use of software engineering
  techniques that foster reproducibility and
  community-wide software process improvements in
  this domain
• Engage an extended community of scientists
  through the National Biological Information
  Infrastructure program
• Empower the ecological, environmental, and public
  health communities by expanding their
  participation in high-performance computing and
  broadening their use of NASA ESE data

11
Modeling Approach
Output GIS - Spatial Statistical Dynamic Models
and Maps
Trend Surface Analysis With Stepwise Multiple
Regression Using OLS, GLS, SAR, or Exhaustive
Regression
Input Variables (150) Remotely Sensed
data (ETM, SPOT, MTI, EO1, etc.) Derived Remote
Sensing (Vegetation Indices, PCA Tasseled Cap,
other) Biotic/Abiotic Data Topographic
Data Species Data Vegetation- Forest Data Soils
Characteristics Cryptobiotic Crusts Wildfire
Severity Biodiversity Air Pollution Geology,
Other Environmental Data
Hot spots of native biodiversity Distribution
of non-native species Potential spread
of invasive species. Barriers to rapid
invasions. Corridors that may accelerate
invasions. Economic and environmental risk
assessments, vulnerability of habitats to
invasion. Priorities for control and
containment.
Testing if There Is Spatial Auto-Correlation In
the Residuals
No
Final Trend Surface Map Large - Small Scale
Variability
Yes
Testing if Residuals Cross-Correlated with Other
Variables
Yes
Yes
No
Model Residuals Using Co-Kriging
Regression Trees Classifications
Model Residuals Using Kriging (Universal,
Ordinary, other)
12
CT/C Milestones (YR 1)

• Software Engineering Plan Completed (4/15/02)
  (5/13/02)Deliver Software Engineering /
  Development Plan, Configuration Management Plan,
  Quality Assurance Plan, Risk Management Plan
• Code Baseline Completed (7/15/02) (1/6/03)
• Document performance characteristics and
  time/space complexity of existing PlantDiversity
  code and modeling process for three canonical
  examples Cerro Grande Fire Site (CGFS), Rocky
  Mountain National Park (RMNP), and Grand
  Staircase-Escalante National Monument (GSENM).
  Determine appropriate multipliers, m and n, to be
  used in Milestones F and G respectively. Deliver
  initial version of Requirements, Software Design,
  and Concept of Operations Documents. Documented
  source code made publicly available via the Web.
  (7/15/02) (1/6/03)
• First Annual Report (8/15/02) (1/6/03)

13
CT/C Milestones (YR 2)

• F. First Code Improvement Completed (7/15/03) gt
  (8/15/03)Improve implementation of
  PlantDiversity to deliver canonical products from
  Milestone E mX faster than the baseline
  implementation. Provide code scaling curves.
  Provide preliminary evaluation of EOS data
  extensions. Deliver updates to Requirements and
  Design Documents. Deliver initial version of Test
  Plan / Procedures Document. Documented source
  code made publicly available via the Web.
• O1. Install Linux Cluster (7/15/03) gt (9/15/03)
• Install Linux clusters at USGS/CSU and
  NASA/GSFC. System configurations will be based on
  recommendations from CT at the time of purchase.
• C. Second Annual Report (8/15/03) gt (9/15/03)

14
CT/C Milestones (YR 3)

• Second Code Improvement Completed
  (7/15/04)Improve implementation of
  PlantDiversity to accommodate 10X more input data
  over Milestones E and F at nX the time required
  in the baseline implementation.  (Depending on
  the science problem, this enhanced capability may
  be used to increase spatial resolution, temporal
  resolution, or coverage.) Provide code scaling
  curves.  Deliver updates to Requirements, Design,
  and Test Documents. Deliver initial User's Guide.
  Documented source code made publicly available
  via the Web.
• Third Annual Report (8/15/04)
• Customer Delivery Accomplished (12/15/04)
• Achieve sustained, evaluative use of
  PlantDiversity by NIIS, GSENM, and 8 additional
  customers. Deliver updated Test Plan / Procedures
  Document and User's Guide. Deliver updated
  Requirements and Design Documents. Deliver
  Maintenance Manual for as-built system.  
  Documented source code made publicly available
  via the Web.
• D. Final Report Delivered (3/15/05)

15
Interdisciplinary Team

• USGS NIISS
• Tom Stohlgren NIISS Director
• USGS HQ
• Gladys Cotter BRD Assoc. Chief Biologist
• Bill Gregg IS Program Manager
• Chip Groat USGS Director
• CSU NREL
• Robin Reich
• Mohammed Kahlkan
• SSAI
• Rob Baker
• Dave Kendig
• Nick Pell
• Rob Simmon
• David Obler

16
Interdisciplinary Team

• NASA GSFC
• Jim Smith Code 920
• Jeff Pedelty Code 923
• Jeff Morisette Code 920
• Curt Tilmes Code 922
• John Dorband Code 935
• Jacqueline LeMoigne Code 935
• Jim Fischer Code 931
• John Schnase Code 930
• NASA HQ
• Ron Birk Code YO
• Ed Sheffner Code YO
• Alex Tuyahov Code YO
• Woody Turner Code YS
• Diane Wickland Cody YS

17
Parallel Kriging

• Jeff Pedelty
• NASA Goddard Space Flight Center

18
MODIS NDVI Time-Series

• Jeff Morisette
• NASA Goddard Space Flight Center

19
Public InterfaceCurrent Deliverables

• Rob Baker and David Kendig
• SSAI
• John Schnase
• NASA Goddard Space Flight Center

20
Public InterfaceMilestones F, O1, C Delivery
Schedule

• By 8/15/03
• New website
• SWE documentation
• Ability to run canonical examples from website
  using user-set parameters
• By 9/15/03
• 16-node (?) cluster bundled with Milestone F
  software and delivered to USGS / NREL

21
USGS Status Report

• Tom Stohlgren
• USGS National Institute of Invasive Species
  Science

22
NASA HQApplications Update

• Ed Sheffner
• NASA Office of Earth Science, Code YO

23
Lunch
24
Big Problem

• The ISFS Team

25
Big ProblemChallenge

• Could go something like this
• Produce a comprehensive, continental-scale
  assessment of habitats vulnerable to invasive by
  Cheat Grass over the next five years
• Or
• Produce a wall-to-wall distribution map for Salt
  Cedar in the United States
• Or
• Document the - 30 to 5 year continental-scale
  invasion trend for _____

26
Big ProblemRationale

• Part of our strategy for operational scaling
• Cerro Grande gt RMNP gt GSENM gt ???
• Milestone F requirements
• Public demand
• IS hot topic!
• Our project needs to respond AND shape
  expectations
• Good politics
• Were ahead of the curve, but its a large and
  fast moving wave
• For invasive species, its location, location,
  location AND timing, timing, timing
• Good science
• Need to continue to ground our national goals in
  real understanding
• Short-term need for brute-force, enumerative
  approaches
• Relative merits of an autecological approach

27
Big ProblemQuestions Round 1 Brainstorming

• What are the priority DOI / USGS invasives?
• How do we scope a national goal?
• What are the appropriate modeling techniques?
• What field data are available to support the
  effort?
• What remote sensing data are needed?
• What are the computational issues?
• What the steps toward iterative improvements in
  fidelity?
• Are the necessary partnerships in place for this?
• Are the politics in place? Who else do we involve
  within USGS?
• How do we implement this? Next years steps? Out
  years?
• How do we get the word out? Publication, PR
  strategy?

28
Mississippi State University

• Jon Arvik, Lori Bruce, John Madsen
• GeoSpatial Sciences Institute

29
REASoN CANThe Invasive Species Data
ServiceToward Operational Use of NASA ESE Data
in the USGS Invasive Species Decision Support
System

• John Schnase
• NASA Goddard Space Flight Center

30
Rationale

• A central challenge to meeting the invasive
  species threat is the problem of searching and
  aggregating data across heterogeneous and often
  domain-specific repositories.
• The essential task of bringing together the
  georegistered satellite data and biological data
  required for invasive species work is a
  fundamental bottleneck to developing new
  applications and pursuing new science questions
  in this area.

31
Modeling Approach
Output GIS - Spatial Statistical Dynamic Models
and Maps
Trend Surface Analysis With Stepwise Multiple
Regression Using OLS, GLS, SAR, or Exhaustive
Regression
Input Variables (150) Remotely Sensed
data (ETM, SPOT, MTI, EO1, etc.) Derived Remote
Sensing (Vegetation Indices, PCA Tasseled Cap,
other) Biotic/Abiotic Data Topographic
Data Species Data Vegetation- Forest Data Soils
Characteristics Cryptobiotic Crusts Wildfire
Severity Biodiversity Air Pollution Geology,
Other Environmental Data
Hot spots of native biodiversity Distribution
of non-native species Potential spread
of invasive species. Barriers to rapid
invasions. Corridors that may accelerate
invasions. Economic and environmental risk
assessments, vulnerability of habitats to
invasion. Priorities for control and
containment.
Testing if There Is Spatial Auto-Correlation In
the Residuals
No
Final Trend Surface Map Large - Small Scale
Variability
Yes
Testing if Residuals Cross-Correlated with Other
Variables
Yes
Yes
No
Model Residuals Using Co-Kriging
Regression Trees Classifications
Model Residuals Using Kriging (Universal,
Ordinary, other)
32
Data Ingest
33
Project Overview

• We propose to build an Invasive Species Data
  Service (ISDS) to provide customized, easily
  accessible data products and tools to support
  invasive species management and policy
  decision-making.
• The ISDS will be a networked service that
  integrates a suite of NASA ESE data providers
  with the data resources of the National
  Biological Information Infrastructure (NBII).
• Aggregated ISDS data will feed directly into the
  National Invasive Species Forecasting System,
  which is a core component of an invasive species
  decision support capability being developed
  jointly by the USGS and NASA.
• In building the ISDS, we will refine the notion
  of Web-based service interoperability using SEEDS
  principles to specialize EOS Clearing House
  (ECHO) technologies.

34
Project Overview

• The result will be a tailored interface that
  combines biological and earth science data to
  meet the specific needs of a large and expanding
  community of ecologists and natural resource
  managers who deal with invasive species.
• A broadly representative users group will help
  shape development of the ISDS and align its
  activities with current and future needs.
• The work will contribute to NASA's plans for
  future ESE data systems by engaging a new client
  community that has a focused, thematic, and
  interdisciplinary data integration problem of
  national importance.
• The ISDS will be made available through NBII and
  the USGS National Institute of Invasive Species
  Science.
• This work will lead to a fully operational
  capability of national scope vital to
  understanding and managing the effects of
  invasive species on human health, the economy,
  native biodiversity, and ecosystem processes.

35
ISDS Objectives

• Create a capability to combine ESE data products
  from selected satellite missions with selected
  biological field, experimental, and collections
  data of the National Biological Information
  Infrastructure to produce thematic,
  interdisciplinary data products for invasive
  species management and policy decision-making
• Use SEEDS guiding principles to create an
  extensible technology framework for
  interdisciplinary data subsetting and aggregation
  which will result in easily-accessible, merged
  products tailored to the needs of future invasive
  species decision support systems
• Contribute to the SEEDS formulation effort by
  engaging a new community of users with an urgent,
  focused, national-scale data integration need

36
ISDS Objectives

• Integrate these new capabilities into a coherent
  and comprehensive solution of national scope the
  Invasive Species Data Service Integrate the
  Invasive Species Data Service into the emerging
  National Invasive Species Forecasting System
• Expand and consolidate a broad coalition of users
  from across the invasive species research,
  education, and applications communities
• Make the resulting capability broadly available
  on a sustainable basis through the USGS National
  Institute of Invasive Species Science

37
Modeling WorkflowApplication Layer
Output GIS - Spatial Statistical Dynamic Models
and Maps
Trend Surface Analysis With Stepwise Multiple
Regression Using OLS, GLS, SAR, or Exhaustive
Regression
Input Variables (150) Remotely Sensed
data (ETM, SPOT, MTI, EO1, etc.) Derived Remote
Sensing (Vegetation Indices, PCA Tasseled Cap,
other) Biotic/Abiotic Data Topographic
Data Species Data Vegetation- Forest Data Soils
Characteristics Cryptobiotic Crusts Wildfire
Severity Biodiversity Air Pollution Geology,
Other Environmental Data
DSSProducts
Modeling
Hot spots of native biodiversity Distribution
of non-native species Potential spread
of invasive species. Barriers to rapid
invasions. Corridors that may accelerate
invasions. Economic and environmental risk
assessments, vulnerability of habitats to
invasion. Priorities for control and
containment.
Testing if There Is Spatial Auto-Correlation In
the Residuals
No
Final Trend Surface Map Large - Small Scale
Variability
Yes
Testing if Residuals Cross-Correlated with Other
Variables
Yes
Yes
Ingest
No
Model Residuals Using Co-Kriging
Regression Trees Classifications
Model Residuals Using Kriging (Universal,
Ordinary, other)
38
ISFS Architecture
39
ISFS Architecture
Carbon
ISDS
???
CT
REASoN
40
ECHO

• ECHO (The Earth Observing System (EOS) Clearing
  HOuse) implements a notion of service
  interoperability that appears to be well suited
  to the Invasive Species Data Service (Pfister et
  al., 2002).
• ECHO specifications define a way to publish and
  discover information about Web services.
• The term Web service describes specific
  business functionality exposed by an
  organization, usually through an Internet
  connection, for the purpose of providing a way
  for other organizations or software programs to
  use the service.
• ECHO is being developed to provide flexibility to
  NASAs EOS Data and Information System to better
  meet the needs of the science community. This
  flexibility includes providing (Application
  Program Interfaces) APIs for alternate user
  interfaces to support special needs in data
  access, providing APIs for brokering data
  services so specialized data services can be
  shared across the user community, and providing
  APIs for easy participation by a broad data
  provider community.
• Another major goal of ECHO is to support new data
  access paradigms that are not supported by
  todays EOSDIS architecture.

41
ECHOArchitecture

• The core component of ECHO is its clearinghouse
  into which providers can place a copy of their
  metadata and clients can perform geospatial,
  temporal and keyword based searches of those data
  using an open set of XML-based APIs.
• Data providers can register with ECHO and provide
  copies of their metadata through an XML file used
  to describe a business entity and its Web
  services.
• Programs and programmers use the ECHO registry to
  locate information about services and, in the
  case of programmers, to prepare systems that are
  compatible with advertised Web services or to
  describe their own Web services for others to
  call.
• XML provides a cross-platform approach to data
  encoding and formatting. SOAP, which is built on
  XML, defines a simple way to package information
  for exchange across system boundaries. SOAP
  bindings for HTTP are built on this packaging
  protocol and define a way to make remote
  procedure calls between systems in a manner that
  is independent of the programming language or
  operating system choices made by individual
  organizations.
• This cross-language, cross-platform approach
  simplifies the problem of making systems at two
  organizations compatible with each other.

42
ECHOPartners

• ECHO Data Partners participate with ECHO to
  provide Earth science data in the form of their
  metadata holdings.
• These metadata are cached within the
  clearinghouse and available for search and
  retrieval as well as navigation and discovery.
• Data Partners also provide a mechanism to allow a
  client (user or machine interface) to access data
  holdings. Partners have complete control over
  what metadata is represented in ECHO on their
  behalf. They can insert new metadata, modify
  existing metadata and remove old metadata .
• Current ECHO Data Partners include the Goddard
  Earth Science (GES) and EROS Data Center (EDC)
  Distributed Active Archive Centers (DAACs). The
  GES DAAC, with its long time-series vegetation
  and thermal infrared brightness temperature data
  sets and MODIS data support will be particularly
  important as will the Landsat and land processes
  collections of the EDC DAAC.

43
NBII

• The biological holdings of the National
  Biological Information Infrastructure are
  currently not a part of the ECHO framework, but
  will be integrated through this project.
• NBII is a broad, collaborative program to provide
  increased access to data and information on the
  Nation's biological resources in much the same
  way that the ESIP Federation works to broaden
  access to Earth science data.
• The NBII links diverse, high-quality,
  non-proprietary biological databases, information
  products, and analytical tools maintained by NBII
  partners and other contributors in government
  agencies, academic institutions, non-government
  organizations, and private industry.
• NBII partners and collaborators also work on new
  standards, tools, and technologies that make it
  easier to find, integrate, and apply biological
  resources information. Resource managers,
  scientists, educators, and the general public use
  the NBII to answer a wide range of questions
  related to the management, use, or conservation
  of this Nation's biological resources.
• Additional information about NBII and its many
  partners can be found at the NBII website at
  www.nbii.gov.

44
Implementation Plan

• (Task 1) Software Engineering Plan We will
  employ software engineering best practices
  throughout the project. We will produce and work
  to a comprehensive Software Engineering /
  Development Plan, Configuration Management Plan,
  Quality Assurance Plan, Requirements Document,
  and Test Plan and Procedures Document. All source
  code will documented and made publicly available
  on the projects website.
• (Task 2) Build ECHO Lite at USGS The
  Invasive Species Data Service will be based on
  ECHO technologies and encapsulate a subset of its
  capabilities for tailored use by the invasive
  species community. The first step is to host the
  ECHO clearinghouse framework at the USGS National
  Institute for Invasive Species Science. We refer
  to this version as ECHO Lite.

45
Implementation Plan

• (Task 3) Make NBII an ISDS Data Partner An
  ECHO (or ECHO Lite / ISDS) data partner is an
  entity that participates with ECHO to provide
  data in the form of its metadata holdings. These
  metadata are then available for search and
  retrieval as well as navigation and discovery
  along with the aggregated metadata from other
  ECHO data partners. We will build mappings
  between appropriate elements of the ECHO data
  model and the data models used by NBII. We will
  develop translation routines that allow NBIIs
  XML metadata to be formatted according to ECHOs
  DTDs for both collections and lower-level data
  granules where possible. We will also create an
  automated mechanism for updating the clearing
  house as new information arrives at NBII.

46
Implementation Plan

• (Task 4) Build an ISFS System Client An ECHO
  client is an entity that has a user or
  machine-to-machine interface that communicates
  with ECHO via its APIs in order to perform
  operations on ECHO holdings. As shown in Figure
  6, we will develop a client that allows the
  Invasive Species Forecasting System to draw on
  the ECHO Lite services of the Invasive Species
  Data Service. We will use various ECHO tools,
  APIs, and DTDs to develop the client.

47
Implementation Plan

• (Task 5) Build an ISDS Public Client We also
  want to develop a mechanism whereby users can
  conveniently register their personal or project
  data sets with the ISDS and access the services
  of the ISDS directly without having to use the
  Invasive Species Forecasting System. To do this,
  we will build a general mechanism for data
  partnering based on that used for institutional
  partners.
• (Task 6) Deploy into Operational Use In
  concert with the development components of the
  project, we will be producing documentation and
  providing the training necessary to create the
  expertise needed within the USGS to deploy these
  capabilities operationally and maintain the
  service into the future. We will design and
  implement a comprehensive transition protocol to
  guide the hand-off.

48
SEEDS

• NASAs Strategy for the Evolution of Earth Data
  Systems (SEEDS) starts from the premise that
  systems and services must be informed by, and
  supportive of, key science concerns and
  questions.
• It also recognizes that individual scientists and
  disciplinary communities of scientists are key
  consumers and producers of data products and
  therefore must be key partners.
• To insure community engagement, we will use SEEDS
  principles to guide an iterative approach in
  which various stakeholders will be deeply
  involved in the effort.
• Ecologists and land managers who already have
  established collaborations with the National
  Institute of Invasive Species Science will be
  part of the development team.

49
SEEDS

• The main objective is to foster community-wide
  participation in the development and use of these
  new services, and specify as clearly as possible
  the types and levels of services needed to make
  it useful, strategies for technological infusion.
• Wherever possible, we will attempt to exploit the
  first-mover rule, which advocates faster
  development of high-priority features that will
  encourage the commitment and continued engagement
  of the end-user community.
• At all stages, we will actively seek community
  feedback on the usage experience of the service
  and the information products produced by the
  ISDS. We will then develop refinements based on
  this feedback and fold these experiences back
  into the SEEDS formulation process.

50
Preliminary Time Line
51
Budget

• Ref. Proposal Cost Plan (p. 22) and Cooperative
  Agreement Payment Schedule (p. 29) for details
• Staffing
• 0.25 FTE Senior Analyst / Technical Manager
• 0.25 FTE Professional clerical
• 2.00 FTE Programmer / Analysts
• Travel, Administrative Fees, USGS Subcontract for
  managing community / advisory group meetings.

52
Discussion
53
Invasive SpeciesScience Team Meeting

• John L. Schnase
• NASA Goddard Space Flight Center
• Greenbelt, Maryland
• Thomas J. Stohlgren
• USGS National Institute of Invasive Species
  Science
• Fort Collins, Colorado
• 10 July 2003

54
Agenda

• Wednesday, 9 July 03
• NASA Status Report (ESTO/CT Milestones, F,O1, C
  G Carbon Years 2 3)
• USGS Status Report (ESTO/CT Milestones, F,O1, C
  G Carbon Years 2 3)
• NASA HQ Report (Program Plans, NASA/USDA, )
• -----
• Big Problem (Priorities, issues, strategies,
  )
• MSU Collaboration (Opportunities, overlaps, )
• REASoN CAN (Initial project overview, HQ
  guidance )
• Thursday, 10 July 03
• Milestone F (Discussion, next steps, task
  assignments)
• Big Problem (Discussion, next steps, task
  assignments)
• MSU Collaboration (Discussion, next steps, task
  assignments)
• REASoN CAN (Discussion, next steps, task
  assignments)
• Misc. (Discussion, next steps, task
  assignments)

55
(No Transcript)
56
Milestones F, O1, B

• By 8/15/03
• New, finished website (Baker)
• SWE documentation (Baker)
• Ability to run canonical examples from website
  using user-set parameters (Kendig, Pedelty)
• By 9/15/03
• n-node (50K) cluster bundled with Milestone F
  software and documentation and delivered to USGS
  / NREL(SSAI, Dorband)

57
Big Problemor Problem, Large

• Challenges
• Produce a comprehensive distribution map for
  tamarisk on the Colorado watershed
• Produce a comprehensive distribution map for
  cheat grass in Colorado and California
• Task (Team) - Initial steps to be completed by
  12/31/03
• Field data assessment acquisition (Crosier,
  Graham, Madsen)
• RS data assessment acquisition (Morisette,
  Pedelty, Bruce)
• Temporal / hyperspectral signature assessments
  (Morisette, Pedelty, Bruce)
• Model assessment development (Stohlgren, Reich,
  Madsen, Moristte, Pedelty, Smith, Schnase)
• Parallel algorithm/code assessment development
  (Pedelty, Morisette, Reich)
• Problem definition, refinement, outreach, PR
  (Stohlgren, Smith, Schnase)
• NASA/USGS Coordination (Groat, Birk, Sheffner,
  Cotter, Hazeltine, Gregg, Posson, Stohlgren,
  Schnase)
• Fall geospatial modeling class at GSFC (Reich,
  Morisette)
• Big Problem White Paper / Strategic Plan
  (Schnase, Stohlgren, Sheffner)

58
REASoN

• Next steps
• Negotiations?
• When do we start?
• Planning Meeting No. 1
• (Schnase, Stohlgren, Smith, Pedelty, Morisette,
  Pfister, Frame, Graham, ???)
• Staffing

59
Miscellaneous

• Contact info
• PPTs
• Maui
• ESA
• USDA
• NISC
• Pubs

60
Invasive SpeciesScience Team Meeting

• John L. Schnase
• NASA Goddard Space Flight Center
• Greenbelt, Maryland
• Thomas J. Stohlgren
• USGS National Institute of Invasive Species
  Science
• Fort Collins, Colorado
• 10 July 2003