JP7417682B1 - Partial route guidance system and partial route guidance method - Google Patents

Abstract

An object of the present invention is to appropriately guide a route even to a destination for which an appropriate route cannot be displayed using other route guidance services. [Solution] A server 2 includes an address registration table 21 that stores the address of a destination reached by a user, a route registration table 22 that stores information including a partial route to reach this destination, and an address registration table 21 that stores the address of a destination reached by a user. When the user sets an address stored in the table 21 as a new destination and the route to the destination satisfies a predetermined ease of getting lost condition, the user's information including the partial route to the destination is It also includes a notification section 25 that notifies the terminal. [Selection diagram] Figure 1

Description

The present invention relates to a partial route guidance system and a partial route guidance method.

The demand for food delivery services is increasing amid the coronavirus pandemic. Food delivery services are often ordered after the customer wants to eat, so compared to home delivery of non-food items, delivery is required to be more strictly within the specified time.

For store delivery, the same delivery person delivers within a limited range each time. As a result, delivery personnel are able to develop local knowledge and deliver in a short time. However, with food delivery services, it is not always the same delivery person who delivers the food, and in many cases it is delivered by someone who is not familiar with the area. Therefore, there are cases where delivery time is significantly delayed due to route errors, etc.

US Pat. No. 5,001,000 includes means for transmitting a location request from a client-side computing device to a map tile server, means for receiving a set of map tiles in response to the location request, and means for assembling the received map. An invention is disclosed. The invention of Patent Document 1 is suitable for supporting delivery operations.

US Patent No. 7894984

Delivery personnel of food delivery services often deliver based on the route guidance service shown in Patent Document 1. However, route guidance services may not provide the correct route on roads that are not accessible to cars. In some cases, you may be directed to the back of the building. Furthermore, current route guidance services may not be able to provide the correct route to a destination due to factors such as ``narrow roads that only people can enter,'' ``houses with height differences,'' and ``inaccurate shortest routes.'' In such cases, the delivery person may not be able to deliver within a reasonable time.

Therefore, an object of the present invention is to provide suitable route guidance even for destinations for which other route guidance services cannot display appropriate routes.

In order to solve the above problems, the partial route guidance system of the present invention includes a communication unit that receives the route from the departure point to the destination guided by the route guidance server, and the address of the destination from the user's terminal. a receiving unit that receives information on the route to reach the destination; an address registration table that stores the address of the destination; and a unit that contacts the route guided by the route guidance server and until the destination is reached a route registration table that stores a partial route, arrival time information, and the weather at that time; an ease of getting lost calculation unit that calculates an index value of how easy it is to get lost on the route to the destination; and the address registration. When the user sets an address stored in the table as a new destination, and the destination satisfies a predetermined ease of getting lost condition, the partial route and arrival are adjusted to the weather when the user sets the destination. The apparatus is characterized by comprising a notification unit that notifies the user's terminal of time information.

The partial route guidance method of the present invention includes the steps of: receiving, by the communication unit, the route from the departure point to the destination guided by the route guidance server; and the receiving unit transmits the address of the destination and the a step of receiving information on the route to reach the destination; a step of storing the address of the destination in an address registration table; A step of storing the partial route to the destination, arrival time information, and the weather at that time, and a probability of getting lost calculation unit calculating an index value of the probability of getting lost on the route to the destination. and if the user sets the address stored in the address registration table as a new destination, and the destination satisfies a predetermined ease of getting lost condition, the notification unit determines that the user has set the destination. The method is characterized by comprising the step of notifying the user's terminal of the partial route and arrival time information tailored to the weather at the time.
Other means will be explained in the detailed description.

According to the present invention, it is possible to provide suitable route guidance even for destinations for which other route guidance services cannot display appropriate routes.

FIG. 1 is a configuration diagram of a route guidance system according to the present embodiment. FIG. 2 is a block diagram illustrating an example of a terminal. FIG. 2 is a block diagram illustrating an example of a server. It is a figure showing an example of an address registration table. It is a figure showing an example of a route registration table. FIG. 3 is a diagram showing a user's trajectory and trajectory information recorded in a route registration table. 12 is a flowchart of a process in which the server notifies a partial route that is independent of an existing map. It is a flowchart of information registration processing of a terminal. It is a flowchart of information registration processing of a server. It is a flowchart of the ease of getting lost calculation process. It is a flowchart of redundant route deletion processing. 12 is a flowchart of error route reference information addition processing. It is a figure showing an example of an address registration table. It is a flowchart of error route correction processing. It is a figure showing an example of an address registration table.

Hereinafter, embodiments for carrying out the present invention will be described in detail with reference to the respective figures.
FIG. 1 is a configuration diagram of a route guidance system according to this embodiment.
The route guidance system is implemented by the server 2. The server 2 is a computer installed in a data center, for example, and receives the delivery trajectory and delivery time from the terminal 1 and transmits a partial route to the terminal 1. This server 2 transmits the departure point and destination to the route guidance server 3, and acquires the entire route from the departure point to the destination.

The terminal 1 is carried by, for example, a delivery person of a food delivery service, and accesses the route guidance server 3 and inputs the departure point (current location) and destination. Get the entire route to.
The route guidance server 3 internally stores map information, road network information, etc., and transmits the entire route from the input starting point to the destination.

The terminal 1 acquires GPS (Global Positioning System) information and transmits to the server 2 information on the trajectory of reaching the destination. Then, when the user of the terminal 1 heads for the destination for the second time or later, the terminal 1 receives the trajectory information from the server 2. Note that when heading to the destination for the first time, the terminal 1 either receives no data or receives trajectory information manually registered by the user of the food delivery service from the server 2.

Of the delivery trajectories received from the terminal 1, the server 2 stores only the shortest distance from the roadway to the destination. Then, the server 2 deletes not the shortest distance from the road to the destination, but the route in which the delivery person got lost. The server 2 does not accumulate information on places that can be reached through route guidance provided by the route guidance server 3. The ease of getting lost in a route is defined by the difference between the estimated arrival time and the actual arrival time. Note that the server 2 excludes areas such as parks, which are places where there is a high possibility that the time-consuming factor is not the complexity of the road, as areas that are not subject to this evaluation of ease of getting lost.

The notification unit 25 of the server 2 notifies the delivery person's terminal 1 of a partial route in advance only for places where the delivery person is likely to get lost. The delivery person understands a suitable delivery route based on the map displayed on the terminal 1 and the partial route information to the destination.

FIG. 2 is a block diagram showing an example of the terminal 1. As shown in FIG.
The terminal 1 includes a GPS positioning section 11, a communication section 12, a control section 13, and a touch panel display 14.

The GPS positioning unit 11 measures the current position based on radio waves received from GPS satellites. The communication unit 12 communicates with the server 2 or the route guidance server 3 via, for example, a carrier communication network.
The control unit 13 performs overall control of this terminal 1.
The touch panel display 14 is configured by laminating a touch panel that detects user operations on a display that displays characters, images, and graphics. Maps, partial routes, etc. are displayed on this touch panel display 14.

FIG. 3 is a block diagram showing an example of the server 2. As shown in FIG.
The server 2 includes an address registration table 21, a route registration table 22, a reception section 23, a registration section 24, a notification section 25, a correction section 26, and a likelihood of getting lost calculation section 27.

The address registration table 21 stores the address of the destination reached by the user and the ID of the route information. The route registration table 22 stores information including partial routes to reach the destination.
The receiving unit 23 receives information about the address of the destination and the route to reach the destination from the user's terminal 1 .

The registration unit 24 registers the address of the destination in the address registration table 21 and registers information including a partial route to the destination in the route registration table 22. Further, the registration unit 24 sets the partial route as a portion of the route to the destination that deviates from the roadway, or a route that deviates from the route indicated by another route guidance service. The registration unit 24 deletes, among the plurality of partial routes stored in the route registration table 22 and headed for the same destination, those that can be reached in the shortest time.

The correction unit 26 corrects the registered partial route. The correction unit 26 disables notification to the terminal 1 of partial routes that have not been used within three years (first predetermined period). This prevents the terminal 1 from being notified of information that has not been used for more than the first predetermined period and lacks reliability. Here, methods for disabling notification of the partial route to the terminal 1 include adding a deletion target mark to the partial route and actually deleting the partial route.
Furthermore, if there are multiple partial routes that have not been used within half a year (second predetermined period), the correction unit 26 will not be able to notify the terminal 1 of any partial routes other than the latest one.

When the user sets an address stored in the address registration table 21 as a new destination and the route to the destination satisfies a predetermined ease of getting lost condition, the notification unit 25 sends information about the part of the journey to the destination. Information including the route is notified to the user's terminal 1. The case where the route to the destination satisfies the predetermined ease of getting lost condition is the case where the index value of the ease of getting lost along the route to the destination exceeds the predetermined threshold value.
Note that the notification unit 25 may notify the user's terminal 1 of information including a partial route to the destination, regardless of the condition of ease of getting lost, and is not limited thereto.

The ease of getting lost calculation unit 27 calculates an index value of the ease of getting lost along the route to the destination. The index value of the ease of getting lost may be a difference or a ratio between a predicted value of travel time and an actual value, or a difference or a ratio between a predicted value of travel distance and an actual value. Further, the method of comparing the predicted value of the moving distance and the actual value is not limited to the difference and ratio, and any calculation may be used. In addition, the comparison is between the predicted value and the actual value of the route to the destination in the partial route, but it may also be a comparison between the predicted value and the actual value of the route from the departure point to the destination.

Note that the ease of getting lost calculation unit 27 stores the index value of the ease of getting lost at the time of registration at the time of first registration, and thereafter stores the index value of the ease of getting lost at the time of use. The index value of the ease of getting lost at the time of registration indicates whether or not it is easy for a delivery person delivering to this destination for the first time to get lost. The index value of the ease of getting lost during use indicates whether or not it is easy for a delivery person who delivers to this destination for the second time or later to get lost.

FIG. 4 is a diagram showing an example of the address registration table 21.
The address registration table 21 includes an ID column, an address column, an ease of getting lost column, a last use date column, and a use frequency column.
The ID column is a column for storing an identifier of route information, and is used to refer to information stored in the ID column of the route registration table 22, which will be described later.
The address field is a field that stores the address of the destination.

The ease of getting lost column is a column that stores an index value of how easy it is to get lost on the route to this destination. This ease of confusion column further stores a registration column and a usage column. The registration column is a column that stores an index value of the ease of getting lost on the route to the destination at the time of registration. The index value stored in the registration field is used as an index indicating whether or not a delivery person delivering to a destination for the first time is likely to get lost.

The usage column is a column that stores an index value of how easy it is to get lost on the route to the destination when the device is used. The index value stored in the use time column is stored as an index indicating whether or not a delivery person delivering to this destination for the second time or later is likely to get lost.
The last use date column is a column that stores the last use date for this address.
The number of uses column is a column that stores the number of times of use for delivery to this destination.

FIG. 5 is a diagram showing an example of the route registration table 22.
The route registration table 22 is configured to include an ID field, a time field, a latitude field, a longitude field, and a start/end field. The route registration table 22 is composed of position information of each point configuring the partial route.

The ID column is a column that stores the identifier of this route information. The same route is given the same identifier. By referring to the address registration table 21 using this identifier, the destination associated with the identifier can be known.
The time column is a column for storing the time at which the terminal 1 arrived at a certain point constituting this partial route.

The latitude column is a column for storing latitude information of a certain point that constitutes this partial route.
The longitude column is a column for storing longitude information of a certain point that constitutes this partial route.
The start/end column is a column that stores information indicating whether this point is the start/end of this partial route or somewhere in between. This position information is acquired by the terminal 1 at predetermined time intervals and transmitted to the server 2. The server 2 uses the registration unit 24 to register the received position information in the route registration table 22.

FIG. 6 is a diagram showing the user's trajectory and trajectory information recorded in the route registration table 22.
FIG. 6 shows map information of a predetermined area, on which a partial route 42, routes 41a to 41c, a starting end 43, and a terminal end 44 are displayed.

The routes 41a to 41c are, for example, routes guided by the route guidance server 3, and are, for example, roads or driveways with a predetermined width or more. The starting end 43 is positional information that is in contact with these existing routes 41a. Termination 44 is the delivery address and destination. The partial route 42 is a partial route that the server 2 guides the user of the terminal 1 to. The partial route 42 is a suitable delivery route that connects a starting end 43 on the roadway to a terminal end 44 that is the destination.

FIG. 7 is a flowchart of a process for notifying a partial route that is independent of existing route guidance.
First, the notification unit 25 of the server 2 obtains the address registration table 21 (step S10) and compares it with the address of the destination. If the destination address is registered in the address registration table 21 (Yes), the notification unit 25 proceeds to step S12. If the destination address is not registered (No), the notification unit 25 ends the process of FIG. 7 .

Next, the notification unit 25 refers to the ease of getting lost column of the address registration table 21 (step S12), and determines whether the destination satisfies a predetermined ease of getting lost condition. If the destination satisfies the predetermined ease of getting lost condition (Yes), the notification unit 25 proceeds to step S13. If the destination does not satisfy the predetermined ease of getting lost condition (No), the notification unit 25 ends the process of FIG. 7 .

In step S13, the notification unit 25 acquires a series of route data with matching destination addresses from the route registration table 22. The notification unit 25 then waits for position information from the terminal 1. The terminal 1 updates the current location (step S14). The updated location information is sent to the server 2.

Next, the notification unit 25 of the server 2 determines whether it is near the starting end of the partial route (step S15). Here, the notification unit 25 determines that the location is near the starting end when it is within a predetermined range from the starting end of the partial route. If the notification unit 25 is not near the start end (No), the process returns to step S14 and updates the current position, and if it is near the start end (Yes), the process proceeds to step S16.

In step S16, the notification unit 25 notifies the user's terminal 1 that it is a partial route and the partial route information. Then, the terminal 1 displays this partial route over the map (step S16), and then ends the process of FIG. 7.

Note that in the case of linking with existing route guidance, existing route search logic can be used instead.

FIG. 8 is a flowchart of the information registration process of the terminal 1.
When the delivery person starts food delivery, the terminal 1 owned by the delivery person starts acquiring information (step S20). Information acquisition here means acquiring positioning information by the GPS positioning unit 11.
Then, the terminal 1 owned by the delivery person determines whether the delivery has been completed (step S21). When the delivery is completed, the delivery person inputs a notification to that effect into the terminal 1. If the delivery has not been completed (No), the terminal 1 returns to the process of step S20, and if the delivery has been completed (Yes), the terminal 1 proceeds to the process of step S22.
In step S22, the terminal 1 uploads the route information to the server 2, and then ends the process of FIG.

FIG. 9 is a flowchart of the information registration process of the server 2.
When the server 2 receives the route information from the terminal 1, it executes the process shown in FIG.
The registration unit 24 of the server 2 executes the doubt ease calculation process shown in FIG. 10 (step S30). Then, the server 2 executes the redundant route deletion process shown in FIG. 11 (step S31).
The registration unit 24 determines whether the destination of this route information is a new address (step S32). If the destination of this route information is a new address (Yes), the registration unit 24 stores the ease of getting lost partial route data (step S34), and ends the process of FIG.

If the destination of this route information is not a new address (No), the registration unit 24 executes the error route reference information addition process shown in FIG. 12 (step S33), and ends the process of FIG. 9.

By managing more detailed route information than other route guidance services as positioning information, delivery times due to route errors can be reduced.

FIG. 10 is a flowchart of the ease of getting lost calculation process.
The likelihood of getting lost calculation unit 27 of the server 2 acquires the predicted distance from the route guidance server 3 (step S40). Then, the ease of getting lost calculation unit 27 of the server 2 obtains the actual travel distance based on the route obtained from the terminal 1 (step S41). Furthermore, the ease of getting lost calculation unit 27 calculates the difference between the predicted distance and the actual travel distance, and uses this as an index of the ease of getting lost (step S42), and ends the process of FIG. 10. Note that when the destination is registered for the first time, the server 2 stores an index of the ease of getting lost in the registration column of the address registration table 21. When a partial route to a registered destination is used, the server 2 stores an index of the ease of getting lost in the use column of the address registration table 21.

Note that the registration unit 24 may calculate the difference between the predicted time to the destination acquired from the route guidance server 3 and the actual travel time of the user, and use this as an index of the ease of getting lost, but is not limited thereto.

FIG. 11 is a flowchart of redundant route deletion processing.
The server 2 uses the receiving unit 23 to acquire GPS information at the time of completion of delivery (step S50). Then, the registration unit 24 of the server 2 determines whether the GPS information matches a road on the existing map, starting from the end (step S51). If the GPS information does not match the road on the existing map (No), the registration unit 24 acquires the previous GPS information (step S52), and returns to step S51.

If the GPS information matches the road on the existing map (Yes), the registration unit 24 stores the compared GPS information as a partial route (step S53), and ends the process of FIG. .

Note that the registration unit 24 may determine whether the GPS information matches the road. Accordingly, the registration unit 24 may set the partial route to a portion of the route to the destination that deviates from the road. I can do it.

The registration unit 24 may determine whether the GPS information matches the entire route indicated by the route guidance server 3. Thereby, the registration unit 24 may determine whether the GPS information matches the entire route indicated by the route guidance server 3. Thereby, the registration unit 24 may determine whether the partial route is the route to the destination. It can be a portion that deviates from the entire route indicated by the guide server 3.

FIG. 12 is a flowchart of error route reference information addition processing.
The registration unit 24 of the server 2 determines whether a registered partial route has been used (step S60). If the registered partial route is not used (No), the registration unit 24 newly stores this destination and stores the route data as another route (step S61). Further, the registration unit 24 stores the ease of getting lost when registering the route data related to the destination in the address registration table 21 (step S62), and then ends the process of FIG. 12.

In step S60, if the registration unit 24 uses the same route as the registered partial route (Yes), the registration unit 24 counts up the number of times this partial route has been used (step S63). The registration unit 24 updates the last use date (step S64). When the registration unit 24 stores the ease of getting lost at the time of registering the route data related to the destination in the address registration table 21 (step S65), the process of FIG. 12 ends.

Note that the server 2 determines whether the route is a different route or not based on the deviation of the lines when the position information of both routes are connected by lines.

FIG. 13 is a diagram showing an example of the address registration table 21.
The address registration table 21 includes an ID column, an address column, an ease of getting lost column, a last use date column, and a use frequency column.

In this address registration table 21, the address columns in the first and third lines are the same, and although the destination is the same, the identifiers in the ID column are different. This ID column indicates the identifier given to the partial route stored in the route registration table 22. The information on the third line has a usage count of 1. This indicates that the partial route with the identifier 3 has been registered for the first time and is a different route from the partial route with the identifier 1.

FIG. 14 is a flowchart of the error route correction process. This error route correction process is a process that is periodically performed on the server 2 side, and is not triggered by the user's use.
First, the correction unit 26 of the server 2 refers to the last use date in the address registration table 21 and determines whether the route has been used within three years (step S70). Here, three years is the first predetermined period.
In step S70, if the route has not been used within three years (No), the correction unit 26 deletes the target partial route (step S71), and ends the process of FIG. 14.

In step S70, if the route has been used within three years (Yes), the correction unit 26 determines whether the number of registered routes to this destination is one or less (step S72).
In step S72, if the number of registered routes to this destination is two or more (No), the correction unit 26 determines whether the route has been used within six months (step S73).

In step S73, if there has been no use within half a year (No), the correction unit 26 marks the deletion target column (see FIG. 15) of the target route, leaving one with the latest usage date (step S74 ), the process in FIG. 14 ends. Here, half a year is the second predetermined period.
In step S72, if the number of registered routes to this destination is one or less (Yes), the correction unit 26 ends the process of FIG. 14.

In step S73, if the correction unit 26 has used it within half a year (Yes), it ends the process of FIG. 14.
Note that each threshold value in the above process is just an example. It is desirable that the threshold value be defined according to the operation.

FIG. 15 is a diagram showing an example of the address registration table 21. As shown in FIG.
The address registration table 21 includes an ID field, an address field, an ease of getting lost field, a date of last use field, a number of times of use field, and a deletion target field.
The deletion target column is a column indicating that the target route has been deleted. Thereby, the registration unit 24 can easily delete the target route.

(Modified example)
The present invention is not limited to the embodiments described above, and includes various modifications. For example, the embodiments described above are described in detail to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the configurations described. It is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is also possible to add, delete, or replace some of the configurations of each embodiment with other configurations.

Part or all of the above configurations, functions, processing units, processing means, etc. may be realized by hardware such as an integrated circuit. Each of the above configurations, functions, etc. may be realized by software by a processor interpreting and executing a program for realizing each function. Information such as programs, tables, and files that implement each function can be stored in a storage device such as memory, hard disk, SSD (Solid State Drive), or recording medium such as a flash memory card or DVD (Digital Versatile Disk). can.

In each embodiment, the control lines and information lines are those considered necessary for explanation, and not all control lines and information lines are necessarily shown in the product. In reality, almost all components may be considered interconnected.
(Modified example)
The present invention is not limited to the above-mentioned embodiments, and can be modified without departing from the spirit of the present invention. Examples include the following (a) to (f).

(a) The route guidance system should not only indicate the starting point of the route on the map, but also show the starting point of the route and a partial route beyond it by superimposing it on a photograph taken of the city. Thereby, the ease of understanding the route guidance can be improved.

(b) The route guidance system may record the route information together with weather or traffic conditions, and guide the arrival time and partial route according to the weather or traffic conditions at the time of delivery.

(c) The recipient may register a preferred route in advance. Since the person receiving the delivery registers, the most suitable partial route can be provided from the beginning.

(d) In addition to delivery, it can also be applied to situations where friends are invited for the first time to share the information, and it can also be used as directions to a company or store.
(e) The route guidance system of this embodiment may be applied to postal delivery, where there is concern about a shortage of human resources.
(f) The index value of the ease of getting lost may be the difference between the predicted and actual travel distance within a predetermined distance of the destination. This is because if a delivery person is lost in his or her route, he or she does not know the entrance to the destination and is therefore likely to have traveled a large distance around that destination. Since the information is acquired within a predetermined distance of the destination, the actual distance traveled within the predetermined distance of the destination can be easily calculated.

1 Terminal 11 GPS positioning unit 12 Communication unit 13 Control unit 14 Touch panel display 2 Server (route guidance system)
21 Address registration table 22 Route registration table 23 Receiving section 24 Registration section 25 Notification section 26 Correction section 27 Loss susceptibility calculation section 3 Route guidance server 41a to 41c Route
42 Partial route 43 Starting end 44 Terminating end

Claims (11)

a communication unit that receives the route from the departure point to the destination guided by the route guidance server;
a receiving unit that receives information about the address of the destination and the route to reach the destination from a user's terminal;
an address registration table that stores the address of the destination;
a route registration table that stores partial routes touching the route guided by the route guide server and reaching the destination, arrival time information, and weather at that time;
an ease of getting lost calculation unit that calculates an index value of how easy it is to get lost on the route to the destination;
When the user sets an address stored in the address registration table as a new destination, and the destination satisfies a predetermined ease of getting lost condition, the portion is adjusted to the weather when the user sets the destination. a notification unit that notifies the user's terminal of route and arrival time information;
A partial route guidance system comprising: The ease of getting lost calculation unit calculates the ease of getting lost on the route to the destination based on the difference or ratio between the predicted distance from the starting point of the route guided by the route guidance server to the destination and the actual travel distance. Calculate the index value,
The partial route guidance system according to claim 1, characterized in that: The ease of getting lost calculation unit calculates the ease of getting lost on the route to the destination based on the difference or ratio between the predicted travel time from the departure point to the destination and the actual travel time of the route guided by the route guidance server. calculate the index value of
The partial route guidance system according to claim 1, characterized in that: The ease of getting lost calculation unit calculates an index value of the ease of getting lost on the route to the destination based on the difference or ratio between the predicted travel distance and the actual travel distance within a predetermined distance from the destination.
The partial route guidance system according to claim 1, characterized in that: The notification unit notifies the terminal of information including the partial route to the destination when the terminal enters a predetermined range from the starting point of the partial route.
The partial route guidance system according to claim 1, characterized in that: a receiving unit that receives information about the address of the destination and the route to reach the destination from the terminal;
a registration unit that registers the address of the destination in the address registration table and registers information including a partial route to the destination in the route registration table;
The partial route guidance system according to claim 1, further comprising:. The registration unit sets the partial route as a portion that deviates from the route indicated by the route guidance server.
7. The partial route guidance system according to claim 6. The registration unit deletes a plurality of partial routes stored in the route registration table and headed for the same destination other than one that can be reached in the shortest time.
7. The partial route guidance system according to claim 6. a correction unit that makes it impossible to notify the terminal of partial routes that have not been used within a first predetermined period;
The partial route guidance system according to claim 1, further comprising:. If there are multiple partial routes that have not been used within a second predetermined period, the correction unit may not notify the terminal of any partial routes other than the latest one.
10. The partial route guidance system according to claim 9. a step of receiving, by the communication unit, the route from the departure point to the destination guided by the route guidance server;
Receiving information about the address of the destination and the route to reach the destination from the user's terminal by the receiving unit;
storing the address of the destination in an address registration table;
storing, in a route registration table, a partial route that touches the route guided by the route guidance server and reaches the destination, arrival time information, and the weather at that time;
a step in which the ease of getting lost calculation unit calculates an index value of how easy it is to get lost on the route to the destination;
When the user sets an address stored in the address registration table as a new destination, and the destination satisfies a predetermined ease of getting lost condition, the notification unit displays information based on the weather at the time the user set the destination. notifying the user terminal of the combined partial route and arrival time information;
A partial route guidance method comprising:

Images