The Indiana Geological Survey's Geologic Names Database

Many geological repositories include large amounts of stratigraphic data. One problem faced by managers of these archives is locating correct stratigraphic nomenclature to complement their data. The Geologic Names Committee (GNC) of the Indiana Geological Survey (IGS) is addressing this problem by developing an online database of geologic names officially recognized by the IGS. The database will facilitate labeling stratigraphic data in IGS digital and paper archives, aid IGS researchers in locating current geologic nomenclature for their publications, and provide Web-based access to IGS geologic nomenclature to a broad spectrum of users from academia, industry, government, and the general public. The GNC, with assistance from the IGS Information Technology Section, focused initial efforts on entering current Paleozoic nomenclature into the database and designing Web-based access to these data. The database and Web site allows users to access information about specific units by entering a formal stratigraphic name, abandoned name, or miscellaneous unofficial name such as “Indiana Limestone” (the Salem Limestone, Mississippian). Options to select units by specifying system(s) and stratigraphic rank(s) allow users to retrieve data for more than one unit and view the data in alphabetic or stratigraphic order. The Web display shows IGS nomenclature for the selected unit(s), names of equivalent units, miscellaneous and abandoned names, and applicable higher-rank stratigraphic terms for each of the five Indiana areas delineated in the Midwestern Basins and Arches Region (COSUNA Project) to emphasize geographic changes in rank, lithic term, and assignment to higher-ranked units.

IGS GNC plans to continue development of the database and Web site to better serve users and maintain compatibility with the GEOLEX database developed by the U.S. Geological Survey. Current plans include adding type localities, unit name histories, reference sections, lithologic descriptions, and correlations to the database.