1 / 19

Resolution No. 48 Inland ECDIS standard 2.3

Resolution No. 48 Inland ECDIS standard 2.3. UNECE February 16, 2012. Procedures for changes of the annexes Example Consequences of changes of the annexes Timeline for changes of the annexes Questions to SC.3/WP.3 Conclusions. Content. Procedures for changes.

brownleed
Download Presentation

Resolution No. 48 Inland ECDIS standard 2.3

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. Resolution No. 48Inland ECDIS standard 2.3 UNECE February 16, 2012

  2. Procedures for changes of the annexes Example Consequences of changes of the annexes Timeline for changes of the annexes Questions to SC.3/WP.3 Conclusions Content www.ris.eu

  3. Procedures for changes CCNR has provided a mandate to the expert groups for changes of the annexes(with explicit restrictions regarding e.g. changes that cause financial burdens for the authorities) The text parts of the annexes have more than 800 pages, in addition there are the electronic parts (lookup tables, symbol library, test charts) A lot of resources are needed to find errors, most of them are only typing errors. Some are only found during implementation. Therefore a mandate for the expert group to make corrections is a minimum requirement www.ris.eu ienc.openecdis.org 3

  4. Procedures for changes: examples Three elementswhich exist inPolandare not coveredby the currentstandard: - fishing nets - reed - marsh www.ris.eu ienc.openecdis.org 4

  5. The necessary amendments for marsh Amendment of the XML Feature Catalogue: <Enumeration value=„2" > <DataDictionaryReference token="HYDRO„ code="CATLND_2" dateAccepted="2000-11-01" > <Name>marsh</Name> <Definition>an area of wet, often spongy ground that is subject to frequent flooding or tidal inundations, but not considered to be continually under water. It is characterized by the growth of non woody plants and by the lack of trees. (Nautical Chart Manual, US National Oceanic and Atmospheric Administration – NOAA, 1992)</Definition> <Reference source="INT-1" >IQ 90;</Reference> <Reference source="M4" >456.1;</Reference> </DataDictionaryReference> </Enumeration> (copied from the S-57 standard of IHO) www.ris.eu ienc.openecdis.org 5

  6. The necessary amendments for marsh Amendment of the Encoding Guide, page D.2.2: Add to the Object Encoding: “CATLND = [2 (marsh)]” Add to the Encoding Instructions:“LNDRGN may be used to encode marshes that should have a label readily displayed for users of the IENC.” www.ris.eu ienc.openecdis.org 6

  7. The necessary amendments for marsh Amendment of the Lookup Tables: "LNDRGN","CATLND2|","AP(MARSHES1)","30","S","STANDARD","21060“ Amendment of the symbol library: (copied from S-52 of IHO) www.ris.eu ienc.openecdis.org 7

  8. The necessary amendments for marsh Amendment of the test charts with a marsh Amendment of the Recommended Validation Checks for Inland ENCs: www.ris.eu ienc.openecdis.org 8

  9. Consequences of the amendments No country has to encode fishing nets, reed or marshes as long as they are no obstacles within the fairway (minimum content) Countries who do not want to use the new elements can still use the older version of the standard The amendment does not create any workload or costs for the countries www.ris.eu ienc.openecdis.org 9

  10. Timeline for changes: example Edition 2.3 was finalized in February 2011 We hope that it will be adopted by UNECE in October 2012 A proposal for an edition 2.4 cannot be discussed before February 2013 and can not enter into force before end of 2013 (most probably later) The new elements can only be used in the charts, when the software applications have been updated and distributed to the end users In 2012, 2013 and most of 2014 there will be no fishing nets, no reeds and no marshes in the Polish charts, if the amendment has to be adopted by WP.3/SC.3 www.ris.eu ienc.openecdis.org 10

  11. Procedures for changes: questions Would it be realistic that WP.3/SC.3 rejects the request of a country and prohibits to encode e.g. fishing nets, reed and marshes in the Inland ENCs? Does WP.3/SC.3 have the resources and time to check the details of the amendments which are proposed by the expert group? According to the proposed mandate every delegation who has these resources is entitled to participate in the decision process of the expert groups. Wouldn’t that be more efficient than a separate discussion within WP.3 and SC.3? www.ris.eu ienc.openecdis.org 11

  12. Types of changes Changes that effect the whole standard:edition 2.3  edition 3.0Adoption by SC.3/WP.3 Amendments of new elements (as in the example):edition 2.3  edition 2.4Mandate for the expert groups (as granted by CCNR)? Corrections of existing annexes (without introduction of new elements or new rules):edition 2.3  edition 2.3 corr.Minimum mandate for the expert groups www.ris.eu ienc.openecdis.org 12

  13. Conclusion The mandate which has already been adopted by CCNR contains very strict regulations to prevent a misuse and ensures that every “political” amendment of the annexes has to be adopted by the international organizations SC.3/WP.3 is invited to decide whether a mandate for the maintenance of the annexes is given to the expert groups If not, SC.3/WP.3 is invited to provide at least a mandate for corrections of the annexes SC.3/WP.3 is invited to adopt edition 2.3 of the Inland ECDIS standard www.ris.eu ienc.openecdis.org 13

  14. Inland ECDIS expert groupwww.ris.euinland-ecdis@ris.eu Bernd Birklhuber Federal Ministry of Transport, Innovation and Technology Radetzkystrasse 2 A-1030 Wien Tel.: +43 1 71162 655902 Mobile: +43 664 8188909 E-mail: bernd.birklhuber@bmvit.gv.at www.ris.eu ienc.openecdis.org 14

  15. Number of Change Requests

  16. Too many and too quick changes? Everyone in the expert group is in favour of a stable standard But if a country has some objects which are not covered by the existing standard, it is hard to tell the country that they will have to wait 4 or 5 years until they can encode these objects in their IENCs Example: the Change Request to add wreck pontoons to the standard has been transmitted in summer 2009, but even if edition 2.3 enters into force this year, it can only be encoded when production tools and Inland ECDIS applications have been updated -> mid 2012 Is this really too quick? www.ris.eu ienc.openecdis.org 16

  17. e.g. objects,attributes andenumerationsof maritimeENCs Inland ENCdomain operational S-100 Geospatial Information (GI) Registry Supplementary FCD Register Inland ENCdomain planned Supplementary Portrayal Register Main Feature Concept Dictionary Register Supplementary Metadata Register Symbolization,under development Main Portrayal Register Supplementary Product Specifications Register Main Metadata Register FutureInland ENCProduct Specificationwill be registered Supplementary Data Producer Code Register Main Product Specifications Register e.g. S-101,underdevelopment Main Data Producer Code Register

  18. Overview IHO standards S-99: Operating rules for the registry (also for users outside of IHO, as e.g. IEHG) S-100: Registry (all inland specific objects are already registered) S-101: new Product Specification for maritime ENCs (until end 2012) S-10x: new Product Specification for bathymetric ENCs (under development) S-10x: new Product Specification for Nautical Publications (under development) www.ris.eu ienc.openecdis.org 18

  19. AML Gridded data ? Nautical Publications(S-102) ? Inland ENC 3D & temporal ? MIO Web services ? ? Sea ice UNCLOS boundaries High density bathymetry Future ENC(S-101) S-100 will support a variety of data sources, products and services S-100

More Related