ISO 17267:2009 インテリジェントトランスポートシステム—ナビゲーションシステム—アプリケーションプログラミングインターフェイス（API） | ページ 5

2.1

address location

application category that deals with the task of expressing a real world position in terms of the data representation

Note 1 to entry: Address location is one of the six application categories supported by the API.

2.2

address type

attribute of road section entity that specifies the type of house number ranges

2.3

application category

basic sub-function within the set of functionality for vehicle navigation and traveller information system applications

Note 1 to entry: This International Standard identifies six application categories: positioning; route planning; route guidance; map display; address location; services and POI information access.

2.4

application programming interface

API

standard interface and set of function calls between application software and data access libraries of vehicle navigation systems, in accordance with this International Standard

2.5

base map

all transportation elements and all services, including their relationships to transportation elements

2.6

branded third-party data

BTPD

information about services which is supplied by third-party data providers (e.g. tourist or motoring organizations), who may impose proprietary restrictions on the use and presentation of the data

Note 1 to entry: Access is subject to authorization and licensing.

Note 2 to entry: BTPD is a subset of third party data (TPD); see 2.54.

2.7

cartographic feature

data model entity that represents geometrical information for display purposes

Note 1 to entry: A cartographic feature has non-explicit topology; it has zero-, one- and two-dimensional types, i.e. Display Point, Polyline, and Polygon.

2.8

cartographic text

data model entity that stores name text associated with all or part of a cartographic feature

Note 1 to entry: Cartographic text is language dependent and may contain a suggested display location, orientation, language code, priority (or importance), suggested scale range, and bounding box.

2.9

condition

information related to link(s) composed of condition type, condition modifiers, and condition scope

2.10

crossroad

data model entity that represents the single instance of the crossing of two named navigable features

Note 1 to entry: Crossroad relates to the set of links and nodes which comprise the crossing, and to the crossing of the navigable features to a place.

2.11

destination node

node at the end of the link toward which travel takes place

Note 1 to entry: See also origin node (2.25), “from” node (2.14), “to” node (2.55), source node (2.50), and target node (2.53). When a link is travelled in the direction of topological orientation, the destination node is the “to” node. When it is travelled in the direction opposite topological orientation, the destination node is the “from” node.

2.12

display point

zero-dimensional type of cartographic feature

2.13

dummy point

optional 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

2.14

“from” node

node at the end of a link away from which the link is topologically oriented

Note 1 to entry: See also “to” node (2.55), origin node (2.25), destination node (2.11), source node (2.50), and target node (2.54). When a link is travelled in the direction of topological orientation, the “from” node is the origin node. When it is travelled in the direction opposite topological orientation, the “from” node is the destination node.

2.15

geocoding

determination of a link or node based on address information describing and/or naming a location

2.16

intersection

geographic data file (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

2.17

junction

data model entity that represents a navigable feature which is either a named GDF junction or named GDF intersection, and that relates a named navigable feature to a set of links and nodes and a place

2.18

landmark

point, line, or area feature, possibly associated with a node or link, that can be used to clarify the directions generated to describe a route

Note 1 to entry: A landmark may not be in the Services, Administrative Areas, or Public Transportation feature themes of a GDF; a facility in which a service is located may be a landmark.

2.19

layer

subset of map data resulting from a subdivision of data of the same coverage area based on contents and which is typically related to one or only a few of the application categories

Note 1 to entry: This is similar to an ISO-GDF layer.

2.20

level

subset of map data resulting from a classification of data of the same semantic content based on the level of detail or density, related to the concept of different map scales

Note 1 to entry: Level 0 is considered the lowest level (greatest detail); higher levels are numbered level 1, level 2, etc.

2.21

link

directed topological connection between two nodes, composed of an ordered sequence of one or more segments and represented by an ordered sequence of zero or more shape points (2.48)

2.22

map display

application category that deals with graphical information presentation

Note 1 to entry: Map display is one of the six application categories supported by the API.

2.23

multilink

ordered aggregation of links which are at the same level, are connected in sequence, and share the same functional classification, form of way, direction of travel, and perhaps additional characteristics

2.24

navigable feature name

data model entity that represents the name for the transportation element, including GDF road element, GDF ferry connection, GDF junction, GDF intersection

Note 1 to entry: Navigable feature name is related to places, crossroads, junctions, and road sections.

2.25

node

data model entity for a topological junction of two or more links or for end-bounding a link

Note 1 to entry: A node stores the coordinate value of the corresponding GDF junction.

2.26

origin node

node at the end of a link from which travel takes place

Note 1 to entry: See also destination node (2.11), “from” node (2.14), “to” node (2.55), source node (2.50), and target node (2.54). When a link is travelled in the direction of topological orientation, the origin node is the “from” node. When it is travelled in the direction opposite topological orientation, the origin node is the “to” node.

2.27

parcel

database partitioning unit corresponding to a certain coverage area, associated with one level and containing data of one or more layers

Note 1 to entry: A parcel contains (at least) all nodes with positions enclosed by or located on the outline of its coverage area plus (parts of) all links attached to these nodes; it can be partitioned so that the amount of data of a parcel may be nearly the same as that of another.

2.28

place

named area which can be used as part of the address location

2.29

place class

attribute of place entity, classifying into highest administrative or geographic division, administrative subdivision, postal, or colloquial (e.g. regions or neighbourhoods)

Note 1 to entry: Place class can be partially ordered as “place class A is below place class B“. This does not imply strict or complete containment.

2.30

place level

level associated with places of place classification “administrative subdivision”

Note 1 to entry: Higher/lower level situations are constituted by the occurrence of a parent/child place relationship between places.

2.31

place relationship

bivalent relationship between place entities, constituting the place tree linking parent and child places

Note 1 to entry: Place relationship does not imply strict or complete containment. It is attributed as: address significant, official, postal or useful for reverse geocoding.

2.32

point of interest

POI

destination and/or site of interest to travellers, usually non-commercial by nature

2.33

polygon

two-dimensional type of cartographic feature

2.34

polyline

one-dimensional type of cartographic feature

2.35

positioning

application category that deals with the determination of vehicle location and map matching

Note 1 to entry: Positioning is one of the six application categories supported by the API.

2.36

postal code

data model entity for a government-designated code used to specify regions for addressing

Note 1 to entry: Postal code is related to link (2.21), navigable feature name (2.23), place (2.27), and POI (2.31).

2.37

rectangle

unit of geographic space defined by two parallels of min./max. latitude and by two meridians of min./max. longitude and that represents the coverage area of the map data enclosed by or located on its outline

2.38

reverse geocoding

determination of the address description of a link or node, i.e. determination of an upwards path across the place tree

2.39

road

GDF level 2 feature composed of one, many or no road elements and joining two intersections, serving as the smallest independent unit of a road network at GDF level 2

2.40

road element side

RES

basic component of the road section entity that represents left or right side of a link and corresponds to one or more unique combinations of a navigable feature and a house number range

2.41

road section

data model entity that represents the house number ranges of both sides of a street and that carries a navigable feature name

Note 1 to entry: Road section corresponds to a link (ID).

2.42

route guidance

application category that deals with the generation of graphical, textual, and/or audio instructions for following a planned route

Note 1 to entry: Route guidance is one of the six application categories supported by the API.

2.43

route planning

application category that deals with the determination of routes between specified points

Note 1 to entry: Route planning is one of the six application categories supported by the API.

2.44

segment

straight section of a link connecting two successive shape points, or a shape point and a node, or two nodes where a link does not contain shape points

2.45

service

data model entity for a commercial activity of interest to travellers as a destination and/or orientation that is associated with road element(s) by which it can be accessed and further described by attributes including (at least) name and type

Note 1 to entry: A service may be associated with other services by parent/child relationships (many to many). Service is used synonymously with POI within the logical data model.

2.46

service attribute

item of descriptive information relating to a service

2.47

services and POI information access

application category that deals with the provision of POI information to the navigation application

Note 1 to entry: Services and POI information access is one of the six application categories supported by the API.

2.48

shape point

position along a link used to more accurately represent its geometric course, bounded by exactly two segments

2.49

signpost

data model entity for a directional sign that represents a logical relationship between signpost information and two associated links

Note 1 to entry: The first link (mandatory) represents the road element along which the signpost is located. The second link (optional) is the first road element which directs exclusively to the destination indicated on the signpost. The position of the signpost along the link and the link direction the signpost is facing is also stored.

2.50

source node

node at the end of a link from which exploration takes place for route calculation

Note 1 to entry: See also target node (2.53), origin node (2.25), destination node (2.11), “from” node (2.14), and “to” node (2.55). When forward exploration is taking place from the origin of the route, the source node of a link is its origin node. When reverse exploration is taking place from the destination of the route, the source node of a link is its destination node.

2.51

super link

aggregation of linearly connected regular links present in the lowest level as a simplified representation of the road network in higher levels

2.52

symbol

data model entity that represents an icon associated with a cartographic feature

2.53

target node

node at the end of a link towards which exploration takes place for route calculation

Note 1 to entry: See also source node (2.50), origin node (2.25), destination node (2.11), “from” node (2.14), and “to” node (2.56). When forward exploration is taking place from the origin of the route, the target node of a link is its destination node. When reverse exploration is taking place from the destination of the route, the target node of a link is its origin node.

2.54

third party data

TPD

information about services, which is supplied by third party data providers (e.g. tourist or motoring organizations), typically with a rich content of descriptive data

2.55

“to” node

node at the end of a link towards which the link is topologically oriented

Note 1 to entry: See also “from” node (2.14), origin node (2.25), destination node (2.11), source node (2.50), and target node (2.54). When a link is travelled in the direction of topological orientation, the “to” node is the destination node. When it is travelled in the direction opposite topological orientation, the “to” node is the origin node.

2.56

traffic location

data model entity that contains an external reference (e.g. VICS or RDS-TMC) and is linked to either place or transportation entities

2.57

transportation element

feature from the Roads and Ferries feature theme of a GDF