A moment of silence for Steve Gebert

1
(No Transcript)
2
A moment of silence for Steve Gebert
Happy fishin, Steve!
3

• Summary of last meeting October 26-27, 2006
• Meeting Goals
• Update the committee on current AOOS and IOOS
  issues, particularly DMAC.
• Discuss AOOS Data Management System Design and
  provide feedback to AOOS Data Manager.
• Discuss quality assurance and quality control as
  it pertains to AOOS.
• Discuss agency contributions to and concerns
  about AOOS operations, particularly DMAC.
• As a component of the AOOS business/operations
  plan, discuss, develop and review the AOOS Data
  Management Plan (basic description of how AOOS
  addresses data issues and policies and insures
  compliancy with IOOS DMAC) that was scheduled for
  AOOS board review in December 2007.

4

• Selected action items
• Solicit candidates for two open AOOS DMAC
  Committee positions present nominations to AOOS
  DMAC Committee. (Work Group 1 McCammon, Schoch,
  Graves)
• Obtain script or templates for PWS FE Portal from
  JPL (Chao). (McCammon, Schoch)
• Present AOOS DMAC nominations and Data Management
  Plan to Governance Committee for approval.
  (McCammon)
• Define standardized requirements and make
  recommendations for ongoing QA/QC. (Work Group
  2 Schoch, Hervey, Chao, Rahe, McClure)
• Develop base maps for AOOS website. (Work Group
  3 Graves, Schoch, Heinrichs, Katrayev, Cermak)
• Merge best set of statewide digital elevation and
  bathymetry data. (Work Group 4 Heinrichs and
  others).
• Provide disclaimer for information delivered
  through AOOS. (IOOS, ARSC, McCammon, Cermak
  form Work Group 5?).

5
Reconciling AOOS DMAC with emerging IOOS standards
IOOS-declared DMAC areas and their standards (Mar
2005)
Metadata IOOS-wide description of data
sets.Standard FGDC-compliant to be
determined Discovery Search for and find data
sets, products and data manipulation
capabilities.Standard to be determined Transport
Access measurements and data products from
computer applications across the
Internet.Standard initially OPeNDAP with
consideration of OGC WFS WCS Browse Evaluate
character of data through commonly available web
browsersStandard initially LAS with
consideration of OGC-compatible GIS web
servers Archival Secure, long-term data storage
using existing and new facilitiesStandard to be
determined
6
The AOOS DMAC Position

• AOOS is refraining from defining standards until
  the system is designated fully pre-operational,
  end-to-end and shown to be interoperable with
  one or more regional associations (within two
  years).
• AOOS has adopted the FGDC metadata standard.
• AOOS uses a combination of flat files, NetCDF,
  HDF, GIS-type files and relational databases for
  data storage.
• Data access and transport are via custom PHP
  scripts and OPeNDAP or FTP. AOOS also will
  deploy web services, e.g., OGC, SOAP, REST for
  access.
• Unique, locally stored data sets are archived in
  two locations.
• IOOS does not provide guidance for QA/QC.
• AOOS is developing new and modified standards to
  be forwarded to IOOS for consideration as
  national standards.

7
Metadata Standards
FGDC metadata standard The Content Standard for
Digital Geospatial Metadata (CSDGM), Vers. 2
(FGDC-STD-001-1998) is the US Federal Metadata
standard. The Federal Geographic Data Committee
originally adopted the CSDGM in 1994 and revised
it in 1998. According to Executive Order 12096
all Federal agencies are ordered to use this
standard to document geospatial data created as
of January, 1995. The standard is often referred
to as the FGDC Metadata Standard and has been
implemented beyond the federal level with State
and local governments adopting the metadata
standard as well.
ISO metadata standard The international
community, through the International Organization
of Standards (ISO), has developed and approved an
international metadata standard, ISO 19115. As a
member of ISO, the US required to revise the
CSDGM in accord with ISO 19115. Each nation can
craft their own profile of ISO 19115 with the
requirement that it include the 13 core elements.
The FGDC is currently leading the development of
a US Profile of the (ISO) international metadata
standard, ISO 19115.
8
ISO 19115 Core Metadata Elements
Mandatory Elements Dataset title Dataset
reference date Dataset language Dataset topic
category Abstract Metadata point of
contact Metadata date stamp
Conditional Elements Dataset responsible
party Geographic location by coordinates Dataset
character set Spatial resolution Distribution
format Spatial representation type Reference
system Lineage statement On-line
Resource Metadata file identifier Metadata
standard name Metadata standard version Metadata
language Metadata character set
9
How to prepare metadata for transition to ISO
Include ISO Dataset Topic Categories as CSDGM
Theme_Keywords. Most of the ISO Core Metadata
Elements either map to existing CSDGM metadata
elements or represent properties of the data that
can be determined and populated using a data
integrated metadata tool. Dataset topic category
is the only mandatory element of the ISO core
metadata set that requires new information that
cannot be directly captured from the data. This
set of 19 high-level subject categories is
provided within the ISO 19115 standard as a means
of quickly sorting and accessing thematic
information. To aid in the transition to ISO
metadata, you are encouraged to include one or
more of the Dataset topic category terms, shown
next (funny truncation and capitalization and
all), as Theme_Keywords within your current CSDGM
metadata.
10
ISO 19115 Topic Categories
farming biota boundaries climatologyMeteorologyAtm
osphere economy elevation environment geoscientifi
cInformation health
imageryBaseMapsEarthCover intelligenceMilitary inl
andWaters location oceans planningCadastre society
structure transportation utilitiesCommunication
11
Suggestions

• Parrot IOOS elements (metadata, discovery,
  transport, browse, archive).
• Serve and/or converse regularly with those
  designees who are evaluating standards.
• For AOOS, implement and test multiple standards
  for each element.
• Share performance criteria and results with IOOS
  and other regional associations.

12
Data Provider Memorandum of Understanding
A Memorandum of Understanding (MoU) is a legal
document describing a bilateral or multilateral
agreement between parties. It expresses a
convergence of will between the parties,
indicating an intended common line of action and
may not imply a legal commitment. It is a more
formal alternative to a gentlemen's agreement,
but in some cases, depending on the exact
wording, lacks the binding power of a contract.
13
Why use an MoU?

• Defines responsibilities of each organization
• Records the intentions of the signatories
• Provides a formal framework for operations
• Outlives the corporate memory of verbal
  agreements
• Is useful in resolving disputes

Here is an applicable example
14
(No Transcript)
15
(No Transcript)
16
(No Transcript)
17
(No Transcript)
18
(No Transcript)
19
Developing an MoU
Step 1 Hold a meeting consisting of all involved
parties to determine what functions, services, or
resources will be shared. Make sure all decision
makers are involved. Discuss a plan as to how
the organizations will operate together. Step
2 Write out the main purpose or goal of the
agreement and determine what specific outcomes
are expected. Step 3 Determine a time line as
to when the partnership and agreement will begin
and when it will end. Be specific regarding the
dates. Step 4 Write down and determine which
organization will be responsible for which
services and resources. Step 5 Draft the
memorandum of understanding based on the
decisions that were made during the meeting.
Include an addendum if necessary to define terms
within the agreement or add necessary forms to be
utilized for services and resources. Let all
parties review, sign, and authorize the MoU. Be
sure that the MoU is signed by a person of
authority.