Parking lot data creation method and device

Abstract

To certainly and accurately generate roof data regarding whether or not a roof is attached to a parking lot on the basis of vehicle travel data from a probe car.SOLUTION: A parking lot data creation device is constituted by comprising: a vehicle travel data storage unit which stores vehicle travel data of a probe car; a vehicle travel data extraction unit which extracts vehicle travel data of the probe car parked at a parking lot from the vehicle travel data stored in the vehicle travel data storage unit; a travel history generation unit in the parking lot which generates an entrance travel history to reach a parking state after entering the parking lot and / or a leaving travel history to reach leaving after termination of parking on the basis of the extracted vehicle travel data; a roof data generation unit which generates roof data regarding presence / absence of a roof of the parking lot on the basis of entrance time, parking start time, and wiper on / off timing in the entrance travel history and / or on the basis of parking termination time, leaving time, and wiper on / off timing in the leaving travel history.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an improvement in a parking lot data generating method and device thereof. The parking lot data relates to whether or not a parking lot has a roof. [Background technology]

[0002] There is a high demand for detailed parking lot data when it comes to map data for navigation. Due to the recent drastic weather changes, such as the sudden heavy rains, whether or not a parking lot has a roof can greatly affect its convenience. Patent Documents 1 to 3 disclose examples in which map data for navigation includes roof data regarding whether or not a parking lot has a roof. Patent Documents 1 and 2 disclose a method for generating roof data using a probe car, in which the presence or absence of a roof in a specific area of ​​a parking lot is identified based on the outside temperature and sunlight conditions, and the roof data is generated based on the identified presence or absence of a roof in a specific area of ​​a parking lot. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-151346 A [Patent Document 2] JP 2018-069429 A [Patent Document 3] JP 2019-133047 A [Patent Document 4] JP 2018-092233 A DISCLOSURE OF THEINVENTION [Problem to be solved by the invention]

[0004] In order to create roof data based on the outside temperature and sunlight conditions measured by a probe car, it is assumed that the probe car uses the parking lot during the day and that sufficient sunlight conditions (amount of sunlight and duration of sunlight) are ensured. Therefore, the data from the probe car that can be applied to creating roof data is limited. Furthermore, since it is necessary to judge whether the sunlight conditions were sufficient for each probe car, the judgment becomes complicated and it is difficult to ensure its accuracy. [Means for solving the problem]

[0005] The present invention aims to solve the above problems and generate roof data on whether a parking lot has a roof, reliably and accurately, based on vehicle travel data from a probe car. The first aspect of the invention is defined as follows. That is, a vehicle driving data storage unit for storing vehicle driving data of the probe car, wherein the vehicle driving data includes coordinate data of the probe car, time data, and wiper data indicating whether the wipers are on or off; a vehicle driving data extraction unit that extracts vehicle driving data of a probe car parked in a parking lot from the vehicle driving data stored in the vehicle driving data storage unit; a parking lot driving history generating unit that generates an in-parking lot driving history from when the vehicle enters the parking lot until the vehicle is parked and / or an out-parking lot driving history from when the vehicle ends parking until the vehicle leaves the parking lot based on the extracted vehicle driving data; a roof data generating unit that generates roof data regarding the presence or absence of a roof in the parking lot based on the entry time, parking start time, and wiper on / off timing in the entry driving history, and / or based on the parking end time, exit time, and wiper on / off timing in the exit driving history; A parking lot data creation device comprising:

[0006] According to the parking lot data creation device of the first aspect thus defined, whether or not a parking lot has a roof is determined based on the timing of the wipers being on and off, and is not affected by the sunlight conditions. This relaxes the restrictions on data from probe cars. In other words, roof data is created based on data from more probe cars, which enables quick creation of roof data. The fact that the wipers are on definitely means that it is raining, and this also improves the reliability of the created roof data.

[0007] The second parking lot data generating device of the present invention is defined as follows. In the parking lot data creation device as defined in the first aspect, a weather data collection unit that collects weather data is further provided, The roof data generating unit generates the roof data by referring to the weather data for the parking lot collected by the weather data collecting unit. According to the device defined in the second aspect defined in this way, since the weather data is referenced, roof data can be generated based on vehicle travel data when the parking lot is objectively in a rainy state, thereby improving the reliability of the roof data.

[0008] One aspect of generating roof data based on the entry travel history is as follows (third aspect). In the parking lot data creation device as defined in the first or second aspect, When the wiper data is on before the entry time in the entry driving history and the on state continues until the parking start time, the roof data generating unit generates roof data A, which indicates that there is no roof in the parking lot from the entrance to the parking space where the probe car in the entry driving history is parked. When, in the entry driving history, the wiper data is on at a time before the entry time, and the wiper data is off at the entry time, and the off state continues until the parking start time, the roof data generation unit generates roof data B, which indicates that there is a roof continuing from the entrance of the parking lot to the parking space where the probe car in the entry driving history is parked. When, in the entry driving history, the wiper data is on at a time before the entry time, and the wiper data is switched between the entry time and the parking start time, and the final data state of the wiper data continues until the parking start time, the roof data generating unit generates roof data C, and this roof data C indicates that there is a roof in a part of the area between the entrance of the parking lot and the parking space where the probe car in the entry driving history is parked. When the wiper data is on at the parking end time in the leaving driving history and the on state continues until the exit time, the roof data generating unit generates roof data a, which indicates that there is no roof in the parking lot from the parking space where the probe car in the leaving driving history was parked to the parking lot exit. When, in the leaving-parking travel history, the wiper data is off before the parking end time, and this off state continues until the exit time, and the wiper data is switched on after the exit, the roof data generation unit generates roof data b, which indicates that there is a roof continuing from the parking space where the probe car in the leaving-parking travel history was parked to the exit of the parking lot. In the leaving driving history, when the wiper data is off before the parking end time, and the wiper data switches between the parking end time and the exit time, and the wiper data is on at the exit time, the roof data generation unit generates roof data c, which indicates that there is a roof over part of the area between the parking space where the probe car in the leaving driving history was parked and the exit of the parking lot.

[0009] As described above, there is a difference between the manner in which the first roof data is generated based on the entry driving history and the manner in which the second roof data is generated based on the outgoing driving history. Therefore, differences may occur in roof data generated from each aspect for the same parking lot. For example, the first roof data based on the entry driving history may specify that parking stalls 1 to 10 have roofs, whereas the second roof data based on the exit driving history may determine that parking stalls 2 to 12 have roofs. In that case, for example, by ANDing the two, it may be possible to specify that parking stalls 2 to 10 have roofs.

[0010] Some modern vehicles are equipped with rain-sensing wipers that will stay on even if the rain has stopped (i.e., you are under a roof) as long as there are raindrops on the windshield. Therefore, when it is heavy rain, the on / off data of the windshield wiper in the driving history for entering the parking lot may not accurately reflect the presence or absence of a roof for a while after entering the parking lot. Therefore, when it is heavy rain, the first roof data generated based on the driving history for entering the parking lot is unreliable. On the other hand, when it is heavy rain, if the vehicle is parked outdoors, the driver will turn on the windshield wiper immediately after parking, so the second roof data generated based on the driving history for leaving the parking lot is unreliable.

[0011] When the weather is light rain, even if the vehicle is parked outdoors, the wipers may not be turned on for a while after parking is completed (after leaving the parking space) as long as there is no hindrance to driving and if a covered area is visible up to the parking lot exit. Therefore, when the weather is light rain, the second roof data generated based on the driving history for leaving the parking lot is less reliable. On the other hand, even if the wipers are raindrop-sensing wipers, the raindrops on the windshield disappear quickly when it is light rain, so the wiper data is quickly turned off if there is a roof after entering the parking lot. Therefore, when the weather is light rain, the first roof data generated based on the driving history for entering the parking lot is more reliable.

[0012] Based on the above findings, a fourth aspect of the present invention is defined as follows. In the parking lot data creation device of the second aspect, a roof position correction unit that corrects the position of the roof in the roof data is further provided, The roof position correction unit corrects the position of the roof based on the depot driving history or by weighting the depot driving history when the weather data indicates light rain; When the weather data indicates heavy rain, the roof position is corrected based on or by weighting the departure driving history.

[0013] In the fourth phase, the distinction between heavy rain and light rain is arbitrary, but for example, rain with an hourly rainfall of less than 3 mm can be considered light rain, and rain with an hourly rainfall of 3 mm or more can be considered heavy rain. Since such weather data is obtained from an external source (e.g., data from the Japan Meteorological Agency), it may not reflect the exact amount of rain at the pinpoint of the target parking lot. On the other hand, it is possible to determine whether it is heavy rain or light rain based on the operating status of the wipers. For example, when the operating status of the wipers is INT (intermittent operation) or LO (weak), it can be determined that it is light rain, and when the operating status of the wipers is HI (strong), it can be determined that it is heavy rain.

[0014] Therefore, the fourth phase can also be defined as follows (fifth phase): The parking lot data creation device according to any one of the first to third aspects further includes a roof position correction unit that corrects a roof position in the roof data, The roof position correction unit corrects the position of the roof based on the driving history for entering the depot or by weighting the driving history for entering the depot when the operation state of the wipers is INT or LO; When the wiper operation state is HI, the roof position data is corrected based on the leaving run history or by weighting the leaving run history.

[0015] The roof data created by the parking lot data creation device according to the first to fifth aspects is preferably incorporated into map data for a navigation device. A navigation device that uses map data incorporating such roof data is defined as a sixth aspect of the present invention. A navigation device comprising map data having a parking lot data storage unit that stores parking lot data including roof data according to any one of items 1 to 3 or roof position data of a parking lot as defined in items 4 or 5, and a guide route generation unit that generates a guide route using the map data, A navigation device including a parking lot selection unit that refers to parking lot data in a parking lot data storage unit and selects a covered parking lot from among parking lots around a destination set by a destination setting unit.

[0016] It is preferable that such a navigation device further includes a weather condition identification unit, and when the weather condition identification unit identifies the weather condition at the destination as rain, the parking lot selection unit selects a parking lot with a roof (seventh aspect). It is preferable that the weather condition determination unit utilizes weather data (forecasted values) at the expected arrival time at the destination.

[0017] In an eighth aspect, the present invention provides a parking lot data generating device according to the first aspect, A parking lot data generation method using a parking lot data generation device including a vehicle driving data storage unit, a vehicle driving data extraction unit, a parking lot driving history generation unit, and a roof data generation unit, The vehicle driving data storage unit stores vehicle driving data of a probe car, and the vehicle driving data includes coordinate data, time data, and wiper data indicating whether the wiper is on or off of the probe car. causing the vehicle travel data extraction unit to extract vehicle travel data of a probe car parked in a parking lot from the vehicle travel data stored in the vehicle travel data storage unit; A step of causing the parking lot driving history generating unit to generate an in-parking driving history from entering the parking lot until the vehicle is parked and / or an out-parking driving history from the end of parking until the vehicle leaves the parking lot, based on the extracted vehicle driving data; and a step of causing the roof data generating unit to generate roof data on the presence or absence of a roof on the parking lot based on the entry time, parking start time, and wiper on / off timing in the entry driving history, and / or based on the parking end time, exit time, and wiper on / off timing in the exit driving history; A method for creating parking lot data including:

[0018] In a ninth aspect of the present invention, a program for a computer that controls the parking lot data generating device according to the first aspect is provided. That is, A computer program for controlling a parking lot data generation device including a vehicle driving data storage unit, a vehicle driving data extraction unit, a parking lot driving history generation unit, and a roof data generation unit, The vehicle driving data storage unit stores vehicle driving data of a probe car, and the vehicle driving data includes coordinate data, time data, and wiper data indicating whether the wiper is on or off of the probe car. causing the vehicle driving data extraction unit to extract vehicle driving data of a probe car parked in a parking lot from the vehicle driving data stored in the vehicle driving data storage unit; The parking lot driving history generating unit generates an in-parking lot driving history from the time the vehicle enters the parking lot until the vehicle is parked and / or an out-parking lot driving history from the time the vehicle ends parking until the vehicle leaves the parking lot, based on the extracted vehicle driving data; and A computer program that causes the roof data generation unit to generate roof data regarding whether or not the parking lot has a roof based on the entry time, parking start time, and wiper on / off timing in the entry driving history, and / or based on the parking end time, exit time, and wiper on / off timing in the exit driving history. [Brief description of the drawings]

[0019] [Figure 1] FIG. 1 is a block diagram showing the configuration of a parking lot data generating device according to an embodiment of the present invention. [Diagram 2]FIG. 2 is a block diagram showing the configuration of a parking lot data generating device according to another embodiment of the present invention. [Diagram 3] FIG. 3 is a block diagram showing the configuration of a parking lot data generating device according to another embodiment of the present invention. [Figure 4] FIG. 4 is a flowchart showing the operation of the parking lot data generating device of FIG. [Diagram 5] FIG. 5 shows details of step 7 (creation of first roof data) in the flowchart of FIG. [Figure 6] FIG. 6 shows details of step 9 (creation of second roof data) in the flowchart of FIG. [Figure 7] FIG. 7 is a schematic diagram showing how a roof is attached to a parking lot. [Figure 8] FIG. 8 is a block diagram showing the configuration of a computer device applied to the parking lot data generating device. [Figure 9] FIG. 9 is a block diagram showing the configuration of a navigation device equipped with parking lot data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 shows a configuration of a parking lot data generating device 1 according to an embodiment of the present invention. This parking lot data generation device 1 includes a vehicle driving data storage unit 3, a vehicle driving data extraction unit 5, a parking lot driving history generation unit 6, a roof data generation unit 7, and a roof data adjustment unit 8.

[0021] The vehicle driving data storage unit 3 stores vehicle driving data of the probe car. Here, vehicle driving data includes probe data (position data (x, y), time data (t)) generally obtained from probe cars, as well as the vehicle's internal data from the probe cars. Here, vehicle internal data refers to data relating to various vehicle conditions output from sensors, control units, and other devices equipped in the vehicle, and is data that can be transmitted over a network installed in the vehicle using various communication protocols including CAN (Controller Area Network). In this invention, data that specifies whether the windshield wipers are on or off (wiper data) is used as this vehicle internal data.

[0022] The vehicle driving data storage unit 3 includes a probe data storage area 31 and a wiper data storage area 33. The probe data storage area 31 stores at least position data (x, y) and time data (t) which are the driving history of the probe car. The wiper data storage area 33 stores the history of wiper use (on, off) by the probe car together with the time (t). Data on the strength of wiper operation (INT, LO, HI) can also be stored.

[0023] The vehicle driving data extraction unit 5 identifies a probe car parked in a parking lot from the vehicle driving data stored in the vehicle driving data storage unit 3 by referring to the coordinate data (x, y) stored in the probe data storage area 31, and extracts vehicle driving data for that probe car from before it enters the parking lot to after it leaves the parking lot.

[0024] Upon receiving the vehicle driving data extracted in this manner, the parking lot driving history generating unit 6 generates a driving history of the probe car within the parking lot. Specifically, the parking lot driving history generating unit 61 of the parking lot driving history generating unit 6 generates a driving history (entering driving history) based on the vehicle driving data from when the vehicle enters the parking lot from the road until when the vehicle is parked. This entering driving history includes the probe data (position data (x, y) and time data (t)) of the probe car from when the vehicle enters the parking lot until when the vehicle completes parking in a parking space. The probe data identifies the time of entry into the parking lot and the time when the vehicle starts parking in a parking space. The wiper data also identifies the timing of when the wipers are turned on and off.

[0025] The leaving driving history generating unit 63 generates a driving history (leaving driving history) based on the vehicle driving data from the end of parking (after leaving the parking space) to the exit from the parking lot. This leaving driving history includes the probe data (position data (x, y) and time data (t)) of the probe car from the end of parking to the exit. The parking end time and the exit time are specified from this probe data. In addition, the wiper on / off timing is specified from the wiper data.

[0026] The entry travel history is sent to a first roof data generating unit 71. The first roof data generating unit 71 generates first roof data relating to the presence or absence of a roof of the parking lot as follows. In the entry driving history, when the wiper data is on before the entry time and the on state continues until the parking start time, the roof data generation unit generates roof data A, which indicates that there is no roof in the parking lot from the entrance to the parking space where the probe car in the entry driving history is parked.

[0027] In the entry driving history, when the wiper data is on before the entry time, and the wiper data is off at the entry time, and the off state continues until the parking start time, the roof data generation unit generates roof data B, which indicates that there is a roof that extends from the entrance of the parking lot to the parking space where the probe car in the entry driving history is parked. In the entry driving history, when the wiper data is on before the entry time, and the wiper data switches between the entry time and the parking start time, and the final wiper data state continues until the parking start time, the roof data generation unit generates roof data C, which indicates that there is a roof in part of the area between the entrance to the parking lot and the parking space where the probe car in the entry driving history is parked.

[0028] The leaving vehicle travel history is sent to the second roof data generating unit 73. The third roof data generating unit 73 generates first roof data relating to the presence or absence of a roof of the parking lot as follows. In the leaving driving history, when the wiper data is on at the parking end time and the on state continues until the exit time, the roof data generation unit generates roof data a, and this roof data a indicates that there is no roof in the parking lot from the parking space where the probe car in the leaving driving history was parked to the parking lot exit.

[0029] In the exit driving history, when the wiper data is off before the parking end time, and this off state continues until the exit time, and the wiper data is switched on after exit, the roof data generation unit generates roof data b, which indicates that there is a roof continuing from the parking space where the probe car in the exit driving history was parked to the exit of the parking lot. In the leaving driving history, when the wiper data is off before the parking end time, and the wiper data switches between the parking end time and the exit time, and the wiper data is on at the exit time, the roof data generation unit generates roof data c, which indicates that there is a roof over part of the area between the parking space where the probe car in the leaving driving history was parked and the exit of the parking lot.

[0030] The roof data thus generated is collected in the roof data adjustment unit 8 and adjusted there. Even in one parking lot, depending on the location of the parking space, some have a roof and some do not. Therefore, the roof data adjustment unit 8 adjusts and integrates the roof data obtained for each parking space to form an overall image of the roof for the parking lot.

[0031] Fig. 2 shows a parking lot data generating device 1A according to another embodiment. In Fig. 2, the same elements as those in Fig. 1 are given the same reference numerals and the description thereof will be omitted. In this example, a weather data collection unit 20 and a roof data correction unit 9 are further provided in the parking lot data generation device shown in FIG.

[0032] The weather data collection unit 20 accesses an external weather database 10 provided by the Japan Meteorological Agency or the like via the Internet or the like to collect weather data necessary for the parking lot. That is, when the parking of the probe car is confirmed, the coordinates of the parking lot where the probe car is parked and the usage time of the parking lot (from entry to exit) are confirmed, and weather data related to the amount of precipitation at the coordinates or in an area including the coordinates during the usage time is collected from the weather database 10. This weather data is sent to the roof data generating unit 7, and the roof data generating unit 7 generates roof data by referring to only the probe data when the weather data indicates rainfall.

[0033] The weather data is also sent to the roof data correction unit 9. The roof data correction unit 9 adopts either the first roof data or the second roof data depending on the weather condition (amount of rainfall). When the weather is heavy rain, the wipers may not be turned off for a while even if there is a roof after entering the garage, so the first roof data based on the driving history for entering the garage may not accurately reflect the presence or absence of a roof. Therefore, when the weather is heavy rain, the use of the first roof data can be stopped and only the second roof data can be used.

[0034] On the other hand, when the weather is light rain, the wipers may not be operated for a while even after parking is completed (after leaving the parking space), so the second roof data based on the departure driving history may not accurately reflect the presence or absence of a roof. Therefore, when the weather is light rain, the use of this second roof data can be stopped and only the roof data generated from the first roof data can be used.

[0035] In addition, the first roof data and the second roof data can be weighted according to the weather conditions and integrated. One method of weighting is to prioritize the number of data to be adopted. For example, when the weather conditions are heavy rain, the number of data pieces of the second roof data can be made greater than the number of data pieces of the first roof data to determine whether or not a roof exists, and when the weather conditions are light rain, the number of data pieces of the first roof data can be made greater than the number of data pieces of the second roof data to determine whether or not a roof exists.

[0036] A parking lot data generating device 1B according to another embodiment of the present invention is shown in Fig. 3. In Fig. 3, the same elements as those in Fig. 1 are given the same reference numerals and their explanation will be omitted. In this example, a roof data correction unit 9B is provided. 2, the roof data is corrected to be more accurate based on the weather conditions (heavy rain, light rain) collected by the weather data collection unit 20. In this example, attention is paid to the fact that the wipers are in the HI state during heavy rain and in the INT or LO state during light rain. In other words, if the turn signal is on HI when entering a parking lot or when parking is completed, it is determined that it is heavy rain, and similarly, if the turn signal is on INT or LO when entering a parking lot or when parking is completed, it is determined that it is light rain, and control is performed in the same manner as the example in Figure 2.

[0037] The operation of the parking lot data generating device 1B in FIG. 3 will be described with reference to the flowcharts in FIGS. In step 1, the vehicle driving data extraction unit 5 extracts vehicle driving data of a probe car with parking history for a specified parking lot from the vehicle driving data storage unit 3. The parking lot may be specified by an operator, or a computer may automatically specify a parking lot that is registered in the map data. The extracted vehicle driving data includes probe data from entering to leaving the parking lot and wiper data during that time (wiper on / off, time and strength (INT, LO, HI)).

[0038] In step 3, the entry driving history generating unit 61 generates an entry driving history from the extracted vehicle driving data. This entry driving history is vehicle driving data (probe data, wiper data) from when the probe car enters the parking lot from the road until it is parked. In step 5, the leaving driving history generating unit 63 generates a leaving driving history from the extracted vehicle driving data. This leaving driving history is vehicle driving data (probe data, wiper data) from the end of parking until the probe car leaves the parking lot.

[0039] In step 7, the first roof data generating unit 71 generates first roof data from the entry travel history. In step 9, the second roof data generating unit 73 generates second roof data based on the leaving vehicle travel history. Details of steps 7 and 9 are shown in Figures 5 and 6, respectively.

[0040] In step 701 in FIG. 5, only the driving history in which the wipers were on when the vehicle entered the garage is extracted. In step 703, the operation state of the warper is confirmed, and if the operation state is INT or LO, which indicates light rain, an L flag is generated and assigned to the entry driving history (step 705). The first roof data generated from this entry driving history is assigned this L flag.

[0041] In step 707, the entry driving history is scanned to check whether the wipers were turned off after entering the parking lot and before parking. If the wipers have not been turned off after entering the parking lot and before parking the vehicle in the desired parking space (step 707: N), roof data A is generated in step 721 to indicate that there is no roof between the parking lot entrance and the parking position. Here, as shown in FIG. 7A, when all the parked probe cars exhibit the same behavior, the roof data is adjusted in the roof data adjustment unit 8 (step 11), and roof data A indicating that the parking lot is completely roofless is assigned to the parking lot.

[0042] On the other hand, if the wipers are turned off before parking, the off position is obtained (step 709). If the wipers remain off until parking, roof data B is generated. If the entire parking lot is covered with a roof, the position in step 709 is the entrance (where the wipers are turned off), and the roof is then extended up to the parking position, so the wipers remain off. As shown in FIG. 7B, when all the parked probe cars exhibit the same behavior, the roof data is integrated in the roof data adjustment unit 8 (step 11), and roof data B indicating that the parking lot has a full roof is assigned to the parking lot.

[0043] If step 711 is NO, this is the behavior of probe cars c1 and c2 in FIG. 7C. If a roof is attached to the lane area in FIG. 7C, the probe cars c1 and c2 that have left the roof will turn their wipers on again (step 711; N). In step S713, their positions are acquired. In the example of FIG. 7C, this corresponds to the left edge of the shaded area representing the roof. If the wipers are still on before parking (step 715: Y), the process proceeds to step 725, where roof data C is created. This roof data C identifies the position of the edge of the roof that is partially attached to the parking lot.

[0044] If the parking lot roof is installed intermittently, the process proceeds from step 715 to step 716, and then returns to step 711. In addition, the processing result of the entry driving history obtained from the probe car c3 in Figure 7C is that of step 723, and the processing result of the entry driving history obtained from the probe cars parked in each parking space of the parking lot specified in Figure 7C is adjusted in the roof data adjustment unit 8 to identify the position of the roof of the parking lot in Figure 7C.

[0045] In step 901 in FIG. 6, only the driving history of the vehicle leaving the parking lot in which the wipers are on is extracted. In step 902, if the wipers are on when parking is completed and the vehicle is about to depart (when the vehicle departs from the parking space), the process proceeds to step 903; if the wipers are off, the process proceeds to step 904. If the wiper-off state is maintained until the time of exit in step 904 (step 904: Y), roof data b is generated in step 923. This roof data b indicates that a roof is provided from the parking space where the probe car was parked to the exit. If the processing results of the exit driving history obtained from all the probe cars in one parking lot are processed in step 923, the parking lot will be entirely covered with a roof. In step 904, when the wiper-off state is not maintained until the exit (step 904: N), the process proceeds to step 913.

[0046] In step 903, the operating state of the wipers is confirmed, and if the operating state is HI, which indicates heavy rain, an H flag is generated and assigned to the leaving-yard travel history (step 905). The second roof data generated from this leaving-yard travel history is assigned this H flag.

[0047] In step 907, the exit driving history is scanned to check whether the wipers were turned on after parking was completed and before the vehicle left the parking lot. If the wipers were kept on from the time the vehicle left the parking space until the time the vehicle left the parking lot (step 907: Y), then in step 921 roof data a is generated to indicate that there is no roof between the parking space and the exit.

[0048] On the other hand, if the wipers are turned off before the vehicle exits (step 907: N), the position where the wipers were turned off is obtained (step 909). If the wiper-off state is maintained until the vehicle exits (step 911: Y), the process proceeds to step 924 and roof data c is generated. This roof data c indicates that a roof is provided from the wiper-off position to the exit.

[0049] When the wipers that were once turned off are turned on in step S911, their positions are acquired in step S913. If the wipers remain on until the vehicle leaves the parking lot (step 915: Y), the process proceeds to step 925, where roof data c' is created. This roof data c' identifies the position of the edge of the roof that is partially attached to the parking lot.

[0050] If the parking lot roof is installed intermittently, the process proceeds from step 915 to step 916, and then returns to step 911. The departure travel history of the probe cars parked in each parking space in the parking lot is adjusted and integrated in the roof data adjustment unit 8. This roof data adjustment unit 8 not only consolidates the second roof data obtained through the processing of Figure 6, but also consolidates the first roof data obtained through the processing of Figure 5 together with the second roof data.

[0051] For example, there may be a difference in the position of the roof in a parking lot between the first roof data obtained by processing the entry driving history and the second roof data obtained by processing the departure driving history. Therefore, in this device 1B, a roof data correction unit 9B is provided to correct the roof data. This roof data correction unit 9B adopts only data with an L flag for the first roof data, and only data with an H flag for the second roof data. This makes it possible to obtain highly reliable roof data.

[0052] FIG. 8 shows the hardware configuration of the roof data generating device 1B. The calculation unit 300 includes a CPU 301, a ROM 303, and a RAM 305, and controls the entire system. It also functions as a parking lot travel history generating unit 6, a roof data generating unit 7, a roof data adjusting unit 8, and a roof data correcting unit 9B. The ROM 303 is a non-volatile memory in which a control program for controlling the calculation unit 300 and the like are stored. The RAM 305 readably stores various setting values ​​preset by a user via an input device 330 such as a keyboard, and provides a working area for the CPU 301. The control program for controlling the calculation unit 300 may be stored not only in the ROM 303, but also in the RAM 305 or the first and second storage devices 340 and 350. Various data are output via the output device 320. Conditions for acquiring vehicle travel data and the like are input via the input device 330.

[0053] The first storage device 340 functions as the vehicle driving data storage unit 3. The first storage device 340 may also be an external server. The second storage device 350 can also function as a buffer memory for the vehicle driving data extracted by the vehicle driving data extraction unit 5, the parking lot driving history generated by the parking lot driving history generation unit 6, and various data generated by the roof data generation unit 7. It is preferable that the first and second storage devices utilize a partial area of ​​a memory device of the server system, such as a hard memory or a flash memory.

[0054] A part of the RAM in the calculation unit can be used as a so-called buffer memory, which serves as a storage unit for temporarily storing data. The devices constituting the computer are connected via a system bus 370 .

[0055] 9 shows a navigation device 200 according to an embodiment of the present invention. The navigation device 200 includes a navigation data storage unit 260 and a navigation execution unit 270. The roof data generated as described above is stored in the roof data storage area 650 of the parking lot data storage unit 265 of the navigation data storage unit 260 in the navigation device 200.

[0056] A map data storage unit 261 of the navigation data storage unit 260 stores a nationwide road map in the form of nodes and links. A traffic data storage unit 263 stores road attributes (speed limits, one-way streets, etc.). A route calculation unit 271 of the navigation execution unit 270 calculates a route to a destination using data stored in the navigation data storage unit 260. In this calculation, the destination is specified via an input unit 277, and the calculated route is displayed on a display unit 278. The current position of the traveling vehicle is displayed on the display unit 278 together with the route by a current position identification unit 272 equipped with a GPS.

[0057] The parking lot display unit 273 of the navigation execution unit 270 refers to the parking lot data in the parking lot data storage unit 265 to display parking lots around the destination, and also refers to the roof data stored in the roof data storage area 650 to display whether or not each parking lot has a roof. This parking lot display unit 273 can also display parking lots in the vicinity of the current position of the vehicle identified by the current position identification unit 272 and whether or not they have roofs. The weather condition identification unit 275 refers to an external weather database via the Internet, etc., to identify the weather conditions at the destination or the current location, and when the weather condition is rainfall, causes the parking lot display unit 273 to display whether or not there is a roof.

[0058] The parking lot selection unit 274 selects a parking lot near the destination according to a predetermined rule. In general, the parking lot closest to the destination is selected preferentially. In this example, the parking lot selection unit 274 preferentially selects a parking lot with a roof and displays it on the display unit of the navigation device. The preferential selection of a covered parking lot by the parking lot selection unit 274 is preferably performed when the weather condition identification unit 275 identifies that the weather condition around the destination is rainfall.

[0059] The present invention is not limited to the above-mentioned embodiment and examples. Various modifications within the scope of the claims and within the scope that can be easily conceived by a person skilled in the art are also included in the present invention. [Explanation of symbols]

[0060] 1, 1A, 1B Parking lot data generator 3. Vehicle driving data storage unit 5. Vehicle driving data extraction unit 6 Parking lot driving history generation unit 7 Roof data generation section 20. Meteorological Data Collection Division 200 Navigation Device 265 Parking Lot Data Storage Department 274 Parking Lot Selection Section

Claims

1. a vehicle driving data storage unit for storing vehicle driving data of the probe car, the vehicle driving data including coordinate data, time data, and wiper data indicating whether the wipers are on or off of the probe car; a vehicle driving data extraction unit that extracts vehicle driving data of a probe car parked in a parking lot from the vehicle driving data stored in the vehicle driving data storage unit; a parking lot driving history generating unit that generates an in-parking driving history from when the vehicle enters the parking lot until the vehicle is parked and / or an out-parking driving history from when the vehicle ends parking until the vehicle leaves the parking lot based on the extracted vehicle driving data; a roof data generating unit that generates roof data regarding the presence or absence of a roof in the parking lot based on the entry time, parking start time, and wiper on / off timing in the entry driving history, and / or based on the parking end time, exit time, and wiper on / off timing in the exit driving history; A parking lot data creation device comprising:

2. A weather data collection unit for collecting weather data is further provided, The device according to claim 1 , wherein the roof data generating unit generates the roof data by referring to meteorological data for the parking lot collected by the meteorological data collecting unit.

3. When the wiper data is on before the entry time in the entry driving history and the on state continues until the parking start time, the roof data generating unit generates roof data A, which indicates that there is no roof in the parking lot from the entrance to the parking space where the probe car in the entry driving history is parked. When, in the entry driving history, the wiper data is on at a time before the entry time, and the wiper data is off at the entry time, and the off state continues until the parking start time, the roof data generation unit generates roof data B, which indicates that there is a roof continuing from the entrance of the parking lot to the parking space where the probe car in the entry driving history is parked. When, in the entry driving history, the wiper data is on at a time before the entry time, and the wiper data is switched between the entry time and the parking start time, and the final data state of the wiper data continues until the parking start time, the roof data generating unit generates roof data C, and this roof data C indicates that there is a roof in a part of the area between the entrance of the parking lot and the parking space where the probe car in the entry driving history is parked. When the wiper data is on at the parking end time in the leaving driving history and the on state continues until the exit time, the roof data generating unit generates roof data a, which indicates that there is no roof in the parking lot from the parking space where the probe car in the leaving driving history is parked to the parking lot exit. When, in the leaving-parking travel history, the wiper data is off before the parking end time, and this off state continues until the exit time, and the wiper data is switched on after the exit, the roof data generating unit generates roof data b, which indicates that there is a roof continuing from the parking space where the probe car in the leaving-parking travel history is parked to the exit of the parking lot.

3. The device according to claim 1, wherein when, in the leaving driving history, the wiper data is off before the parking end time, and the wiper data switches between the parking end time and the exit time, and the wiper data is on at the exit time, the roof data generation unit generates roof data c, and this roof data c indicates that there is a roof over part of the area between the parking space where the probe car in the leaving driving history is parked and the exit of the parking lot.

4. A roof position correction unit is further provided for correcting the position of the roof in the roof data, The roof position correction unit corrects the position of the roof based on the depot driving history or by weighting the depot driving history when the weather data indicates light rain; 3. The apparatus of claim 2, wherein when the weather data indicates heavy rain, the roof position is corrected based on or by weighting the leaving driving history.

5. A roof position correction unit is further provided for correcting the position of the roof in the roof data, The roof position correction unit corrects the position of the roof based on the driving history for entering the depot or by weighting the driving history for entering the depot when the operation state of the wipers is INT or LO; 4. The device according to claim 1, wherein when the wiper operation state is HI, the roof position data is corrected based on the leaving driving history or by weighting the leaving driving history.

6. The roof data according to any one of claims 1 to 3 or A navigation device comprising map data having a parking lot data storage unit that stores parking lot data including the position data of the roof of the parking lot according to claim 3 or 5, and a guide route generation unit that generates a guide route using the map data, A navigation device including a parking lot selection unit that refers to parking lot data in a parking lot data storage unit and selects a covered parking lot from among parking lots around a destination set by a destination setting unit.

7. A weather condition identification unit is further provided, 7. The navigation device according to claim 6, wherein when the weather condition specifying section determines that the weather conditions at the destination are rainy, the parking lot selecting section selects the parking lot with a roof.

8. A parking lot data generation method using a parking lot data generation device including a vehicle driving data storage unit, a vehicle driving data extraction unit, a parking lot driving history generation unit, and a roof data generation unit, The vehicle driving data storage unit stores vehicle driving data of the probe car, and the vehicle driving data includes coordinate data, time data, and wiper data indicating whether the wipers are on or off of the probe car. causing the vehicle travel data extraction unit to extract vehicle travel data of a probe car parked in a parking lot from the vehicle travel data stored in the vehicle travel data storage unit; A step of causing the parking lot driving history generating unit to generate an in-parking driving history from entering the parking lot until a parked state and / or an out-parking driving history from the end of parking until exiting the parking lot based on the extracted vehicle driving data; and A step of causing the roof data generating unit to generate roof data regarding the presence or absence of a roof of the parking lot based on the entry time, parking start time, and wiper on / off timing in the entry driving history, and / or based on the parking end time, exit time, and wiper on / off timing in the exit driving history, A method for creating parking lot data including:

9. A computer program for controlling a parking lot data generation device including a vehicle driving data storage unit, a vehicle driving data extraction unit, a parking lot driving history generation unit, and a roof data generation unit, The vehicle driving data storage unit stores vehicle driving data of the probe car, and the vehicle driving data includes coordinate data, time data, and wiper data indicating whether the wipers are on or off of the probe car. causing the vehicle driving data extraction unit to extract vehicle driving data of a probe car parked in a parking lot from the vehicle driving data stored in the vehicle driving data storage unit; The parking lot driving history generating unit generates an in-parking lot driving history from the time the vehicle enters the parking lot until the vehicle is parked and / or an out-parking lot driving history from the time the vehicle ends parking until the vehicle leaves the parking lot, based on the extracted vehicle driving data; and A computer program that causes the roof data generation unit to generate roof data regarding whether or not the parking lot has a roof based on the entry time, parking start time, and wiper on / off timing in the entry driving history, and / or based on the parking end time, exit time, and wiper on / off timing in the exit driving history.

Images