JP5022881B2 - Travel support planning system, travel support planning method, and navigation device - Google Patents

Description

  The present invention relates to a travel plan support system that connects to a travel plan support server from an external client terminal and sets a route to be used in a navigation device, and in particular, map data used in the travel plan support server and the navigation device. The present invention relates to a travel support planning system for setting an effective route in different cases, a travel support planning method and a navigation device used therefor.

  Conventional navigation devices have a narrow display screen and poor operability, making it difficult to perform complicated settings. For this reason, for example, there is a function of connecting to a travel plan support server through the Internet from a client terminal such as a PC (Personal Computer) outside the navigation device, performing user authentication, and performing complicated settings of the corresponding navigation device. Has been developed. Such a function is often provided as a dedicated service for navigation device users.

  On the other hand, as a service for general users, there are many services such as Google (registered trademark) Maps and Yahoo! (registered trademark) Maps that search for map information through the Internet. Being offered. Recent navigation apparatuses have a function of interpreting tag data provided by such a service, and when the current location approaches a designated region, a service for presenting content in that region has been provided. ing.

  In a dedicated service intended for users of conventional navigation devices, the travel plan support server receives a starting point and a destination set by the client terminal and a plurality of waypoints set as necessary, and starts from the starting point. It has a function to search a route to a destination via a plurality of waypoints and display the result on a map. In general, road connection data used for route search is described by a node corresponding to an intersection and a link corresponding to a road connecting the intersection, and the result of the route search is provided as a link ID string.

  Since the travel plan support server and the navigation device may use different versions of map data, the route set by the travel plan support server cannot be passed as the link ID string. Therefore, the travel plan support server transfers the departure point and destination, and if necessary, a plurality of waypoints to the navigation device, and the navigation device routes from the departure point to the destination via the plurality of waypoints. A means for searching and setting as a route to be used for navigation is taken.

  In addition, in order to approach the route confirmed by the client terminal, there is provided means for selecting a number of coordinate points on the route other than the waypoint and passing it to the navigation device (hereinafter referred to as “transfer method using shape data”).

  Further, for example, in Patent Document 1, when a user designates a desired starting point and destination on a terminal, a route is calculated by a route calculation server based on the designated starting point and destination, and a map image including the calculated route display is displayed on the terminal. A technique is disclosed that can be transmitted and viewed on a terminal.

Japanese Patent Laid-Open No. 11-296074

  However, the travel plan support server and the navigation device may have different map data versions or different settings such as the cost used for route search. For this reason, there is a problem that a route different from the route confirmed by the client terminal is set in the navigation device.

  Further, in the transfer method using shape data, in order to reproduce the route, a large number of coordinate points must be passed, and there is a problem that the amount of data becomes enormous.

  In addition, the technology described in Patent Document 1 is based on route information calculated by the route calculation server, and converts the map image including the route display created by the map server into GIF data and sends it to the user's terminal. There was a problem of becoming enormous.

  Also, when using the map search service on the Internet as a travel plan support server, the travel plan support server and the navigation device differ not only in the version of the map data used but also in the map data itself. There is a possibility that the ID is attached differently or the coordinates are shifted. Even if all the coordinate points on the route set by the travel plan support server are passed, the coordinates will be shifted in the navigation device, so it is necessary to align by map matching. When passing all the coordinate points on the route to the navigation device, there is a problem that the amount of data becomes enormous and the calculation load due to map matching increases.

  The present invention has been made in view of such circumstances, and in particular, a travel plan support system and a travel plan support for setting an effective route when different map data are used between the travel plan support server and the navigation device. It is an object to provide a method and a navigation device.

  In order to solve the above-described problems, a travel plan support system according to the present invention includes a navigation device that executes processing related to navigation of a mobile object, and a travel plan that is connected to a communication network and supports creation of a travel plan for the mobile object. A travel plan support system comprising a support server, wherein the travel plan support server searches for a route from the departure point to the destination based on the input departure point and destination, and selects a feature node on the route. The navigation device includes a control unit that extracts and converts route data including name data and traveling direction corresponding to feature nodes, name data and travel distance corresponding to feature links between feature nodes, and stores the route feature information. The route feature information is received from the travel plan support server, the name data included in the route feature information, the traveling direction and the travel distance A control unit for restoring the route used to Luo navigation device.

  Furthermore, in the travel plan support system according to the present invention, the control unit of the travel plan support server further receives one or more waypoints and searches for a route from the departure point to the destination via the waypoint.

  Furthermore, in the travel plan support system according to the present invention, the route feature information includes the coordinates of feature nodes.

  Furthermore, in the travel plan support system according to the present invention, when the control unit of the travel plan support server includes a newly opened road not included in the map data of the navigation device on the route, the newly opened road is included in the route feature information. Include the feature link coordinates corresponding to.

  Further, in the travel plan support system according to the present invention, the departure place and the destination are input by a client terminal connected to the travel plan support server through a communication network.

  Furthermore, the present invention provides a travel plan support method and a navigation device used in the travel plan support system.

  According to the present invention, the route feature information described by the link between the feature node such as a corner on the route and the feature node is used as the data format when the route is transmitted from the travel plan support server to the navigation device. It is possible to provide a travel plan support system that reduces the amount of data compared to the case of transferring the upper coordinate point, and to provide a travel plan support method used for the system.

  In the navigation device, the route used for navigation is restored from the name data included in the route characteristic information, the traveling direction, and the travel distance. Therefore, the map data differs between the travel plan support server and the navigation device, and the coordinates are shifted. Even if it is, effective route setting is possible.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
FIG. 1 is a diagram showing an embodiment of a travel plan support system to which the present invention is applied. The travel plan support system includes a navigation device 1 that executes processing related to navigation of a mobile object, a travel plan support server 3 that is connected to a communication network 4 and supports creation of a travel plan for the mobile object, and a travel plan support server 3. And the client terminal 2 operated by the user. A plurality of wireless base stations 5 are connected to the communication network 4 to which the travel plan support server 3 is connected, and further connected to the navigation apparatus 1 via the wireless communication network 6. The client terminal 2 can also pass data to the navigation device 1 via the external storage medium 7. Here, the external storage medium 7 is configured by a storage medium such as a CD (Compact Disk), a DVD (Digital Versatile Disk), or a flash memory.

  The navigation device 1 includes a control unit 11 that controls the entire device, a data storage unit 12 that stores map data, a current location acquisition unit 13 that acquires a current location of a moving object using a GPS (Global Positioning System) sensor, and the like. An input unit 14 that receives input from the user, a display unit 15 that displays a user operation screen and a map, and the travel plan support server 3 via the wireless communication network 6, the wireless base station 5, and the communication network 4. The wireless communication unit 16 includes an external storage medium I / F (interface) 17 for receiving data from the client terminal 2 via the external storage medium 7.

  The client terminal 2 includes a PC 21 including a main body, a display, a mouse, a keyboard, and the like, and a communication unit 22 for connecting to the travel plan support server 3 via the communication network 4.

  The travel plan support server 3 includes a control unit 31 that controls the entire server, a data storage unit 32 that stores map data, and a communication unit 33 that is connected to the client terminal 2 via the communication network 4. Consists of.

  FIG. 2 is a diagram illustrating a configuration of the travel plan support server 3. The control unit 31 includes a processor 301 and a memory 302, and a program executed by the processor 301 is stored in the memory 302. When accepting a connection from the client terminal 2 or the navigation device 1, the memory 302 receives a user ID and password and collates with the authentication data 309 stored in the data storage unit 32 to perform authentication. A data search unit 304 that searches for necessary map data 308 from the data storage unit 32, a starting point and a destination set in the client terminal 2, and a plurality of waypoints set as necessary, A route search unit 305 for searching for a route from a departure point to a destination via a plurality of waypoints, and a feature on the route of the search result is extracted and converted into route feature information to be described later. A route registration unit 306 registered in the personal data 310 and a route in response to a request from the client terminal 2 or the navigation device 1. And a route distribution unit 307 which distributes feature information. The memory 302 includes a ROM (Read Only Memory) and a RAM (Random Access Memory), and stores map data 308 read from the data storage unit 32 in addition to the execution program.

  FIG. 3 is a diagram illustrating a configuration of the navigation device 1. The control unit 11 includes a processor 101 and a memory 102, and a program executed by the processor 101 is stored in the memory 102. The memory 102 includes a data search unit 103 that searches for necessary map data 107 and the like from the data storage unit 12, a route search unit 104 that executes a route search from a specified departure point to a destination, and a route along the route. A route guidance unit 105 that performs navigation and a route setting unit 106 that restores and sets a route based on the route feature information received from the travel plan support server 3 are provided. The memory 102 includes a ROM and a RAM, and stores map data read from the data storage unit 12 and route characteristic information received from the travel plan support server 3 in addition to the execution program.

  Here, a receiving unit that receives route characteristic information and the like includes a wireless communication unit 16 that performs wireless communication with the outside, and an external storage medium I / F (for receiving data from the client terminal 2 via the external storage medium 7). Interface) 17.

  The data storage unit 12 is configured by a relatively large capacity storage medium such as a hard disk drive or a flash memory. The data storage unit 12 stores map data 107 used for map display and route search, and personal data 108 such as a route set by connecting to the travel plan support server 3 from the client terminal 2. The input unit 14 includes a touch panel and operation buttons, and may further include a microphone or the like for voice input. The display unit 15 includes a display screen such as a liquid crystal display, and may further include a speaker or the like for outputting sound.

  Here, the map data will be described in detail.

  FIG. 4 is a diagram showing a configuration example of the map data. The map data is stored in the travel plan support server and the navigation device, respectively, and map display data 41 and route calculation data 42 are stored. The map display data 41 is data for displaying a map on the display unit 15, and includes road data 41a, background data 41b, and name data 41c. The road data 41a includes road shape data for displaying a road map, and the background data 41b includes data serving as the background of the road map such as railways, rivers, and buildings. The name data 41c includes annotation character string data such as place names, road names, and intersection names. Furthermore, the route calculation data 42 is data for performing route search by the route search units 104 and 305, and is constituted by connection data 42a.

  FIG. 5 is a diagram illustrating a configuration example of the map display data 41. Roads are often managed with a data structure based on nodes corresponding to intersections and links between nodes. As shown in FIG. 5A, the road data 41a associates a link ID with a road type, a road name, the number of coordinate points, and a coordinate point sequence. Of the number of coordinate points n, (X coordinate 1, Y coordinate 1) represents an intersection serving as the start point of the road, and (X coordinate n, Y coordinate n) represents an intersection serving as the end point of the road. Coordinates represented by (X coordinate 2, Y coordinate 2) to (X coordinate n-1, Y coordinate n-1) represent a shape interpolation point that interpolates a winding point on the road. As illustrated in FIG. 5B, the background data 41b describes a background ID, a background type, a background name, the number of coordinate points, and a coordinate point sequence in association with each other. As shown in FIG. 5C, the name data 41c describes a name ID, a name type, character information, and center coordinates in association with each other.

  Here, the travel plan support server 3 stores the correspondence of the name data between the map data 107 and 308 of the travel plan support server 3 and the navigation device 1, and the map data 107 used in the navigation device 1 is stored in the map data 107. In response, the name data included in the route feature information is converted. Further, when a newly opened road not included in the map data 308 of the navigation device 1 is included on the route, the coordinates of the feature link corresponding to the newly opened road are included in the route feature information.

  FIG. 6 is a diagram illustrating a configuration example of the route calculation data 42. The connection data 42a is data for performing a route search. As shown in FIG. 6, the link connection relationship and link cost in a certain node are described in association with the link ID and node ID. That is, if the number of adjacent nodes adjacent to the node is k, the adjacent node is described as a connection node ID1, ..., connection node IDk. For example, the node and the connection node ID1 are connected by a link ID1, and the link ID1 The cost is described as link cost 1.

  FIG. 7 is a diagram showing a flow of processing performed between the client terminal 2 and the travel plan support server 3 in the travel plan support system.

  First, when a communication connection is requested from the client terminal 2 to the travel plan support server 3 (S1), a communication connection between the travel plan support server 3 and the client terminal is established (S2). Next, when the ID and password are transmitted from the client terminal 2 to the travel plan support server 3 (S3), the travel plan support server 3 checks the received ID and password against the authentication data 309 (S4). When the collation is completed, the travel plan support server 3 generates a data editing screen and transmits it to the client terminal 2 (S5). Next, when the user operates the client terminal 2, a spot list corresponding to the departure place and the destination is set as spot list data shown in FIG. 9 (S6). Furthermore, it is possible to set a plurality of waypoints by including them in the point list data. When a route search based on the set spot list data is requested by the operation of the client terminal by the user (S7), the spot list data set by the user is transmitted to the travel plan support server 3 (S8). When the location list data is received (S9), the travel plan support server 3 performs route search processing (S10), generates a screen displaying the search result as a route on the map, and transmits it to the client terminal 2 (S11). ). When the route registration for registering this route is requested by the operation of the client terminal by the user (S12), the travel plan support server 3 extracts the feature on the route and converts it into route feature information (S13). For the registration process (S14), it is stored in the personal data 310 as route data 43 shown in FIG.

  Depending on whether or not to use the external storage medium 7 (S15), when downloading is requested by the operation of the client terminal 2 by the user (S16), the travel plan support server 3 uses the client terminal 2 Route data is transmitted to 2 (S17). The client terminal 2 receives the route data (S18) and stores the route data in the external storage medium 7 (S19). Finally, when communication disconnection is requested from the client terminal 2 to the travel plan support server 3 (S20), the communication connection between the travel plan support server 3 and the client terminal 2 is disconnected (S21).

  In this way, the feature of the route selected by the user is extracted, converted into route feature information, and stored as personal data 310, so that the same route feature information is stored in the travel plan support server 3 and the client terminal 2. It becomes possible to share with.

  8 to 10 are diagrams showing examples of the structure of data including the above-described route feature information.

  FIG. 8 is a diagram illustrating a configuration example of route data. As shown in FIG. 8, route data 43 includes route name 43a given to distinguish registered routes, point list data 43b including a departure point and destination set by the user and a plurality of waypoints, travel plan support The base map version 43c, route search version 43d, route search condition 43e, and route interpolation data 43f corresponding to the search result in the travel plan support server 3 are described.

  FIG. 9 is a diagram illustrating a configuration example of the spot list data 43b. As shown in FIG. 9A, the point list data 43b includes departure point data, destination data, and a plurality of waypoint data. Furthermore, these individual data are defined as point data, and are described by a point name, an address, and coordinates as shown in FIG. 9B.

  FIG. 10 is a diagram illustrating a configuration example of the route interpolation data 43f. As shown in FIG. 10A, the route interpolation data 43f is configured by section route data obtained by dividing a route from a departure place to a destination at a waypoint. The section route data is a result of extracting a feature node corresponding to a corner or the like on the route, and is composed of feature node data and feature link data as shown in FIG. As shown in FIG. 10C, the characteristic link data is described by a link ID string, a road type, a road name, and a travel distance. Further, the feature node data is described by coordinates, intersection type, intersection name, and traveling direction, as shown in FIG. Here, the advancing direction represents the advancing direction at the feature node, and for example, it may be described by an angle difference from the straight advancing direction, and the distinction between the right turn direction and the left turn direction may be described by a code. Alternatively, the surroundings of the feature nodes may be classified into, for example, eight directions, and codes may be assigned and described.

  FIG. 11 is a diagram for explaining section route data from route point A to route point B as a route search result. Here, N1 to N5 represent nodes (intersections), L1 to L6 represent links (roads), and P represents a shape interpolation point for interpolating and displaying the shape of a winding route that is not an intersection. . R represents a road on the route, and Q represents a road other than the route.

  FIG. 12 is a diagram for explaining processing for extracting route feature information using section route data from waypoint A to waypoint B corresponding to FIG. In FIG. 11, N2 and N4 are extracted as feature nodes corresponding to corners at intersections on the route. In FIG. 12, these feature nodes are described as N1 * and N2 *, respectively, and feature links are described as L1 * to L4 *.

  FIG. 13 is a diagram showing the flow of processing for feature node determination. The feature node determination is performed for each node on the route. First, when the number of branches at a node is 2 or less, it is not regarded as a feature node. Next, when the traveling direction at the node is not a road, it is determined as a feature node. Even in the case of a road, if a road attribute such as a road name or a road type changes, it is set as a feature node.

  FIG. 14 is a diagram for explaining the number of branches in the node. That is, the single road as shown in FIG. 14 (a) has two branches, the three-way road as shown in FIG. 14 (b) has three branches, and the four-way road as shown in FIG. 14 (c) has a branch number. 4 is judged.

  FIG. 15 is a diagram for explaining road determination in a node. As shown in FIG. 15 (a), it is determined that there is a road when the angle difference with the traveling direction is less than or equal to the threshold value, and as shown in FIG. 15 (b), even if the angle difference with the traveling direction is less than or equal to the threshold value. When there are a plurality of such roads, it is determined that the road is not a road. Further, as shown in FIG. 15 (c), when the angle difference from the traveling direction is equal to or larger than the threshold value, it is determined that there is no road.

  FIG. 16 is a diagram showing a flow of processing performed when the navigation apparatus 1 and the travel plan support server 3 are connected via the wireless communication network 6 in the travel plan support system.

  First, when a communication connection is requested from the navigation device 1 to the travel plan support server 3 (S31), a communication connection between the travel plan support server 3 and the navigation device 1 via the wireless communication network 6 is established (S32). Next, when the ID and password are transmitted from the navigation device 1 to the travel plan support server 3 (S33), the travel plan support server 3 collates the received ID and password with the authentication data 309 (S34). When the collation is completed, the travel plan support server 3 reads the index of the route list registered by the user with the client terminal 2 from the personal data 310 (S35), generates a route selection screen, and transmits it to the navigation device 1 (S36). . When one route is selected by the user operation in the navigation device 1 (S37), the travel plan support server 3 reads the route data designated by the user from the personal data 310 (S38) and displays the route data on the map. The generated screen is generated and transmitted to the navigation device 1 (S39). Further, when download is requested by the user operating the navigation device (S40), the travel plan support server 3 transmits route data to the navigation device 1 (S41). When the navigation device 1 receives the route data (S42), it requests the travel plan support server 3 to disconnect communication (S43), and the communication connection between the travel plan support server 3 and the navigation device 1 via the wireless communication network 6 is disconnected. (S44).

  Further, the navigation device 1 sets a route to be used for navigation based on the received route data (S45), displays the route data on the map (S46), and allows the user to confirm the route guidance. Start (S47).

  As described above, the navigation apparatus can display a route on the map by using the route feature information including the name data and the distance received from the travel plan support server 3.

  Next, processing of the navigation device 1 when the external storage medium 7 is used will be described. FIG. 17 is a diagram illustrating a flow of processing performed by the navigation device when setting route data using the external storage medium 7.

  First, the index of the route list is read from the external storage medium 7 (S51), and a route selection screen is displayed (S52). When one route is selected by the operation of the navigation device by the user (S53), the route data shown in FIG. 8 designated by the user is read from the external storage medium 7 (S54), and the route used for navigation based on the route data. Is set (S55). Further, the route is displayed on the map (S56), and after the user is confirmed, the route guidance is started (S57).

  As described above, by using the external storage medium, it is possible to restore the route in the navigation device even when the communication is disabled.

  FIG. 18 is a diagram showing a flow of route setting processing in the navigation device 1. First, each piece of point data in the point list data 43b shown in FIG. 9 is set in association with the map data 107 of the navigation device 1 (S71). Next, based on the feature link data and feature node data of the section route data shown in FIG. 10, the route is restored by matching with the map data 107 (S72). In this embodiment, the route is restored by following the link corresponding to the section route data, starting from the departure point or waypoint. From the information of the characteristic link data shown in FIG. 10, a link having the same road type and road name is extracted for the travel distance. Further, from the information of the feature node data shown in FIG. 10, the coincidence of the intersection type and the intersection name is confirmed, and the link in the traveling direction is extracted. Such a restoration method is described in Yoshihiro Suzuki and two others, “The Journal of the Institute of Electronics, Information and Communication Engineers, 1998/12, Vol. J81-D-II, No. 12, 3.2 Identification of Route on Road Network”. Are listed. Such an operation is repeated, and the route corresponding to the section route data is partially restored. Finally, a route search is performed for the section for which the route could not be restored, and the route is interpolated (S73).

  In this way, even when the map data of the travel plan support server and the navigation device are different and the coordinates are shifted, the navigation device restores the route from the name data, the traveling direction, and the travel distance included in the route characteristic information. be able to.

  Next, an embodiment of the travel plan support system according to the present invention is compared with the conventional system. The conventional method is a transfer method based on shape data (description using a start point, an end point, and an interpolation point). On the other hand, as described above, the travel plan support system according to the embodiment of the present invention has a transfer method based on feature points and attributes ( (Description of attributes consisting of coordinates and types and names of feature points).

Evaluation is based on the data transfer size (speed) from the travel planning support server to the car navigation system
The comparison was made.

  In the conventional transfer method using shape data, the shape of each link is described by a start point, an end point, and an interpolation point, and the coordinates of each point are estimated to be about 8 bytes per point. The coordinates are described by mesh codes and in-mesh coordinates. If the mesh code is about 4 bytes and the in-mesh coordinates are x and y about 2 bytes, respectively, it is estimated that about 8 bytes per point. Since there are about one interpolation point for each link in an urban area, the data size per link is estimated to be about 16 bytes, and it is estimated to be larger in the countryside and mountains.

  Assuming a route (general road) of about 50 km as the size of data to be transferred, the number of links is about 500, so the data size is about 8 kBytes, and it is expected that the data size will be larger in the countryside and mountains.

  On the other hand, in the transfer method using feature points and attributes according to the present embodiment, the coordinates of the feature points are estimated to be about 8 bytes per point as in the conventional method. The attribute is described by the type and name, and is estimated to be about 20 bytes, although it varies depending on the length of the name. The data size is estimated to be about 50 bytes per link row between feature points.

  The size of the data to be transferred is about 10 bytes when the route (general road) of about 50 km is assumed, and considering the concentration of the feature points near the starting point and the destination, it is about 500 bytes. .

  As described above, when the present embodiment is compared with the conventional example, the transfer rate of the present embodiment is about 1/10 that of the conventional example. Furthermore, in the case of a shape including many interpolation points such as mountain roads, it can be considered that the transfer speed is about 1/100 of the conventional example, and the effect of this embodiment can be sufficiently confirmed.

1 is a block diagram of a travel plan support system according to an embodiment of the present invention. It is a block diagram which shows the structure of the travel plan assistance server in the said system. It is a block diagram which shows the structure of the navigation apparatus in the said system. It is a figure which shows the flow of the process implemented between the client terminal and travel plan support server in the said system. It is a figure which shows the flow of the process implemented between the navigation apparatus and travel plan assistance server in the said system. It is a figure which shows the flow of the process implemented with the said navigation apparatus using an external storage medium. It is a figure which shows the structural example of the map data in the said system. It is a figure which shows the structural example of the data for map display in the said system. It is a figure which shows the structural example of the data for route calculation in the said system. It is a figure which shows the structural example of the route data in the said system. It is a figure which shows the structural example of the point list data in the said system. It is a figure which shows the structural example of the route interpolation data in the said system. It is a figure for demonstrating the area route data in the said system. It is a figure for demonstrating the process which extracts the route characteristic information in the said system. It is a figure which shows the flow of a process of characteristic node determination in the said system. It is a figure for demonstrating the number of branches of the node in the said system. It is a figure for demonstrating the way determination of the node in the said system. It is a figure which shows the flow of the route setting process of the navigation apparatus in the said system.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Navigation apparatus, 2 ... Client terminal, 3 ... Travel plan support server, 4 ... Communication network, 5 ... Wireless base station, 6 ... Wireless communication network, 7 ... External storage medium, 11 ... Control part, 12 ... Data storage part , 13 ... current location acquisition unit, 14 ... input unit, 15 ... display unit, 16 ... wireless communication unit, 17 ... external storage medium I / F, 21 ... PC, 22 ...: communication unit, 31 ... control unit, 32 ... data Storage unit, 33... Communication unit.

Claims (11)

A travel plan support system comprising: a navigation device that executes processing related to navigation of a mobile object; and a travel plan support server that is connected to a communication network and supports creation of a travel plan for the mobile object,
The travel plan support server searches for a route from the departure point to the destination based on the input departure point and destination , and the number of branches on the searched route is greater than 2 and a straight direction A node whose angle difference is greater than or equal to a threshold value or whose road attribute changes is extracted as a feature node, name data corresponding to the feature node and a traveling direction, name data corresponding to a feature link between the feature nodes, and A control unit that converts and stores route characteristic information including travel distance;
The said navigation apparatus is equipped with the control part which receives the said route characteristic information from the said travel plan support server, and restore | restores the route used for navigation based on the said route characteristic information. The travel plan support system characterized by the above-mentioned. 2. The travel according to claim 1, wherein the control unit of the travel plan support server further receives one or more waypoints and searches for a route from the departure point to the destination via the waypoint. Planning support system. The travel plan support system according to claim 1, wherein the route feature information includes coordinates of the feature node. The control unit of the travel plan support server, when a newly opened road not included in the map data of the navigation device is included on the route, the feature link coordinates corresponding to the newly opened road in the route feature information The travel planning support system according to claim 1, further comprising: The travel plan support system according to claim 1, wherein the departure place and the destination are input by a client terminal connected to the travel plan support server through the communication network. A travel plan support method comprising: a navigation device that executes processing related to navigation of a mobile object; and a travel plan support server that is connected to a communication network and supports creation of a travel plan for the mobile object,
The travel plan support server searches for a route from the departure point to the destination based on the input departure point and destination , and the number of branches on the searched route is greater than 2 and a straight direction A node whose angle difference is greater than or equal to a threshold value or whose road attribute changes is extracted as a feature node, name data corresponding to the feature node and a traveling direction, name data corresponding to a feature link between the feature nodes, and Convert to route feature information including mileage and store it,
The navigation device receives the route feature information from the travel plan support server, and restores a route used for navigation based on the route feature information. The control unit of the travel plan support server further receives one or more waypoints, and searches for a route from the departure point to the destination via the waypoints. Travel planning support method. The travel plan support method according to claim 6, wherein the route feature information includes coordinates of the feature node. The control unit of the travel plan support server, when a newly opened road not included in the map data of the navigation device is included on the route, the feature link coordinates corresponding to the newly opened road in the route feature information The travel planning support method according to claim 6, further comprising: The travel plan support method according to claim 6, wherein the departure place and the destination are input by a client terminal connected to the travel plan support server through the communication network. A navigation device that executes processing related to navigation of a moving object,
Corresponding to the feature node, which is a node on the route from the departure point to the destination , the number of branches is greater than 2, and the angle difference from the straight direction is greater than or equal to a threshold value or the road attribute changes. A receiving unit for receiving route feature information including name data and a traveling direction, and name data and a travel distance corresponding to a feature link between the feature nodes;
A control unit for restoring a route used for navigation based on the route characteristic information;
A navigation device comprising: a display unit that displays the route.

Images