欢迎转载,转载时请注明出处和作者联系方式
文章出处:http://blog.csdn.net/shaojieli
作者联系方式:李少杰 <lishaojie@126.com>
9. Region DataManagement Frame
name [Region Data Management Frame]
No. | offset | Data length | Data type | Item name | Remarks | Classification |
1 | 0 | B1 |
| Region Data Management Distribution Header |
| a |
2 | - | - | - |
|
| c |
3 | free | B2 |
| Relation Management Table |
| a |
4 | - | - | - |
|
| c |
5 | free | B3 |
| Common Traffic Condition Table | (1) | c |
(1) Common Traffic Condition Table
This table contains traffic codes that are common toall route planning data frames. The detail is similar to the description ofTraffic Condition Table provided in Chapter 10.
9.1 Region Data ManagementDistribution Header
Level management records areplaced, according to the level, so that higher level one will always precedelower level one. If a dummy region management record exists, the header alwaysretains, in the first position, the level management record that designates thedummy region management record.
name [Region Data ManagementDistribution Header]
No. | offset | Data length | Data type | Item name | Remarks | Classification |
1 | 0 | 2 | SWS | Header Size | (1) | a |
2 | 2 | 2 | :B | Region Management Record Type Code | (2) | a |
3 | 4 | 4 | N | Total Number of Region Management Records | (3) | a |
4 | 8 | 4 | DSA | Address of Region Management Table | (4) | a |
5 | 12 | 2 | BS | Size of Region Management Table | (5) | a |
6 | 14 | 12 | C | File Name of Region Management Table | (6) | b |
7 | 26 | 4 | DSA | Address of Common Traffic Condition Table | (7) | b |
8 | 30 | 2 | BS | Size of Common Traffic Condition Table | (8) | b |
9 | 32 | 12 | C | File Name of Common Traffic Condition Table | (9) | b |
10 | 44 | 2 | SWS | Common Traffic Condition Record Size | (9-1) | b |
11 | 46 | 1 | N | Total Number of Level Management Records | (10) | a |
12 | 47 | 1 |
| (RESERVED) |
| a |
13 | 48 | 2 | SWS | Level Management Record Size | (11) | a |
14 | 50 | 16*n |
| A Sequence of Level Management Records |
| a |
9. 区域数据管理帧
名称 [区域数据管理帧]
序号 | 偏移量 | 长度 | 数据类型 | 项名称 | 备注 | 类别 |
1 | 0 | B1 |
| 区域数据管理分布头 |
| a |
2 | - | - | - |
|
| c |
3 | free | B2 |
| 关系管理表 |
| a |
4 | - | - | - |
|
| c |
5 | free | B3 |
| 公共交通条件表 | (1) | c |
(1) 公共交通条件表
本表包含了对所有路线规划数据帧都通用的交通代码,具体内容和第10章描述的交通条件表相似。
9.1 区域数据管理分布头
层管理记录是根据层的内容来生成的,所以较高的一层总是优先于较低的一层,如果存在一个虚拟的区域管理记录,分布头总是保留在第一位,由层管理记录指定虚拟的区域管理记录。
名称 [区域数据管理分布头]
序号 | 偏移量 | 长度 | 数据类型 | 项名称 | 备注 | 类别 |
1 | 0 | 2 | SWS | 分布头大小 | (1) | a |
2 | 2 | 2 | :B | 区域管理记录类型码 | (2) | a |
3 | 4 | 4 | N | 区域管理记录数 | (3) | a |
4 | 8 | 4 | DSA | 区域管理表地址 | (4) | a |
5 | 12 | 2 | BS | 区域管理表大小 | (5) | a |
6 | 14 | 12 | C | 区域管理表文件名 | (6) | b |
7 | 26 | 4 | DSA | 公共交通条件表地址 | (7) | b |
8 | 30 | 2 | BS | 公共交通条件表大小 | (8) | b |
9 | 32 | 12 | C | 公共交通条件表文件名 | (9) | b |
10 | 44 | 2 | SWS | 公共交通条条件记录大小 | (9-1) | b |
11 | 46 | 1 | N | 层管理记录总数 | (10) | a |
12 | 47 | 1 |
| (预留) |
| a |
13 | 48 | 2 | SWS | 层管理记录大小 | (11) | a |
14 | 50 | 16*n |
| 层管理记录序列 |
| a |
(1) Header Size
Thisfield describes the size of the region data management distributionheader. If the header entity does notexist, 0 is assigned to this field.
(2) RegionManagement Record Type Code
No. | bit | Description |
1 | 15 to 8 | (RESERVED) |
2 | 7 to 0 | Represents the region management record type code. The value ranges from 0 to 254, and 255 is assigned to "null." How to mange region management records differs, according to the record type. The values more than 200 are assigned for the user extension type code. |
(3) Total Number of Region Management Records
Thisfield describes the number of region management records that constitute aregion management table managed by the region data management distributionheader.
(4) Address of Region Management Table
Thisfield describes the storage location of a region management table managed bythe region data management distribution header.
(5) Size of Region Management Table
Thisfield describes the size of a region management table managed by the regiondata management distribution header.
(6) File Name of Region Management Table
If afile is used to store the region management table managed by the region datamanagement distribution header, the file name setting must be specified. Specify the file name setting in 12 bytesincluding its extension. Left justify the setting and pad space with 00(16). Ifno file information is required, pad all the area of 12 bytes with 00(16).
(7) Address of Common Traffic Condition Table
Thisfield describes the storage location of a common traffic condition table managedby the region data management distribution header.
(8) Size of Common Traffic Condition Table
Thisfield describes the size of a common traffic condition table managed by theregion data management distribution header.
(9) File Name of Common Traffic Condition Table Ifa file is used to store the common traffic condition table managed by theregion data management distribution
header,the file name setting must be specified. Specify the file name setting in 12 bytes including its extension. Leftjustify the setting and pad space with 00(16). If no file information isrequired, pad all space of 12 bytes with 00(16). (9-1) Common Traffic ConditionRecord Size
Designatesthe size of common traffic condition records that constitute the common trafficcondition table.
(10)Total Number of Level Management Records
Thisfield describes the number of level management records managed by the regiondata management distribution header.
(11)Level Management Record Size
This field describesone record size of the level management records managed by the region datamanagement distribution header. If the level management records have noexpansion data, the record size is set with 8 (16) bytes. If the records have expansion fields, therecord size including the expansion fields must be described.
(1) 分布头大小
描述区域数据管理分布头大小,如果头实体不存在,值为0。
(2) 区域管理数据类型码
序号 | 位 | 描述 |
1 | 15 to 8 | (保留) |
2 | 7 to 0 | 表示区域管理记录类型码。取值范围为0-254,255表示值为空,根据记录的类型来管理区域管理记录。大于200的值用来表示用户扩展类型。 |
(3)区域管理记录总数
描述区域管理记录数。区域数据管理分布头管理区域管理表,区域管理表是由区域管理记录构成。
(4)区域管理表地址
区域管理分布头所管理的区域管理表的存储位置。
(5)区域管理表大小
区域管理公布头所管理的区域管理表大小。
(6)区域管理表文件名
如果有一个文件来存储区域管理表,则必须指定这个文件的文件名。文件名的规则为:包含扩展名在内,共12个字节,如果不足12字节,则左端以十六进制的数字零填充(00)。如果文件信息是不需要的,则全部用0填充。
(7)公共交通条件表地址
描述公共交通条件表存储位置。
(8)公共交通条件表大小
描述公共交通条件表的大小。
(9)公共交通条件表文件名
如果有一个文件来存储公共交通条件表,则必须指定这个文件的文件名。 文件名的规则为:包含扩展名在内,共12个字节,如果不足12字节,则左端以十六进制的数字零填充(00)。如果文件信息是不需要的,则全部用0填充。
(9-1) 公共交通条件记录大小
指定公共交通条件记录的大小。
(10) 层管理记录总数
描述层管理记录的总数。
(11) 层管理记录大小
描述层管理记录的大小,如果层管理记录不含扩展数据,记录的大小为8(16)字节,如果包含扩展数据,则记录的大小和扩展字段必须被描述。
9.1.1 Level Management Record
The number of levels that canbe managed is a maximum of eight, except the dummy record. name [LevelManagement Record]
No. | offset | Data length | Data type | Item name | Remarks | Classification |
1 | 0 | 2 | I: | Level Code | (1) | b |
2 | 2 | 2 | N | Total Number of Region Management Records | (2) | a |
3 | 4 | 2 | SWS | Region Management Record Size | (3) | a |
3 | 6 | 2 | SWS | Node Record Size | (4) | a |
4 | 8 | 2 | SWS | Link Record Size | (5) | a |
5 | 10 | 2 | SWS | Link Cost Record Size | (6) | a |
6 | 12 | 2 | SWS | Between-links Restriction Record Size | (7) | a |
7 | 14 | 2 | SWS | Size of Between-links Cost Record | (8) | a |
8 |
|
|
| (Expansion Field) | (9) | c |
(1) Level Code
No. | bit | Description |
1 | 15 to 10 | Represents a level managed by the region management record. Level code representation falls within the range from -31 to +31, and -32 is assigned to "null." Set -32 to designate a dummy region management record. |
2 | 9 to 8 | (RESERVED) |
3 | 7 to 4 | Number of Sequences of Basic Route Planning Data Frame Management Records (1-1) |
4 | 3 to 0 | Number of sequences of extended Route Planning Data Frame Management Records (1-1) |
(1-1) Number ofSequences of Basic and Extended Route Planning Data Frame Management Records
For each level, setthe number of sequences of basic and extended route planning data frames.
If the setnumber is smaller than the number of sequences defined in META, data frames areremoved from the tail of the basic and extended route planning data framesequences of that level. Thus, the #n and #m number of sequences of routeplanning distribution header items 4 and 5 are equal to the settings in thesefields.
(2)Total Number of Region Management Records
Thisfield describes the total number of region management records for the regionsthat constitute the level managed by the level management record.
(3)Region Management Record Size
Thisfield describes one record size of region management records for the regionsthat constitute the level managed by the level management record.
(4)Node Record Size
Thisfield describes the size of node records for the route planing data frames of thatlevel. If the node records have noexpansion data, the record size is set with 3 (6) bytes. If the records haveexpansion fields, the record size including the expansion fields must bedescribed.
9.1.1 层管理记录
除了虚拟记录外,最大层数为8。
名称 [层管理记录]
序号 | 偏移量 | 数据长度 | 数据类型 | 项目名称 | 备注 | 类别 |
1 | 0 | 2 | I: | 层代码 | (1) | b |
2 | 2 | 2 | N | 区域管理记录总数 | (2) | a |
3 | 4 | 2 | SWS | 区域管理记录大小 | (3) | a |
3 | 6 | 2 | SWS | 节点记录大小 | (4) | a |
4 | 8 | 2 | SWS | 弧段记录大小 | (5) | a |
5 | 10 | 2 | SWS | 弧段成本记录大小 | (6) | a |
6 | 12 | 2 | SWS | 弧段间(Between-links)限制记录大小 | (7) | a |
7 | 14 | 2 | SWS | 弧段间成本记录大小 | (8) | a |
8 |
|
|
| (扩展字段) | (9) | c |
(1) 层代码
序号 | 位 | 描述 |
1 | 15 to 10 | 取值范围为-31到 +31, 当值为-32 时,表示虚拟层。 |
2 | 9 to 8 | (保留) |
3 | 7 to 4 | 基础路线规划数据帧管理记录的序列数(1-1) 。 |
4 | 3 to 0 | 扩展路线规划数据帧管理记录的序列数(1-1) 。 |
(1-1) 基础和扩展的路线规划数据帧管理记录的序列数
对于每一层,设置基础和扩展路线规划数据帧的编号。
如果设置的号码比元数据中定义的号码小,数据帧会被从相应层中的基础和扩展路线规划数据帧序列的尾部移除,所以路线规划分布头中的第#n和第#m第4项和第5项在这些字段中的设置是相同的。
(2) 区域管理记录总数
层管理记录中所掌控的区域管理记录总数。
(3) 区域管理记录大小
层管理记录中所掌控的区域管理记录大小。
(4) 节点记录大小
路线规划数据帧中的节点记录大小,如果节点记录没有扩展数据,记录的大小设置为3(6)个字节,如果节点记录有扩展字段,记录包含扩展字段必须被描述。
(5)Link Record Size
Thisfield describes the link record size. This is limited to the link record size for non-boundary noderecords. If the link records have noexpansion data, the record size is set with 3 (6) bytes. If the records haveexpansion fields, the record size including the expansion fields must bedescribed.
(6)Link Cost Record Size
Thisfield describes the size of the fixed-length part of link cost records forroute planning data frames of that level. If the link cost records have no expansion data, the record size is setwith 6 (12) bytes. If the records haveexpansion fields, the record size including the expansion fields must bedescribed.
(7)Size of Between-links Restriction Record
Thisfield describes the size of between-links restriction record for route planningdata frames of that level. If theserecords have no expansion data, the record size is set with 1 byte (2 bytes).If the records have expansion fields, the record size including the expansionfields must be described.
(8)Size of Between-links Cost Record
Thisfield describes the size of between-links cost records for route planning dataframes of that level. If these recordshave no expansion data, the record size is set with 2 (4) bytes. If the recordshave expansion fields, the record size including the expansion fields must bedescribed.
(9)Expansion Field
Determine whetherexpansion fields exist, referring to the level management record size describedin the appropriate region data management distribution header.
9.2 Region Management Table
Regionmanagement records are placed in sequence in which higher level records alwaysprecede lower ones. The region management records of the same level are placedin the ascending order of region numbers. The first region management record ofthe level is assigned region number 0 when stored and each subsequent record isassigned a region number, according to its storage order relative to the firstrecord. For further information about the region-numbering rule, see supplement2 in this chapter.
name[Region Management Table]
No. | offset | Data length | Data type | Item name | Remarks | Classification |
1 | 0 |
|
| A Sequence of Region Management Records | (1) | a |
(1) A Sequenceof Region Management Records
The region management table retains the management informationincluding region data storage address, size, range, and mutual relationshipbetween levels (tree structure). A first stored region management record is theroot of the tree structure. If multiple regions exist at the uppermost level,place a dummy region management record at the top of the tree so that only asingle root always exists.
(5) 弧段记录大小
本字段描述弧段记录的大小,只表示非边界节点弧段记录的大小,如果弧段记录没有扩展数据,记录的大小设置为3(6)个字节,如果节点记录有扩展字段,记录包含扩展字段必须被描述。
(6) 弧段成本记录大小
本字段描述路线规划数据帧中的固定长度的弧段成本记录大小,如果弧段成本记录没有扩展数据,记录的大小设置为6(12)个字节,如果节点记录有扩展字段,记录包含扩展字段必须被描述。
(7) 弧段间限制记录大小
本字段描述弧段间限制记录的大小,如果弧段间限制记录没有扩展数据,记录的大小设置为1(2)个字节,如果节点记录有扩展字段,记录包含扩展字段必须被描述。
(8) 弧段间成本记录大小
本字段描述弧段间成本记录的大小,如果弧段间成本记录没有扩展数据,记录的大小设置为2(4)个字节,如果节点记录有扩展字段,记录包含扩展字段必须被描述。
(9) 扩展字段
根据区域数据管理分布头中的层管理记录大小判断是否有扩展字段存在。
9.2 区域管理表
区域管理记录集按顺序放置,按这个顺序,高一层的记录总是优先于低一层的记录。同一层中的区域管理记录按区域记录号升序排列,第一个区域管理记录的序号为0,之后的区域序号根据第一个记录号增量排列。想要了解区域号的更多信息,请参考本章的补充2。
名称 [区域管理表]
序号 | 偏移量 | 数据长度 | 数据类型 | 项目名称 | 备注 | 类别 |
1 | 0 |
|
| 区域管理记录序列 | (1) | a |
(1) 区域管理记录序列
区域管理表保留了区域数据存储地址、大小、范围、层间关联信息(树结构)等区域信息,如果在最上层出现多个区域,则在树的顶层安排一个虚拟区域记录来确保总是只有一个树根结点。
9.2.1 RegionManagement Record
name[Region Management Record]
No. | offset | Data length | Data type | Item name | Remarks | Classification |
1 | 0 | 3 | B:N | Uppermost Latitude of Region | (1) | b |
2 | 3 | 3 | B:N | Lowest Latitude of Region | (1) | b |
3 | 6 | 3 | B:N | Leftmost Longitude of Region | (1) | b |
4 | 9 | 3 | B:N | Rightmost Longitude of Region | (1) | b |
5 | 12 | 2 | N | The Corresponding Higher Level Region Number | (2) | b |
6 | 14 | 2 | N | Foremost Number of the Corresponding Lower-level Region | (3) | b |
7 | 16 | 2 | N | Number of Lower-level Regions | (4) | b |
8 | 18 | ?*m |
| Data Storage Location Record | (5) | a |
9 | 01 |
|
| (Expansion Field) | (6) | c |
(1) Longitudesand Latitudes of Region
The respective contents of No. 1 to No. 4 fields of a regionmanagement record correspond to uppermost and lowest latitudes and leftmost andrightmost longitudes of the area in which a group of nodes exist that arestored in the node data frame for the region (route planning data frame)managed by the region management record. For a dummy region management record,these longitude and latitude fields contain FFFFFF(16).
No. | bit | Description | ||
1 | 23 | North/South Latitude or West/East | bit23 | Meaning |
|
| Longitude Flag | 0 | North latitude or east longitude |
|
|
| 1 | South latitude or west longitude |
2 | 22 to 0 | Latitude or latitude is represented in 1/8-second units |
Uppermost latitude
Agroup of nodes stored in the node data frame
Lowest latitude Leftmost longitude Rightmost longitude
Figure 9-1 Nodes included in Node Data Frame