JP2017009308A - Route output program, route output system, and route output method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a route output program, a route output system, and a route output method capable of outputting, for each vehicle, a route which has a record that vehicles larger than a relevant vehicle have passed.SOLUTION: Receiving an input a start point and a destination point of a vehicle, the route output system extracts a travel route of vehicles the size or weight of which is larger than that of own vehicle while referring to a storage which stores travel routes of each of the vehicles while associating with date and time. From the extracted travel routes, the route output system outputs a travel route which includes the start point and the destination point.SELECTED DRAWING: Figure 15

Description

  The present invention relates to a route output program, a route output device, and a route output method for outputting a route from a departure point to a destination point.

  In a conventional in-vehicle navigation system or the like, a technique for presenting a route reflecting past traffic jam information, road regulation information, or the like is already known.

Japanese Patent Laid-Open No. 2003-272082 JP 2003-315077 A

  For example, a large vehicle such as a truck may not be able to pass even on a road without restrictions. Specifically, for example, there is a case where there is a sharp curve, a corner, or the like, or a case where only a large vehicle is prohibited due to road construction.

  In one aspect, an object is to provide a route output program, a route output device, and a route output method capable of outputting a route with a track record that a vehicle having a scale larger than the vehicle has traveled.

  The disclosed technology accepts input of a starting point and a destination point of a vehicle, refers to a storage unit that stores a traveling route for each vehicle in association with a date and time, and stores a vehicle or a vehicle whose size is larger than the size of its own vehicle. A computer extracts a travel route of a vehicle whose weight is equal to or greater than the weight of its own vehicle, and outputs a travel route including the departure point and the destination point in the extracted travel route.

  Each of the above processes may be a functional unit that realizes each of the above processes, a method of causing each computer to execute each process as a procedure, or a computer-readable storage medium that stores a program.

  For each vehicle, it is possible to output a route with a track record that a vehicle of a size larger than the vehicle has traveled.

It is a figure which shows an example of the route output system of 1st embodiment. It is a figure which shows an example of the hardware constitutions of a server. It is a figure which shows an example of a driving | running | working data database. It is a figure which shows an example of a vehicle database. It is a figure which shows an example of a driving | running | working performance database. It is a figure which shows an example of a route database. It is a figure explaining the functional structure of the server of 1st embodiment. It is a flowchart explaining the update of the driving | running | working performance database of the server of 1st embodiment. It is a 1st flowchart explaining the process of the route output process part of 1st embodiment. It is a 2nd flowchart explaining the process of the route output process part of 1st embodiment. It is a 1st figure explaining the process of a route output process part. It is a 2nd figure explaining the process of a route output process part. It is a figure explaining route information. It is a flowchart explaining the process of the display of a route of 1st embodiment. It is a figure which shows the example of the screen where the list | wrist of the route was displayed. It is a 1st figure which shows the example of the screen on which the route | root of 1st embodiment was displayed. It is a 2nd figure which shows the example of the screen where the route of 1st embodiment was displayed. It is a flowchart explaining the process by a route search part. It is a figure which shows an example of the route output system of 2nd embodiment. It is a figure which shows an example of a display form database. It is a figure explaining the functional structure of the server of 2nd embodiment. It is a flowchart explaining the process of the display of the route of 2nd embodiment. It is a figure which shows the example of the screen on which the route of 2nd embodiment was displayed. It is a figure which shows an example of the route output system of 3rd embodiment.

(First embodiment)
The first embodiment will be described below with reference to the drawings. FIG. 1 is a diagram illustrating an example of a route output system according to the first embodiment.

  The route output system 100 of this embodiment includes a server 200 and an electronic device 300.

  The electronic device 300 according to the present embodiment is, for example, an in-vehicle car navigation device mounted on the vehicle M, and requests the server 200 to search for a route indicating a route from the departure point to the destination point.

  When receiving the search request, the server 200 according to the present embodiment outputs a route passing through a road on which a vehicle equivalent to or more than the vehicle M has traveled among the routes acquired as a search result, and displays the route on the electronic device 300. Let

  As described above, in this embodiment, as a result of the route search request, a route with a track record in which a vehicle having a size equal to or larger than the vehicle on which the electronic device 300 is mounted in the past is output. Therefore, according to the present embodiment, for example, even when the vehicle M is a large lorry, it is possible to avoid a situation in which the vehicle M cannot actually pass through the displayed route.

  The electronic device 300 according to the present embodiment acquires its own position information by, for example, GPS (Global Positioning System), and transmits it to the server 200 together with date / time information indicating the date / time when the position information is acquired. Note that the position information of this embodiment includes latitude and longitude.

  The server 200 of the present embodiment includes a travel data database 210, a vehicle database 220, a travel performance database 230, and a route database 240. Further, the server 200 of this embodiment includes a route output processing unit 250. Details of each database of the server 200 and the route output processing unit 250 will be described later.

  The travel data database 210 stores travel data indicating a travel history for each vehicle. The vehicle database 220 stores vehicle data indicating the vehicle type for each vehicle. The travel record database 230 stores travel record data indicating whether or not the vehicle is traveling on the road. The route database 240 stores a route (travel route) on which the vehicle traveled for each vehicle.

  When receiving the position information and the date / time information from the electronic device 300, the server 200 according to the present embodiment stores the position information and the date / time information in the travel data database 210 as a part of the travel data of the vehicle on which the electronic device 300 is mounted. Store. Further, the server 200 according to the present embodiment updates travel record data corresponding to the road on which the vehicle M traveled in the travel record database 230 based on the position information.

  The server 200 of the present embodiment receives a search request for a route to the destination point from the electronic device 300, searches a road map database provided in an external server or the like, and extracts the route to the destination point. Then, the server 200 collates the extracted route with the travel record database 230, and outputs a route indicated by a road section having a travel history as a recommended route. Therefore, the server 200 of this embodiment functions as a route output device that outputs a route (route) for guiding the vehicle to the destination point.

  In the example of FIG. 1, there is one electronic device 300, but there may be a plurality of vehicles on which the electronic device 300 is mounted. The electronic device 300 of the present embodiment is not limited to an in-car car navigation device. The electronic device 300 according to the present embodiment only needs to have a function of acquiring position information using GPS, and may be, for example, a smartphone or a tablet-type terminal.

  Next, the hardware configuration of the server 200 of this embodiment will be described with reference to FIG. FIG. 2 is a diagram illustrating an example of a hardware configuration of the server.

  The server 200 according to this embodiment includes an input device 21, an output device 22, a drive device 23, an auxiliary storage device 24, a memory device 25, an arithmetic processing device 26, and an interface device 27 that are connected to each other via a bus B.

  The input device 21 includes a keyboard and a mouse, and is used for inputting various signals. The output device 22 includes a display device and the like, and is used to display various windows and data. The interface device 27 includes a modem, a LAN card, and the like, and is used for connecting to a network.

  The route output program is at least a part of various programs that control the server 200. The route output program is provided, for example, by distributing the recording medium 28 or downloading from the network. The recording medium 28 on which the route output program is recorded is information such as a CD-ROM, a flexible disk, a magneto-optical disk, etc., a recording medium for recording information optically, electrically or magnetically, a ROM, a flash memory, etc. Various types of recording media, such as a semiconductor memory that electrically records data, can be used.

  The root output program is installed in the auxiliary storage device 24 from the recording medium 28 via the drive device 23 when the recording medium 28 recording the root output program is set in the drive device 23. The route output program downloaded from the network is installed in the auxiliary storage device 24 via the interface device 27.

  The auxiliary storage device 24 stores the installed route output program and stores necessary files, data, and the like. The memory device 25 reads and stores the route output program from the auxiliary storage device 24 when the computer is activated. The arithmetic processing unit 26 implements various processes as described later according to the route output program stored in the memory device 25.

  Next, each database included in the server 200 of this embodiment will be described with reference to FIGS.

  FIG. 3 is a diagram illustrating an example of a travel data database. The travel data database 210 of the present embodiment is provided for each vehicle ID described later.

  The travel data database 210 of the present embodiment includes acquisition date / time, latitude, longitude, post-adsorption latitude, post-adsorption longitude, link number, link distance, required time, and speed as information items.

  In the travel data database 210 of this embodiment, the item “acquisition time” is associated with other items. In the following description, information including the value of the item “acquisition time”, the value of the item “acquisition time”, and the values of other items is referred to as travel data.

  The value of the item “acquisition time” indicates the date and time when the electronic device 300 acquired the position information (latitude and longitude) of the own device. That is, in the present embodiment, the date / time information received from the electronic device 300 is stored as the value of the item “acquisition time”. The values of the item “latitude” and the item “longitude” are the latitude and longitude values of the own device acquired by the electronic device 300.

  The value of the item “latitude after adsorption” is a value obtained by correcting the value of the item “latitude”. The value of the item “longitude after adsorption” is a value obtained by correcting the value of the item “longitude”. Specifically, the value of the item “latitude after adsorption” and the value of the item “longitude after adsorption” are the position information (latitude and longitude) so that the vehicle indicated by the position information is located on the road on which the vehicle travels. Is a corrected value.

  The value of the item “link number” is a value that identifies a road section including the value of the item “latitude after adsorption” and the value of the item “longitude after adsorption”. Details of the road section will be described later.

  The value of the item “link distance” is a value indicating the distance of the road section specified by the value of the item “link number”. The value of the item “required time” indicates the time required for the vehicle to travel the link distance at a speed described later. The value of the item “speed” indicates the speed of the vehicle. For example, when the position information is received, the speed of the vehicle may be calculated based on the position of the vehicle when referring to the position information received in the past and the elapsed time from that time.

  Here, the road section of this embodiment will be described. The server 200 of the present embodiment refers to, for example, a road map database provided in an external server or the like, and generates travel data and searches for a route. In the road map database of this embodiment, the road network is expressed by a combination of nodes and links. The node of the present embodiment indicates, for example, an intersection or other nodal point on the road network expression. The link in this embodiment indicates a road section between nodes. The link numbers in the present embodiment are numbers created by arranging the numbers given to the nodes at both ends of the link from the smallest.

  FIG. 4 is a diagram illustrating an example of a vehicle database. The vehicle database 220 of the present embodiment includes a vehicle ID, a vehicle type, and a total vehicle weight as information items. In the vehicle database 220 of the present embodiment, the item “vehicle ID” is associated with other items. In the following description, information including the value of the item “vehicle ID” and the values of other items is referred to as vehicle data.

  The value of the item “vehicle ID” in the present embodiment is a value assigned to each vehicle. The value of the item “vehicle ID” in this embodiment may be assigned to the vehicle in advance, and in this case, even if the value of the vehicle ID of the vehicle on which the device is mounted is set in the electronic device 300. good. The value of the item “vehicle ID” may be given when the vehicle data is stored in the vehicle database 220.

  The value of the item “vehicle type” indicates the type of vehicle. The value of the item “total vehicle weight” indicates the sum of the vehicle weight and the maximum load capacity of the vehicle.

  In addition, although the vehicle database 220 of this embodiment shall have the three items mentioned above, it is not limited to this. The vehicle database 220 may have items other than the three items described above. Specifically, for example, it may be included as an item indicating a passenger capacity, an exhaust amount, or the like.

  In addition, the vehicle database 220 of this embodiment may be provided from a business owner who owns a large lorry, for example. Moreover, the vehicle database 220 of this embodiment may store vehicle data input by the electronic device 300.

  FIG. 5 is a diagram illustrating an example of a travel record database. The travel performance database 230 of the present embodiment is generated based on travel data collected in a predetermined period for each predetermined period. For example, the travel performance database 230 shown in FIG. 5 is generated using travel data collected during the period from 1:00 on 2014/11/19 to 23/59 on 2014/11/19.

  The travel record database 230 of the present embodiment includes a link number, a large truck 1, a large truck 2, and a large truck 3 as information items. In the travel record database 230, the item “link number” is associated with other items. In the following description, information including the value of the item “link number” and the values of other items associated with the value of the item “link number” is referred to as travel record data.

  The values of the items “Large Lorry Car 1”, “Large Lorry Car 2”, and “Large Lorry Car 3” in the present embodiment indicate values indicating whether or not there is a traveling history of the type of the corresponding vehicle. In FIG. 5, the values indicating the presence / absence of the travel history are indicated as “present” and “absent”, but the values indicating the presence / absence of the travel history are values indicating the number of times the corresponding type of vehicle has traveled, for example. May be. In the following description, the presence of a travel history is expressed as having a travel record, and the absence of a travel history is expressed as having no travel record.

  Moreover, although the driving performance database 230 of this embodiment has three items “large lorry 1”, “large lorry 2”, and “large lorry 3” indicating the type of vehicle, It is not limited. The travel record database 230 can add an arbitrary vehicle type to the item, and store the presence / absence of the travel record of the corresponding vehicle for each link number.

  FIG. 6 is a diagram illustrating an example of the route database. The route database 240 of this embodiment has vehicle ID, vehicle type, departure point, destination point, route, and travel date as information items. In the following description, information including the value of the item “vehicle ID” and the values of other items associated with the item “vehicle ID” in the route database 240 is referred to as route data.

  The value of the item “departure point” indicates the departure point of the vehicle on which the electronic device 300 is mounted. The value of the item “departure point” indicates the destination point of the vehicle on which the electronic device 300 is mounted. The values of the items “departure point” and “destination point” are values input from the electronic device 300.

  The value of the item “route” indicates a route (travel route) that the vehicle specified by the vehicle ID travels from the departure point to the destination point. In the present embodiment, the value of the item “route” is indicated by a link number. For example, in FIG. 6, the vehicle with the vehicle ID “1” has the road sections corresponding to the link numbers 100, 101, and 103 before arriving at the XX factory that is the destination point from the XX company that is the departure point. You can see that you have run.

  The value of the item “traveling time” indicates the time traveled from the departure point to the destination point of the vehicle specified by the vehicle ID. For example, in FIG. 6, it can be seen that the vehicle with the vehicle ID “1” traveled from 0/45 to 0/55 on 2014/11/19. That is, in FIG. 6, the vehicle with the vehicle ID “1” departs from the XX company at 0:45 on 2014/11/19 and travels on the road sections of the link numbers 100, 101, and 103. / 19: It can be seen that we arrived at the factory at 0:55.

  Next, the function of the server 200 of this embodiment will be described with reference to FIG. FIG. 7 is a diagram illustrating the functional configuration of the server according to the first embodiment.

  The server 200 of this embodiment includes a position information acquisition unit 231, a travel data generation processing unit 232, a travel performance generation processing unit 233, a route output processing unit 250, a display setting reception unit 260, a display control unit 270, and a route storage unit 280. Have.

  The position information acquisition unit 231 acquires position information from the electronic device 300 and date / time information indicating the date / time when the position information was acquired. The position information acquisition unit 231 acquires the vehicle ID of the vehicle on which the electronic device 300 is mounted, along with the position information and date / time information.

  The travel data generation processing unit 232 stores the position information and date / time information in the travel data database 210 of the corresponding vehicle ID. Further, the travel data generation processing unit 232 generates travel data based on the acquired position information.

  Hereinafter, generation of travel data will be described. The travel data generation processing unit 232 of the present embodiment refers to the road map database and the like, calculates the post-adsorption latitude and the post-adsorption longitude from the latitude and longitude included in the position information, and includes the post-adsorption latitude and the post-adsorption longitude. Get the link number of the road section. Further, the travel data generation processing unit 232 acquires the distance (link distance) of the road section indicated by the link number from the road map database or the like, and the speed of the vehicle and when the vehicle travels on the road section corresponding to the link number. The required time is calculated.

  Then, the travel data generation processing unit 232 associates position information (latitude, longitude), post-adsorption latitude, post-adsorption longitude, link number, link distance, required time, and speed with the date and time information as travel data. Store in database 210.

  The travel performance generation processing unit 233 includes a vehicle type determination unit 234 and a performance association unit 235. The travel performance generation processing unit 233 of the present embodiment refers to the travel data database 210 and the vehicle database 220 and generates travel performance data. Details of the processing of the running record generation processing unit 233 will be described later.

  The route output processing unit 250 of the present embodiment refers to the travel record database 230, and in the route from the departure point of the electronic device 300 to the destination point, the same vehicle type as the vehicle on which the electronic device 300 is mounted or the electronic device 300 A route with a running record of a vehicle larger than the installed vehicle is output.

  The route output processing unit 250 according to the present embodiment includes an input receiving unit 251, a route searching unit 252, a performance presence / absence determining unit 253, a determination result holding unit 254, a route specifying unit 255, and a route output unit 256.

  The input receiving unit 251 receives the departure point and the destination point input in the electronic device 300. The electronic device 300 may use the departure point as the current location of the electronic device 300.

  The route search unit 252 searches and extracts a route from the departure point to the destination point with reference to the road map database.

  For each route extracted by the route search unit 252, the result presence / absence determination unit 253 includes the same vehicle type or electronic device 300 as the vehicle in which the electronic device 300 is mounted in each of the road sections included in each route. It is determined whether there is a running record of a vehicle larger than the vehicle.

  The determination result holding unit 254 holds the determination by the result presence / absence determination unit 253. The route specifying unit 255 specifies a route to be output as a recommended route according to the determination result held in the determination result holding unit 254.

  In the present embodiment, a condition for specifying the recommended route may be set by the user of the electronic device 300. Specifically, for example, the route with the shortest distance may be set as the recommended route, or the route with the latest period corresponding to the referenced travel record database 230 is set as the recommended route. Also good. Further, the condition for specifying the recommended route may be set, for example, as having a track record in a road section corresponding to all link numbers included in the route.

  The route output unit 256 outputs the route specified by the route specifying unit 255. The route output unit 256 also holds route information that associates the determination result held by the determination result holding unit 254 with the identified route. Details of the route information will be described later.

  The display setting reception unit 260 receives the display setting of the output route. The display setting is, for example, a setting for displaying a route other than the recommended route or a setting for displaying a list of extracted routes.

  The display control unit 270 generates screen data for displaying a screen corresponding to the setting received by the display setting reception unit 260 and causes the electronic device 300 to display the screen data.

  The route storage unit 280 stores the route traveled by the vehicle on which the electronic device 300 is mounted in the route database 240 in association with the travel date and time of the vehicle. For example, when the vehicle travels along the recommended route displayed on the electronic device 300, the route storage unit 280 of the present embodiment stores the travel date and time of the vehicle and the recommended route in the route database 240 in association with each other. Also good.

  Next, the operation of the server 200 of this embodiment will be described. First, the process of updating the travel record database 230 will be described with reference to FIG.

  FIG. 8 is a flowchart illustrating the update of the travel performance database of the server according to the first embodiment. The process of FIG. 8 is executed every time position information and date / time information are acquired from the electronic device 300.

  The server 200 according to the present embodiment acquires the vehicle ID, position information, and date / time information of the vehicle on which the electronic device 300 is mounted by using the position information acquisition unit 231 (step S801). Subsequently, the server 200 generates travel data by the travel data generation processing unit 232 and stores the travel data in the travel data database 210 corresponding to the vehicle ID (step S802). The generation of the travel data by the travel data generation processing unit 232 is as described above.

  Subsequently, the server 200 refers to the vehicle database 220 by the vehicle type determination unit 234 of the travel record generation processing unit 233, and identifies the vehicle type corresponding to the vehicle ID (step S803). Subsequently, the travel performance generation processing unit 233 acquires the link number included in the travel data generated in step S802 by the performance association unit 235 (step S804).

  Subsequently, the travel record generation processing unit 233 refers to the travel record database 230 by the record association unit 234 and determines whether there is a link number that matches the acquired link number (step S805). In step S805, if the corresponding link number does not exist, the link number acquired in step S804 is added to the travel record database 230, and the process proceeds to step S807 described later (step S806).

  When there is a corresponding link number in step S805, the performance association unit 235 determines whether or not the vehicle type specified in step S803 is associated with the link number in the travel performance database 230 (step S807).

  If the vehicle type and the link number are not associated with each other in step S807, the record association unit 235 associates the link number with the vehicle type in the travel record database 230 (step S808), and proceeds to step S809 described later. .

  In step S807, when the vehicle type and the link number are associated with each other, the record association unit 235 updates the value of the vehicle type corresponding to the link number in the travel record database 230 to “present” (step S809), and processing Exit. That is, the performance association unit 235 determines that there is a travel performance of the vehicle type of the road section corresponding to the link number.

  In the present embodiment, the traveling performance database 230 is updated (generated) by the above processing.

  Next, route output by the route output processing unit 250 of the present embodiment will be described with reference to FIGS. 9 and 10.

  FIG. 9 is a first flowchart for explaining the processing of the route output processing unit of the first embodiment.

  The route output processing unit 250 of this embodiment determines whether or not the input reception unit 251 has received a route search request from the electronic device 300 (step S901). In addition, the input reception part 251 of this embodiment receives the input of vehicle ID, a departure point, and a destination point with a search request. If the search request is not accepted in step S901, the route output processing unit 250 waits until the search request is accepted.

  When a route search request is received in step S901, the route search unit 252 searches a route indicating a route from the departure point to the destination point by referring to a road map database or the like held by an external server or the like (step S902). ).

  Subsequently, the route output processing unit 250 sets the number of routes obtained as a search result of the route search unit 252 by the record presence / absence determination unit 253 as a variable N (step S903). Subsequently, the performance presence / absence determination unit 253 acquires the shortest distance route having the shortest distance from the routes obtained as a search result, and sets the variable N = 1 (step S904).

  Subsequently, the record presence / absence determination unit 253 extracts a link number for each road section forming the acquired route (step S905). The link number for each road section is acquired from a road map database or the like referred to when performing a route search.

  Subsequently, the performance presence / absence determination unit 253 refers to the travel performance database 230 and determines whether the travel performance of the vehicle type corresponding to the vehicle ID is “present” for all the extracted link numbers ( Step S906).

  In addition, the performance presence / absence determination unit 253 may refer to the travel performance database 230 having the latest period of acquiring travel performance data when executing the process of step S906. Further, the performance presence / absence determination unit 253 may determine whether or not the travel performance of a vehicle type of a vehicle larger than the vehicle corresponding to the vehicle ID is “present” in the process of step S906. Further, “a vehicle larger than the vehicle corresponding to the vehicle ID” in the present embodiment refers to, for example, the vehicle database 220 in which the total vehicle weight is greater than the total vehicle weight of the vehicle corresponding to the vehicle ID. good.

  If it is determined in step S906 that all link numbers have a running record, the process proceeds to step S909 described later.

  In step S906, when there is no traveling record for all the link numbers, the record presence / absence determining unit 253 extracts all link numbers having no traveling record (step S907).

  Subsequently, the route output processing unit 250 searches the route when the route search unit 252 uses the start point of the road section corresponding to the extracted link number as the start point and the end point as the destination point (step S908). Details of the processing in step S908 will be described later.

  Subsequently, the route output processing unit 250 determines whether or not the processing from step S905 to step S908 has been executed for all routes obtained as a search result by the route search unit 252 (step S909).

  If the process is not executed in step S909, the route output processing unit 250 acquires the next route from the route extracted in step S902, sets the value of the variable N to N + 1 (step S910), and returns to step S905. .

  When the process is executed in step S909, the route output processing unit 250 specifies the route to be output by the route specifying unit 255 (step S911). For example, the route specifying unit 255 may specify a route that satisfies the conditions of the route to be output as the recommended route. This condition may be set by the user of the electronic device 300 before the route search request is input in the electronic device 300, for example.

  Subsequently, the route output processing unit 250 outputs the route specified by the route output unit 256 (step S912), and ends the process. In the present embodiment, the route output by the route output unit 256 is held in a predetermined storage area of the auxiliary storage device 24 or the memory device 25 of the server 200 as route information to be described later.

  Next, the process of step S908 will be described with reference to FIG. FIG. 10 is a second flowchart for explaining the processing of the route output processing unit of the first embodiment. The process shown in FIG. 10 is a process of searching for a road section with a running record from the start point to the end point of a road section with no running record.

  The route output processing unit 250 of this embodiment sets the number of link numbers extracted in step S907 as a variable n, and sets n = 1 (step S1001). Subsequently, the route output processing unit 250 acquires a link number indicating a road section closest to the departure point among the extracted link numbers (step S1002).

  Subsequently, the route output processing unit 250 searches the route search unit 252 for a route from the start point to the end point of the road section corresponding to the acquired link number (step S1003). Subsequently, the route output processing unit 250 collates the link number indicating the road section included in the route acquired as the search result with the travel record database 230 by the record presence / absence determination unit 253 (step S1004).

  Subsequently, the performance presence / absence determination unit 253 determines whether or not all the link numbers indicating the road sections included in the route have a travel performance of the same vehicle type as the vehicle type on which the electronic device 300 is mounted (step S1005). ).

  In step S1005, if all road sections have a running record, the route output processing unit 250 replaces the road section corresponding to the extracted link number with the route obtained by the search in step S1003 (step S1006), which will be described later. The process proceeds to step S1010.

  In step S1005, when all road sections have no travel record, that is, when a road section with no travel record is included, whether or not the road sections extracted in step S907 in FIG. 9 are divided into a predetermined number or more is determined. Determination is made (step S1007). Note that the predetermined number is set in advance.

  In step S1007, when it is not divided into the predetermined number or more, the route output processing unit 250 extracts the link number of the road section determined not to have a driving record by the track record determination unit 253 in step S1004 (step S1008). ), The process returns to step S1003.

  In step S1007, if the route output processing unit 250 has been divided into a predetermined number or more, the route output processing unit 250 has a route with a running record in the route from the start point to the end point of the road section that is the target of the route search in step S1003. Judge that it is not. Then, the route output processing unit 250 retains information indicating that the road section subjected to the route search in step S1003 has no running record (step S1009).

  Subsequently, the route output processing unit 250 determines whether or not the processing after step S1003 has been performed for n link numbers (step S1010).

  If the process is not performed in step S1010, the route output processing unit 250 obtains a link number indicating the next road section closest to the departure point, sets the value of the variable n to n + 1 (step S1011), and returns to step S1003. .

  When the process is performed in step S1010, the route output processing unit 250 proceeds to step S909 in FIG.

  Below, with reference to FIG.11 and FIG.12, the process of the route output process part 250 of this embodiment is further demonstrated.

  FIG. 11 is a first diagram illustrating the processing of the route output processing unit. FIG. 11A is a diagram illustrating an example of a route acquired as a result of the route search when the departure point set in the electronic device 300 is the point P1 and the destination point is the point P4. FIG. 11B is a diagram showing the results of a route search that connects the start point and end point of a road section that has no travel record in the route shown in FIG. FIG. 11C is a diagram illustrating an example of an output route.

  FIG. 11 shows a case where the road from the departure point to the destination point can be connected by a road section with a track record.

  As shown in FIG. 11A, the route 11 extracted as a search result by the route search unit 252 is indicated by road sections corresponding to link numbers 200, 201, and 202.

  The road section indicated by the link number 200 has a point P1 as a start point and a point P2 as an end point. The road section indicated by the link number 201 has a point P2 as a start point and a point P3 as an end point. The road section indicated by the link number 202 has a point P3 as a start point and a point P4 as an end point.

  In FIG. 11, consider a case where the road section indicated by the link number 201 does not have a running record of the same vehicle type as the vehicle ID “1” or a vehicle type larger than the vehicle with the vehicle ID “1”.

  At this time, the route output processing unit 250 extracts the link number 201 as a link number with no travel record.

  Then, the route output processing unit 250 causes the route search unit 252 to search for a route from the point P2 to the point P3. At this time, the route search unit 252 excludes the route indicated by the link number 201 from the search result.

  In FIG. 11, as shown in FIG. 11B, the routes indicated by the link numbers 211 and 212 are extracted as the route connecting the point P2 to the point P3. The link number 211 is a road section starting from the point P2 and ending at the point P5. The link number 212 is a road section starting from the point P5 and ending at the point P3. Here, it is assumed that the link numbers 211 and 212 have a running record of the same vehicle type as the vehicle ID “1” or a vehicle type of a vehicle larger than the vehicle with the vehicle ID “1”.

  At this time, the route output processing unit 250 replaces the link number 201 of the route 11 with the link number 211 and the link number 212. In other words, as shown in FIG. 11C, the route output processing unit 250 changes the road section connecting the point P2 to the point P3 from the road section indicated by the link number 201 to the road section indicated by the link number 211, Replace with the road section indicated by the link number 212.

  Then, the route output processing unit 250 outputs the route 11A shown in FIG.

  At this time, the route output processing unit 250 stores, as route information, a link number included in the route 11A and a value indicating that all link numbers have a running record in association with each other. The route information is referred to in a route display process to be described later.

  As described above, in the present embodiment, a route search request is received, and a route having a running record of a vehicle having a size equal to or larger than that of the vehicle on which the electronic device 300 that has made the route search request is mounted is output. . Therefore, according to the present embodiment, it is possible to avoid the situation of encountering a road that cannot actually pass when traveling according to the output route.

  FIG. 12 is a second diagram for explaining the processing of the route output processing unit. FIG. 12A shows a route similar to the route shown in FIG. FIG. 12B is a diagram showing a route search result that connects the start point and the end point of a road section that has no running record in the route shown in FIG. FIG. 12C is a diagram illustrating an example of an output route.

  FIG. 12 shows a case where the route connecting from the departure point to the destination point includes a road section with no running record. FIG. 12 shows a case where the predetermined number that can be divided is set to 3 for one road section acquired as a result of route search from the departure point to the destination point.

  In FIG. 12, a case is considered where the road section indicated by the link number 201 does not have a running record of the same vehicle type as the vehicle ID “1” or a vehicle type larger than the vehicle with the vehicle ID “1”.

  At this time, the route output processing unit 250 extracts the link number 201 as a link number with no travel record. Then, the route output processing unit 250 causes the route search unit 252 to search for a route from the point P2 to the point P3. At this time, the route search unit 252 excludes the route indicated by the link number 201 from the search result.

  In FIG. 12, it is assumed that the routes indicated by the link numbers 221 and 223 are extracted as the route connecting the point P2 and the point P3 as shown in FIG. At this time, the road section indicated by the link number 221 has a running record of the same vehicle type as the vehicle ID “1” or the vehicle type of the vehicle larger than the vehicle of the vehicle ID “1”. Further, the road section indicated by the link number 223 has no running record of the same vehicle type as the vehicle ID “1” or the vehicle type of the vehicle larger than the vehicle ID “1”.

  At this time, the road section indicated by the link number 201 is in a state of being divided into two, a link number 221 and a link number 223.

  Therefore, the route output processing unit 250 extracts the link number 223 and searches for a route connecting the point P5 that is the start point of the road section indicated by the link number 223 and the point P3 that is the end point. The route extracted here is a route including the link number 222 and the link number 224.

  At this time, the road section indicated by the link number 224 has no running record of the same vehicle type as the vehicle ID “1” or the vehicle type of the vehicle larger than the vehicle of the vehicle ID “1”. At this time, the road section indicated by the link number 201 is divided into three road sections indicated by the link numbers 221, 222, and 224.

  Therefore, as shown in FIG. 12C, the route output processing unit 250 uses the route specifying unit 255 to specify the route that outputs the route 11B including the road section indicated by the link number 224, and the route output unit 256 The route 11B is output. The route 11B includes link numbers 200, 221, 222, 224, and 202.

  At this time, the route output processing unit 250 stores that there is no running record in the road section indicated by the link number 224. Specifically, the route output processing unit 250 causes the determination result holding unit 254 to hold the link number 224 included in the route 11B as a route information that associates a value indicating that there is no running record. The route information is referred to in a route display process to be described later.

  In the present embodiment, when searching for a route that connects the starting point and the ending point of the road section when the driving record is obtained, it is determined that there is no route having a driving record when the road section is divided into a predetermined number or more. However, it is not limited to this. In this embodiment, for example, when searching for a route connecting the start point and end point of a road section, even if the required time from the start point to the end point is a predetermined time or more, if a route with a running record is not found, It may be determined that there is no route with a running record.

  The route information will be described below with reference to FIG. FIG. 13 is a diagram illustrating an example of route information.

  The route output processing unit 250 of this embodiment holds the route output by the route output unit 256 as route information 130. The route information 130 includes, as information items, a route ID, a link number, a travel record flag, and a travel record acquisition time. In the route information 130, the item “route ID” is associated with other items.

  The value of the item “route ID” is a value given to the identified route by the route identifying unit 255 when the route identifying unit 255 identifies the route, for example. The value of the item “link number” is a link number included in the route indicated by the corresponding route ID.

  The value of the item “travel record flag” is a value indicating whether or not there is a travel record in the road section indicated by the corresponding link number. More specifically, the value of the item “travel performance flag” is a value indicating a determination result by the performance presence / absence determination unit 253. In the example of FIG. 13, when the value of the item “travel record flag” is 1, it indicates that there is a travel record, and when the value of the item “travel record flag” is 0, it indicates that there is no travel record.

  The item “travel performance acquisition time” indicates a period associated with the travel performance database 230 referred to when the travel performance flag is assigned.

  In FIG. 13, the route ID of the route 11A shown in FIG. 11C is “11”, and the route ID of the route 11B shown in FIG. 12C is “12”. In FIG. 13, the link numbers included in the route 11 </ b> A of the route ID “11” are 200, 211, 212, and 202, and in the travel record database 230 in which the travel record data acquired on 2014/11/19 is stored, It can be seen that there is a track record in the road section corresponding to the link number. In FIG. 13, the link numbers included in the route 11B of the route ID “12” are 200, 221, 222, 224, 202, and the travel record database storing the travel record data acquired on 2014/11/19. In 230, it can be seen that there is no running record only in the road section corresponding to the link number 224.

  Next, display of a route by the server 200 of this embodiment will be described. FIG. 14 is a flowchart for explaining a route display process according to the first embodiment. In this embodiment, the route output processing unit 250 outputs a route and the route display processing shown in FIG. 14 are separated. However, the route output processing and the route display processing are different. May be performed continuously.

  The server 200 of this embodiment determines whether or not a display instruction has been received by the display control unit 270 (step S1401). In step S1301, when a display instruction is not received, the display control unit 270 waits until a display instruction is received.

  When receiving a display instruction in step S1301, the display control unit 270 reads the route information held by the route output processing unit 250 (step S1402).

  Subsequently, the display control unit 270 determines whether or not the route information includes a route including a road section having no travel record (step S1403).

  If there is no corresponding route in step S1403, the display control unit 270 proceeds to step S1408 described later.

  If there is a corresponding route in step S1403, the display control unit 270 determines whether or not it is set to display a route including a road section having no travel record (step S1404). Specifically, the display control unit 270 determines whether or not the display setting reception unit 260 has received a setting for displaying a route including a road section having no running record.

If the corresponding setting is not made in step S1404, the display control unit 270 proceeds to step S1408 described later.
If the corresponding setting is made in step S1404, the display control unit 270 generates and outputs screen data for displaying a list of all routes indicated by the route information (step S1405).

  Subsequently, the display control unit 270 determines whether or not the selection of a route including a road section having no travel record has been received in the list (step S1406).

  In step S1406, when the selection of the corresponding route is received, the display control unit 270 generates and outputs screen data for displaying the route by distinguishing the road section having no travel record from the road section having the travel record. . The display control unit 270 includes a message notifying that a road section having no running record is included in the screen data for displaying the route (step S1407).

  If there is no corresponding route in step S1403, or if no corresponding setting is made in step S1408, the display control unit 270 refers to the route information and displays a list of routes that have a track record of all road sections. The screen data to be generated is generated and output (step S1408). Subsequently, the display control unit 270 displays the route selected in the list (step S1409).

  Next, an example of a screen displayed based on the screen data generated by the display control unit 270 will be described with reference to FIGS. 15 to 17. FIG. 15 is a diagram illustrating an example of a screen on which a list of routes is displayed.

  A screen 151 illustrated in FIG. 15 is displayed on the electronic device 300, for example. The screen 151 shows a case where there are three routes output by the route output processing unit 250. Further, the screen 151 shows an example in which a list of all routes indicated by the route information is displayed, and the list includes routes having road sections with no running record.

  At this time, on the screen 151, a list 152 of routes having a track record in all road sections and a list 153 of routes including a road segment having no track records may be displayed separately.

  Further, in the present embodiment, for example, when it is set to display only a route having a track record in all road sections, only the list 152 may be displayed on the list screen.

  For example, when a route included in the list 152 or 151 is selected on the screen 151, the server 200 causes the display control unit 270 to generate screen data for displaying the selected route and display the data on the electronic device 300.

  Further, the screen 151 displays an option 154 for displaying all routes on the same screen as options for displaying the route. When the option 154 is selected on the screen 151, the server 200 causes the display control unit 270 to generate screen data for simultaneously displaying the route 1 to the route 3 and display the data on the electronic device 300.

  In the above description, the presence / absence of the driving record is given as an example of the item set for the display of the route list. However, the item set for the display of the route list may be other. Specifically, the display of the list of routes may be set to display the list of routes in ascending order of the time required from the departure point to the destination point, for example. In this case, route 3 shown on the screen 151 is displayed at the beginning of the list, and route 2 and route 1 are displayed in this order.

  Further, the display of the list of routes may be set to display in order from the route with the latest travel performance data acquisition period in the travel performance database 230 referred to when the route is acquired.

  FIG. 16 is a first diagram illustrating an example of a screen on which a route according to the first embodiment is displayed. A screen 161 shown in FIG. 16 shows a case where route 1 is selected in the list 151 of routes that have a track record in all road sections on the screen 151. In this case, on the screen 161, a line 162 indicating the route 1 is displayed on the map.

  FIG. 17 is a second diagram illustrating an example of a screen on which a route according to the first embodiment is displayed. A screen 171 illustrated in FIG. 17 illustrates a case where the route 3 is selected in the route list 153 including a road section having no travel record on the screen 151. In this case, a line indicating the route 3 is displayed on the map on the screen 171.

  At this time, the display control unit 270 of the server 200 may display the line type indicating a road section with a running record different from the line type indicating a road section with no running record. In the example of FIG. 17, the thickness of the line 173 indicating the road section having no travel record is made thinner than the thickness of the line 172 indicating the road section having the travel record. For example, the display color of the lines 172 and 173 may be changed, or the line 173 may be a broken line. In the present embodiment, it is only necessary to display the line 173 indicating a road section having no travel record and the line 172 indicating a road section having a travel record.

  Further, on the screen 171, a message 174 indicating that a road section having no running record is included is displayed.

  In the present embodiment, in this way, by indicating that the displayed route includes a road section having no driving record, the user of the electronic device 300 is alerted about the road section having no driving record. can do.

  In the present embodiment, for example, when a route is selected from a list of routes and the vehicle actually travels along the selected route, the traveled route and the travel time of the vehicle are associated with each other and stored in the route database 240.

  Therefore, the server 200 of this embodiment may extract a route output by the route output processing unit 250 from the routes stored in the route database 240.

  The route output using the route database 240 will be described below with reference to FIG. FIG. 18 is a flowchart for explaining processing by the route search unit.

  The route output processing unit 250 of the present embodiment determines whether or not the input reception unit 251 has received a route search request (step S1801). If the search request is not accepted in step S1801, the route output processing unit 250 stands by.

  When the search request is received in step S1801, the route output processing unit 250 refers to the vehicle database 220 and identifies the vehicle type corresponding to the vehicle ID received together with the search request (step S1802).

  Subsequently, the route output processing unit 250 refers to the route database 240 by the route search unit 252, and the route of the vehicle of the same vehicle type as the vehicle type specified in step S1802 or the vehicle route larger than the vehicle of the vehicle type specified in step S1802 Is extracted (step S1803).

  Subsequently, the route output processing unit 250 determines whether there is a route including the input departure point and destination point among the extracted routes (step S1803).

  If there is no corresponding route in step S1803, the route output processing unit 250 proceeds to step S9002 in FIG.

  In step S1803, when the corresponding route exists, the route output processing unit 250 extracts the corresponding route by the route search unit 252, and outputs the route extracted by the route output unit 256 (step S1804).

  As described above, in this embodiment, it is possible to reduce the load of the route search process by referring to the route database 240 in which the route actually traveled by the vehicle is stored. Further, in the present embodiment, by extracting the search result route from the route on which the vehicle actually traveled, it is possible to output, for each vehicle, a route that has been proven to pass by vehicles of a scale larger than the vehicle. In addition, when extracting a route from the route database 240, a corresponding route may be extracted from routes within a predetermined period.

(Second embodiment)
The second embodiment will be described below with reference to the drawings. The second embodiment is different from the first embodiment in that the route display form based on the travel record is changed based on the time when the travel record database 230 is generated. Therefore, in the following description, only differences from the first embodiment will be described, and those having the same functional configuration as those of the first embodiment will be given the same reference numerals as those of the first embodiment. Description is omitted.

  FIG. 19 is a diagram illustrating an example of a route output system according to the second embodiment. The route output system 100A of this embodiment includes a server 200A.

  The server 200A includes a display form database 290 in addition to the databases included in the server 200 of the first embodiment. In addition, the server 200A of the present embodiment includes a route output processing unit 250A.

  FIG. 20 is a diagram illustrating an example of a display form database. The display form database 290 of this embodiment shows the display form of the route line on the screen when displaying the route.

  The item information includes the number of days elapsed, color, thickness, and line type. In the display form database 290 of the present embodiment, the item “Elapsed Days” is associated with other items.

  The value of the item “elapsed days” indicates the number of days that have elapsed since the vehicle traveled. The value of the item “color” indicates the color of the line to be displayed. The value of the item “thickness” is a value indicating the thickness of the line to be displayed. The value of the item “line type” indicates the type of line to be displayed. In the present embodiment, a line to be displayed is a line indicating a route on the screen.

  In FIG. 20, for example, when the route 1 is displayed as a route search result when the number of days elapsed since the vehicle traveled on the route 1 is 0, a thick blue line is displayed. In FIG. 20, for example, when the route 1 is displayed as a route search result when five days have passed since the vehicle traveled on the route 1, the route 1 is displayed as a solid yellow solid line. Is done.

  Note that “standard”, “thin”, and “thick” that are values indicating the thickness of the line in FIG. 20 may be associated with a value indicating the thickness of the line, for example.

  FIG. 21 is a diagram illustrating the functional configuration of the server according to the second embodiment. The server 200A of the present embodiment includes a display form determination unit 295 in addition to the units included in the server 200 of the first embodiment.

  The display form determination unit 295 of the present embodiment refers to the display form database 290 and determines the line display form when displaying the route. Specifically, the display form determination unit 295 specifies the time when the travel performance data referred to when the route output processing unit 250 acquires the route is generated, and the specified time and the display form database 290 are identified. Based on this, the display form of the line is determined.

  FIG. 22 is a flowchart illustrating a route display process according to the second embodiment. The processes in steps S2201 and S2202 in FIG. 22 are the same as the processes in steps S1401 and S1402 in FIG.

  Subsequent to step S2202, the display form determination unit 295 refers to the route information (see FIG. 13), and the time when the traveling performance data stored in the referenced traveling performance database 230 is acquired for each output route. Is identified (step S2203).

  Subsequently, the display form determination unit 295 refers to the display form database 290 and determines the display form of each route according to the time specified for each route in step S2203 (step S2204).

  Steps S2205 to S2211 are the same as the processes from step S1403 to step S1410 in FIG. 14 except that the route is displayed according to the display form determined in step S2204. Omitted.

  FIG. 23 is a diagram illustrating an example of a screen on which a route according to the second embodiment is displayed. A screen 221 shown in FIG. 23 is an example of a screen on which all routes included in the route information are displayed. More specifically, the screen 221 shows a case where the option 154 is selected on the screen 151 shown in FIG.

  In the screen 221, a line 222 is a line indicating the route 1, a line 223 is a line indicating the route 2, and a line 224 is a line indicating the route 3.

  In the present embodiment, route 1 is a route output with reference to the travel record database 230 generated the day before the route search request is made. In the present embodiment, the route 2 is a route that is output with reference to the travel record database 230 generated five days before the date when the route search request is made. In the present embodiment, the route 3 is a route that is output with reference to the travel record database 230 generated three weeks before the date of the route search request.

  Therefore, on the screen 221, the line 222 indicating the route 1 is displayed as a thick solid line, the line 222 indicating the route 2 is displayed as a solid line having a standard thickness, and the line 224 indicating the route 3 is displayed as a thin broken line. .

  As described above, according to the present embodiment, the display form of the route is changed according to the time when the travel performance database 230 referred to when the route is output is generated. Therefore, according to the present embodiment, for example, for the user of the electronic device 300, it is possible to display the route extracted based on the latest traveling performance in a state where it can be easily recognized.

(Third embodiment)
The third embodiment will be described below with reference to the drawings. The third embodiment is different from the first embodiment in that the vehicle database 220 is provided in an external server. Therefore, in the following description of the third embodiment, only differences from the first embodiment will be described, and those having the same functional configuration as those of the first embodiment are the same as those of the first embodiment. Reference numerals are assigned and description thereof is omitted.

  FIG. 24 is a diagram illustrating an example of a route output system according to the third embodiment. The route output system 100B of this embodiment includes a server 200B, an electronic device 300, and a server 400.

  The server 200B of this embodiment is different from the server 200 of the first embodiment in that the vehicle database 220 is not included.

  The server 400 of this embodiment is, for example, a management server that manages a vehicle on which the electronic device 300 is mounted, and the vehicle database 220 is provided in the server 400.

  The server 200B of this embodiment is the same as that of the first embodiment except that the server 200B accesses the server 400 when referring to the vehicle database 220.

  In the present embodiment, the vehicle database 220 is provided in the server 400, but the present invention is not limited to this. In the present embodiment, for example, the travel data database 210 may also be provided in the server 400.

In the disclosed technology, forms such as the following supplementary notes are conceivable.
(Appendix 1)
Accepts input of vehicle departure and destination points,
Referring to the storage unit that stores the travel route for each vehicle in association with the date and time, extracts the travel route of the vehicle whose size is greater than or equal to the size of its own vehicle or whose weight is greater than the weight of its own vehicle. ,
A route output program for causing a computer to execute a process of outputting a travel route including the departure point and the destination point among the extracted travel routes.
(Appendix 2)
Accept the input of the starting point and destination point of the vehicle, extract the route from the starting point to the destination point,
Reference is made to a storage unit that is generated using travel data indicating a travel history for each vehicle and stores travel performance data indicating the presence or absence of the travel history of the vehicle for each road section.
Among the extracted routes, a route that outputs a route having a running history of a vehicle whose size is equal to or larger than the size of the own vehicle or a vehicle whose weight is equal to or larger than the weight of the own vehicle is to cause the computer to execute processing. Output program.
(Appendix 3)
When there are a plurality of routes having a running history of a vehicle whose size is equal to or larger than the size of its own vehicle or a vehicle whose weight is equal to or greater than the weight of its own vehicle, the route with the shortest distance or the traveling of the route The route output program according to appendix 2, which causes the computer to execute a process for outputting a route having the shortest required time.
(Appendix 4)
The route with the travel history is
The route output program according to appendix 2 or 3, including a route including a road section having no travel history.
(Appendix 5)
Appendices 2 to 2 for outputting screen data for displaying a screen in which a display mode is different between a road section having the travel history and a road section having no travel history in a route including the road section having no travel history. The route output program according to any one of 4.
(Appendix 6)
In the road section without the travel history, extract a route different from the road section connecting the end point from the start point of the road section,
Appendix 5 that causes the computer to execute a process of replacing a road section without the travel history with all road sections included in the different route when all road sections included in the different route have a travel history. Root output program.
(Appendix 7)
When all road sections included in the other route include a road section without the travel history, and the number of all the road sections is a predetermined number or more,
The route output program according to appendix 6, which causes the computer to execute a process of determining that the output route includes a road section having no travel history.
(Appendix 8)
The travel performance data is generated for each period using the travel data collected within a predetermined period,
Specify the period in which the travel performance data referred to when acquiring the route to be output is generated,
The route output program according to appendix 7, wherein a display form of the route is determined according to the number of days elapsed from when the input of the departure point and the destination point is received.
(Appendix 9)
An input reception unit for receiving input of a departure point and a destination point of the vehicle;
Referring to the storage unit that stores the travel route for each vehicle in association with the date and time, extracts a travel route of a vehicle whose size is greater than or equal to the size of its own vehicle or whose weight is greater than or equal to the weight of its own vehicle. A route search part;
A route output device, comprising: a route output unit that outputs a travel route including the departure point and the destination point in the extracted travel route.
(Appendix 10)
A route search unit that accepts input of a departure point and a destination point of a vehicle and extracts a route from the departure point to the destination point;
Of the extracted routes, referring to a storage unit that is generated using the travel data indicating the travel history for each vehicle and stores travel performance data indicating the presence or absence of the travel history of the vehicle for each road section. A route output unit that outputs a route having a running history of a vehicle whose length is equal to or greater than the size of the own vehicle or a vehicle whose weight is equal to or greater than the weight of the own vehicle.
(Appendix 11)
A route output method by a computer, wherein the computer
Accepts input of vehicle departure and destination points,
Referring to the storage unit that stores the travel route for each vehicle in association with the date and time, extracts the travel route of the vehicle whose size is greater than or equal to the size of its own vehicle or whose weight is greater than the weight of its own vehicle. ,
A route output method for outputting a travel route including the departure point and the destination point among the extracted travel routes.
(Appendix 12)
A route output method by a computer, wherein the computer
Accept the input of the starting point and destination point of the vehicle, extract the route from the starting point to the destination point,
Reference is made to a storage unit that is generated using travel data indicating a travel history for each vehicle and stores travel performance data indicating the presence or absence of the travel history of the vehicle for each road section.
A route output method for outputting a route having a travel history of a vehicle having a size greater than or equal to the size of the own vehicle or a vehicle having a weight greater than or equal to the weight of the own vehicle among the extracted routes.

The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

100, 100A, 100B Route output system 200, 200A, 200B, 400 Server 210 Travel data database 220 Vehicle database 230 Travel performance database 231 Location information acquisition unit
232 Travel data generation unit 233 Travel result generation unit 240 Route database 250 Route output processing unit 251 Input reception unit 252 Route search unit 253 Result presence determination unit 254 Result determination holding unit 255 Route specification unit 256 Route output unit 270 Display control unit 280 Route Accumulation unit 290 Display format database 295 Display format determination unit 300 Electronic device

Claims (9)

Accepts input of vehicle departure and destination points,
Referring to the storage unit that stores the travel route for each vehicle in association with the date and time, extracts the travel route of the vehicle whose size is greater than or equal to the size of its own vehicle or whose weight is greater than the weight of its own vehicle. ,
A route output program for causing a computer to execute a process of outputting a travel route including the departure point and the destination point among the extracted travel routes. Accept the input of the starting point and destination point of the vehicle, extract the route from the starting point to the destination point,
Reference is made to a storage unit that is generated using travel data indicating a travel history for each vehicle and stores travel performance data indicating the presence or absence of the travel history of the vehicle for each road section.
Among the extracted routes, a route that outputs a route having a running history of a vehicle whose size is equal to or larger than the size of the own vehicle or a vehicle whose weight is equal to or larger than the weight of the own vehicle is to cause the computer to execute processing. Output program.   When there are a plurality of routes having a running history of a vehicle whose size is equal to or larger than the size of its own vehicle or a vehicle whose weight is equal to or greater than the weight of its own vehicle, the route with the shortest distance or the traveling of the route The route output program according to claim 2, wherein the computer executes a process of outputting a route having the shortest required time.   The route data including a road section having no travel history outputs screen data for displaying a screen in which a display form of a road section having the travel history and a road section having no travel history are different. Or the route output program of 3. The travel performance data is generated for each period using the travel data collected within a predetermined period,
Specify the period in which the travel performance data referred to when acquiring the route to be output is generated,
The route output program according to any one of claims 2 to 4, wherein a display form of the route is determined according to the number of days elapsed from the time when the input of the departure point and the destination point is received. An input reception unit for receiving input of a departure point and a destination point of the vehicle;
Referring to the storage unit that stores the travel route for each vehicle in association with the date and time, extracts a travel route of a vehicle whose size is greater than or equal to the size of its own vehicle or whose weight is greater than or equal to the weight of its own vehicle. A route search part;
A route output device, comprising: a route output unit that outputs a travel route including the departure point and the destination point in the extracted travel route. A route search unit that accepts input of a departure point and a destination point of a vehicle and extracts a route from the departure point to the destination point;
Of the extracted routes, referring to a storage unit that is generated using the travel data indicating the travel history for each vehicle and stores travel performance data indicating the presence or absence of the travel history of the vehicle for each road section. A route output unit that outputs a route having a running history of a vehicle whose length is equal to or greater than the size of the own vehicle or a vehicle whose weight is equal to or greater than the weight of the own vehicle. A route output method by a computer, wherein the computer
Accepts input of vehicle departure and destination points,
Referring to the storage unit that stores the travel route for each vehicle in association with the date and time, extracts the travel route of the vehicle whose size is greater than or equal to the size of its own vehicle or whose weight is greater than the weight of its own vehicle. ,
A route output method for outputting a travel route including the departure point and the destination point among the extracted travel routes. A route output method by a computer, wherein the computer
Accept the input of the starting point and destination point of the vehicle, extract the route from the starting point to the destination point,
Reference is made to a storage unit that is generated using travel data indicating a travel history for each vehicle and stores travel performance data indicating the presence or absence of the travel history of the vehicle for each road section.
A route output method for outputting a route having a travel history of a vehicle having a size greater than or equal to the size of the own vehicle or a vehicle having a weight greater than or equal to the weight of the own vehicle among the extracted routes.

Images