Practically all systems falling into the category of “IVHS” have a need for computerized spatial data, whether they be in-car navigation devices, dispatching or fleet management services or route guidance systems. System developers are faced with having to build customized spatial databases as an additional cost and headache beyond hardware, software and marketing challenges.Despite the wide range of functions that various types of IVHS systems perform, there is a large amount of overlap in database content required to support these systems. The author proposes an elemental definition of a generic database supporting most IVHS functions.Several Federal agencies provide pieces of a generic IVHS spatial data infrastructure. The paper reviews these database resources from the standpoints of basic needs of various IVHS components, missions of database providers and of various IVHS and mapping committees and study groups. Models for provision of an IVHS database infrastructure are outlined.