[GLIMS] High Mountain Asia Hazards and Satellite Observations--Pre-AGU workshop

[Jeffrey]

Dear colleagues:
Apologies for cross-listing.  This will likely be the final message on this string sent tothe GLIMS mailing list.
Each of you on the primary recipients' list has indicated what I believe is a confirmation of intentions to participate in the 1-day pre-AGU workshop in San Francisco (Sunday Dec. 11),Venue TBD.  Today some announcements of AGU abstract acceptance and scheduling wentto authors, so I imagine many people now will be making flight reservations (andhotels-- they are filling up!).  I have two requests at this time:
1. Participants should indicate whether you wish to make a science or technology orsatellite data acquisition planning presentation (or other related topic) at the workshop... 5 to 20minutes or whatever is needed.    There's no harm in giving a talk that overlaps with an AGUpresentation.
2. Those of you on the GLIMS list (cc'ed)  who have not already scheduled your flight and are interested in attending the workshop, you are welcome to sign up. However, our meeting venue will be determined soon, and for that we need a final count of participants.  So pleasesignal your wish to participate if that is your intention.  Feel free to forward this solicitationof interest to other people interested in mountain cryosphere or high-mountain hazards.
A few of you have already signaled to me you presentation plan
I append the provisional workshop schedule.

















PROVISIONAL
AGENDA (Dec. 11, San Francisco, venue TBD).  We will compress from this if warranted, but not lengthen the day: MORNING:
8:10 AM - 12:30 PM0. Greet
and light breakfast (fruit, bagels, danish, coffee, tea, water, juice). 30
minutes.1.
Introduction of the meeting and its purpose and agenda, explain also about
meeting #2. Kargel moderate, 5 minutes.2. Find
two reporteurs: 2 minutes3.
Around-the-room personal/professional introductions. 10 minutes.  4. What
is CEOS and the CEOS Hazards/Disasters working group? Green moderate, 5 minutes5. What
specifically do we hope to get out of this meeting? Green moderate, 5 minutes6. Brief
science presentations (5-15 minutes each) on multihazard hotspots 
  Probably about 10 presentations, start with 5 of them, 12 minutes
average each one. 60 minutes. Kargel moderate. 7. 20
minutes break 8. Five
more science and technology presentations, 60 minutes. Green moderate.9. What
satellites/sensors' data can we bring to bear? 10 minutes. Green10.
Group freeform discussion: Where are the multihazard hotspots?  Make a
list. 10 minutes. Kargel.11. What
image data archival/server, data dissemination, data analysis archive/server
options exist that could help us? 
    Green, Raup, and Zemp 20 minutes 
    18 minutes to spare.12.
Lunch 90 minutes.AFTERNOON,
2 PM- 4:45 PM13.
Group thematic discussion: What are the attributes of multihazards, their
frequency, their associated vulnerabilities and overall risks (Ranked list of
various regions) 45 minutes.  Kargel.14. What
satellite data are available and abundant? 30 minutes. Green.15. Of
this list and the highly ranked regions (meaning high hazard, multihazard
processes, high risk), who is willing to sign onto a specific region to serve
as a region advocate and scientific expert for (a) development of a
proposal/presentation to CEOS, and (b) analysis of a snippet of acquired data?
Around the room: 15 minutes. Kargel.16.
Group discussion: Fitting into the High Mountain Asia program and other
regional and global programs. 15 minutes. Green.17. Develop
 outline of a report/proposal/presentation to CEOS Disasters group. With
writing assignments and deadlines. Discussa
written report of the meeting, and where we go next. 30 minutes. (Kargel)18.
Thank you and invitation to continue activities and solicit further community
interest. 5 minutes. (Kargel & Green)








































































       25 more
minutes to spare. 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://nsidc.org/pipermail/glims/attachments/20161004/0303dc16/attachment.html>