Integrating WP 10400 Data Sharing and Infrastructure Catalogue Requirements Capture

1
Integrating WP 10400 Data Sharing and
InfrastructureCatalogue Requirements Capture

• Donna Kodz
• A presentation to GMOSS Work Packages
• April 2005

2
Aims of Integrating WP 10400

• To monitor and promote the sharing of data and
  infrastructure within the Network.
• Obtain licences for the partnership.
• To look after the IPR of the partnership.
• Make a proposal for a data catalogue.

3
Data / Software Shares Recording Application
4
Recording Data / Software Shares (1 of 6)

• Why is this important?
• Degree of integrated work achieved through GMOSS
  will be quantitatively measured in part by the
  amount of information, software and facilities
  that are shared between consortium members
  through formal agreements.
• A measure of the success of GMOSS.
• What should be recorded?
• Any data / software which is exchanged between
  consortium partners / organisations for use
  within GMOSS.
• How can this be recorded?
• An application is available via the GMOSS website
  for members to record data and software shared.
• Entries are monitored and reported every 6 months.

5
Recording Data / Software Shares (2 of 6)

• Application welcome page
• Outlines purpose of application
• News
• Login usernames and passwords provided to work
  package leaders

6
Recording Data / Software Shares (3 of 6)

• Homepage
• Data sharing
• Software sharing
• View list of data shares
• View list of software shares
• View status of GMOSS licensing agreements

7
Recording Data / Software Shares (4 of 6)

• Data sharing form
• Data provider / receiver
• Details of share
• Additional information
• Submit posts information entered to database
  hosted at QinetiQ

8
Recording Data / Software Shares (5 of 6)

• Database listing of recorded shares
• Currently no facility to delete or edit a share
  but can e-mail a request for change

9
Recording Data / Software Shares (6 of 6)

• Application and logons were made available Sept
  2004
• Entries made where information gained from e-mail
  exchanges prior to availability of application
• Few records of shares entered to date why?
• Little data / software shared?
• Not aware of application?
• Not a priority?
• Application not user friendly?
• Application does not fulfil requirement?
• Should the application be extended to record
  other measures of the success of GMOSS?
• eg staff exchanges that have taken place
• Please discuss and provide feedback

10
GMOSS Data Licenses
11
GMOSS Data Licenses

• Iain Shepherd has taken the lead on negotiating
  GMOSS imagery licenses eg
• European Union Satellite Centre addition of
  GMOSS partners to JRC license
• Eurimage GMOSS upgade
• Space Imaging negotiating NATO style licence
• Radarsat SAR / fine mode 40 80 surcharge
• Radarsat2 bid in for free research and testing
  licence
• Latest status available in spreadsheet accessed
  from data / software sharing homepage

12
GMOSS Purchased Data
13
GMOSS Intellectual Property Rights
14
Intellectual Property Rights

• Independent advisory role for issues on IPR
• Reviewed the GMOSS contract with respect to IPR
  with QinetiQ in-house contracts staff
• Issued a reminder to GMOSS partners about the
  possibility of protecting pre-existing know-how
  by updating Attachment II of the GMOSS contract
• Available for arbitration to assist in resolving
  IPR issues
• Phase 2 to continue this role.

15
GMOSS Data Catalogue - Requirements Capture
16
Data Catalogue Overview
Requirements Capture

• 12 month report to propose a data catalogue
• Requires input from GMOSS WP2XXXX members
• Questions for catalogue requirements capture on
  next slides
• Need to keep it simple to get something up and
  running
• to provide the basics which can be built on
• Implementation by Sept 2005

17
Data Catalogue Data Types / Resources
Requirements Capture

• 1) What data types / resources are required to
  be catalogued?
• Satellite imagery?
• Aerial photography?
• Other geospatial data?
• Non-geospatial data eg reports, software tools?
  ie a general GMOSS resources catalogue?
• 2) What form should the catalogue take?
• Spreadsheet?
• On-line query application eg extension to data
  / software sharing application?

18
Data Catalogue GMOSS Data / Metadata
Requirements Capture

• Consortium members will responsible for making
  their resources available for use under GMOSS by
  publishing metadata in the catalogue.
• 3) Would it be reasonable to expect consortium
  members to log available data using an online
  metadata entry system?
• Any existing metadata is likely to be in
  different formats eg different / field names,
  will require input into a common GMOSS metadata
  schema.
• 4) What data should be listed in the catalogue?
  And how should it be recorded? (In addition to
  data specifically purchased under GMOSS)
• High level descriptions of individual
  organisations data holdings?
• Detailed list of data holdings of individual
  organisations / link to catalogue of
  organisation?
• Links to data sources external to GMOSS?

19
Data Catalogue Query Interface
Requirements Capture

• 6) Options for query dependent on metadata
  entered. Search by
• location eg country, study area
• date
• data type eg SAR imagery
• WP
• others?

20
Data Catalogue Results
Requirements Capture

• 7) Requirements for results
• List of metadata returned for query matches
• Potentially thumbnails for data if provided
• Information on how to obtain the data eg staff
  contact details, FTP site
• Others?
• (Note not feasible to enable data viewing /
  download via catalogue as data custodians
  retain control over release of data)

21
Catalogue Proposal Case Study Locations
22
Catalogue Proposal Imagery Footprint
23
Catalogue Proposal - Metadata
24
Thank you for your time. Please provide
requirements / feedback toDonna Kodz (WP
10400)E-Mail dmkodz_at_QinetiQ.com
25
WP 20300 Change Detection Update

• Alex Rodrigues
• April 2005

26
Early Warning Natural
27
Early Warning Natural
28
Early Warning Natural
29
Early Warning Natural
30
Early Warning Man-Made
31
Early Warning Combination
32
Monitoring Population
33
Tsunami Damage Assessment
34
WP 10300 Standards

• Mike Palmer
• April 2005

35
Why are Standards Important?

• Facilitate flow, timeliness and confidence level
  of information
• Enables interoperability
• For exploitation of GMOSS, standards will be
  essential to minimise future cost and time
• Need to be considered now and implemented as part
  of the network.

36
Questionnaires

• Initial questionnaire May 2004
• response disappointing only 7 partners
  responded
• network immature
• Six month reports showed 3 WPs considering
  standards
• WP 20100, 20200 20700
• 12 month questionnaire
• 6 nil returns
• 5 completed questionnaires

37
Conclusions

• Many researchers do not see the need for the use
  of standards at this time
• Others have little background in standards and so
  need more support.
• Some WPs are starting to think about standards
• A view is emerging for use of open standards in
  general and OGC standards in particular.
• To maximise exploitation possibilities the
  infrastructure required by an operational system,
  based on the use of standards, needs to be
  considered within the current work programme.

38
Recommendations

• Produce a diagram of information flow throughout
  GMOSS
• to include a work breakdown structure defining
  inputs and outputs of each WP and links between
  them.   
• Look at acceptance criteria for information, and
  how it is to be imported into GMOSS,
• Eg when it is received immediately after a crisis
  in an undefined format
• Standards workshop proposed within next 18 months
  work
• encourage discussion on a network view of
  standards