System and method for viewing and correcting data in a street mapping database

[0001] The present invention relates generally to a system and method for creating, using and maintaining a database of street mapping data and, more particularly, to a system and method for updating street data and identifying errors in the database.

[0002] Detailed street mapping data is available from companies such as NavTeq and Tele Atlas. The street mapping data may include street location, street names, posted speed limits, numbers of lanes, travel direction, and other information. This street mapping data is used in vehicle navigation systems to provide map displays and other information to drivers. Typically, the only information displayed to a driver is a street map and limited other information, such as the name of the street being used by a vehicle and/or the name of the city or municipality in which the street is located. Other street mapping data may be available for a current street or roadway, but that information is not available to the driver. The street mapping data is used in some applications to evaluate driver performance, such as comparing vehicle speeds to posted speed limits recorded in the street mapping data. If the street mapping data is wrong, such as an incorrect posted speed limit, the driver will not know that a navigation system or vehicle monitoring system using the street mapping data may be using the wrong fundamental parameters to evaluate driver performance and/or vehicle operation. Furthermore, maintaining accurate mapping data can be a very costly endeavor.

[0003] These and other problems are generally solved or circumvented, and technical advantages are generally achieved, by preferred embodiments of the present invention in which street mapping data is available to a vehicle driver. The driver may then evaluate the accuracy of the street mapping data and may report errors in the street mapping data.

[0004] In one embodiment, a system and method for using street map data comprises broadcasting a warning to a driver, wherein the warning is triggered when a vehicle operating parameter does not comply with a limitation (e.g., a speed limitation, direction limitation, or otherwise) for a current street in a street mapping database; broadcasting the limitation for the current street to the driver; and receiving an indication that the limitation for the current street is incorrect. Broadcasting the warning to the driver may be providing an audible warning and/or a visual warning to the driver. Broadcasting the limitation for the current street to the driver may include displaying the limitation to the driver or playing a spoken message to the driver. The limitation may be a posted speed limit or a traffic direction, for example. The indication that the limitation is incorrect may be sent to a third party.

[0005] In another embodiment, a system and method for identifying errors in a street mapping database, comprises determining driving limitations for a current vehicle location; determining current operating parameters for a vehicle; identifying one or more current operating parameters that violate the driving limitations; broadcasting a warning to a vehicle driver, wherein the warning notifies the driver that one or more driving limitations have been violated; and displaying a stored value of the one or more driving limitations to the driver. The current vehicle location may be displayed to the driver on a map. Broadcasting a warning to a vehicle driver may include displaying a visual warning to the driver identifying one or more categories of driving limitations that have been violated. The one or more categories of driving limitations may be posted speed limits or traffic directions. The stored value may be a stored posted speed limit for the current vehicle location. An indication that the stored value is incorrect may be received, for example, from a driver, and the indication may be sent to a street mapping database provider and/or to a supervisor. For example, if an operator identifies an incorrect speed limitation value, such error can be communicated for purposes of correcting it. The database provider or supervisor, such as fleet manager, navigation system provider, or mapping data provider, may use the indication to evaluate or update a street map database. A replacement entry may be received for the stored value, for example, from a driver. The replacement entry may be sent to a street mapping database provider and/or a supervisor to evaluate or update a street map database.

[0006] In a another embodiment, a system and method for updating a street map database, comprises displaying a stored street use parameter to a driver, wherein the street use parameter is associated with vehicle operation on a street being used by the driver; and receiving a replacement value for the street use parameter from the driver. A street map database in a vehicle may be updated by replacing the stored street use parameter with the replacement value. A central street map database may be updated by replacing the stored street use parameter with the replacement value. The street use parameter may be selected from the group consisting of, for example, a speed limit, a traffic flow direction, a traffic signal status, a road condition, a traffic density, a road construction status, a street name, a municipality name, and a road hazard.

[0015] The present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific ways to make and use the invention, and do not limit the scope of the invention.

[0016] With reference to FIG. 1, there is shown vehicle monitoring unit 101 that is coupled to one or more systems in vehicle 102. Processor 103 controls the operation of monitoring unit 101. Processor 103 may be a general use processing device having software designed to control unit 101. Alternatively, processor 103 may be a specially designed circuit or device, such as an application specific integrated circuit (ASIC), that is particularly designed for use in unit 101. Processor 103 may use firmware or software, such as an operating system, for control and operation. Operating firmware, software and other data may be stored in random access memory (RAM) 104, read only memory (ROM) 105, electrically erasable programmable memory (EEPROM) devices, or other storage devices, such as magnetic media.

[0017] Monitoring unit 101 includes one or more vehicle system interfaces 106 that allow unit 101 to interact with systems in vehicle 102, such as vehicle ignition system 107 and vehicle electrical system 108. Signals exchanged between interface 106 and vehicle ignition system 107 may allow monitoring unit 101 to determine the operating status of vehicle 102 and to command the ignition system to start or shutdown the engine of vehicle 102. Signals exchanged between interface 106 and vehicle electrical system 108 may allow monitoring unit 101 to determine the status of other vehicle systems and to command other systems to operate. For example, vehicle electrical system 108 may provide control of the vehicle's horn, interior and/or exterior lights, entertainment system, navigation system, heating and/or air conditioning systems, alarm, or other vehicle system.

[0018] Vehicle diagnostic system interface 109 provides a connection between monitoring unit 101 and vehicle diagnostic system 110. Vehicle diagnostic system 110 may be an on-board diagnostic (OBD) II system or a controller area network (CAN) system in vehicle 102 that is accessed via a port or data bus. The OBD/CAN system provides access to engine performance and status data, speedometer, odometer and tachometer data, and data from other vehicle systems. Power supply 111 provides power to monitoring unit 101. Power supply 111 may be a self-contained battery, for example, or it may be coupled to another power source, such as vehicle battery 112. There may be a connection between power supply 111 and vehicle battery 112 or power supply 111 may receive vehicle power via the vehicle's OBD/CAN bus, for example.

[0019] In addition to vehicle sensors and diagnostic systems, such as OBD/CAN 110, monitoring unit 101 may be coupled to other original equipment and aftermarket sensors 113 in vehicle 102. For example, monitoring unit 101 may be coupled an RF transmission sensor, which is configured to detect transmissions such as cellular voice and data signals that originate from or are received at vehicle 102, such as the sensors described in U.S. patent application Ser. No. 11/866,247, entitled “System and Method for Detecting Use of a Wireless Device in a Moving Vehicle,” filed Oct. 2, 2007, the disclosure of which is hereby incorporated herein by reference in its entirety. Other sensors may include, for example, seatbelt use sensors, alcohol or ethanol vapor sensors, cameras, microphones, accelerometers, adaptive control devices, angular acceleration sensors, traction control, ABS, or crash detectors.

[0020] Monitoring unit 101 further includes geographic position locating system 114, which provides location information for vehicle 102, such as a latitude/longitude, street address, or map coordinates, for example. In one embodiment, geographic position locating system 114 may be a global positioning system (GPS) that uses satellite signals to determine location. Other navigation or location-determining systems may also be used, such as inertial navigation systems that update a vehicle's location as it moves from a known position or terrestrial-based radio navigation systems, such as Long Range Aid to Navigation (LORAN). In other embodiments, position locating system 114 may use transmissions or data from cellular or wireless network towers to determine a geographical location.

[0021] Monitoring unit 101 may include one or more systems that provide communications with other devices and systems. For example, monitoring unit 101 may include cellular or mobile telephone transmitter/receiver 115 that allows unit 101 to communicate with other devices and to send or receive data via a cellular or mobile network. Satellite transmitter/receiver 116 allows unit 101 to communicate with other devices and to send or receive data via satellite network communications. Bluetooth transmitter/receiver 117 allows unit 101 to communicate with other devices that have Bluetooth capability. Data network transmitter/receiver 118 allows unit 101 to communicate via networks, such as data communication networks using WiFi, IEEE 802.11, WiMAX, or other standards or protocols, for example. Monitoring unit 101 may further include one or more antennas 119 to support such communications. Antennas 119 may be internal to monitoring unit 101, may be formed as an integral part of a housing for unit 101, may be externally mounted on vehicle 102, or may be embodied in any antenna configuration now known or later developed.

[0022] Vehicle monitoring unit 101 may also be used to provide information, such as vehicle status or location, to a driver and passengers in vehicle 102 using driver displays and interface 120. For example, processor 103 may be configured to identify alarm conditions, such as when vehicle 102 is operated outside of preselected conditions, and to provide feedback or alarms to the driver. Upon detection of an alarm condition, processor 103 may present a warning to the driver, such as text messages, alarm horn, audible tone or message, or a visual warning via driver displays and interface 120. Driver displays and interface 120 may include, for example, speakers, horns, warning lights, keypads, graphics, text or image display screens, or touch-screen displays. Possible displays may include the vehicle's OEM equipment.

[0023] Driver displays and interface 120 may also provide position and routing data to the driver, such as street maps, maps of current or destination locations, suggested or actual routes, vehicle heading, vehicle speed, estimated trip duration, predicted destination arrival time, points of interest, and the like. The position and routing information may be provided to driver display and interface 120 from processor 103 or from geographic position locating system 114, for example. Vehicle monitoring unit 101 may further include street mapping database 121 for use with geographic position locating system 114 and/or processor 103. For example, street mapping database 121 may include street maps for multiple locations and street data for specific streets, such as posted speed limits, lane number and direction, road conditions, and traffic conditions. The data in street mapping database 121 may be stored in a compact disc (CD), digital video disc (DVD), random access memory, read only memory, electrically erasable programmable memory, or other magnetic media or electronic storage.

[0024] In other embodiments, street mapping database 121 may be stored in RAM 104 or ROM 105, or in geographic position locating system 114. In one embodiment, geographic position locating system 114 or processor 103 determine a current location of vehicle 102 and use data from street mapping database 121 to display a map of the current location to the driver via displays and interfaces 120, such as the current street on which vehicle 102 is driving. Additional information may be presented to the driver, such as a street name, driving direction, posted speed limit, expected traffic conditions, or the like.

[0025] In one embodiment, the street mapping information stored in database 121 may be updated, for example, by the driver or a third party. The driver may enter data, such as updated traffic or construction information, updated posted speed limits, street names, or street closures, via driver interfaces 120. Alternatively, or additionally, monitoring device 101 may receive updated street mapping data, such as via a wireless transmissions received by one or more of transceivers 115-118, from a third party, such as monitoring service operator, street mapping data provider, fleet manager, or other person or entity.

[0026] Vehicle monitoring unit 101 may also include accelerometer module 122, which includes at least one accelerometer for measuring at least one of lateral (sideways), longitudinal (forward and aft) and vertical acceleration, for determining whether the driver is operating vehicle 102 in an unsafe or aggressive manner. For example, excessive lateral acceleration may be an indication that the driver is operating vehicle 102 at an excessive speed in a turn. Excessive lateral acceleration, defined herein as “hard turns,” may be indicative of aggressive driving by the driver and may contribute to excessive wear on tires and steering components as well as potentially causing the load such as a trailer to shift and potentially overturn. Additionally or alternatively, accelerometers 122 may include a self-contained and tamper-resistant event data recorder or crash data recorder (CDR) similar to that which is shown and disclosed in U.S. Pat. Nos. 6,266,588 and 6,549,834 issued to McClellan et al., (the disclosures of which are hereby incorporated by reference herein in their entirety) and which is commercially known as “Witness” and commercially available from Independent Witness, Inc. of Salt Lake City, Utah. The CDR is adapted to continuously monitor vehicle motion and begin recording upon supra-threshold impacts whereupon it records the magnitude and direction of accelerations or G-forces experienced by the vehicle as well as recording an acceleration time-history of the impact event and velocity change between pre- and post-impact for a configurable duration following an impact. In one embodiment, the recordings are time-date stamped and are available to processor 103 for subsequent transmission to a supervisor or central monitoring facility if vehicle accelerations exceed an impulse threshold. Such accelerometers and CDRs are described in U.S. patent application Ser. No. 11/805,238, entitled “System and Method for Monitoring and Updating Speed-by-Street Data,” filed May 22, 2007, the disclosure of which is hereby incorporated herein by reference in its entirety.

[0027] FIG. 2 illustrates monitoring unit 201 installed or mounted in vehicle 202. Monitoring unit 201 may include the elements of monitoring unit 101 and may be coupled to systems in vehicle 202 as illustrated, for example, in FIG. 1. Monitoring unit 201 may be mounted in any location within vehicle 202, such as in a trunk, under a seat, in a glovebox, or on a window or dashboard. Monitoring unit 201 is coupled to one or more antennas 203, which may be used to communicate with one or more satellite or terrestrial communications networks. Monitoring unit 201 may be capable of communicating with one or more networks or systems, such as cellular or mobile telephone network 204, having base stations or cell sites 205 and 206, wireless data network 207, such as a Bluetooth, WiFi, WiMAX or 802.11 network, or satellite 208. Monitoring unit 201 may also be in communication with or receive signals from satellites 213, which may be part of a geographical position locating system, such as a GPS system.

[0028] Monitoring unit 201 is coupled to and in communication with on board diagnostic system 209 in vehicle 202. Vehicle monitoring unit 201 has access to certain vehicle operating parameters including, but not limited to, vehicle speed such as via the speedometer, engine speed or throttle position such as via the tachometer, mileage such as via the odometer reading, seat belt status, condition of various vehicle systems including anti-lock-braking (ABS), turn signal, headlight, cruise control activation, adaptive cruise control, traction control, and a multitude of various other diagnostic parameters such as engine temperature, brake wear, and the like. Monitoring unit 201 may also be coupled to driver displays and interfaces, such as warning lights or touch-screen display 223 and/or speaker 224. Monitoring unit 201 may also be coupled to additional sensors 210, such as an RF sensor, camera, microphone, ethanol vapor sensor or the like.

[0029] Server 214 may be any processor-based system that is capable of communicating with external networks and processing data associated with wireless device usage and vehicle monitoring units. Server 214 may be coupled to multiple networks, such as cellular network 204 or wireless data network 207, via networks 215 and 216, which couple server 214 to other communication networks, may be any public or private data network, such as an Internet, intranet, extranet, or wide or local area network (WAN/LAN). Server 214 may be coupled to satellite 208 via antenna 222. In one embodiment, users may communicate with server 214 via a local or remote personal computer (PC), laptop computer, or terminal, such as devices 217 or 218. Alternatively, server 214 may communicate with users via a wireless device (not shown) or a wireline connection, such as telephone 219, using, for example, voice signals, an interactive voice response (IVR), a voice response unit (VRU), or dual tone multi-frequency (DTMF) tones. Telephone 219 may be coupled to public switched telephone network (PSTN) 220.

[0030] Memory 221 may be used to store information, such as user account data, vehicle data, vehicle monitoring unit information, or street mapping data. Server 214 may access data stored on memory 221 and may store data to memory 221. Users may access memory 221, for example, to enter, update, or edit account data, via terminals or computers 217 and 218. Memory 221 may be internal or external to server 214 and may be located near to or remote from server 214. Communication between monitoring unit 201 and server 214 may be via cellular network 204, data network 207 and/or communication satellite network 208 depending upon availability of each network, the urgency of the message, and/or user configuration.

[0031] Vehicle monitoring unit 201 may transmit reports to server 214, such as driving conditions, vehicle operation parameters, or violations of operating requirements or limitations. Server 214 may then take action to record, report and/or mentor this behavior. For example, a user may configure server 214 to take certain action upon detecting that vehicle 202 is speeding. Server 214 may command monitoring unit 201 to broadcast warnings, such as audible messages or tones or visual lights or text, to the driver of vehicle 202. Additionally, server 214 may report the wireless device use to the driver's parent, supervisor, fleet manager or other authority. Such vehicle operation violations may trigger any number of actions preselected by the user and/or default actions in server 214.

[0032] The user may configure server 214 to send warning feedback to vehicle 202 upon detection of a potentially unsafe driving condition, such as speeding, driving the wrong way, or other conflicts with street mapping data. Such messages may warn the driver of the type of violation and/or direct the driver to discontinue the action or violation. Server 214 may take further action to warn or mentor the driver, notify a supervisor, or otherwise document the event as appropriate. Server 214 may also provide a report or notification to a supervisor or authority of the potentially unsafe driving conditions, such as by calling a fleet manager or parent via telephone 219 or by sending an email or text message to the supervisor.

[0033] Driver performance may be measured using vehicle monitoring equipment that is installed in a vehicle and collects information, such as the vehicle's speed, acceleration, and location. The unit may capture data identifying where the vehicle is driven, when the vehicle is driven, and how the vehicle is driven (i.e. driver performance). One embodiment of a vehicle monitoring unit is described in U.S. patent application Ser. No. 11/805,237, entitled “System and Method for Monitoring Vehicle Parameters and Driver Behavior,” filed May 22, 2007, the disclosure of which is incorporated by reference herein in its entirety. The vehicle monitoring unit may receive inputs from internal and external sources and sensors such as accelerometers, geographic position locating systems, global positioning systems (GPS), vehicle on-board diagnostic systems, seatbelt sensors, wireless device, or cell phone use detectors, alcohol vapor detectors, or trans-dermal ethanol detection. The vehicle monitoring unit may be used to evaluate and grade driver behavior, as described in U.S. patent application Ser. No. 11/755,556, filed on May 30, 2007, entitled “System and Method for Evaluating Driver Behavior,” the disclosure of which is hereby incorporated by reference herein in its entirety. The vehicle monitoring unit may also be used to provide feedback and mentoring to the driver in order improve the driver's performance and driving behavior, such as described in U.S. patent application Ser. No. 11/768,056, filed on Jun. 25, 2007, entitled “System and Method for Monitoring and Improving Driver Behavior,” the disclosure of which is hereby incorporated by reference herein in its entirety.

[0034] In one embodiment, vehicle monitoring unit 101 (FIG. 1) may evaluate a driver's performance based upon the operation of vehicle 102 compared to data in street mapping database 121. For example, the speed of vehicle 102 may be compared to posted speeds, road conditions, or traffic conditions stored in street mapping database 121, or the heading of vehicle 102 may be compared to traffic direction data stored in street mapping database 121. If vehicle monitoring unit 101 detects a violation of an operating parameter, then the vehicle monitoring unit may broadcast a warning or other feedback to the driver. In one embodiment, if a vehicle speed that is more than a posted speed stored in street mapping database 121, then a speeding warning is broadcast to the driver. In another embodiment, if a vehicle speed that is too fast for an expected road or traffic condition stored in street mapping database 121, then an audible and/or visual warning or other mentoring feedback may be broadcast to the driver. In another embodiment, if vehicle 102 is driving on a street in the wrong direction compared to a driving direction stored in street mapping database 121, then another audible and/or visual warning or other mentoring feedback may be broadcast to the driver. In addition to such driver warnings, reports or notification may be sent to third parties, such as a supervisor, fleet manager, or parent.

[0035] In known driver warning and feedback systems, when a driving violation or alert condition is detected, an audible and/or visual warning is broadcast to the driver noting the type of violation, such as speeding, but the underlying data that triggers the alert is not presented to the driver. For example, if a posted speed of 45 MPH is stored in a street mapping database for a particular street, and a vehicle is traveling at 50 MPH on that street, then the vehicle monitoring unit may broadcast an audible and/or visual speeding warning to the driver and may instruct or recommend to the driver to reduce speed. However, in known driver warning and feedback systems, the vehicle monitoring unit does not identify the underlying data to the driver, such as the posted speed limit stored in the street mapping database. In the example above, when the vehicle monitoring unit determines that the vehicle speed is greater than a posted speed limit stored in a street mapping database, a warning is broadcast, but neither the posted speed limit nor the amount of the violation—such as a number of miles-per-hour or a percentage that the actual speed is exceeding a posted speed limit in the database—are presented to the driver. Accordingly, if the posted speed limit data in the street mapping database is in error, then the driver will be improperly warned or reported for a speeding violation.

[0036] FIG. 3 illustrates a flowchart for an exemplary embodiment of a method for using street mapping data. The method illustrated in FIG. 3 may be implemented, for example, using vehicle monitoring unit 101 or 201, but is not intended to be limited to such configurations. Moreover, it will be understood that the steps illustrated in FIG. 3 may be performed in the order indicated, or in any other order, or simultaneously, or in conjunction with other steps or methods. In step 301, a vehicle's current location is determined. The vehicle's location may be determined using, for example, a geographic position locating system, a satellite-based positioning system, a GPS, or a vehicle monitoring unit. The vehicle location may be associated with specific street or roadway. In step 302, a stored posted speed limit for the vehicle's current location is determined. The stored posted speed limit may be retrieved from a street mapping database, such as database 121 (FIG. 1), using the current vehicle location. The stored posted speed limit may be a speed limit for a street or roadway on which the vehicle is traveling. In step 303, the current speed of the vehicle is determined. The vehicle's speed may be determined, for example, using a vehicle monitoring unit, a GPS, a vehicle navigation system, a vehicle speedometer, or determined from data collected from a vehicle on-board diagnostic system. In step 304, the vehicle's current speed is compared to the stored posted speed limit. In step 305, an evaluation is made to determine if the current vehicle speed exceeds the stored posted speed limit.

[0037] If the current vehicle speed is at or below the stored posted speed limit, then the process returns to step 301. If the current vehicle speed is above the stored posted speed limit, then the process moves to step 306 in which a warning is displayed to the driver. Alternatively, or additionally, a warning or notice may be sent to a third party, such as a fleet manager, parent, supervisor, or other authority. The driver warning may be a visual display and/or an audible message, horn or other noise and/or in conjunction with a tactile alert. In step 307, the stored posted speed is displayed to the driver. If the driver believes that the stored posted speed is incorrect, then in step 308, the driver may send an indication that the stored posted speed limit is erroneous. The indication from the driver may be, for example, a signal or input to the driver interface 120 (FIG. 1) that indentifies a correct or current posted speed limit (step 309), or merely a signal or input that the stored posted speed limit is incorrect. In one embodiment, if a vehicle monitoring unit displays a speeding violation warning to the driver, and the driver believes that he is driving at or under the speed limit, then the driver can compare the displayed stored posted speed limit with an actual observation of a posted speed limit on the street or roadway. The driver may input the correct speed limit into the unit, or the driver may press a button, for example, on vehicle monitoring unit 101 or 201, to indicate that a speeding warning is erroneous. In step 310, the stored posted speed limit may be updated. For example, a stored posted speed limit in database 121 (FIG. 1) may be updated. In another embodiment, the corrected posted speed limit may be transmitted to a third party, such as a service provider for use in updating a master database. In the alternative, the driver may be exceeding the actual posted speed and notice that the device is not alerting them to the speed overage. The device may display an erroneously high speed in which case the driver may depress a button or other possible alert mechanisms so that the speed limit database may be updated.

[0038] FIG. 4 illustrates one embodiment of a street mapping display that may be used, for example, to display vehicle location information to a driver. Display 400 may be used, for example, in connection with a GPS or other geographic position locating system to display vehicle location information. Vehicle location is shown by icon 401 located in the middle of display 400. Streets, railroad tracks, rivers, lakes, and other geographic features are displayed on display 400. Heading information may be displayed, for example, using compass 402, which points to North, or using heading direction 403, which displays an approximate or exact vehicle heading. A current street name 404 may also be displayed to the driver. Other current location information, such as a city or county name, may also or additionally be displayed. Routing information 405 may be shown on display 400, such as upcoming turn warning 406, distance to destination 407, and time to destination 408. As is well known, other location, route and destination information may be displayed, such as a turn list or maneuver list for a selected route, an elapsed route timer, alternate routing options, display zoom and pan controls, and current vehicle speed display. In the event that the system has a display, listing the posted speed limit as well as the vehicle's actual speed and/or the differential is desirable. The displayed information may also be provided to the driver in an audible format, such as a spoken message that recites a current street, current city, upcoming turn or routing directions, or warnings.

[0039] Display 400 illustrates the typical information provided in a GPS display. However, additional data may be available from a street mapping database, such as posted speed limits, normal traffic direction, expected traffic conditions, or traffic restrictions. This additional information is not provided to the driver in known GPS or navigation systems. FIG. 5 illustrates additional information that may be provided to a driver. Display 500 provides current location 501, which may be a current street address, city, latitude/longitude, and/or other geographic location or coordinates. Other information for the current street, road or other thoroughfare may be displayed, such as the number of traffic lanes 502, a traffic direction 503, which may designate if a street, lane or other portion of a street is two-way, one-way, and/or what direction traffic normally flows. The posted speed limit 504, known construction conditions 505, and general road condition 506 may also be displayed. The street mapping data shown in display 500 may be obtained by querying a vehicle-based street mapping database, such as database 121 (FIG. 1), or retrieved wirelessly from an external database, such as database 221 (FIG. 2).

[0040] In one embodiment, the street mapping data may be used to evaluate driver behavior and performance, such as to detect speeding conditions. For example, when the vehicle's current speed exceeds the posted speed limit that is stored in the street mapping database for the current location, a warning may be issued to the driver. Additionally or alternatively, a notice may be sent to a third party when a speeding or other violation occurs. A grace period, such as a number of seconds or minutes, may be used before reporting the violation to a third party in order to allow the driver to correct the violation and thereby avoid third-party notification.

[0041] FIG. 6 illustrates one embodiment of a driver display during a violation, such as exceeding a posted speed limit. Display 600 includes visual warning notice 601 that may overlay or replace the usual location information. Warning notice 601 may be accompanied by or replaced by an audible alarm, horn, tone, or recorded or spoken message. Warning notice 601 preferably identifies a violated parameter, such as a posted speed limit or street travel direction. Additional violation information 602 may be presented to the user. For example, the posted speed limit and/or current vehicle speed may be displayed during a speeding violation condition. Due to data entry error, changes in signage, or temporary road conditions, the actual posted speed limit on the street may be different than the stored posted speed limit in the street mapping database. For example, if the posted speed limit data that is stored in the street mapping database was entered as 35 MPH, but the actual posed speed limit is 45 MPH, then the driver will be warned of a speeding condition while driving at a legal speed between 36 MPH and 45 MPH. Existing navigation systems do not provide users with the capability to correct or report such errors. In one embodiment, display 600 provides the driver with an option, such as update button 603, to enter correct data or to report errors.

[0042] FIG. 7 illustrates a data correction and/or error reporting display 700. In one embodiment, the driver may select update button or feature 603 to cause display 600 to change to display 700. Displays 400, 500, 600, 700 may be touch screens that allow a user to select features, such as 603, by touching the feature. Alternatively, the user may highlight or otherwise selecting the feature using buttons or switches external to the display or using other inputs to the display, such as a cursor or other highlighting tool. Display 700 displays the stored street mapping data to the driver and allows the driver to identify and report errors and to confirm correct entries in the street mapping data. Like display 500, the street mapping data shown in display 700 may be obtained by querying a vehicle-based street mapping database, such as database 121 (FIG. 1), or retrieved wirelessly from an external database, such as database 221 (FIG. 2).

[0043] In one embodiment, the posted speed data 504 may be highlighted or otherwise selected automatically or manually in display 700. Options 701-703 may be provided to the driver. Confirm option 701 may be selected by the driver to confirm that the stored posted speed limit data 504 in the street mapping database is correct. Update option 702 may be selected by the user to initiate a procedure to enter corrected posted speed limit data. For example, after selecting update feature 702, the driver may be presented with a screen or field in which the correct posted speed may be entered. The corrected data may then be used to update or evaluate the street mapping database. Report error option 703 may be used to send a notice to a third party, such as a fleet manager, navigation system manufacturer, or street mapping data provider, that identifies the posted speed limit error. Report error 703 may be used to simply identify that an error may be present or to enter a corrected posted speed limit.

[0044] The third party may use the reported error information in a number of ways, such as collecting error reports from a plurality of drivers until the number of error reports for a particular data entry reach a preselected level. For example, instead of correcting the street mapping data after one error report, the third party may conduct a visual inspection of the location to verify the posted speed limit before editing the street mapping database. Alternatively, the third party may wait until multiple drivers report the error before correcting the database, such as waiting for 25, 50 or 100 error reports or some other number of statistically significant error reports from different drivers or vehicles before the posted speed limit stored in the street mapping is changed or updated. This would allow the third party to identify “hot spots” of frequent error reports. The third party may be, for example, a monitoring service operator, street mapping data provider, fleet manager, or other person or entity that is responsible for maintaining the street mapping database. Additionally, individuals that report database speed errors may have their system adjusted to a temporary higher speed limit until the speed database error can be assessed and corrected if necessary. At that point the temporary speed adjustment would default the database speed. Each reported speed inaccuracy would also be reported to track potential excessive or fraudulent speed database errors.

[0045] It will be understood that displays 500 and 700 may be available at anytime and not just during warning conditions. For example, a user may highlight or select vehicle icon 401 or street name 404 (FIG. 4) to request street mapping data 700. Once the street mapping data display 700 is shown, the driver may review the data and verify the data or correct or report errors in the data. Additionally, it will be understood that the correctable or reportable errors are not limited to posted speed limits, but that any street mapping database field may be reviewed and corrected using the embodiments described herein. Moreover, other warnings may also be provided to the driver. For example, if the street mapping data shows that a particular street is configured for one-way traffic in a southern direction, and the vehicle is traveling north-bound on that street, then a warning may be provided to the driver, similar to what is shown in display 600 (FIG. 6). The warning may display “Warning: Traffic Direction,” for example. If the driver believes that the warning is in error, the driver may select display 500 or 700 to view and possibly correct traffic direction 503.

[0046] Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present invention, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present invention. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.