1、 Reference number ISO/TS 20452:2007(E) ISO 2007TECHNICAL SPECIFICATION ISO/TS 20452 First edition 2007-06-15 Requirements and Logical Data Model for a Physical Storage Format (PSF) and an Application Program Interface (API) and Logical Data Organization for PSF used in Intelligent Transport Systems
2、(ITS) Database Technology Exigences et modle de donnes logiques pour un format de stockage physique (PSF), une interface de programme dapplication (API) et une organisation de donnes logiques pour un PSF utilis dans la technologie de base de donnes des systmes de transport intelligents (ITS) ISO/TS
3、20452:2007(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloadi
4、ng this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the Gene
5、ral Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given
6、 below. COPYRIGHT PROTECTED DOCUMENT ISO 2007 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the a
7、ddress below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2007 All rights reservedISO/TS 20452:2007(E) ISO 2007 All righ
8、ts reserved iii Contents Page Foreword iv Introduction v 1 Scope . 1 2 Normative references . 1 3 Terms and definitions. 1 4 Symbols and abbreviated terms . 7 4.1 Abbreviations 7 4.2 Syntax notation used in data model diagrams 8 5 Application categories . 9 5.1 Positioning 9 5.2 Route Planning 11 5.
9、3 Route Guidance 15 5.4 Map Display . 17 5.5 Address Location 21 5.6 Service and POI Information Access 32 6 Logical Data Model . 37 6.1 Overall model 37 6.2 Transportation Entities. 39 6.3 Address Location entities 42 6.4 Service/POI entities 43 6.5 Cartographic entities 44 6.6 Dynamic Traffic Info
10、rmation entities 46 7 Logical Data Organization . 47 7.1 Global architecture . 47 7.2 Detailed Road Data . 51 7.3 Detailed Background Data . 51 7.4 Map Display Data 51 7.5 Route Planning data . 52 7.6 Address Location data . 52 7.7 Service Data 52 7.8 Traffic Information 53 7.9 Metadata 53 Bibliogra
11、phy . 54 ISO/TS 20452:2007(E) iv ISO 2007 All rights reservedForeword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical commi
12、ttees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the I
13、nternational Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft Internationa
14、l Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. In other circumstances, particularly when there is an urgent market requirement for such do
15、cuments, a technical committee may decide to publish other types of normative document: an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in an ISO working group and is accepted for publication if it is approved by more than 50 % of the members of th
16、e parent committee casting a vote; an ISO Technical Specification (ISO/TS) represents an agreement between the members of a technical committee and is accepted for publication if it is approved by 2/3 of the members of the committee casting a vote. An ISO/PAS or ISO/TS is reviewed after three years
17、in order to decide whether it will be confirmed for a further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an International Standard or
18、 be withdrawn. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO/TS 20452 was prepared by Technical Committee ISO/TC 204, Intelligent transport sys
19、tems. ISO/TS 20452:2007(E) ISO 2007 All rights reserved v Introduction ISO/NP 14826, Physical Storage for TICS Database Technology, was introduced into ISO/TC 204 with the objective of standardizing a physical storage format (PSF) for navigation map data and related information stored on physical me
20、dia used by in-vehicle navigation systems. The intent was to facilitate an interoperable in-vehicle navigation market environment by developing a standard PSF that would enable navigation media offered by different providers to be used by any navigation system and navigation systems made by any deve
21、loper to be able to read the same media. There was widespread international participation in this effort. Many of the different companies within the different participating national delegations possessed their own respective formats 1)that were commercially available. It was decided early on that si
22、nce none of these existing formats would be adopted wholesale as the standard physical storage format, the functional requirements of these existing systems would be submitted and consolidated into a universal set and organized into the major categories of application functionality predominantly use
23、d by in-vehicle navigation systems. This gathering of market-driven requirements was the first step of an agreed development process that would proceed according to a top-down development approach. A sequential work plan was defined which included a logical data model based on the requirements, foll
24、owed by the development of a logical organization of the data types used in the model. This logical data organization (LDO) would be used as a basis for the definition of a physical data organization (PDO), which would be defined to a sufficient level of granularity to specify a single standard PSF.
25、 It took several years to develop and gain consensus on the requirements, the logical data model, and the logical data organization. During the development there were several input documents submitted by various national delegations. At the beginning of the development of the PDO it was decided to u
26、se a Japanese PDO input document 2)as a framework for the PDO discussion. Shortly after the PDO discussion began, the project ISO/NP 14826 expired and there was not sufficient international support for resubmitting a new work item proposal to continue the work, nor was there consensus that the PDO w
27、ork could be finished within an acceptable time frame. Consequently, a standard PSF as envisioned within the scope of the work item would not be realized. However, the requirements, logical data model, and logical data organization documents developed in this process reflect international consensus
28、and still provide value for the navigation system market and other emerging products and services which use navigation map data. Thus it was agreed to convert these documents into a Technical Specification which could be used for future developments. This Technical Specification can help developers
29、of applications that use map databases to realize efficiencies by providing guidelines on setting up an appropriate architecture for navigation systems. This provides a potential benefit to the developers ability to develop systems in a shorter timeframe, thereby shortening time-to-market for produc
30、ts. Although this Technical Specification was originally developed for navigation system applications, it may also facilitate other market development activities by providing insight into solving common data modelling and organization issues in the fields of telematics and location-based services. 1
31、) These formats are identified in the Bibliography of this Technical Specification. 2) Kiwi Format Specification version 1.2.2 (see Bibliography). TECHNICAL SPECIFICATION ISO/TS 20452:2007(E) ISO 2007 All rights reserved 1 Requirements and Logical Data Model for a Physical Storage Format (PSF) and a
32、n Application Program Interface (API) and Logical Data Organization for PSF used in Intelligent Transport Systems (ITS) Database Technology 1 Scope This Technical Specification describes the functional requirements and Logical Data Model for PSF and API and the Logical Data Organization for PSF that
33、 were completed under ISO/NP 14826. It does not specify a Physical Data Organization. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of
34、the referenced document (including any amendments) applies. ISO 14825, Intelligent transport systems Geographic Data Files (GDF) Overall data specification 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 Address Location application category
35、that deals with the task of expressing a real-world position in terms of the PSF data representation NOTE Address Location is one of the six application categories supported by the PSF and the API. 3.2 address type attribute of road section entity, specifying the type of house number ranges EXAMPLE
36、distinction between base address, county address, commercial address, etc., or no address. 3.3 application category basic sub-function within the set of functionality for vehicle navigation and traveller information system applications NOTE This Technical Specification identifies six application cat
37、egories: Positioning, Route Planning, Route Guidance, Map Display, Address Location, Services and POI Information Access. ISO/TS 20452:2007(E) 2 ISO 2007 All rights reserved3.4 Application Program Interface API ISO context specification interface and set of function calls between application softwar
38、e and data access libraries of vehicle navigation systems 3.5 base map the whole of all transportation elements and all services, including their relationships to transportation elements 3.6 Branded Third Party Data BTPD information about services which is supplied by third party data providers (e.g
39、. tourist or motoring organizations) who may impose proprietary restrictions on the use and presentation of the data NOTE 1 Access to BTPD is subject to authorization and licensing. NOTE 2 BTPD is a sub-set of Third Party Data (TPD). 3.7 cartographic feature data model entity that represents geometr
40、ical information for display purposes, having non-explicit topology and 0-, 1- and 2-dimensional types EXAMPLES Display Point, Polyline and Polygon. 3.8 cartographic text data model entity that stores name text that is associated with all or part of a cartographic feature NOTE It is language-depende
41、nt and can contain a suggested display location, orientation, language code, priority (or importance), suggested scale range, and bounding box. 3.9 condition information related to link(s) which is composed of condition type, condition modifiers and condition scope 3.10 crossroad data model entity t
42、hat represents the single instance of the crossing of two named navigable features; it relates to the set of links and nodes which comprise the crossing, and to the crossing of the navigable features to a place 3.11 display point 0-dimensional type of cartographic feature 3.12 dummy point non-requir
43、ed entity that represents a position along a link where the link crosses a parcel boundary and does not necessarily coincide with a shape point or node 3.13 geocoding determination of a link or node based on address information describing and/or naming a location ISO/TS 20452:2007(E) ISO 2007 All ri
44、ghts reserved 3 3.14 intersection GDF level 2 representation of a crossing which bounds a road or a ferry as a complex feature composed of one or more GDF level 1 junctions, road elements and enclosed traffic areas 3.15 junction data model entity that represents a navigable feature which is either a
45、 named GDF junction or named GDF intersection, and that relates a named navigable feature to a set of links and nodes and a place 3.16 landmark point, line or area feature that can be used to clarify the directions generated to describe a route NOTE 1 It can be associated to a node or a link. NOTE 2
46、 A landmark cannot be in the Services, Administrative Areas, or Public Transportation Feature themes of the GDF; however a facility in which a service is located can be a landmark. 3.17 layer sub-set of map data resulting from a subdivision of data of the same coverage area based on contents (simila
47、r to ISO-GDF layer) and which is typically related to one or only a few of the application categories EXAMPLE Route guidance data can be considered as one layer. 3.18 level sub-set of map data resulting from classification of data of the same semantically contents based on the level of details/densi
48、ty, related to the concept of different map scales NOTE Level 0 is considered the lowest level (greatest detail); higher levels are numbered level 1, level 2, etc. EXAMPLE Map display data can be organized into 6 levels representing different zoom scales. 3.19 link directed topological connection be
49、tween two nodes, composed of an ordered sequence of one or more segments and represented by an ordered sequence of zero or more shape points 3.20 Map Display application category that deals with graphical information presentation NOTE Map Display is one of the six application categories supported by the PSF and the API. 3.21 multilink ordered aggregation of links which are at the same level, connected in sequence, share the same functional classification, form of way, direction of travel, and perhaps additional PSF-builder-specified chara
