Y E A R 1

1. Disturbance Mapping Goals Q1 Q4 Q3 Q4 Q2 Q3 Q1 Q2 Q4 Q1 Q2 Q3 Y E A R 2 Y E A R 1 Y E A R 3

3. Tele con • Goal: • Would you add another theme? • What is missing ? • The comments: • Did this summarize well? • Comments that warrant discussion? Should save most of the discussion for the meeting, this is meant to inform the discussions at the meeting, not start them now. • The 90 minutes to discuss each groups activities • 30 (?) minutes to present, then open up for discussion? • Please specifically provide: • Dependencies (your group needs what from whom, and should be delivering what to whom) • Timeline • Algorithm specifics: input – code/package - • Deliverables

4. Blast-off Meeting : NAFD III Overall Goal: Coordination of activities for effective, interactive flow of information and sharing of data Slides 2-4 Slide headings are themes that were universal across the groups, with comments gleaned from your contributions. Comments are color coded: Disturbance mapping Validation Assessment Causal processes mapping Regrowth mapping Slides 5-6 Suggested agenda

5. Gain familiarity with AMES and address specific issues • Age of archive, file structure, coding language available code libraries (?), project interfaces • Is there currently a way to extract data from the NEX ? • What ancillary data is already on the NEX system? • A presentation/demonstration of NEX might be useful • Better understanding of issues surrounding portation of TImeSync to NEX • Port TimeSync software to NEX at ARC and enable use via the web • Need to understand how to code new modules for NEX – is there an API to allow parallel implementation?  Who has the responsibility to take serial C code and “vectorize” it for NEX (if that’s the right term)? • how to extract reflectance time series data for FIA remeasured plot data without violating MOU. • Nationwide processing of causal models. Is this going to “happen” at Ames ? 3 levels of probability or classification models

6. Coordinating data / data flow • Coordinating validation with training data for causal models. • models including contextual metrics along with trajectory parameters and ancillary data • Better understanding of how to work with FIA re-measured plot data. • Feed disturbance agent interpretations to Moisen team • Draw and interpret initial sample using ancillary disturbance datasets • Compare VCT year of disturbance against FIA age • The sampling blocks as the unifying analysis unit of all the groups for the first year or so? Will they validation sampling block be coordinated with the FIA plot data? What % will they pick up? • how do Imagery and Map QC/QA diagnostics and reports flow back to Maryland from ARC? • How will data for validation sample block location (magnitude, masks, SR imagery, FI files and (composites)) flow out of AMES to UMD and the rest of the group? • How will inter-coordination of NAFD groups work – has to be more bottom up and equal without a “project manager”

7. Discussion and feedback about the project as a whole and each component of NAFD phase 3 • Intermediate and final data products.It would helpful to outline the products each team is responsible for, with a timeline. This includes a discussion about uncertainty associated with these products. • VCT adaptations.Do we have a mechanism or desire to keep tract of adaptations and possible user improvements for incorporation into the “final run”? • Parallel causal models. we want to make sure the group understands the approach. • An overall data flow chart. showing which code modules will be implemented at ARC (and which “offline” at UMD or GSFC), as well as a detailed discussion of the operational status of each module.   This should also include back-of-the envelope calculation of product sizes and the data traffic volume between UMD and ARC. •  A discussion of QA (in addition to validation) approaches.   • Discussion of and feedback on validation sample design • Learn about the plan for VCT map products: thematic detail and product timing • Understand the plan for characterizing variability in recovery trajectories • Expected Final UMD NAFD III Products are disturbance Year Maps & disturbance magnitude (with Metadata, Spatial and Temporal aggregation TBD, Revisiting Jeff’s list from 2007….) • How will inter-coordination of NAFD groups work? Will each group have a “go-to” person, or telecom per quarter decided ahead of time and each team is responsible for scheduling one per year?

8. Working Agenda: Tuesday June 14th • 8 am • meet Rama at visitor center to AMES for badges and entrance. • 8:30 – 10:30 • tour AMES/NEX • 10:30 - 11 am • Ed Sheffner: a NASA perspective • 11-12 am • Introduce NAFD phase III Synthesis flow chart timeline • Working strawmanof individual group data needs, deliverables & timelines • Calibration data 6 months in available • 12-1 pm • lunch !!! • 1- 4 pm • getting to know NEX workshop • 4-5 pm • Revisit and update NAFD III working strawman • Reflect, discuss • 7-9 • Dinner?

9. Working Agenda: Wednesday June 15th • 8 am • meet Rama at visitor center to AMES for badges and entrance. • 8:30 – 10:00 am • Discussion of the Disturbance Mapping Component • 10:15 – 11:45 am • Discussion of the Validation Component • 12:45 -1:45 pm • Lunch !!!! • 2:00 – 3:30 pm • Discussion of the Regrowth Component • 3:45- 5:15 pm • Discussion of the Causal Process Mapping Component • 5:15 - 6 pm • Revisit and update fleshed out NAFD III straw man • Agree on quarterly telecon schedule