JP6373374B2 - Map data processing system, storage specification data creation system - Google Patents

Description

  The present invention relates to a technique for shortening the reading time of map data.

  The map data used for the navigation device is being standardized. In recent years, the standard data for which the standard has been established is commonly used in various navigation devices.

  However, navigation device manufacturers often use extended data separately from standard data for the navigation device in order to show their uniqueness. For example, Patent Literature 1 shows map data having area-specific extended data in addition to standard data.

JP-A-01-223600

  However, the map data shown in Patent Document 1 has a data structure for adding unique functions to the last, and has not been data for improving the acquisition time of standard data.

  In view of the above-described problems, an object of the present invention is to provide a technique for reading map data at high speed.

A map data processing system according to the present invention includes a map data acquisition unit that acquires map data including standard data having a fixed format, and a standard data reading unit that reads standard data. If the data has stored specification data indicating the storage of the standard data specifications, to read out the standard data based on the storage specification data, standard data is sequence data record, storing specification data for all records of the standard data Data indicating common storage specifications .

A storage specification data creation system according to the present invention includes a standard data acquisition unit that acquires standard data having a fixed format among map data, and a storage that generates storage specification data indicating the storage specification of the standard data based on the standard data. A standard data is record array data, and the storage specification data is data indicating a storage specification common to all records of the standard data .

A map data processing system according to the present invention includes a map data acquisition unit that acquires map data including standard data having a fixed format, and a standard data reading unit that reads standard data. If the data has stored specification data indicating the storage of the standard data specifications, to read out the standard data based on the storage specification data, standard data is sequence data record, storing specification data for all records of the standard data Data indicating common storage specifications . Therefore, standard data can be acquired at high speed based on the storage specification data.

A storage specification data creation system according to the present invention includes a standard data acquisition unit that acquires standard data having a fixed format among map data, and a storage that generates storage specification data indicating the storage specification of the standard data based on the standard data. A standard data is record array data, and the storage specification data is data indicating a storage specification common to all records of the standard data . Therefore, when another device accesses the map data, the standard data can be acquired at high speed by referring to the storage specification data.

  Objects, features, aspects, and advantages of the present invention will become more apparent from the following detailed description and the accompanying drawings.

It is a figure which shows the data structure of the map data which concerns on Embodiment 1. FIG. It is a figure which shows the correspondence of the storage state of the link record in standard data, and a link ID ascending order flag. It is a block diagram which shows the structure of the map data processing system which concerns on Embodiment 1. FIG. It is a block diagram which shows the structure of the map data processing system which concerns on Embodiment 1 by the combination of a server and a vehicle-mounted apparatus. It is a block diagram which shows the structure of the map data processing system which concerns on Embodiment 1 by the combination of a server, a smart phone, and a vehicle-mounted apparatus. It is a flowchart which shows the link attribute acquisition process of the map data processing system which concerns on Embodiment 1. FIG. It is a flowchart which shows the link attribute acquisition process in case there is no storage specification data of the map data processing system which concerns on Embodiment 1. FIG. It is a flowchart which shows the link attribute acquisition process in case there exists storage specification data of the map data processing system which concerns on Embodiment 1. FIG. It is a figure which shows the data structure of the map data which concerns on Embodiment 2. FIG. It is a block diagram which shows the structure of the map data processing system which concerns on Embodiment 2. FIG. It is a block diagram which shows the structure of the map data processing system which concerns on Embodiment 3. FIG. 10 is a flowchart showing standard data acquisition processing by the map data processing system according to the third embodiment. 10 is a flowchart showing storage specification data creation processing by the map data processing system according to the third embodiment. It is a block diagram which shows the structure of the map data processing system which concerns on the modification of Embodiment 3. 10 is a flowchart showing a storage specification data creation process by a map data processing system according to a modification of the third embodiment. It is a flowchart which shows the standard data acquisition process by the map data processing system which concerns on the modification of Embodiment 3. 10 is a flowchart illustrating a storage specification data cache process by a map data processing system according to a modification of the third embodiment. It is a block diagram which shows the structure of the storage specification data creation system which concerns on Embodiment 4. FIG.

<A. Embodiment 1>
<A-1. Map data>
The structure of the map data according to Embodiment 1 will be described. The map data is recorded on a recording medium and used for a navigation device or other map data processing device. The feature of the map data according to the first embodiment is that it has storage specification data indicating the storage specification of the standard data in addition to the standard data for which the standard is determined in advance.

  FIG. 1 shows the data structure of map data, taking a road network as an example. The road network is expressed by a combination of nodes indicating nodes such as intersections and links indicating road sections between the nodes.

  Standard data is used to realize basic functions of the map data processing system such as navigation. In the example of the road network, the standard data includes a node record indicating node information, the number of node records, a link record indicating link information, and the number of link records.

  The node record includes, as fields, node coordinates representing a position, node attributes representing attributes such as intersections, the number of connection links indicating the number of links connected to the nodes, and connection link numbers.

  The link record includes, as fields, a link ID, a link attribute, a start point side node number, and an end point side node number, which are unique numbers for each link. The link attribute includes, for example, a road type indicating whether it is a highway or a national road, a link type indicating whether it is a main line or a connected road, a link cost indicating the ease of passing a link used for route search, And a link cost presence / absence flag.

  The storage specification data includes, for example, a link ID ascending order flag, a link ID descending order flag, a link cost existence flag, and a link attribute size. The link ID ascending order flag indicates whether the list of link records in the standard data is the ascending order of the link IDs or the other order. The order of the link records is not the ascending order of the link IDs if the link ID ascending order flag is 0, but the ascending order of the link IDs if the link ID ascending order flag is 1.

  The link ID descending order flag indicates whether the order of the link records in the standard data is the descending order of the link ID or the other order. If the link ID descending order flag is 0, the link record is not in the descending order of the link ID, and if the link ID descending order flag is 1, the link record is in the descending order of the link ID.

  The link cost presence flag indicates whether the standard data includes a link cost as a link attribute. For example, if all the link records in the standard data include the link cost as the link attribute, that is, if the cost presence flag is “1”, the link cost existence flag is “1”, otherwise the link cost existence flag Becomes “0”.

  The link attribute size indicates the data size of the link attribute that is a field of the link record. If the size of all link records in the standard data is common, the link attribute size can be used as the storage specification data. In the example of FIG. 1, when all link records have the four items of road type, link type, cost presence flag, and link cost as link attributes, the link attribute size is 4.

  FIG. 2 is a diagram illustrating a correspondence relationship between the storage state of the link record in the standard data and the link ID ascending order flag. When link records are stored in ascending order of link IDs, the link ID ascending order flag is “1”. On the other hand, when the link record is not stored in the ascending order of the link ID, the link ID ascending order flag is “0”. Therefore, the storage order of data in the standard data can be identified by referring to the storage specification data.

  The above-described link ID ascending order flag, link cost existence flag, and link attribute size are merely examples of storage specification data. Depending on the standard, the link ID may not be included in the standard data in the road network data. In that case, link IDs are stored in ascending order, for example, in storage specification data, and link records are also stored in standard data in the same order as link IDs, that is, in ascending order. Then, the data storage order of the standard data can be identified by referring to the data storage order of the link ID. The link ID in the storage specification data in this case can be said to be data indicating the storage specification of the standard data.

<A-2. Map data processing system>
FIG. 3 is a block diagram showing the configuration of the map data processing system 101 according to Embodiment 1 of the present invention. Hereinafter, the map data processing system 101 illustrated in FIG. 3 will be described as being configured by an in-vehicle navigation device.

  The map data processing system 101 includes a map data acquisition unit 11 that acquires the map data described in <A-1>, and a standard data reading unit 12 that reads standard data from the map data acquisition unit 11. The map data acquisition unit 11 may be configured to acquire map data by communication from the outside. Further, it may be configured by a memory such as an HDD (Hard Disk Drive) or a RAM (Random Access Memory) and store map data.

  The map data acquired by the map data acquisition unit 11 includes standard data and storage specification data. The standard data reading unit 12 reads the standard data at high speed by referring to the storage specification data.

  The map data processing system 101 is configured by an in-vehicle device, and a part of the configuration is realized by a server remote from the mobile body and a portable terminal that can be brought into a vehicle such as a PDA (Personal Digital Assistant) and a smartphone. It may be realized by a combination of these.

  For example, when the map data processing system 101 is configured by a combination of a server and an in-vehicle device, the server has a map data storage unit 11A and a standard data reading unit 12 as shown in FIG. The read standard data may be acquired and used by the standard data acquisition unit 12A of the in-vehicle device. In the server, the map data storage unit 11A is used instead of the map data acquisition unit 11.

  Further, when the map data processing system 101 is configured by a combination of a server, a smartphone, and an in-vehicle device, as shown in FIG. 5, the server configures a map data storage unit 11A and a standard data reading unit 12, and the smartphone transmits and receives data. The in-vehicle device can constitute the standard data acquisition unit 12A. The standard data acquisition unit 12 </ b> A of the in-vehicle device acquires the standard data read by the standard data reading unit 12 via the data transmission / reception unit 19.

  FIG. 6 is a flowchart showing the link attribute acquisition process of the map data processing system 101. First, the standard data reading unit 12 determines whether there is storage specification data in the map data of the map data acquisition unit 11 (step S1). If there is storage specification data, an acquisition process (step S2) using the storage specification data is executed, and if there is no storage specification data, a normal (without storage specification data) acquisition process (step S3) is executed.

  FIG. 7 is a flowchart showing details of normal acquisition processing (step S3 in FIG. 6). In the normal acquisition process, the standard data reading unit 12 extracts link records one by one from the standard data (step S31). Then, it is determined whether or not the link ID of the extracted link record is equal to a predetermined designated link ID (step S32). If they are equal, the link attribute of the link record of the link ID is acquired (step S33), and the process is terminated as successful acquisition of the link attribute.

  If the link ID of the extracted link record is not equal to the specified link ID determined in advance in step S32, it is determined whether or not the extracted link record is the link ID of the last link record in the standard data (step S32). S34). If it is not the link ID of the last link record, the link ID of the next link record is acquired (step S35). Then, the process returns to step S32. Even if link IDs are sequentially acquired up to the last link record, if the acquired link ID is not equal to the designated link ID (Yes in step S34), the processing ends as a link attribute acquisition failure.

  FIG. 8 is a flowchart showing details of the acquisition process (step S2 in FIG. 6) using the storage specification data. Hereinafter, the acquisition process using the storage specification data will be described using the case where the link ID ascending order flag is storage specification data as an example. First, the standard data reading unit 12 determines whether or not the link ID ascending order flag of the storage specification data is “1” (step S21). If it is not “1”, the normal acquisition process described in FIG. 7 is executed (step S25). If “1”, a link record having a link ID equal to the designated link ID is searched by a binary search (step S22). The binary search is a general process used for the sorted data, and a higher-speed process can be expected than the method of sequentially processing from the top described with reference to FIG. As a result, if there is a record having a link ID that matches the specified link ID (Yes in step S23), the link attribute of the corresponding record is acquired (step S24).

  If there is no record having a link ID that matches the specified link ID as a result of the binary search (No in step S23), the process ends as a link attribute acquisition failure.

  As described above, by referring to the link ID ascending order flag of the storage specification data and performing the binary search when the link ID ascending order flag is 1, the link attribute of the specified link ID can be acquired at high speed.

  When the storage specification data includes the link cost existence flag, it is not necessary to acquire the link cost presence / absence flag for each link record and determine the presence / absence of the link cost. Therefore, link attributes can be acquired at high speed.

  Also, when the storage specification data includes the link attribute size, it is not necessary to calculate the link attribute size for each link record, so the address where the link attribute of the specified link ID is stored can be calculated at high speed. It is possible to obtain.

<A-3. Effect>
The computer-readable recording medium according to the first embodiment records map data having standard data with a fixed format and storage specification data indicating the storage specification of the standard data. A map data processing system 101 according to Embodiment 1 includes a map data acquisition unit 11 that acquires the map data, and a standard data reading unit 12 that reads standard data. The standard data reading unit 12 stores map data. When the storage specification data indicating the storage specification of the standard data is included, the standard data is read based on the storage specification data. Accordingly, standard data can be acquired at high speed based on the storage specification data.

  The storage specification data includes data indicating that the standard data is stored in either the ascending order or descending order of the IDs attached to each data. Examples of storage specification data include a link ID ascending order flag indicating whether the order of link records in the standard data is ascending order of the link ID or other order, or the order of the link records in the standard data is descending order of the link ID or other There is a link ID descending order flag indicating the order. Therefore, when the storage specification data is the link ID ascending order flag, for example, when acquiring the link attribute from the road network data, whether or not the link records are stored in the ascending order of the link ID with reference to the storage specification data. Can know. If the data are stored in ascending order, the link attribute of the specified link ID can be acquired at high speed by performing a binary search.

  The storage specification data includes data indicating whether or not predetermined data is included in the standard data. For example, when the storage specification data includes a link cost presence flag, it is not necessary to acquire a link cost presence / absence flag for each link record and determine the presence / absence of the link cost. Therefore, link attributes can be acquired at high speed.

  The storage specification data includes data indicating that the data size of the standard data is fixed or variable. For example, when the storage specification data includes the link attribute size, it is not necessary to calculate the link attribute size for each link record, so the address where the link attribute of the specified link ID is stored can be calculated at high speed. It is possible to obtain.

  The standard data is record array data, the record has a plurality of fields, the storage specification data has record ID data, and the storage order of the ID data in the storage specification data is determined in the standard data. Match the storage order of records. Thereby, the data storage order of the standard data can be identified by referring to the storage order of the ID data in the storage specification data.

<B. Second Embodiment>
<B-1. Map data>
FIG. 9 shows the data structure of the map data according to the second embodiment. The map data according to Embodiment 2 is characterized by being divided for each area of the map. Therefore, the map data has standard data and storage specification data for each area, and the storage specification of the standard data may be different for each area. As shown in FIG. 9, the map data includes the number of map areas and data for each area. The data for each area includes an area code such as a regional mesh code for specifying the area, standard data and storage specification data prepared for each area.

<B-2. Map data processing system>
FIG. 10 is a block diagram showing a configuration of the map data processing system 102 according to the second embodiment of the present invention. The configuration of the map data processing system 102 is the same as that of the map data processing system 101 according to the first embodiment. However, the standard data reading unit 12 of the map data processing system 102 reads the standard data from the map data acquiring unit 11 by designating the area code if the area code of the map data to be acquired is known.

  For example, when the map data processing system 102 is an in-vehicle navigation system, a position information acquisition unit may be provided when displaying a map around the vehicle position. That is, the vehicle position information is acquired from a position information acquisition unit (not shown), and the area code of the map to be displayed is determined based on the acquired vehicle position information. Then, standard data is acquired based on the storage specification data of the area code.

  Alternatively, the map data processing system 102 may include an operation unit (not shown) that receives user operations. In this case, the area code of the map data to be acquired by user operation is determined, and the standard data is acquired based on the storage specification data of the area code.

  According to map data having such a data structure, for example, when acquiring a link attribute, the link attribute is acquired by searching only the standard data of the corresponding area based on the area code of the area where the map is to be displayed. Therefore, reading can be performed efficiently.

<B-3. Effect>
In the second embodiment, standard data and storage specification data included in map data are divided for each region. Therefore, for example, when acquiring the link attribute, the link attribute can be acquired by searching only the standard data of the corresponding area based on the area code of the area where the map is to be displayed. Can be read.

<C. Embodiment 3>
<C-1. Configuration>
FIG. 11 is a block diagram showing the configuration of the map data processing system 103 according to Embodiment 3 of the present invention. If there is no storage specification data in the map data acquired by the map data acquisition unit 11, the map data processing system 103 creates storage specification data from the standard data and reads the standard data at high speed based on the generated storage specification data. Features. In the map data processing system 101, if there is no storage specification data in the map data, the storage specification data cannot be used and the standard data reading speed is reduced. However, the map data processing system 103 solves such a problem. Is done.

  The map data processing system 103 includes a storage specification data creation unit 14, an operation unit 15, and a presentation unit 16 in addition to the configuration of the map data processing system 101.

  When there is no storage specification data in the map data acquired by the map data acquisition unit 11, the storage specification data generation unit 14 generates storage specification data from the standard data and outputs it to the standard data reading unit 12.

  The presentation unit 16 presents to the user whether the map data acquired by the map data acquisition unit 11 includes storage specification data.

  The operation unit 15 is a general operation input unit for the map data processing system 103, and the user selects the type of storage specification data to be created, such as a link ID ascending order flag, a link cost existence flag, and a link attribute size. Accepts operation input to make it possible. Further, the timing for creating the storage specification data may be designated from the operation unit 15.

  However, if the user does not provide a function for designating the type of storage specification data and the creation timing, the operation unit 15 and the presentation unit 16 are not essential components for the present invention.

<C-2. Operation>
Next, standard data acquisition processing by the map data processing system 103 will be described with reference to the flowcharts of FIGS.

  In FIG. 12, when acquiring the link attribute of the predetermined link ID from the map data, the standard data reading unit 12 determines whether or not the storage specification data exists in the map data (step S41). If there is storage specification data, a link attribute acquisition process using the storage specification data is performed (step S44), and the process ends. This step is the same as step S2 of FIG. 6 whose details are described in FIG.

  If there is no storage specification data in step S41, the standard data reading unit 12 reads standard data from the map data (step S42). Then, the storage specification data creation unit 14 creates storage specification data based on the standard data (step S43). Thereafter, the standard data reading unit 12 performs a link attribute acquisition process for a predetermined link ID based on the stored specification data (step S44).

  FIG. 13 is a flowchart showing details of the storage specification data creation process (step S43 in FIG. 12) based on the standard data. In FIG. 13, the storage specification data creation unit 14 first determines whether or not the link records are arranged in ascending order of link IDs in the standard data (step S431). If the link records are arranged in ascending order of the link IDs, storage specification data with the link ID ascending order flag set to “1” is created (step S432). If the link records are not arranged in ascending order of the link IDs, storage specification data with the link ID ascending order flag set to “0” is created (step S433).

  The above is an example of creating the link ID ascending order flag as the storage specification data. However, when creating the link cost existence flag, the cost presence / absence flags in the link attributes of all the link records of the standard data are referred to. If there is a link cost for all link records, the link cost existence flag is set to “1”. If there is no link cost for all link records, the link cost existence flag is set to “0”.

  When creating the link attribute size as the storage specification data, the link attribute of all the link records of the standard data is referred to and the size is acquired. If the link attribute size is the same for all link records, the link attribute size is created as storage specification data.

  Note that it is possible to allow the user to select from the operation unit 15 which storage specification data is to be created.

  According to the map data processing system 103 of the third embodiment, even when the map data does not include the storage specification data, by creating the storage specification data by itself, the link for specifying the standard data can be efficiently performed after the creation. It is possible to acquire attributes and the like.

  In addition, when using the map data divided | segmented for every area of Embodiment 2, it is not necessary to create storage specification data simultaneously with respect to all the standard data. For example, by creating storage specification data for the area around the vehicle position and creating storage specification data for other areas later, map data necessary for efficiently displaying the map around the vehicle position can be acquired. Is possible.

<C-3. Modification>
FIG. 14 is a block diagram illustrating a configuration of a map data processing system 103A according to the first modification of the third embodiment. In addition to the configuration of the map data processing system 103, the map data processing system 103A includes a storage specification data recording unit 17 that records the storage specification data created by the storage specification data creation unit. The configuration other than the storage specification data recording unit 17 is the same as the configuration of the map data processing system 103.

  If the storage specification data is not included in the map data acquired by the map data acquisition unit 11, the storage specification data generation unit 14 generates storage specification data in advance using the same method as the map data processing system 103. The created storage specification data is recorded in the storage specification data recording unit 17.

  When reading the map data, the standard data reading unit 12 acquires the storage specification data from the storage specification data recording unit 17 and reads the standard data at a high speed based on this.

  With this configuration, it is possible to create storage specification data in advance. The timing may be, for example, when the map data processing system 103A is activated, or may be arbitrarily set by the user. In any case, it is not necessary to create storage specification data every time standard data is acquired, and overhead due to the creation of storage specification data can be prevented.

  FIG. 15 is a flowchart showing the creation processing of storage specification data by the map data processing system 103A. 15, steps S51 to S53 are the same as steps S41 to S43 of FIG. 12 showing the standard data acquisition process of the map data processing system 103, and thus the description thereof is omitted. When the storage specification data creation unit 14 creates the storage specification data (step S53), it records the created storage specification data in the storage specification data recording unit 17 (step S54).

  The storage specification data recording unit 17 is configured by a memory such as an HDD or a RAM, but may be configured as a cache memory.

  FIG. 16 is a flowchart showing standard data acquisition processing of the map data processing system when the storage specification data recording unit 17 is configured as a cache memory. In FIG. 16, the standard data reading unit 12 determines whether there is storage specification data in the storage specification data recording unit 17 (step S61). If there is storage specification data in the storage specification data recording unit 17, standard data acquisition processing is performed using the storage specification data (step S63). The specific operation in step S63 has already been described with reference to FIG. If there is no storage specification data in the storage specification data recording unit 17, the storage specification data creation unit 14 performs a cache process of the storage specification data (step S62).

  FIG. 17 is a flowchart showing the storage specification data cache processing (step S62 in FIG. 16). First, the storage specification data creation unit 14 reads standard data (step S621), and then performs storage specification data creation processing (step S622). The specific operation in step S622 has already been described with reference to FIG. Then, the created storage specification data is recorded in the cache memory (storage specification data recording unit 17).

<C-4. Effect>
The map data processing system 103 according to the third embodiment further includes a storage specification data creation unit 14 that creates storage specification data based on standard data when the map data does not have storage specification data. Therefore, even when the map data does not include the storage specification data, the storage specification data can be created by itself and the standard data can be acquired at high speed using the generated storage specification data.

  The map data processing system 103 may further include a storage specification data recording unit 17 that records the storage specification data created by the storage specification data creation unit 14. Thereby, the storage specification data creation unit 14 can create storage specification data at an arbitrary timing, and the storage specification data can be recorded in the storage specification data recording unit 17 and used when standard data is read.

  For example, the storage specification data creation unit 14 may create the storage specification data when the map data processing system 103 is activated or whenever the standard data reading unit 12 reads the standard data. According to the former, when standard data is acquired in the map data processing system 103, overhead due to creation of storage specification data can be prevented. Further, according to the latter, it is possible to avoid a decrease in the startup time of the map data processing system 103 by creating the storage specification data.

  In addition, a cache memory may be used for the storage specification data recording unit 17, and even when the map data does not include the storage specification data, the storage specification data is created by itself and standard data is created using the generated storage specification data. Can be acquired at high speed.

  The storage unit further includes a presentation unit 16 that presents the user with the presence or absence of storage specification data in the map data, and an operation unit 15 that receives an input operation of the user. The storage specification data creation unit 14 stores the data based on the user input operation. Specification data may be created. In this case, storage specification data can be created at a timing specified by the user, and standard data can be acquired at high speed using the created storage specification data.

<D. Embodiment 4>
<D-1. Storage specification data creation device>
FIG. 18 is a block diagram illustrating a configuration of the storage specification data creation system 104 according to the fourth embodiment. The storage specification data generation system 104 includes a standard data acquisition unit 12A that acquires standard data converted according to the standardization specifications from non-standardized data for generating map data, and storage specification data from the standard data. And a storage specification data creation unit 20 for creating the data. Since the method in which the standard data creation unit 18 creates standard data from the original data is a known technique, description thereof is omitted. Further, the method for creating the storage specification data from the standard data by the storage specification data creation unit 20 is the same as the method for creating the storage specification data by the storage specification data creation unit 14 of the map data processing system 102 in the third embodiment. Yes, various modifications applied to the storage specification data creation unit 14 are also applied to the storage specification data creation unit 20.

  Also, by preparing a plurality of storage specification data creation units 20 and generating different types of storage specification data, map data for a plurality of navigation systems can be created efficiently.

<D-2. Effect>
The storage specification data creation system 104 according to the fourth embodiment includes a standard data acquisition unit 12A that acquires standard data having a fixed format among map data, and storage specification data that indicates the storage specification of the standard data based on the standard data. A storage specification data creating unit 20 for creating Using the storage specification data created by the storage specification data creation unit 20, standard data can be obtained at high speed.

  The storage specification data includes data indicating that the standard data is stored in either the ascending order or descending order of the IDs attached to each data. Accordingly, when the map data processing system that has acquired the storage specification data acquires link attributes from road network data, for example, with reference to the storage specification data, whether or not link records are stored in ascending order of link IDs. Can know. If the data are stored in ascending order, the link attribute of the specified link ID can be acquired at high speed by performing a binary search.

  The storage specification data includes data indicating whether or not predetermined data is included in the standard data. For example, if the storage specification data includes a link cost existence flag, the presence or absence of the link cost can be known by referring to the storage specification data. Therefore, when acquiring standard data, the link cost presence flag is acquired for each link record. There is no need to determine whether or not there is. Therefore, link attributes can be acquired at high speed.

  The storage specification data includes data indicating that the data size of the standard data is fixed or variable. For example, when the storage specification data includes the link attribute size, it is not necessary to calculate the link attribute size for each link record, so the address where the link attribute of the specified link ID is stored can be calculated at high speed. It is possible to obtain.

  The standard data is array data of records having a plurality of fields. When the storage specification data includes record ID data, the storage order of the ID data in the storage specification data matches the storage order of the records in the standard data. Let Thereby, the data storage order of the standard data can be identified by referring to the storage order of the ID data in the storage specification data.

  Further, the standard data and the storage specification data may be divided for each area of the map. Therefore, for example, when acquiring the link attribute, the link attribute can be acquired by searching only the standard data of the corresponding area based on the area code of the area where the map is to be displayed. Can be read.

  It should be noted that the present invention can be freely combined with each other within the scope of the invention, and each embodiment can be appropriately modified or omitted.

  Although the present invention has been described in detail, the above description is illustrative in all aspects, and the present invention is not limited thereto. It is understood that countless variations that are not illustrated can be envisaged without departing from the scope of the present invention.

  11 Map data acquisition unit, 11A Map data storage unit, 12 Standard data reading unit, 12A Standard data acquisition unit, 14 Storage specification data creation unit, 15 Operation unit, 16 Presentation unit, 17 Storage specification data recording unit, 18 Standard data creation Section, 19 data transmission / reception section, 20 storage specification data creation section.

Claims (18)

A map data acquisition unit for acquiring map data including standard data having a fixed format;
A standard data reading unit for reading the standard data,
When the map data has storage specification data indicating the storage specification of the standard data, the standard data reading unit reads the standard data based on the storage specification data,
The standard data is record array data,
The storage specification data is data indicating a storage specification common to all the records of the standard data.
Map data processing system. The storage specification data includes data indicating that the standard data is stored in either ascending order or descending order of IDs attached to each data.
The map data processing system according to claim 1. The storage specification data includes data indicating whether or not predetermined data is included in the standard data.
The map data processing system according to claim 1. The storage specification data includes data indicating that the data size of the standard data is fixed or variable.
The map data processing system according to claim 1. The record has a plurality of fields,
The storage specification data includes ID data of the record,
The storage order of the ID data in the storage specification data matches the storage order of the records in the standard data.
The map data processing system according to claim 1. The standard data and the storage specification data are divided for each area of the map,
The map data processing system according to claim 1. When the map data does not have the storage specification data, further comprising a storage specification data creation unit that creates the storage specification data based on the standard data,
The map data processing system according to claim 1. A storage specification data recording unit for recording the storage specification data created by the storage specification data creation unit;
The map data processing system according to claim 7. The storage specification data creation unit creates the storage specification data based on the standard data when the map data does not have the storage specification data when the map data processing system is activated.
The map data processing system according to claim 8. The storage specification data creation unit creates the storage specification data based on the standard data each time the standard data reading unit reads the standard data when the map data does not have the storage specification data.
The map data processing system according to claim 7. The storage specification data recording unit is a cache memory;
The map data processing system according to claim 8. A presentation unit that presents to the user the presence or absence of the storage specification data in the map data;
An operation unit that accepts a user's input operation,
When the map data does not have the storage specification data, the storage specification data creation unit creates the storage specification data based on the input operation of the user,
The map data processing system according to claim 7. A standard data acquisition unit for acquiring standard data in a fixed format among map data;
A storage specification data creating unit that creates storage specification data indicating a storage specification of the standard data based on the standard data;
The standard data is record array data,
The storage specification data is data indicating a storage specification common to all the records of the standard data.
Storage specification data creation system. The storage specification data includes data indicating that the standard data is stored in either ascending order or descending order of IDs attached to each data.
The storage specification data creation system according to claim 13. The storage specification data includes data indicating whether or not predetermined data is included in the standard data.
The storage specification data creation system according to claim 13. The storage specification data includes data indicating that the data size of the standard data is fixed or variable.
The storage specification data creation system according to claim 13. The record has a plurality of fields,
The storage specification data includes ID data of the record,
The storage order of the ID data in the storage specification data matches the storage order of the records in the standard data.
The storage specification data creation system according to claim 13. The standard data and the storage specification data are divided for each area of the map,
The storage specification data creation system according to claim 13.

Images