Populating geospatial database for onboard intelligent vehicle applications

• US 20030023614A1
• Filed: 07/17/2002
• Published: 01/30/2003
• Est. Priority Date: 07/18/2001
• Status: Active Grant

• Current Assignee: Regents of The University of Minnesota (University of Minnesota), University of Minnesota
• Original Assignee: Regents of The University of Minnesota (University of Minnesota)
• Inventors: Newstrom, Bryan J., Donath, Max, Shankwitz, Craig R.
• Granted Patent: US 7,552,008 B2
• Time in Patent Office: Days
• US Class Current: 707/104.1
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

The present invention is an apparatus and a method for populating a geospatial road database. In accordance with one embodiment of the invention, a geospatial database management system is mounted on a host vehicle and manages geospatial data relating to a travel path for the host vehicle. The embodiment further comprises a geospatial database to store data elements indicative of objects and their location. The embodiment further comprises a database manager component to maintain the geospatial database and receive database queries from a driver assist subsystem. The embodiment further comprises a database developer component is configured to develop the data elements in the geospatial database and receive database inputs from a lane level digitizer subsystem configured to receive inputs from a plurality of sensors mounted on the host vehicle. Finally, the embodiment comprises the plurality of sensors may include a Digital Global Positioning System, a digital camera, and a scanning range sensor. The present invention includes a method for implementing the steps performed by the embodiment of the apparatus.

Claims

1. A geospatial database generation system (GDGS), mounted on a host vehicle, generating geospatial data relating to travel paths having one or more lanes, comprising:

a database developer component including a lane level data system configured to receive inputs from a plurality of sensors mounted on the host vehicle, and to develop data elements in the geospatial databased based on sensor inputs, the data elements being indicative of objects and a location of the objects in three dimensional space, the objects having a lane-level resolution.

2. The GDGS of claim 1, wherein the lane level data system generates the data elements such that the location has an accuracy of approximately one decimeter or less.

3. The GDGS of claim 1, wherein the plurality of sensors includes a location sensor sensing a location in three dimensional space.

4. The GDGS of claim 3, wherein the plurality of sensors includes a Differential GPS (DGPS) receiver.

5. The GDGS of claim 3, wherein the plurality of sensors includes an object sensor sensing an object.

6. The GDGS of claim 5, wherein the host vehicle is a lane marking machine configured to mark the one or more lanes along the travel path.

7. The GDGS of claim 6, wherein the lane marking machine has an applicator device that applies a marking material to mark the one or more lanes.

8. The GDGS of claim 7, wherein the object sensor includes an actuation sensor sensing actuation of the applicator device.

9. The GDGS of claim 7, wherein the location sensor is mounted on the applicator device to sense a location of the applicator device in three dimensional space.

10. The GDGS of claim 7, wherein the lane marking machine has a plurality of applicator devices that apply marking material at a plurality of locations along the travel path.

11. The GDGS of claim 10, wherein the location sensor includes a plurality of location sensors, one sensor being mounted on each of the applicator devices.

12. The GDGS of claim 5, wherein the object sensor includes a digital camera.

13. The GDGS of claim 5, wherein the object sensor includes a scanning range sensor.

14. The GDGS of claim 5, wherein the location sensor is spatially offset from the object sensor and wherein the database developer accounts for the offset in generating the data elements.

15. The GDGS of claim 5, wherein the plurality of sensors includes a plurality of object sensors and a single location sensor.

16. The GDGS of claim 5, wherein the database developer component is configured to generate the data elements from sensor inputs from the plurality of sensors as data objects having an attribute portion and a spatial data portion, the attribute portion including attributes indicative of the data object and the spatial data portion including data indicative of the location of the object in three dimensional space.

17. The GDGS of claim 16, wherein the sensor inputs include a LaneBoundary object representative of a roadway lane boundary.

18. The GDGS of claim 16, wherein the sensor inputs include a RoadShoulder object representative of a roadway shoulder.

19. The GDGS of claim 16, wherein the sensor inputs include a RoadIsland object representative of a roadway island.

20. The GDGS of claim 16, wherein the sensor inputs include a LaneCenter object representative of a roadway lane center.

21. The GDGS of claim 16, wherein the sensor inputs include objects representative of structures adjacent to the travel paths.

22. The GDGS of claim 21, wherein the sensor inputs are representative of one or more of mailboxes, jersey barriers, guard rails, bridge abutments, tunnel walls, ground plane and ceiling, curbs, curb cutouts, fire hydrants, light posts, traffic signal posts, sign and sign posts, pavement edge, drop-off, and other of the structures adjacent to the travel paths.

23. The GDGS of claim 16, wherein one or more of the sensor inputs are calculated from one or more other of the sensor inputs.

24. A method of populating a geospatial database in a geospatial database management system (GDMS), mounted on a host vehicle, managing geospatial data relating to travel paths having one or more lanes, comprising:

developing data elements in the geospatial database from inputs generated by a plurality of sensors mounted on the host vehicle; and

storing the data elements, indicative of objects and a location of the objects in three dimensional space, in the geospatial database.

25. The method of claim 24, wherein developing the data elements comprises:

developing the data elements in the geospatial database as data objects having an attribute portion and a spatial data portion, the attribute portion including attributes indicative of the data object and the spatial data portion including data indicative of the location of the object in three dimensional space.

26. The method of claim 24, wherein developing data elements comprises:

receiving object sensor inputs from object sensor; and

receiving location sensor inputs from a location sensor indicative of a location in three dimensional space.

27. The method of claim 26, wherein developing data elements further comprises:

calculating an offset between the location sensor and the object sensor.