Presentation to the International Ice Charting Working Group VI26 October, 2005 Ice In ECDIS (Reaching out to our marine users) C. Douglas O’Brien Timothy V. Evangelatos
Ice In ECDIS - Overview • ECDIS and its Potential for Safer Navigation • Vision for “Ice In ECDIS” and its History • Base Standards incorporating Ice Objects • Status of Ice Objects/Registry • Authority for Ice Objects • Conclusions and Recommendations • Future Steps
ECDIS and its Potential for Safer Navigation • Marine Electronic Highway (MEH) • Power of ECDIS lays in integration of databases • Delivering INTERNET onboard at low cost is key Organize bridge for real time information • Optimize use of smart data in an enhanced “intelligent” marine transportation system for safer navigation, environmental protection and marine transportation efficiency per Captain John Pace, Ice In ECDIS, June 2000
ENC – Electronic Navigational ChartSt Lawrence River Area Canadian Hydrographic Service
ENC – Electronic Navigational Chart US National Ocean Service
Ice info CIS FINAL PRODUCT DELIVERY Notice to Mariners CCG ECDIS updates Tide info Currents CHS Used with permission from Dr. Ahmed Elrabbany
Ice In ECDIS Vision • In the far northern and southern hemispheres ice is a major factor in safe navigation and the integration of real time or near real-time ice information into ECDIS is an important and natural step. • To achieve this vision one primary requirement is the development of an ICE feature data dictionary to work with ECDIS.
Ice In ECDIS - History After many years of effort an ICE Feature Data Dictionary is now available as a register compatible with IHO and others • 1992 – Workshop: S57 Object Catalogue - Ottawa • 1995 Workshop: Standards for Ice Information in ECDIS - Ottawa • Draft Ice Object Catalogue, Version 1.0 • 1996 Workshop: ECDIS in Ice Navigation – Hamburg • Ice Object Catalogue, Version 2.0 • 1999 The ECDIS Ice Chart Project, SevenCs AG & Co. • 2000 Ice In ECDIS Workshop – St. John’s, NFLD • Ice Object Catalogue, Version 3.0 • 2002 Integration of Sea Ice into ECDIS, University of New Brunswick Project • 2004 DGIWG develops structure for Feature Data Dictionary Register (Draft) • 2005 IHO Ice Registry (Draft)
Why Registers and Registries? … and then leveraging technology -- a means to the ends, not an end • Fundamentally, a register is little more than a managed list which assists in defining and implementing good business practices • Objective is to rethink what we currently do,why we do it, and … how we’d rather be doing it • Three major business problems • Content update/release is slow • Cycle time must be in weeks, not months/years • There will be more than one “domain” data dictionary • E.g., feature data dictionaries DGIWG FADD, & military profiles of FADD S57 Feature Object Data Dictionary, ICAO aeronautical features, environmental features, etc. • Concepts may come from multiple sources and be managed by different authorities • Problem is multi-level; bigger than a “base level” catalogue • Consider features and attributes: • Need feature data dictionaries for definitions, feature catalogues tobind features and attributes to support product specifications (and/or feature information content specifications) • And mappings between different feature catalogues/data product specifications to allow for interworking Change management model, develop better tools, improve access Use source referencing and compound registers to “pull them together” Layered family of registers with “downward” dependencies & “upward” reuse
ISO/TC 211 conformant registr(ies) ISO 19135 Procedures for the Registration of Geographic Information Content Information Model Populated & Operational Registry Register Model RegisterInformation Model + + Purpose Content DGIWG FADD,S-57, ICE, ICAO, AML DGIWG FDD registry IHO compound FDDICAO registry Feature DataDictionaries ISO 19126 ISO 19126 MGCP Product Spec DGIWG Products ECDIS Product Spec ICAO Product Spec AML product Specs MGCP Feature Catalogue DGIWG Feature Catalogue ECDIS Feature Catalogue ICAO Feature Catalogue AML Feature Catalogue FeatureCatalogs ISO 19110 ISO 19126 GeoSym S-52 EMS/HLS OOB (2525B) Portrayal Catalogs GeoSymS-52EMS ISO 19117 TBD Registr(ies) Model is ISO based * Note: MGCP is the military Multinational Geospatial Co Production project
Registry Management A Registry is the system that supports the Register • Registry Owner: • Primary responsibility for the management, dissemination and intellectual content of the registry • Registry User: • Any person or organization interested in accessing or influences the content of the register • Registry Manager: • Responsible for the administration of the registry content. Follows ISO 19135…… IHO will establish a compound register that may contain multiple registers for different domains in one registry. This will include ICE features and attributes.
Standards-based Geo- feature Registries AeronauticalFDD Registry Hydrographic & LittoralFDD Registry Meteorology & OceanographicFDD Registry Other OrganizationsFDD Registry S-57 Register FAA Register Register JMBL Register ICE Register Eurocontrol/AIXM Register AML Register NOAA Register ICAO Register OEF Register • ISO 19110, 19135, 19126 • A single information model • A single management mechanism • A common cross-community technical realization
Ice Coverage Type - Attributes continued
qualifier 1..* owner Executive 1 qualifiedBy Register Owner Submitting Organization delegator Level 1 1 1 appointer 1..* submitter appointedBy 1..* 1..* delegatedBy 1 Management decisionAuthority 1 receiver Control Body Register Manager Level contentManager 1..* decisionRequester 1..* 1..* systemManager 1 contentController 1 manager Registry Manager 1 operator controlled 1 system 1..* Deployment 1..* Level 1..* managed Register Registry register usedBy 1..* content 1..* 1 storedOn 1..* accessedBy User Level 1..* 1..* Register User user accessor Roles and Responsibilities ETSI Ice and Hydro charting communities ETSI Designate ESTI-WG Registry Management Same Registry Manager as IHO ETSI IHO Clients
Approval of ICE Register • Content of ICE Register presented to the JCOMM Expert Team on Sea Ice (ETSI • Content will be reviewed by the ETSI team. Deadline for comments to be set at the ETSI meeting. • Comments on the ICE register prepared by the TSMAD in spring 2004 were primarily editorial or related to integration with S-57 objects and have already been included in the register. • ICE Catalogue document V 3 has not been updated yet awaiting review of the register and a single baseline document will be prepared when the register is reviewed by the Ice Committee. (differences are primarily editorial) • The draft implementation of the ICE register has been mounted by the UKHO at http://126.96.36.199/.
Conclusions and Recommendations • The technology to produce and view ice objects exists (e.g. CARIS (GIS) and OSL (ECDIS)). • The Ice Object and Presentation Specifications exist (e.g. IHO and AML). • Promote the Ice Object Registry. • Encourage/Help National Ice Services to use/expand the Ice Registry • Develop a Demonstration Project • Baltic Sea or St. Lawrence River? (Ice already planned to be a minor part of the lower St Lawrence integrated chart project) • How to Kick start? (Military and/or Coast Guard support)
For more Information C. Douglas O’Brien, IDON Technologies Inc. Timothy V. Evangelatos, Terraqueous Technologies Acknowledgement: The authors would like to thank the Canadian Hydrographic Service for their support in preparing this presentation.