S-57 Appendix B.2 IHO Object Catalogue Data Dictionary Product Specification. This document must only be used with Edition 3.1 of S-57. Edition 2.



Similar documents
S-57 MAINTENANCE DOCUMENT (Cumulative)

Core Fittings C-Core and CD-Core Fittings

Best Practices for Data Dictionary Definitions and Usage Version

Guidelines for exchange of danmarc2 records in MarcXchange

ANNEX C to ADDITIONAL MILITARY LAYERS GRIDDED SEDIMENT ENVIRONMENT SEABED BEACH PRODUCT SPECIFICATION Version 1.0, 26th July 2005

Geospatial Information in the Statistical Business Cycle 1

Enterprise Data Dictionary Standards

Schema Design Patterns for a Peta-Scale World. Aaron Kimball Chief Architect, WibiData

Product Navigator User Guide

Common Event Expression

AHDS Digital Preservation Glossary

Core Components Data Type Catalogue Version October 2011

NATIONAL BANK OF ROMANIA

ENHANCEMENTS TO SQL SERVER COLUMN STORES. Anuhya Mallempati #

Caml Virtual Machine File & data formats Document version: 1.4

Inventory Update API User Documentation

Transaction Inquiries

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands

Streaming Lossless Data Compression Algorithm (SLDC)

Modbus and ION Technology


SenseLink TM. End-Point Controller. Addendum

IT2304: Database Systems 1 (DBS 1)

Communicating access and usage policies to crawlers using extensions to the Robots Exclusion Protocol Part 1: Extension of robots.

IT2305 Database Systems I (Compulsory)

DATA ITEM DESCRIPTION

Question 1. Relational Data Model [17 marks] Question 2. SQL and Relational Algebra [31 marks]

SQL Server 2008 Core Skills. Gary Young 2011

Course Syllabus. Course 80011: Development I in Microsoft Dynamics AX Key Data. Introduction. Audience

From Data Modeling to Data Dictionary Written Date : January 20, 2014

Section of DBMS Selection & Evaluation Questionnaire

EMBL-EBI. Database Replication - Distribution

Field Properties Quick Reference

HP LeftHand SAN Solutions

DATA_TYPE Values and Data File Storage Formats

GetLibraryUserOrderList

KMx Enterprise: Integration Overview for Member Account Synchronization and Single Signon

DIGITAL SIGNATURE FOR EANCOM MESSAGES

Chapter 5: The DAITSS Archiving Process

1. Write the query of Exercise 6.19 using TRC and DRC: Find the names of all brokers who have made money in all accounts assigned to them.

Chapter 1: Introduction

Automating SQL Injection Exploits

ISO/TMB/JTCG N 359. N0359 JTCG FAQ to support Annex SL. Document type: Other committee document. Date of document:

XES. Standard Definition. Where innovation starts. Den Dolech 2, 5612 AZ Eindhoven P.O. Box 513, 5600 MB Eindhoven The Netherlands

Secure Envelope specification

Reporting Suite ETD March 2014 DTCC

Lecture 5: Foundation of Network Management

INTERNATIONAL TELECOMMUNICATION UNION

Conversion of Measurement Data from MDF to ATFX

A Rational Software Whitepaper

System and Network Management

Designing Hash functions. Reviewing... Message Authentication Codes. and message authentication codes. We have seen how to authenticate messages:

F o r e i g n p a y m e n t i n P o l a n d Page 1 of 6 B u s i n e s s O n l i n e

DICOM Conformance Statement

Cadastre in the context of SDI and INSPIRE

SIX Trade Repository AG

[MS-SPACSOM]: Intellectual Property Rights Notice for Open Specifications Documentation

Raima Database Manager Version 14.0 In-memory Database Engine

Nintex Workflow 2013 Help

mdwfs Model-driven Schema Translation for Integrating Heterogeneous Geospatial Data

Cloud Powered Mobile Apps with Azure

QUALITY ASSURANCE and QUALITY CONTROL DATA STANDARD

In-memory databases and innovations in Business Intelligence

Data Discovery & Documentation PROCEDURE

997 Functional Acknowledgment

Clemens Portele interactive instruments GmbH

Chapter 8 Access Database

ALLIED PAPER : DISCRETE MATHEMATICS (for B.Sc. Computer Technology & B.Sc. Multimedia and Web Technology)

Format description of MT103 (Multicash PLA) foreign payment file.

EPSS Helpdesk - workdays from 08:00 to 20:00 - Phone: support@epss-fp7.org

Managed App Configuration for App Developers. February 22, 2016

Analysis of Web Archives. Vinay Goel Senior Data Engineer

Lesson 8: Introduction to Databases E-R Data Modeling

Extensible Data Model with Applications for Trading Systems

Developer Guide. Christian W. Günther Library version: 1.0 RC7 Revision: 7

HOST EUROPE CLOUD STORAGE REST API DEVELOPER REFERENCE

Table Of Contents. iii

DRAFT S-100 UNIVERSAL HYDROGRAPHIC DATA MODEL

Translating QueueMetrics into a new language

Enabling embedded maps

Parquet. Columnar storage for the people

LICENSE4J LICENSE MANAGER USER GUIDE

Core Syllabus. Version 2.6 B BUILD KNOWLEDGE AREA: DEVELOPMENT AND IMPLEMENTATION OF INFORMATION SYSTEMS. June 2006

Services and Data Definitions

Software Requirements Specification. Task Management System. for. Prepared by. Version 1.0. Group Name: Pink and Purple. Date:

Arithmetic Coding: Introduction

EXCEL IMPORT user guide

Title Page. payplace.express giropay Connection for traders and integrators

DBMS Questions. 3.) For which two constraints are indexes created when the constraint is added?

Abstract Syntax Notation One ASN.1. ASN.1 Abstract Syntax Notation One

Transcription:

S-57 Appendix B.2 IHO Object Catalogue Data Dictionary Product Specification This document must only be used with Edition 3.1 of S-57 Edition 2.0

IHO Object Catalogue Data Dictionary Product Specification Page intentionally left blank Edition 2.0 November 2000 S-57 Appendix B.2

IHO Object Catalogue Data Dictionary Product Specification i CONTENTS 1. Introduction...1 1.1 General...1 1.2 Contents of the document...1 2. Provision of data...1 2.1 Content of an exchange set...1 2.2 Implementation...1 2.3 Compression...1 2.4 File naming...1 2.5 Media...1 3 Updating...1 4 Application profile...2 4.1 General...2 4.2 File structure...2 4.2.1 Field content...3 4.2.1.1 Data Dictionary Definition field - DDDF...3 4.2.1.2 Data Dictionary Definition Reference field...3 4.2.1.3 Data Dictionary Domain Identified field...3 4.2.1.4 Data Dictionary Domain field...4 4.2.1.5 Data Dictionary Domain Reference field...4 4.2.1.6 Data Dictionary Schema Identifier field...4 4.2.1.7 Data Dictionary Schema field...4 S-57 Appendix B.2 November 2000 Edition 2.0

ii IHO Object Catalogue Data Dictionary Product Specification Page intentionally left blank Edition 2.0 November 2000 S-57 Appendix B.2

IHO Object Catalogue Data Dictionary Product Specification 1 1. Introduction 1.1 General The Data Dictionary Product Specification is a set set of rules that must be followed in the encoding of a data dictionary exchange set based on the IHO Object Catalogue (Appendix B of S-57). 1.2 Contents of the document The Data Dictionary Product Specification contains an application profile that defines the records, fields and subfields that are to be used in the transfer of the information contained in the Object Catalogue (Appendix B of S-57). 2. Provision of data 2.1 Content of an exchange set A data dictionary exchange set consists of one file containing data dictionary records. An optional README.TXT file may be provided. There may not be any other files associated with a data dictionary exchange set. 2.2 Implementation Only ASCII text may be used in the exchange set. 2.3 Compression The Data Dictionary file may be compressed using any appropriate compression algorithm. Use of such algorithms must be described in the README.TXT file which must not be compressed. 2.4 File naming The data dictionary file must be named IHOOCDD.XXX where: IHOOCDD is the mandatory file name XXX is used to indicate the edition number of the Object Catalogue used for this exchange set; i.e. 031 for this edition (3.1) README.TXT is the mandatory name of the optional text information file. 2.5 Media Data may be provided via telecommunications links or any physical media. 3 Updating The content of a data dictionary exchange set can only be updated by direct replacement. Therefore, changes to any information within the exchange set require that a complete new exchange set is generated. 4 Application profile S-57 Appendix B.2 November 2000 Edition 2.0

2 IHO Object Catalogue Data Dictionary Product Specification 4.1 General The application profile defines the structure and content of the data dictionary file. 4.2 File structure Only records and fields that are defined in the following tree structure diagrams may be used in the data dictionary file. The order of records within the data dictionary file must be the same as that shown in the following tree structure diagrams (i.e. all Data Dictionary Definition records before any Data Dictionary Domain records etc.). In the tables following the tree structure diagrams mandatory subfields are shown by "M" in the "use" column. If there is nothing in this column it means the use of the subfield is optional. Where a value is prescribed it is shown in the "value" column. "OC" in the comment column is used to indicate the Object Catalogue (Appendix B of S-57). Data dictionary file <R> Data Dictionary Definition record 0001 ISO 8211 Record identifier DDDF Data Dictionary Definition field DDDR* Data Dictionary Definition Reference field <R> Data Dictionary Domain record 0001 8211 Record identifier DDDI Data Dictionary Domain Identifier field <R> DDOM Data Dictionary Domain field DDRF* Data Dictionary Domain Reference field <R> Data Dictionary Schema record 0001 ISO 8211 Record identifier DDSI Data Dictionary Schema Identifier field DDSC* Data Dictionary Schema field Edition 2.0 November 2000 S-57 Appendix B.2

IHO Object Catalogue Data Dictionary Product Specification 3 4.2.1 Field content 4.2.1.1 Data Dictionary Definition field - DDDF tag subfield name use value commment RCNM Record name M ID RCID Record identification number M OORA Object or attribute M O for object A for attribute OAAC Object or attribute acronym M acronym from the OC OACO Object or attribute label/code M numeric code from the OC OALL Object or attribute long label M long label from the OC OATY Type of object or attribute M M Meta object $ Cartographic object G Geo object C Collection object F Feature attribute N Feature national attribute S Spatial attribute DEFN Definition M definition from the OC AUTH Authorizing agency M from Annex A of the OC COMT Comment 4.2.1.2 Data Dictionary Definition Reference field RFTP Reference type from the OC RFVL Reference value from the OC 4.2.1.3 Data Dictionary Domain Identifier field RCNM Record name M IO RCID Record identification number M ATLB Attribute label/code M numeric code from the OC ATDO Attribute domain type M E Enumerated L List F Float I Integer A Coded string S Free text format ADMU Attribute domain value measurement for float and integer attributes units ADFT Attribute domain format AUTH Authorizing agency M from Annex A of the OC COMT Comment S-57 Appendix B.2 November 2000 Edition 2.0

4 IHO Object Catalogue Data Dictionary Product Specification 4.2.1.4 Data Dictionary Domain field RAVA Range or value M M DVAL contains the maximum value N DVAL contains the minimum value V DVAL contains a specific value DVAL Domain value M attribute value from the OC DVSD Domain value short description M attribute value description from the OC DEFN Domain value definition M attribute value definition from the OC AUTH Authorizing agency M from Annex A of the OC 4.2.1.5 Data Dictionary Domain Reference field RFTP Reference type RFVL Reference value 4.2.1.6 Data Dictionary Schema Identifier field RCNM Record name M IS RCID Record identification number M OBLB Object label/code M numeric code from the OC 4.2.1.7 Data Dictionary Schema field ATLB Attribute label/code M numeric code from the OC ASET Attribute set M A attribute set A B attribute set B C attribute set C AUTH Authorizing agency M from Annex A of the OC Edition 2.0 November 2000 S-57 Appendix B.2