UN Economic Commission for EuropeSection 2: Data Standard
Inland ECDIS StandardAppendix B: Product Specifications
Edition 1.0
31.05.2001
Standard
Electronic Chart Display and Information System
for Inland Navigation
Inland ECDIS
SECTION 2
Data Standard for Inland ECDIS
Appendix B
Product Specification for Inland ECDIS
in addition to the
IHO-S-57 ENC Product Specification
Contents
1General...... 107
2Additions to the ENC Product Specification of IHO...... 107
to 2.2Cells...... 107
to 3.3Objects permitted for use in ENC and their geometric primitives...... 107
to 3.4Meta objects...... 108
to 3.5.2Mandatory attributes...... 108
to 3.7Time varying objects...... 108
to 4.1Horizontal datum...... 108
to 5.6.3Data set files......
to 6.3.2.1Data set identification field...... 110
1General
This Product Specification for Inland ECDIS is a set of specifications intended to enable ENC manufacturers to produce consistent Inland ENC, and to use data efficiently in an ECDIS application that satisfies the Performance Standards for Inland ECDIS (Section 1 of this Standard for Inland ECDIS). An Inland ENC shall be produced in accordance with the regulations defined in these documents:
- this Product Specification for Inland ECDIS
- Annex A "Use of the Object Catalogue for Inland ECDIS"
- Appendix B.1 to the Standard IHO-S-57 ("ENC Product Specification")
- the documents, that are listed as references in Section 1 of this Standard for Inland ECDIS in clause 2. 2
Definitions of the used terms may be found in Section 5 ("Glossary of Terms") of this standard.
The numbering correlates to S-57 Appendix B.1.
2Additions and Clarifications to the "ENC Product Specification" of the IHO
Further to 2.2Cells
In the ENC Product Specification of S-57 (Appendix B.1 it ) it is stated that areas of a cell which do not contain data must be indicated by a meta object M_COVR with CATCOV=2. This shall not be applied to Inland ENCs.
Further to 3.3Objects permitted for use in ENC and their geometric primitives
The following object classes were copied for use in Inland ENC.
Achare / P / A / achbrt / P / A / berths / P / L / A / bridge / P / L / ACblohd / L / canbnk / L / depare / A / dismar / P
Feryrt / L / A / hrbare / A / hrbfac / P / A / lokbsn / A
m_nsys / A / rdocal / P / L / resare / A / rivbnk / L
Sistat / P / sistaw / P / topmar / P
Table 3.1
P = point, L = line, A= area
The official object classes CANBNK and RIVBNK are existing in S-57 but their application is not permitted any more.
The copied object class depare may only be applied if it shall be updated to the current waterlevel.
The following object classes were added for use in Inland ENC.
Bcnwtw / P / brgare / A / boywtw / P / bunsta / PComare / A / hrbbsn / A / locare / A / lkbspt / A
Notmrk / P / prtare / A / refdmp / P / P / A
Trnbsn / P / A / wtwaxs / L / wtwprf / L
Table 3.2
The application of the waterway axis object class wtwaxs (waterway axis) with the object dismar (distance mark) is mandatory.
Further to 3.4Meta objects
The meta object m_nsys with the attribute marsys (to indicate the system of navigational marks) must provide an exhaustive non-overlapping coverage of the part of the cell containing data.
Further to 3.5.2Mandatory attributes
The following attributes are mandatory for object classes, which were
- added for use in Inland ENC (new) or
- which already exist and have been extended for use in Inland ECDIS (copied):
Object Class / Attributes
Bcnwtw / catwwm / BCNSPH / COLOUR
Bcnwtw / catwwm / BOYSHP / COLOUR
Bridge / if fixed
if not fixed / VERCLR
VERCCL / VERCOP
Cblohd / VERSCA / or if this is unknown / VERCLR
Depare / DRVAL1 / DRVAL2
Dismar / if located on axis / INFORM
Notmrk / fnctnm / catnmk / dirimp
Topmar / marsys / TOPSHP
Wtwaxs / OBJNAM
Table 3.3
Further to 3.7Time varying objects
The Inland ENC may contain time independent depth information as "minimum required depth" (Solltiefe in German) related to a reference waterlevel (on the Rhine river the "Equivalent Water Level" GlW).
Besides that Inland ECDIS may also contain time-variable depth information related to the actual water level at reference gauges. The rules for this will be formulated in an update of this standard when sufficient experience is gained.
Further to 4.1Horizontal datum
The horizontal datum of an Inland ENC shall be WGS-84. In the case that the data are transformed to WGS-84 from a local datum the responsible authority shall define the area where the local transformation parameters apply. Within this area, the difference between transformed coordinates and the surveyed WGS84 coordinates may not exceed 0.5 m. For approval purposes, the responsible authority shall define appropriate reference points (surveyed WGS-84 coordinates) preferably exactly at the limit line of two adjacent areas. Reference points, transformation parameters and the algorithm shall be published and shall be the basis for Inland ENC production for that area.
To 5.6.3Data set files
A valid data set file must be uniquely identified world wide by its name.
The data set files are named according to the specifications given below:
CCPRRDDD.EEE
|||||
|||||-----EEE= update number
||||------DDD= waterway distance (kilometre)
|||------RR= waterway code
||------P= navigational purpose
|------CC= producer code
The main part forms an eight-character identifier where:
- The first two characters (CC) identify the producer. This list is given in Section 2, Appendix A, Annex A (Codes for Producers and Waterways).
- the third character (P) indicates the navigational purpose (see clause 2.1 of the IHO Product Specification).
- the fourth and fifth characters (RR) identify the waterway. (This list is also given in Section 2, AppendixA, Annex A).
- the sixth to eighth characters (DDD) are used for the waterway distance, e.g. if the cell covers the stretch from km 640 to km 650 the string will be “640”.
The primarily produced base cell file has the extension (EEE) 000.
The extension is used for updating. Update cell files have the same name as the original base cell file, with an extension number greater than or equal to 001. They cover the same geographical area as the base cell file to which they apply.
To 6.3.2.1Data set identification field
Inland ENCs are considered as an independent product besides ENCs. To recognise a S-57 dataset as an Inland ENC the content of following two subfields has to be changed.
tag / subfield name / use / value / commentSTED / Edition number of S-57 / M / 03.1 * / ASCII
PRSP / Product Specification / M / {2} / = INC, binary
* This is the edition number of the Inland ECDIS Standard
Edition 1.0Section 2_Appendix BPage 1
31.05.2001