Presentation to the Presentation to the International Ice Charting Working Group VIInternational Ice Charting Working Group VI

26 October, 200526 October, 2005

C. Douglas O’BrienC. Douglas O’Brien

Timothy V. EvangelatosTimothy V. Evangelatos

Ice In ECDIS(Reaching out to our marine users)

Ice In ECDIS - OverviewIce In ECDIS - Overview

ECDIS and its Potential for Safer NavigationECDIS and its Potential for Safer Navigation Vision for “Ice In ECDIS” and its HistoryVision for “Ice In ECDIS” and its History Base Standards incorporating Ice ObjectsBase Standards incorporating Ice Objects Status of Ice Objects/RegistryStatus of Ice Objects/Registry Authority for Ice ObjectsAuthority for Ice Objects Conclusions and RecommendationsConclusions and Recommendations Future StepsFuture Steps

ECDIS and its Potential for Safer ECDIS and its Potential for Safer NavigationNavigation

Marine Electronic Highway (MEH)Marine Electronic Highway (MEH) Power of ECDIS lays in integration of databasesPower of ECDIS lays in integration of databases Delivering INTERNET onboard at low cost is key Delivering INTERNET onboard at low cost is key

Organize bridge for real time informationOrganize bridge for real time information Optimize use of smart data in an enhanced Optimize use of smart data in an enhanced

“intelligent” marine transportation system for “intelligent” marine transportation system for safer navigation, environmental protection and safer navigation, environmental protection and marine transportation efficiencymarine transportation efficiency

per Captain John Pace, Ice In ECDIS, June 2000

ENC – Electronic Navigational ChartENC – Electronic Navigational ChartSt Lawrence River AreaSt Lawrence River Area

Canadian Hydrographic Service

ENC – Electronic Navigational ChartENC – Electronic Navigational Chart

US National Ocean Service

CCGNotice to Mariners

CISIce info

ECDIS updatesTide infoCurrents

FINAL PRODUCT DELIVERYFINAL PRODUCT DELIVERY

CHS

Used with permission from Dr. Ahmed Elrabbany

Ice In ECDIS VisionIce In ECDIS Vision

In the far northern and southern In the far northern and southern hemispheres ice is a major factor in safe hemispheres ice is a major factor in safe navigation and the integration of real time navigation and the integration of real time or near real-time ice information into ECDIS or near real-time ice information into ECDIS is an important and natural step. is an important and natural step.

To achieve this vision one primary To achieve this vision one primary requirement is the development of an ICE requirement is the development of an ICE feature data dictionary to work with ECDIS. feature data dictionary to work with ECDIS.

Ice In ECDIS - HistoryIce In ECDIS - History

1992 – Workshop: S57 Object Catalogue - Ottawa1992 – Workshop: S57 Object Catalogue - Ottawa 1995 Workshop: Standards for Ice Information in ECDIS - Ottawa 1995 Workshop: Standards for Ice Information in ECDIS - Ottawa

• Draft Ice Object Catalogue, Version 1.0Draft Ice Object Catalogue, Version 1.0 1996 Workshop: ECDIS in Ice Navigation – Hamburg1996 Workshop: ECDIS in Ice Navigation – Hamburg

• Ice Object Catalogue, Version 2.0Ice Object Catalogue, Version 2.0 1999 The ECDIS Ice Chart Project, SevenCs AG & Co.1999 The ECDIS Ice Chart Project, SevenCs AG & Co. 2000 Ice In ECDIS Workshop – St. John’s, NFLD2000 Ice In ECDIS Workshop – St. John’s, NFLD

• Ice Object Catalogue, Version 3.0Ice Object Catalogue, Version 3.0 2002 Integration of Sea Ice into ECDIS, University of New Brunswick 2002 Integration of Sea Ice into ECDIS, University of New Brunswick

ProjectProject 2004 DGIWG develops structure for Feature Data Dictionary Register 2004 DGIWG develops structure for Feature Data Dictionary Register

(Draft)(Draft) 2005 IHO Ice Registry (Draft)2005 IHO Ice Registry (Draft)

After many years of effort an ICE Feature Data Dictionary is After many years of effort an ICE Feature Data Dictionary is now available as a register compatible with IHO and othersnow available as a register compatible with IHO and others

Why Registers and Registries?Why Registers and Registries?

… … and then and then leveraging leveraging

technology -- technology -- a means to a means to

the ends, not the ends, not an end an end

… … and then and then leveraging leveraging

technology -- technology -- a means to a means to

the ends, not the ends, not an end an end

Change Change management management

model, develop model, develop better tools, better tools,

improve accessimprove access

Change Change management management

model, develop model, develop better tools, better tools,

improve accessimprove access

Use source Use source referencing and referencing and

compound compound registers to registers to “pull them “pull them togethertogether”

Use source Use source referencing and referencing and

compound compound registers to registers to “pull them “pull them togethertogether”

Layered family Layered family of registers with of registers with

“downward” “downward” dependencies & dependencies & “upward” reuse“upward” reuse

Layered family Layered family of registers with of registers with

“downward” “downward” dependencies & dependencies & “upward” reuse“upward” reuse

Fundamentally, a register is little more than a managed list which Fundamentally, a register is little more than a managed list which assists in assists in defining and implementing good business practicesdefining and implementing good business practices– Objective is to rethink what we currently do,Objective is to rethink what we currently do,

why we do it, and … how we’d rather be doing itwhy we do it, and … how we’d rather be doing it Three major business problemsThree major business problems

– Content update/release is slowContent update/release is slow Cycle time must be in weeks, not months/yearsCycle time must be in weeks, not months/years

– There will be more than one “domain” data dictionaryThere will be more than one “domain” data dictionary E.g., E.g., feature data dictionaries DGIWG FADD, & military profiles of FADDfeature data dictionaries DGIWG FADD, & military profiles of FADD

S57 Feature Object Data Dictionary, ICAO aeronautical features, S57 Feature Object Data Dictionary, ICAO aeronautical features, environmental features, etc.environmental features, etc.–Concepts may come from multiple sources Concepts may come from multiple sources and and be managed bybe managed by different authorities different authorities –Problem is multi-level; bigger than a “base level” catalogueProblem is multi-level; bigger than a “base level” catalogue

Consider features and attributes:Consider features and attributes:–Need feature data dictionaries for definitions, feature catalogues toNeed feature data dictionaries for definitions, feature catalogues tobind features and attributes to support product specifications (and/or bind features and attributes to support product specifications (and/or feature information content specifications)feature information content specifications)–And mappings between different feature catalogues/data product And mappings between different feature catalogues/data product specifications to allow for interworkingspecifications to allow for interworking

Registr(ies) Model is ISO basedRegistr(ies) Model is ISO based

ISO/TC 211 conformantregistr(ies)

Feature DataDictionaries ISO 19126

DGIWG FDD registryIHO compound FDD

ICAO registry

DGIWG FADD,S-57, ICE, ICAO, AML

FeatureCatalogs

ISO 19126

MGCP Feature Catalogue DGIWG Feature CatalogueECDIS Feature CatalogueICAO Feature CatalogueAML Feature Catalogue

MGCP Product SpecDGIWG Products

ECDIS Product SpecICAO Product SpecAML product Specs

PurposePopulated &

Operational RegistryContentRegister

ModelContent

Information Model Register

Information Model

PortrayalCatalogs

GeoSymS-52

EMS/HLSOOB (2525B)

GeoSymS-52EMS

ISO 19117

ISO 19110

ISO 19126

TBDTBD

ISO 19135 Procedures for the Registration of Geographic Information

+ +

* Note: MGCP is the military Multinational Geospatial Co Production project

Registry ManagementRegistry Management

Registry Owner: Registry Owner: – Primary responsibility for the management, dissemination and Primary responsibility for the management, dissemination and

intellectual content of the registryintellectual content of the registry

Registry User:Registry User:– Any person or organization interested in accessing or influences Any person or organization interested in accessing or influences

the content of the registerthe content of the register

Registry Manager:Registry Manager:– Responsible for the administration of the registry content. Follows Responsible for the administration of the registry content. Follows

ISO 19135……ISO 19135……

A Registry is the system that supports the Register

IHO will establish a compound register that may contain multiple IHO will establish a compound register that may contain multiple registers for different domains in one registry. This will include registers for different domains in one registry. This will include ICE features and attributes.ICE features and attributes.

1414

• ISO 19110, 19135, 19126• A single information model

• A single management mechanism• A common cross-community technical realization

• ISO 19110, 19135, 19126• A single information model

• A single management mechanism• A common cross-community technical realization

AeronauticalFDD RegistryAeronauticalFDD Registry

FAA RegisterFAA Register

ICAO RegisterICAO Register

Eurocontrol/AIXM Register

Eurocontrol/AIXM Register

Hydrographic & LittoralFDD Registry

Hydrographic & LittoralFDD Registry

S-57 RegisterS-57 Register

ICE RegisterICE Register

AML RegisterAML Register

OEF RegisterOEF Register

Meteorology & OceanographicFDD Registry

Meteorology & OceanographicFDD Registry

JMBL RegisterJMBL Register

NOAA RegisterNOAA Register

Other OrganizationsFDD Registry

Other OrganizationsFDD Registry

RegisterRegister

Standards-based Geo- feature Standards-based Geo- feature RegistriesRegistries

More

Ice Coverage Type

- Attributes continued

Roles and ResponsibilitiesRoles and Responsibilities

Register Owner Submitting Organization

Control Body Register Manager

Register Registry

Register User

1

1..*qualifier

qualifiedBy

1

1..*

appointer

appointedBy 1..*

1

delegatedBy

delegator1

1..*

owner

register

1

1..*

receiver

submitter

1..*

1

managed

manager

1..* 1content storedOn

1

1..*

operator

system

1

1

contentController

controlled

1..*

1..*

usedBy

user

1..*

1..*

accessor

accessedBy

ManagementLevel

User Level

ExecutiveLevel

DeploymentLevel

Registry Manager

1..*1..*

contentManager

systemManager

1..*

1decisionAuthority

decisionRequester

ETSI

ESTI-WG

ETSI

Clients

Ice and Hydro charting communities

ETSI Designate

Same Registry Manager as IHO

IHO

Registry Management

Approval of ICE RegisterApproval of ICE Register Content of ICE Register presented to the JCOMM Expert Content of ICE Register presented to the JCOMM Expert

Team on Sea Ice (ETSITeam on Sea Ice (ETSI

Content will be reviewed by the ETSI team. Deadline for Content will be reviewed by the ETSI team. Deadline for comments to be set at the ETSI meeting.comments to be set at the ETSI meeting.

Comments on the ICE register prepared by the TSMAD in Comments on the ICE register prepared by the TSMAD in spring 2004 were primarily editorial or related to integration spring 2004 were primarily editorial or related to integration with S-57 objects and have already been included in the with S-57 objects and have already been included in the register.register.

ICE Catalogue document V 3 has not been updated yet ICE Catalogue document V 3 has not been updated yet awaiting review of the register and a single baseline document awaiting review of the register and a single baseline document will be prepared when the register is reviewed by the Ice will be prepared when the register is reviewed by the Ice Committee. (differences are primarily editorial)Committee. (differences are primarily editorial)

The draft implementation of the ICE register has been The draft implementation of the ICE register has been mounted by the UKHO at mounted by the UKHO at http://195.217.61.120/http://195.217.61.120/..

Conclusions and RecommendationsConclusions and Recommendations

The technology to produce and view ice objects The technology to produce and view ice objects exists (e.g. CARIS (GIS) and OSL (ECDIS)).exists (e.g. CARIS (GIS) and OSL (ECDIS)).

The Ice Object and Presentation Specifications exist The Ice Object and Presentation Specifications exist (e.g. IHO and AML).(e.g. IHO and AML).

Promote the Ice Object Registry. Promote the Ice Object Registry. Encourage/Help National Ice Services to Encourage/Help National Ice Services to

use/expand the Ice Registryuse/expand the Ice Registry Develop a Demonstration ProjectDevelop a Demonstration Project

– Baltic Sea or St. Lawrence River? (Ice already planned to Baltic Sea or St. Lawrence River? (Ice already planned to be a minor part of the lower St Lawrence integrated chart be a minor part of the lower St Lawrence integrated chart project)project)

– How to Kick start? (Military and/or Coast Guard support)How to Kick start? (Military and/or Coast Guard support)

For more InformationFor more InformationC. Douglas O’Brien, IDON Technologies Inc.C. Douglas O’Brien, IDON Technologies Inc.

Timothy V. Evangelatos, Terraqueous TechnologiesTimothy V. Evangelatos, Terraqueous Technologies

Acknowledgement:

The authors would like to thank the Canadian Hydrographic Service for their support in preparing this presentation.