1 / 17

DEVELOPMENT OF A COMPREHENSIVE ONLINE CATALOGUE OF AVAILABLE OFFICIAL CHARTS.

DEVELOPMENT OF A COMPREHENSIVE ONLINE CATALOGUE OF AVAILABLE OFFICIAL CHARTS. WEND Stakeholders Meeting September 2006 Anthony Pharaoh - IHB. Requirement to Determine ENC Coverage. 6th WEND COMMITTEE MEETING Norfolk, Va, USA, 18-19 May 2001

raisie
Download Presentation

DEVELOPMENT OF A COMPREHENSIVE ONLINE CATALOGUE OF AVAILABLE OFFICIAL CHARTS.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. DEVELOPMENT OF A COMPREHENSIVE ONLINE CATALOGUE OF AVAILABLE OFFICIAL CHARTS. WEND Stakeholders Meeting September 2006 Anthony Pharaoh - IHB

  2. Requirement to Determine ENC Coverage 6th WEND COMMITTEE MEETING Norfolk, Va, USA, 18-19 May 2001 “Germany recommended that IHB produce a catalogue that accurately shows the actual coverage and availability of ENC data for the shipping community”. IHB issued CL 67/2002 asking “…..Member States are requested to provide the information below for every ENC cell already produced, under production or planned” • ENC Cell name • Navigational purpose code, • Cell limits • S-57 Edition, i.e. 3.0 or 3.1; • Date of production; • Date of issuance, i.e. when the ENC cell is on the market; • Website and/or e-mail address where further details on the cell and information on how to obtain the data can be found.

  3. Responses from CL 67/2002 IHB Developed a static catalogue – available on the IHO web site. CL 67/2002 • Presented to the: • 7th WEND Meeting (Lima, Peru, May 2003) • 15th CHRIS Meeting (IHB, June 2003) • Norway offered to assist the IHB in developing an interactive web catalogue

  4. IHO ENC Catalogue Thematic criteria were to establish what ENCs were; - planned or in production (red) - released but not yet commercially available (blue) - commercially available (black) Administrative interface developed to enable MS and RENCS to login and update the system.

  5. IHO ENC Catalogue – Administrative Interface

  6. Requirement for a new Catalogue IMO/IHO Corresponding Group (CG) • NAV50 established a CG • CG endorsed a proposal from IHO to develop an online catalogue. • NAV51 endorsed this proposal • NAV51 prepared a draft specification • NAV51 re-established the CG and tasked it to review the draft specification.

  7. Focus and Scope of the New WEB Catalogue • Focus • Only those ENCs that areavailable for use. (i.e. on the shelf). • Scope • The new catalogue need to show; • ENC coverage • RNCs coverage for those areas where no ENC coverage exists • A list of “adequate backup” paper charts.

  8. Lessons Learned from Previous Catalogue Development • Requirement for ENC data limits – not just cell limit • Need to keep a historical record of coverage evolution. • Need to improve the mechanism for acquiring coverage and metadata information (harvesting tools). • Need for more detailed metadata • Need to be standards based – interoperability • Need to develop mechanisms to keep the catalogue current • As far as possible, take account of the needs of stakeholders (RENCs, Data Servers/VARs, Distributors and OEMs). • Need to make a coverage (dataset) and metadata resource available for use by all stakeholders.

  9. Sources of Coverage Information and Metadata RENC 1 RENC 2HOs ENC HO 1 HO 2 HO 3 RNC Maritime Authorities and HOs “adequate backup” paper charts

  10. Types of Information Required Coverage Information Metadata Information Identifier(ENC Cell name - RNC/Chart number) Issuing authority(possibly on behalf of another Member State) Producer Authority Standard format(e.g. S-57 Edition 3.1, BSB,HCRF) Distribution Method(e.g. issuing HO, RENC, free download) Allowance of SENC distribution: Yes/No Compilation scale / usage band Co-ordinates of edges Edition date RNC ENC

  11. Metadata Resources IHO S-100 Discovery Metadata Profile Update Information

  12. Coverage Information Metadata <extent> <EX_GeographicBoundingBox> <westBoundLongitude>-127.46</westBoundLongitude> <eastBoundLongitude>-122.48</eastBoundLongitude> <southBoundLatitude>43.71</southBoundLatitude> <northBoundLatitude>49.73</northBoundLatitude> </EX_GeographicBoundingBox> <EX_BoundingPolygon> <polygon> -123.45, 43.71 -123.00, 46.23 -123.00, 48.35 -123.22, 49.23 -123.45, 49.73</polygon> </EX_BoundingPolygon> </extent> <extension base="double"> <attribute name=“metadata" type=URI “http://www.responsibleRENC.com#sw33492.mta" use="required"/> </extension>

  13. Coverage Data Files • The ENC and RNC Coverage Files; • will be used to generate ENC and RNC coverage limits in the new catalogue • should be made available on the IHO web site in a standard format for all stakeholders to use • should be regularly maintained through the issue of updates, and new editions • all historical versions of coverage data files should be kept.

  14. Paper Chart Layer List of paper Charts CHART12200 TITLE Cape May to Cape Hatteras SCALE 1/200 000 CHART1521 TITLE Baleto to Punchino SCALE 1/200 000 Paper Chart lists maintained by Maritime Authorities/HOs via a form interface situated on the IHO catalogue server.

  15. ENC RENCs/HOs MetadataDataset MetadataDataset Harvesting Application WMS/WFS MetadataDataset MetadataDataset HOs ENC Dataset RNCs RNC Dataset Internet Browser Harvesting Application ? OEM MSAs/HOs Paper Chart Information

  16. Summary of Key Components • Needs the cooperation of RENCs HOs and MSA to ensure coverage and metadata information is kept current. • As far as possible the generation of coverage and metadata information should be automated as output from a database or using harvesting tools. • It should take into account the needs of Distributors, VARs, OEMs and other stakeholders. • Should be standards based – ensure interoperability.

  17. Thank You

More Related