GEON: The Geosciences Network

1
GEON The Geosciences Network

• Chaitan Baru
• San Diego Supercomputer Center (SDSC)
• California Institute for Telecommunications and
  Information Technology (Calit2)

2
Data Management
DATA COLLECTION
DATA PUBLICATION
DATA ACCESS
DATA ANALYSIS
3
GEON Background

• See website www.geongrid.org, and portal
• Began as a collaboration among 15 institutions
• Goals
• Provide a Cyberinfrastructure-based Interpretive
  Environment for Earth Science research, e.g. for
  data acquired in EarthScope
• Support for data discovery
• A platform for data integration
• Train students and geoscience researchers in
  state-of-the-art and advanced IT concepts, i.e.
  technical aspects of geoinformatics
• Two-Tier approach
• Develop working systems, while also doing
  research and building advanced prototypes
• The focus this year is on registering content and
  tools at portal and providing a number of
  reference datasets
• The end goal is to provide science
  infrastructure. Support for both hosted and
  non-hosted data

4
Topics for Today

• LIDAR data management and processing in GEON
• Courtesy Prof. Ramon Arrowsmith, Arizona State
• Data Registration
• Linkage with other geoinformatics, CI projects
• Wont cover details of grid computing,
  visualization, data integration,

5

• Example Data Set
• Northern San Andreas fault and associated
  marine terraces.
• Flown February 2003
• Funded by NASA in collaboration w/ USGS.
• 418 Square Kilometers

1.2 billion data points
6
1.1 million data points To produce this DEM
7
(No Transcript)
8
(No Transcript)
9
(No Transcript)
10
(No Transcript)
11
(No Transcript)
12
(No Transcript)
13
(No Transcript)
14
(No Transcript)
15
(No Transcript)
16
(No Transcript)
17
(No Transcript)
18
(No Transcript)
19
Lidar Processing Workflow Using Kepler
Analyze
Visualize
Subset
move
process
move
render
display
Fledermaus (or ASU OpenGL tool LViz)
iView3D/Browser
CreateScene file
sd
d2
d2 (grid file)
d1
d1
d2
NFS Mounted Disk
20
LiDAR DATA SETS COMMITTED (?) TO GEON
DISTRIBUTION
Data Set of points Schema Source
Northern San Andreas (NSAF) 1.2 billion 10 column (x,y,z attributes) NASA / USGS
West Rainier 800 million 1 billion (est.) 10 column (x,y,z attributes) NASA / USGS
Southern SAF Laser Scan ?? Likely to be 5 billion ?? NCALM
NAPA 500M ?? NCALM
E. CA Shear Zone (E. Mohave) 500M ?? NCALM
Antarctic Dry Valleys 10-100M? ?? Bea Csatho (Ohio State)
Hector Mine EQ 10-100M? ?? Ken Hudnut (USGS)
Alvord (Tripod) 16.6M 4 column (x,y,z intensity) John Oldow (U. Idaho)
21
Current Activities

• Release of GLWGEON LIDAR Workflow capability
• Incorporation of ground-based LIDAR data
• Ground-based Data Collection Workshop, organized
  by John Oldow, April 6-7, 2006, SDSC/Calit2
  Synthesis Center. Sponsored by NSF

22
Data Registration GEONsearch
www.geongrid.org
23
GEONsearch and myGEON
Search Condition(s) spatial temporal
concept
GEON Catalog
GEONsearch
Log
Gazetteer
Geologic Age
Web services
extracted information/indexes
GEON Datasets
24
The 1-2-3 of GEON Data Registration

• Register dataset, tool to index terms
• Allows users to more easily discover relevant
  resources
• Register dataset schema to ontology
• E.g. Age_MA ? Geologic Age
• Could be relational dbms, shapefile, Excel,
  netCDF,
• Allows discovery of datasets that have
  information of interest, e.g. all datasets that
  have velocity data
• Register data values to ontology
• E.g. Jur ? Jurrasic Age from Geologic Age
  ontology
• Allows advanced data integration, e.g. integrate
  Paleobiology data with Paleostrat, or Neptune,
  Janus, etc.
• Prerequisite ontologies need to be defined (by
  community), represented in OWL, and registered

25
GEON Data Registration
Ontology Registration
Dataset Registration (hosted)
Data Item (Schema) Registration (hosted /
non-hosted)
Data Item Detail Registration (values)
Service Registration
Resource Registration
26
Data Registration Activities

• GEON Mini-Workshop on Information Exchange from
  Distributed Data Systems, Feb 7th, 2006
• Co-organized by Chuck Meertens, UNAVCO/GEON and
  Ben Domenico, Unidata/LEAD
• Goal Register netCDF/OpenDAP data in GEON portal

27
GEON IDV

• Courtesy Dr. Chuck Meertens, UNAVCO
• Adapt IDV for earth science datasets
• Incorporate web service calls in IDV to invoke
  GEONsearch
• and access and manipulate netCDF-based 3D, 4D
  data sets

28
Geo-ontologies

• Data Registration and Ontology meetings
• GEON Data Registration meeting, March 10-11, SDSC
• Volcano Ontology meeting, sponsored by NASA SESDI
  project (Semantically-Enabled Scientific Data
  Integration), Feb 16/17, SDSC
• An opportunity for the community to develop
  community standards for knowledge representation,
  e.g.
• Schemas, controlled vocabularies, ontologies
• And, choose a common representation system, e.g.
  OWL

29
Linkage with Other Geoinformatics, CI Projects

• CUAHSI Hydrologic Information System (HIS)
• HIS is using GEON data registration and search
  capability, and mapping services, and GEON PoP
  node structure and the GEON Pack (i.e. a common
  software stack),
• CHRONOS
• Database federation
• Hosting Paleo-pollen databases
• Hosting NAVDAT
• IT collaborations with NCMIR/BIRN (NIH), SESDI
  (NASA), LEAD, GRASP (Grid Benchmarking), Globus
  (Data Replication Service middleware)

30
E.g, CHRONOS Federated Databases

• The following databases are all part of the
  CHRONOS Federated Database at SDSC based on IBMs
  DB2 Information Integrator. Federated database is
  registered in GEON.
• Neptune
• PaleoStrat
• PaleoBiology
• Janus
• TimeScale
• FAUNMAP
• MIOMAP

31
Opportunities

• Leverage CI from existing projects in same or
  even different disciplines
• Adopt a service-oriented architecture (SOA)
• i.e. standardize on Web service interfaces for
  tools, applications, and data
• E.g. Web Mapping Services for map image services,
  and WFS, WCS, and other standards, e.g for
  accessing geologic maps, gravity data, sensor
  data,
• Need to deal with .NET and Java compatibility
• Develop centralized community services, e.g. for
  LIDAR processing
• Develop community standards for knowledge
  representation
• Schemas, controlled vocabularies, ontologies.
  Choose common representation system, e.g. OWL
• Organize community meetings, workshops,
  conferences
• Develop Meta-workflow frameworks
• Support inter-operation among different
  scientific workflow systems
• There may be an opportunity to work through a
  proposed new GSA Division on Geoinformatics and
  AGU working group on IT
• Geoinformatics 2006. See www.geongrid.org/geoinfor
  matics2006