IICWG DICS Action 6.1.1 DC 6.1.1: Interoperable Data Formats Clearly define the objective of developing common data base i.e. seamless customer support.

Slides:



Advertisements
Similar presentations
Castlemilk Moorit Breeding Programme April 2009 Update.
Advertisements

The IICWG Ad Hoc Format Working Group
Outlines and Text Structure ©Feb 2003 Dr. Bradley C Paul.
Kendle Implementation of Clinical Data Acquisition Standards Harmonization Dr Elke Sennewald Kendle 9th German CDISC User Group Meeting Berlin, 28 September.
Variation Management of Key Characteristics
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
3/5/2009Computer systems1 Analyzing System Using Data Dictionaries Computer System: 1. Data Dictionary 2. Data Dictionary Categories 3. Creating Data Dictionary.
International Ice Charting Working Group IICWG IV Data, Information & Customer Service Standing Committee Report Co-Chairs Henrik Steen Andersen & Bob.
International Ice Charting Working Group IICWG V Data, Information & Customer Support Standing Committee Report Co-Chairs Ari Seina & Florence Fetterer.
GIS-Based Technology of Ship Routing in Ice Igor Stepanov, Sergey Frolov, Sergey Klyachkin, Yury Scherbakov (Arctic & Antarctic Research Institute, St.
Final Project: Project 9 Part 1: Neural Networks Part 2: Overview of Classifiers Aparna S. Varde April 28, 2005 CS539: Machine Learning Course Instructor:
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Runtime alignment system SOFTWARE DESIGN IDEAS Wed 4 th May 2005 P Coe.
Experience of short-range (1-5 days) numerical ice forecasts for the freezing seas. Sergey Klyachkin, Zalman Gudkovich, Roman Guzenko Arctic and Antarctic.
Report Writing Three phases of report writing Exploratory phase (MAPS)
GMWG - 2. March 2005 Brian Parish AML Specifications Manager UKHO Brian Parish AML Specifications Manager UKHO.
IPUMS to IHSN: Leveraging structured metadata for discovering multi-national census and survey data Wendy L. Thomas 4 th Conference of the European Survey.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
Proceedings and Report of the Expert Meeting: Arrangements Proceedings and Report of the Expert Meeting: Arrangements.
Foundation Degree IT Project Milestone 3: Implementation, Testing and Evaluation.
CIS 895 – MSE Project KDD-Research Entity Search Tool (KREST) Presentation 2 Eric Davis
An Introduction to Software Architecture
Session 21-2 Session 11 Common Origination and Disbursement (COD) & Commonline: Dispel the Myths.
Expert Team on Sea Ice (ETSI)‏ Vasily Smolyanitsky Arctic and Antarctic Research Institute (AARI)‏ ETSI chair THE JOINT WMO/IOC COMMISSION FOR OCEANOGRAPHY.
WPM What’s behind the icon? Work Programme Management.
Data, Information & Customer Support Standing Committee Action Items from IICWG-8 26 October 2007 Co-Chairs Marie-France Gauthier & Ari Seina.
Incident Threading for News Passages (CIKM 09) Speaker: Yi-lin,Hsu Advisor: Dr. Koh, Jia-ling. Date:2010/06/14.
Ray Chartier Jr Director NIC 23 October 2007 North American Ice Service (NAIS) Update to International Ice Charting Working Group Scott Rogerson Commander.
Rev. 0 CONFIDENTIAL Mod.19 02/00 Rev.2 Mobile Terminals S.p.A. Trieste Author: M.Fragiacomo, D.Protti, M.Torelli 31 Project Idea Feasibility.
1 What’s Next for Financial Management Line of Business (FMLoB)? AGA/GWSCPA 6 th Annual Conference Dianne Copeland, Director, FSIO May 8, 2007.
25 June 2009, London Impact significance in air quality assessment Application of EPUK criteria to road schemes?
Interoperable Data Formats Technical Session Summary Report International Ice Charting Working Group – VI Ottawa, October 2005 John Falkingham.
Extension of the ice services for the Southern Ocean - status and briefs from ETSI-V, IAW-4 Caryn Panoviwicz, NIC Nick Hughes, NIS Vasily Smolyanitsky,
AIXM 5 Metadata. Requirements for AIXM Metadata AIXM Metadata Model Examples Requirements for AIXM Metadata AIXM Metadata Model Examples.
Sea Ice Mapping Systems Archive Browser Interface Distribution IngestProduction Ice Analyst Application Database Henrik Steen AndersonDMI Paul SeymourNIC.
An analysis of Russian Sea Ice Charts for A. Mahoney, R.G. Barry and F. Fetterer National Snow and Ice Data Center, University of Colorado Boulder,
Chapter 21: The Glacier Systems and the Ice Age Presentation.
Data, Information & Customer Support Standing Committee Report on Action Items at Close of IICWG-7 28 September 2006 Co-Chairs Florence Fetterer & Ari.
Presentation to the International Ice Charting Working Group 22 November 2007 Ice In Electronic Navigation Charts (ENCs) (A Status Report)
Foundation Degree IT Project Milestone 2: Research and Analysis.
International Federation of Accountants April 28, 2009 Impact Assessment Process for IFAC Linda Lach and Alta Prinsloo.
Definition of Sea Ice terms and Nomenclature in XML language IICWG-III, DNMI, Tromso, Vasily Smolyanitsky, Arctic and Antarctic Research.
Dr Vasily Smolyanitsky ETSI chair Arctic and Antarctic Research Institute (AARI) St.Petersburg, Russia Sea ice climatology Doc. 7.5 Expert Team on Marine.
Vendor Bid System (VBS) Seminar. Agenda Vendor Bid System Overview Step-by-Step Advertisement Posting Editing Active Advertisements Recommended Practices.
Data, Information & Customer Support Standing Committee Report on Action Items from IICWG-7 23 October 2007 Co-Chairs Florence Fetterer & Ari Seina With.
Mark Dixon 1 Tech – Final Report. Mark Dixon 2 Aims & Objectives Give guidance on: –Project Report –Demonstration.
SDP Simple Capability Negotiation (SDP Simcap) draft-andreasen-mmusic-sdp-simcap-reqts-00.txt draft-andreasen-mmusic-sdp-simcap-01.txt 50th IETF - March.
SevenCs the ECDIS Company
Data, Information and Customer Support Action Item CD Standardise colour coding for ice charts as part of longer term strategy to place ice information.
PRO/ARC and TST/PRO joint sessions at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:
PIDF-LO Profile James Winterbottom, Martin Thomson IETF-65.
Concept of DCEG Editor and Prototype Development Republic of Korea (KHOA) NIPWG2 HB, Monaco (21-24, March 2016)
Describing Arc Flash Incident Energy per Feeder Length in the Presence of Distributed Resources Tom R. Chambers, P.E. Power System Engineering, Inc. Madison,
IICWG VI Data, Information & Customer Support Standing Committee Report - Open Action Items for IICWG-7 Co-Chairs Florence Fetterer & Ari Seina.
1 Environmental and Disposal Liabilities Intranet Reporting System March 2006 Training Guide.
Or “why should I bother writing it all down? since I know it all anyways...”
Software Metrics 1.
Technical Report Writing
Report Writing Three phases of report writing Exploratory phase (MAPS)
Vasily Smolyanitsky, ETSI chair / AARI IAW-5, USNIC, May 2016
GSC-EM TF goal, as defined initially
WHO Model Formulary (WMF)
Session I NAUTICAL PUBLICATIONS
Updates to Draft Specification for DTN TCPCLv4
An Introduction to Software Architecture
S-127 – Marine Traffic Management Release Candidate NIPWG 6 30 January 2019 Raphael Malyankar Eivind Mong Sponsored by IHO.
Updating S-49 (Mariners’ Routeing Guide)
Software Requirements Specification (SRS) Template.
MIB TruthValue Usage Patterns Presentation
MIB TruthValue Usage Patterns Presentation
Presentation transcript:

IICWG DICS Action DC 6.1.1: Interoperable Data Formats Clearly define the objective of developing common data base i.e. seamless customer support vs. ice service interoperability: Complete final version of the Ice Objects Catalogue –editorial changescorrect references –review for consistency w/ Sea Ice Nomenclature / SIGRID-3 Responsible: P. Seymour / Vasily Smolianitsky. Target Date: April, 2006 Status: Editorial changes:First draft of recommendations Correct references:First draft of addition of references Compare w/ Nomenclature:First draft completed Compare w/ SIGRID: By default, some progress made

IICWG DICS Action Background Important milestone: met with Dr. Paul Birkel in May Authored a critique of the catalog that was presented during the interoperability session during last meeting Access to an expert / Access to the actual IHO database This access is absolutely necessary Steady progress since this meeting in May, 2006 Dr. Birkel is working with the NGA to write similar databases for all product specifications

IICWG DICS Action Database Description 1 Ice Catalog looks like a spreadsheet It is actually a relational database There is a method to the apparent madness The Ice Objects Catalog divided into three sections:

IICWG DICS Action Database Description 2 The higher level are the Features - Main objects Sea Ice, Land Ice Ice Openings, Icebergs and Ice Fracture etc. The middle level are the Attributes - Descriptors Concentration Total, Floe Sizes Iceberg Shape, Fracture Type etc. The lower level are the Attribute Listed Values These are enumerators for the Attributes. –Represent ice codes used to describe ice eggs List of Iceberg Shapes Codes for Ice Stages Fracture types: Crack, Very Small Fracture

IICWG DICS Action Summary of Progress 1 Completed: Reviewed Features in the catalogue –Notes on comparison to: Nomenclature Each other –Recommendations on supporting attributes –These notes are contained in additional fields in the spreadsheet and in the Feature Report

IICWG DICS Action Summary of Progress 2 Completed: Reviewed Attributes in the catalogue Made notes on how they compare to: –Nomenclature –How they relate to each other These notes are contained in additional fields in the spreadsheet and in the Attribute Report

IICWG DICS Action Summary of Progress 3 Completed: Reviewed Attribute Listed Values Made notes on how they compare to: –Nomenclature –Symbology or ice codes –Other sources such as the CIS MANICE.

IICWG DICS Action Remaining Work 1 Reverse process to compare the nomenclature and symbology to the objects Smooth draft documents for consistency The project has to be completed –Definitions and descriptions harmonized with Nomenclature Ice codes On another level, nomenclature and ice codes –Updated with the goal of facilitating electronic charting –Make ice objects fit that review

IICWG DICS Action Conclusions 1 At highest level, three Features that are overarching: –Sea Ice, Land Ice (is Ice of Land Origin), Lake Ice –One inconsistency is that there is no River Ice Many of other Features are subsets of these three: List of Ice Objects Features: Floeberg, Ice Advisory Area Ice Dynamics Ice Movement Ice Ridge Ice Topology Ice Fracture Ice Lead Ice Opening Ice Polynya Ice Line (represents the ice extent or ice edge) Ice Route, Ice/Snow Thickness, Iceberg, Iceberg Area Lake Ice Land Ice Sea Ice

IICWG DICS Action Conclusions 2 Examples of overlap between openings Features –Ice Openings* –Ice Fracture* –Ice Polynya* –Ice Lead* Examples of overlap between topology Features –Ice Topology** –Ice Ridge** Examples of overlap between drift –Ice Dynamics*** –Ice Movement***

IICWG DICS Action Conclusions 3 The enumerators should be in a logical format and the units should be spelled out… –Kilometers, metres or centemetres not cms or ms –Nautical miles not knots Measurements should not overlap or leave gaps. Example: –4Very Small Fracture metres –5Small Fracture metres –6Medium Fracture metres –Should probably read > 50 to < = 200 etc Descriptions: plain language not "ice" language –We know what a "floe" is –Definitions should refer to it as a piece of ice (floe)

IICWG DICS Action Conclusions 4 Some definitions do not match the nomenclature Ice Object Feature Land Ice NomenclatureIce of Land Origin Ice Object FeatureIce Line NomenclatureIce Edge There are some features that are not ice terms at all such as Ice Advisory Area or Ice Route (from NATO). a. Will we adopt those definitions? There could be sea ice nomenclature terms that should have an Ice Objects Feature. One example is River Ice.

Recommendations Where To Go From Here? 1. Use the Ice Object Catalog in its current form –Little work but a lot of inconsistencies –Not recommended 2. Make Ice Objects conform to definitions in the nomenclature and symbology and then come up with recommended changes to the nomenclature –Moderate work but more consistency –Makes a difference in the short run 3. Redo the nomenclature and coding for ice charting and then harmonize the Ice Objects with electronic charting in mind –Very Large amount of work but maximum usefulness/consistency –There is a large risk that we will modify the ice code and then we may not be compatible with our legacy data

Questions and Comments Larson B Feb., 2002

Appendix A Examples of Duplication 1 Feature: Ice Fracture: Attribute: Fracture Type: Code Name 1 Crack 2 Tide Crack 3 Flaw Valid 4 Very Small Fracture 5 Small Fracture Valid 6 Medium Fracture 7 Large Fracture 8 Undetermined or Unknown There is also a feature called Feature: Ice Opening Attribute: Ice Opening Type CodeName 1 Crack 2 Tide Crack 3 Flaw 4 Very Small Fracture 5 Small Fracture 6 Medium Fracture 7 Large Fracture 8 Non-Recurring Polynya 9 Recurring Polynya 10 Open Lead 11 Frozen Lead 12 Undetermined or Unknown Attribute Listed Value (or Enumeration) for Fracture Type: 1Crack 2Tide Crack 3Flaw 4Very Small Fracture metres. Small Fracture metres. 6Medium Fracture metres. 7Large Fracture Greater than 500 metres. 8Undetermined or Unknown With the following enumerations: 1Crack 2Tide Crack 3Flaw 4Very Small Fracture < 50 metres in length 5Small Fracture metres in length 6Medium Fracture metres in length Large Fracture > 500 metres in length 8Non-Recurring Polynya 9Recurring Polynya 10Open Lead 11Frozen Lead 12Undetermined or Unknown

Appendix A Examples of Duplication 2 Feature: Ice Polynya Attribute 1: Ice Polynya Type Attribute 2: Ice Polynya Status Code Name 1 Polynya 2Shore Polynya 3 Flaw Polynya 1 Polynya: An unspecified type of polynya. 2Shore Polynya A polynya between ice and the coast or between ice and an ice front. 3Flaw Polynya A polynya between ice +fast ice. Code Name 1 Non-Recurring Polynya (This is our “general or non-specific” polynya) 2 Recurring Polynya A polynya which recurs in the same position every year.