showShow Editing Controls
You must be logged in to an account with appropriate access to edit this page.


Team Members: Mike Taber (Curriculum developer and team facilitator), Liping Di (Data Manager), Frank Granshaw (Educator), Wei Luo (Scientist), Meixia Deng (Tool Specialist)

2008 GeoBrain AccessData Team

Meeting Room:

Pre-meeting Sharing Space

Please introduce yourself to your team members. Give a brief description of your role in facilitating the use of data in education. You can also post links, files, or images.

To add text, files, or images to this page, click the "Show Editing Controls" link in the upper right of this window, then click "Edit this page." Click the Editing Help link for details. Note that the infrastructure of these editable web pages are still under development. As possible, avoid simultaneous editors.

Add Pre-Meeting Notes here:
On April 21, the GeoBrain team discussed possible science questions to explore, under the auspices of Global Warming. One idea was to look at temporal and spatial ice cover changes in the polar region. Another idea was to explore ice-mass changes on Greenland, although DEM data does not cover Greenland at a desirable resolution. We did discuss the idea of structuring the question around "What if _____ changes, then sea-level will ____." Focusing on a consequence to coastal areas is another idea.

Session 1 - Thursday Morning
Meet your team members. Learn about the data, tools, and expertise represented on your team. Review DataSheet(s) and explore data and tools.

Team members meet each other and share their experiences and viewpoints on using data in education. Review and discuss DataSheet(s) begun by the data representative(s) for your team. Explore datasets and tools and consider how the expertise on the team can complement them. If you haven't already done so, narrow down the range of datasets the team is considering using to a manageable number.

Add Session 1 Notes here:
GeoBrain Data Sheet (Microsoft Word 101kB May1 08)

Meixia demonstrated GeoBrain data access to the team.

The EET target user is the faculty member who wants to "mine" data for a student centered research project.

Can start with a google earth map interface. When you zoom in the window bound box is defined. User can pre-define the lat long bounding box. Can specify by location, like state or county, city, etc.... We chose Oregon. Maybe we want to get some watershed data on Columbia County, OR. Prompted for Raster or vector data selection. (What if the user does not know the format?)

Now finding data related to the research area... At this point, GeoBrain is serving as a data portal access, not yet an analysis tool. Later, the user will use GeoBrain for analysis

Now user can choose data "raster data selection." Can specify date/time and other attributes. All the instruments are in Acronyms and may not be know for the user. For now, we are doing SRTM...

User can customize the data for their needs.

User can change the resolution. GeoBrain does this on the fly for the user. (i.e., original resolution of SRTM is 30m - we changed to 100m).

Can now patch the four together using the "mosaic" function under "Raster." Click and add each layer from the data list. Format for Float32...

Through the web service call, we can make a web service call on Grass_Raster_Stream Extraction. User can get a sense of the service (some metadata).

Add the patch layer to the value field, with threshold of 100 and invoke the web service for the geotiff dataset.

Note that the running time is due to server process the requests, then sending to the user. Add to current project after web service call.

Can save and export the project to kml for Google Earth...Launch directly into Google earth. GeoBrain does export to desired coordinate system, with out user having to worry about re-projecting.

We now chose Landsat bands 3 and 4 (looking at vegetation).

Web algebra service is there for computing NDVI (Land4 minus land3).

Can you render the DEM as a relief map? Overlay LandSat? Look at vegetation and streams?

Transparency on layers is on the server side, not user side

Chapter 1 - Landsat data on my backyard - export to desired tool: ArcGIS, MyWorldGIS, Google Earth

Chapter 2 - online analysis

Chapter 3 - processing model

Couple of possible scenarios: Tsunami run up, sea-level rise, other geohazards. This could be used to generate a series of scenarios, grab a bunch for stacking screen shots. Give the novice user a simple controller to animate.

Data access portal requires knowledge of data types and will need to have a lots of metadata.

If we have users get landsat data, users will need to know what the different bands mean.

Geobrain is basically a WFS accessor to data

Session 2 - Thursday Afternoon
Brainstorm data-use storylines

Brainstorm a set of possible storylines for valid investigations of the dataset(s) you have selected. Come up with at least one compelling scenario that will give users a reason to work through the technological steps necessary to perform an analysis of the data.

The Activity Outline Guide (Microsoft Word 42kB Apr9 08) provides an outline for the minimum information needed for the team's activity outline.

Add Session 2 Notes here:

Do we want to stick with the geohazard approach? For tsunami run up, we are trying to determine who is going to be safe, who isn't, what are the evacuation routes? This could be on a 10m run up...
Slope stability takes a look at identifying slopes of a certain grade/angle, and can we some how meld that with data such as vegetation cover and soil type? Cross search these defining a reduced risk or high risk. This is another risk analysis.
For slope, we need to test more - doable, is available in GRASS. Is soil/vegetation available?
Defining a watershed by using the stream extraction feature
Geobrain as a research for data tool...a platform for accessing data

Definition of the geographic area using the google maps is a powerful feature. Allows for the user to zoom in on their backyard. Google earth can give you the visualization. Once you visualize, want to get real data, learn how to derive information/handling the data...
Geosciences is a placed based discipline. This activity has to have a component of drawing people back to their own locality.
Make a "grab" for a problem simple enough, then do the cookbook, then back to inquiry with my background.
What is the grabber?
Tsunami run-up on SRTM, making contours (not yet available), then convert to shaded relief, export as KML, then overlay onto Google Earth. The case is Cannon Beach, OR.

Sessions 3 and 4 - Friday Morning
Select a data-use scenario and perform a proof-of-concept check

Use the complementary expertise on the team to check that the task you are envisioning can actually be completed in an educational setting. Identify a target grade level for the activity and choose a working title.

Please limit the scope of the activity to tasks that can be accomplished by accessing existing data and tools. Discuss and agree upon the content limits of the activity as well. Consider that the major goal of these activities is to develop user familiarity with the data and tools.

Add Session 3 and 4 Notes here:

Tsunami run-up risk factors:population centersExisting reliefLateral extent run-up - direction and vertical extent.
Places Astoria, Cannon Beach, Seaside Oregon
We could do volume of water that can be contained with in a confined bay or river run-up.
See activity sheet for more information on the tasks.
GeoBrain Activity Outline (Microsoft Word 605kB May3 08)

Sessions 5 and 6 - Friday Afternoon
Develop your case study storyline and outline the procedures for data access and analysis Case Study Development

Record ideas, bullet points, or actual text that will become part of the case study to introduce users to the issues and concepts of the activity. Gather links for appropriate images, diagrams, and background text.

Data Access and Analysis Procedures

Record the name and URL of all datasets and access/analysis software tools to be used. List the major tasks users will complete, then perform a deliberate walk-through of each task to capture the full sequence of procedures. Give special attention to the most difficult or least intuitive steps, and note points in the sequence where additional information will be helpful.

Add Session 5 and 6 Notes here:

See activity sheet for more information on the tasks.

Session 7 - Saturday Morning
Enhance your step-by-step procedures by adding "About" sections that provide extra information; List several ideas for "Going Further" with the data or tools

Fill in any gaps in your activity outline and add sections that can help users make meaning of the data. Suggest several ideas for the "Going Further" section that challenge users to work with the data and/or tools in other investigations. These suggestions provide launching points for scientific inquiry which is facilitated by the skills learned in the activity.

Add Session 7 Notes here:

Session 8 - Final Team Breakout
Finalize your Activity outline and DataSheet, Generate PowerPoint slides for the report out session, Upload all resources to this page

Create a 2- or 3-slide ppt file for the report out session.

  • Slide 1: Team name, names of team members, and a brief phrase to describe each individual's contribution
  • Slide 2: Working title for your activity, names of dataset(s) and tool(s) utilized
  • Slide 3: Your choice of something to illustrate your team's vision of the completed activity

Attach the file plus any other documents produced by the team to this page. Include final versions of the team's DataSheet.

Add Session 8 Notes here:
GeoBrain PowerPoint Summary (PowerPoint 1.7MB May3 08)