Geographic Names Information System

Last updated

The logo of the United States Geological Survey (USGS) USGS logo green.svg
The logo of the United States Geological Survey (USGS)

The Geographic Names Information System (GNIS) is a database of name and location information about more than two million physical and cultural features throughout the United States and its territories; the associated states of the Marshall Islands, Federated States of Micronesia, and Palau; and Antarctica. It is a type of gazetteer. It was developed by the United States Geological Survey (USGS) in cooperation with the United States Board on Geographic Names (BGN) to promote the standardization of feature names.

Contents

Data were collected in two phases. [1] Although a third phase was considered, which would have handled name changes where local usages differed from maps, it was never begun. [2]

The database is part of a system that includes topographic map names and bibliographic references. The names of books and historic maps that confirm the feature or place name are cited. Variant names, alternatives to official federal names for a feature, are also recorded. Each feature receives a permanent, unique feature record identifier, sometimes called the GNIS identifier. [3] The database never removes an entry, "except in cases of obvious duplication." [4]

Original purposes

The GNIS was originally designed for four major purposes: to eliminate duplication of effort at various other levels of government that were already compiling geographic data, to provide standardized datasets of geographic data for the government and others, to index all of the names found on official U.S. government federal and state maps, and to ensure uniform geographic names for the federal government. [5]

Phase 1

Phase 1 lasted from 1978 to 1981, with a precursor pilot project run over the states of Kansas and Colorado in 1976, and produced 5 databases. [6] [1] [7] It excluded several classes of feature because they were better documented in non-USGS maps, including airports, the broadcasting masts for radio and television stations, civil divisions, regional and historic names, individual buildings, roads, and triangulation station names. [8]

The databases were initially available on paper (2 to 3 spiral-bound volumes per state), on microfiche, and on magnetic tape encoded (unless otherwise requested) in EBCDIC with 248-byte fixed-length records in 4960-byte blocks. [9]

The feature classes for association with each name included (for examples) "locale" (a "place at which there is or was human activity" not covered by a more specific feature class), "populated place" (a "place or area with clustered or scattered buildings"), "spring" (a spring), "lava" (a lava flow, kepula, or other such feature), and "well" (a well). [10] Mountain features would fall into "ridge", "range", or "summit" classes. [11]

A feature class "tank" was sometimes used for lakes, which was problematic in several ways. [12] This feature class was undocumented, and it was (in the words of a 1986 report from the Engineer Topographic Laboratories of the United States Army Corps of Engineers) "an unreasonable determination", with the likes of Cayuga Lake being labelled a "tank". [12] The USACE report assumed that "tank" meant "reservoir", and observed that often the coordinates of "tanks" were outside of their boundaries and were "possibly at the point where a dam is thought to be". [12]

National Geographic Names database

The National Geographic Names database (NGNDB [1] hereafter) was originally 57 computer files, one for each state and territory of the United States (except Alaska which got two) plus one for the District of Columbia. [13] The second Alaska file was an earlier database, the Dictionary of Alaska Place Names that had been compiled by the USGS in 1967. [13] A further two files were later added, covering the entire United States and that were abridged versions of the data in the other 57: one for the 50,000 most well known populated places and features, and one for most of the populated places. [14] The files were compiled from all of the names to be found on USGS topographic maps, plus data from various state map sources. [13]

In phase 1, elevations were recorded in feet only, with no conversion to metric, and only if there was an actual elevation recorded for the map feature. [15] They were of either the lowest or highest point of the feature, as appropriate. [15] Interpolated elevations, calculated by interpolation between contour lines, were added in phase 2. [15]

Names were the official name, except where the name contained diacritic characters that the computer file encodings of the time could not handle (which were in phase 1 marked with an asterisk for update in a later phase). [16] Generic designations were given after specific names, so (for examples) Mount Saint Helens was recorded as "Saint Helens, Mount", although cities named Mount Olive, not actually being mountains, would not take "Mount" to be a generic part and would retain their order "Mount Olive". [16]

The primary geographic coordinates of features which occupy an area, rather than being a single point feature, were the location of the feature's mouth, or of the approximate center of the area of the feature. [17] Such approximate centers were "eye-balled" estimates by the people performing the digitization, subject to the constraint that centers of areal features were not placed within other features that are inside them. [18] alluvial fans and river deltas counted as mouths for this purpose. [17] For cities and other large populated places, the coordinates were taken to be those of a primary civic feature such as the city hall or town hall, main public library, main highway intersection, main post office, or central business district regardless of changes over time; [17] [lower-alpha 1] these coordinates are called the "primary point". [lower-alpha 2]

Secondary coordinates were only an aid to locating which topographic map(s) the feature extended across, and were "simply anywhere on the feature and on the topographic map with which it is associated". [17] [22] [23] River sources were determined by the shortest drain, subject to the proxmities of other features that were clearly related to the river by their names. [23]

USGS Topographic Map Names database

The USGS Topographic Map Names database (TMNDB [24] hereafter) was also 57 computer files containing the names of maps: 56 for 1:24000 scale USGS maps as with the NGNDB, the 57th being (rather than a second Alaska file) data from the 1:100000 and 1:250000 scale USGS maps. [25] Map names were recorded exactly as on the maps themselves, with the exceptions for diacritics as with the NGNDB. [26]

Unlike the NGNDB, locations were the geographic coördinates of the south-east corner of the given map, except for American Samoa and Guam maps where they were of the north-east cornder. [25]

The TMNDB was later renamed the Geographic Cell Names database (GCNDB [24] hereafter) in the 1990s. [24]

Generic database

The Generic database was in essence a machine-readable glossary of terms and abbreviations taken from the map sources, with their definitions, grouped into collections of related terms. [27]

National Atlas database

The National Atlas database was an abridged version of the NGNDB that contained only those entries that were in the index to the USGS National Atlas of the United States, with the coördinates published in the latter substituted for the coördinates from the former. [27]

Board on Geographic Names database

The Board on Geographic Names database was a record of investigative work of the USGS Board on Geographic Names' Domestic Names Committee, and decisions that it had made from 1890 onwards, as well as names that were enshrined by Acts of Congress. [28] Elevation and location data followed the same rules as for the NGNDB. [29] So too did names with diacritic characters. [29]

Phase 2

Phase 2 was broader in scope than phase 1, extending the scope to a much larger set of data sources. [1] It ran from the end of phase 1 and had managed to completely process data from 42 states by 2003, with 4 still underway and the remaining 4 (Alaska, Kentucky, Michigan, and New York) awaiting the initial systematic compilation of the sources to use. [1]

Many more feature classes were included, including abandoned Native American settlements, ghost towns, railway stations on railway lines that no longer existed, housing developments, shopping centers, and highway rest areas. [2]

The actual compilation was outsourced by the U.S. government, state by state, to private entities such as university researchers. [1]

Antarctica Geographic Names database

The Antarctica Geographic Names database (AGNDB [24] hereafter) was added in the 1990s and comprised records for BGN-approved names in Antarctica and various off-lying islands such as the South Orkney Islands, the South Shetland Islands, the Balleny Islands, Heard Island, South Georgia, and the South Sandwich Islands. [24] It only contained records for natural features, not for scientific outposts. [24]

Additional media

The media on which one could obtain the databases were extended in the 1990s (still including tape and paper) to floppy disc, over FTP, and on CD-ROM. [30] The CD-ROM edition only included the NGNDB, the AGNDB, the GCNDB, and a bibliographic reference database (RDB); but came with database search software that ran on PC DOS (or compatible) version 3.0 or later. [30] The FTP site included extra topical databases: a subset of the NGNDB that only included the records with feature classes for populated places, a "Concise" subset of the NGNDB that listed "major features", and a "Historical" subset that included the features that no longer exist. [30]

Populated places

There is no differentiation amongst different types of populated places. [31] In the words of the aforementioned 1986 USACE report, "[a] subdivision having one inhabitant is as significant as a major metropolitan center such as New York City". [31]

In comparing GNIS populated place records with data from the Thematic Mapper of the Landsat program, researchers from the University of Connecticut in 2001 discovered that "a significant number" of populated places in Connecticut had no identifiable human settlement in the land use data and were at road intersections. [32] They found that such populated places with no actual settlement often had "Corner" in their names, and hypothesized that either these were historical records or were "cartographic locators". [32] In surveying in the United States, a "Corner" is a corner of the surveyed polygon enclosing an area of land, whose location is, or was (since corners can become "lost" [33] or "obliterated" [34] ), marked in various ways including with trees known as "bearing trees" [35] ("witness trees" in older terminology [36] ) or "corner monuments". [37]

From analysing Native American names in the database in order to compile a dictionary, professor William Bright of UCLA observed in 2004 that some GNIS entries are "erroneous; or refer to long-vanished railroad sidings where no one ever lived". [38] Such false classifications have propagated to other geographical information sources, such as incorrectly classified train stations appearing as towns or neighborhoods on Google Maps. [39]

Name changes

The GNIS accepts proposals for new or changed names for U.S. geographical features through The National Map Corps. The general public can make proposals at the GNIS web site and can review the justifications and supporters of the proposals.[ citation needed ]

The usual sources of name change requests are an individual state's board on geographic names, or a county board of governors. [40] This does not always succeed, the State Library of Montana having submitted three large sets of name changes that have not been incorporated into the GNIS database. [41]

Conversely, a group of middle school students in Alaska succeeded, with the help of their teachers, a professor of linguistics, and a man who had been conducting a years-long project to collect Native American placenames in the area, in changing the names of several places that they had spotted in class one day and challenged for being racist, including renaming "Negrohead Creek" to an Athabascan name Lochenyatth Creek and "Negrohead Mountain" to Tl'oo Khanishyah Mountain, both of which translate to "grassy tussocks" in Lower Tanana and Gwichʼin respectively. [42] Likewise, in researching a 2008 book on ethnic slurs in U.S. placenames Mark Monmonier of Syracuse University discovered "Niger Hill" in Potter County, Pennsylvania, an erroneous transcription of "Nigger Hill" from a 1938 map, and persuaded the USBGN to change it to "Negro Hill". [43]

Removal of racial and ethnic slurs

In November 2021, the United States Secretary of the Interior issued an order instructing that "Squaw" be removed from usage by the U.S. federal government. [44] Prior efforts had included a 1962 replacement of the "Nigger" racial pejorative for African Americans with "Negro" and a 1974 replacement of the "Jap" racial pejorative for Japanese Americans with "Japanese". [44] [40] [45]

In 2015, a cross-reference of the GNIS database against the Racial Slur Database had found 1441 racial slur placenames, every state of the United States having them, with California having 159 and the state with the most such names being Arizona. [40] [45] One of the two standard reference works for placenames in Arizona is Byrd Howell Granger's 1983 book Arizona's Names: X Marks the Place, which contains many additional names with racial slurs not in the GNIS database. [40] [46] Despite "Nigger" having been removed from federal government use by Stewart Udall, its replacement "Negro" still remained in GNIS names in 2015, as did "Pickaninny", "Uncle Tom", and "Jim Crow" and 33 places named "Niggerhead". [40] There were 828 names containing "squaw", including 11 variations on "Squaw Tit" and "Squaw Teat", contrasting with the use of "Nipple" in names with non-Native American allusions such as "Susies Nipple". [40]

Other authorities

See also

Notes

  1. "Additional guidelines were suggested for determining the center of large populated places, such as the location of the city hall or town hall, main post office, main library, central business district, or main intersection." [17]
  2. "Primary Point: The official feature location is a single point to which the official feature name is associated in order to ensure positive and unique identification and association, also referred to as the primary point. The location is determined by the authoritative source and is approved or recognized as official by the U.S. Board on Geographic Names by decision or by policy delegation to the authoritative source. The placing of the location point is governed by policies of the Board as defined in the Names Data Users Guide and GNIS metadata, generally at or near the geographic center, but there are exceptions for certain classes of features." [19] "Question 17: In the GNIS database, the Primary coordinate values for communities are taken at the center of the "original" community meaning the city hall, main post office, main intersection, etc. [20] "Primary Point: The official feature location is a single point to which the official feature name is associated in order to ensure positive and unique identification and association, also referred to as the primary point. The location is determined by the authoritative source and is approved or recognized as official by the U.S. Board on Geographic Names by decision or by policy delegation to the authoritative source. The placing of the location point is governed by policies of the Board as defined in the Names Data Users Guide and GNIS metadata, generally at or near the geographic center, but there are exceptions for certain classes of features. For example, the official feature location of flowing bodies of water (streams, rivers, creeks, etc.) or trending linear features (valleys, gulchs, gullys, hollows, etc.) is at the mouth. A geographic feature may have only one official location regardless of size, extent, composition, structure, or boundaries. The location point is coincident with, but in addition to and independent of, any other geospatial representation or boundary definition that may be attached to the feature in other datasets. Linear and aerial features may have secondary points as defined in the Names Data Users Guide and GNIS metadata. Locations are stored in the Geographic Names Information System as latitude and longitude in decimal degrees to seven places." [21]

Related Research Articles

<span class="mw-page-title-main">United States Board on Geographic Names</span> US geographic naming government agency

The United States Board on Geographic Names (BGN) is a federal body operating under the United States Secretary of the Interior. The purpose of the board is to establish and maintain uniform usage of geographic names throughout the federal government of the United States.

<span class="mw-page-title-main">Zzyzx, California</span> Unincorporated community in California, United States

Zzyzx, formerly Soda Springs, is an unincorporated community in San Bernardino County, California, within the boundaries of the Mojave National Preserve, managed by the National Park Service (NPS), an agency of the U.S. Department of Interior, as public land. It is the former site of the Zzyzx Mineral Springs and Health Spa and now the site of the Desert Studies Center. The site is also the location of Lake Tuendae, originally part of the spa, and now a refuge habitat of the endangered Mohave tui chub.

<i>The National Map</i> USGS topographical information

The National Map is a collaborative effort of the United States Geological Survey (USGS) and other federal, state, and local agencies to improve and deliver topographic information for the United States. The purpose of the effort is to provide "...a seamless, continuously maintained set of public domain geographic base information that will serve as a foundation for integrating, sharing, and using other data easily and consistently".

The GEOnet Names Server (GNS), sometimes also referred to in official documentation as Geographic Names Data or geonames in domain and email addresses, is a service that provides access to the United States National Geospatial-Intelligence Agency's (NGA) and the US Board on Geographic Names's (BGN) database of geographic feature names and locations for locations outside the US. The database is the official repository for the US Federal Government on foreign place-name decisions approved by the BGN. Approximately 20,000 of the database's features are updated monthly. Names are not deleted from the database, "except in cases of obvious duplication". The database contains search aids such as spelling variations and non-Roman script spellings in addition to its primary information about location, administrative division, and quality. The accuracy of the database had been criticised.

This is a list of properties and historic districts in Tennessee that are listed on the National Register of Historic Places. There are over 2,000 in total. Of these, 29 are National Historic Landmarks. Each of Tennessee's 95 counties has at least one listing.

The United States Census Bureau defines a place as a concentration of population which has a name, is locally recognized, and is not part of any other place. A place typically has a residential nucleus and a closely spaced street pattern, and it frequently includes commercial property and other urban land uses. A place may be an incorporated place or it may be a census-designated place (CDP). Incorporated places are defined by the laws of the states in which they are contained. The Census Bureau delineates CDPs. A small settlement in the open countryside or the densely settled fringe of a large city may not be a place as defined by the Census Bureau. As of the census, 26% of the people in the United States lived outside of places.

<span class="mw-page-title-main">Wind River (Washington)</span> River in Washington, United States

The Wind River is a tributary of the Columbia River, in the U.S. state of Washington. Its entire course of 30 miles (48 km) lies within Skamania County. Crusattes River is an old variant name.

<span class="mw-page-title-main">Tilton River</span> River in Washington, United States

The Tilton River is a tributary of the Cowlitz River, in the U.S. state of Washington. Named for territorial surveyor James Tilton, it flows for about 29 miles (47 km), entirely within Lewis County.

<span class="mw-page-title-main">National Register of Historic Places listings in Carbon County, Wyoming</span>

This is a list of the National Register of Historic Places listings in Carbon County, Wyoming.

<span class="mw-page-title-main">United States Geological Survey</span> Scientific agency of the United States government

The United States Geological Survey (USGS), founded as the Geological Survey, is an agency of the United States government whose work spans the disciplines of biology, geography, geology, and hydrology. The agency was founded on March 3, 1879, to study the landscape of the United States, its natural resources, and the natural hazards that threaten it. The agency also makes maps of extraterrestrial planets and moons based on data from U.S. space probes.

The Brassiere Hills are a pair of summits in the City and Borough of Juneau, Alaska, United States. It is located at the northern end of Taku Inlet, 4.5 miles (7.2 km) north of Taku Point and 18 miles (29 km) northeast of the city of Juneau. The peaks are 2,405 feet (733 m) and 2,360 feet (719 m) high and a stream named Zipper Creek runs between them.

<span class="mw-page-title-main">Elkhorn Creek (Marion County, Oregon)</span> River in Oregon, United States

Elkhorn Creek is a 7.6-mile (12 km) long stream in Marion County, Oregon, United States. Its source is on the northern edge of the Willamette National Forest, about 3.5 miles (5.6 km) north of Big Cliff Reservoir. The creek flows mostly west, receiving Big Twelve Creek, Buckhorn Creek, and Buck Creek all from the south, and it enters the Little North Santiam River just south of Elkhorn Woods Park, about 5 miles (8.0 km) north of the city of Gates. The stream's valley is surrounded by the western Cascade foothills, covered with coniferous trees characteristic of the Pacific Northwest, and lined with red alders at the water's edge. The creek supports runs of rainbow and coastal cutthroat trout, as well as Pacific giant salamanders. On September 30, 1996, a 6.4-mile (10.3 km) portion of the stream, from the mouth nearly to the source, was protected as part of the National Wild and Scenic Rivers System.

Buckskin Mountain is a 16-mile (26 km) mountain ridge that spans from Coconino County, Arizona to Kane County, Utah in the United States, that is divided almost equally between the two counties.

<span class="mw-page-title-main">Neepaulakating Creek</span> Tributary of Papakating Creek

Neepaulakating Creek is a 2.4-mile long (3.8 km) tributary of Papakating Creek in Wantage Township in Sussex County, New Jersey in the United States. It is one of three streams feeding the Papakating Creek, a major contributor to the Wallkill River. Although the stream was dammed in the 1950s to create Lake Neepaulin as the focal point of a private residential development, the stream did not receive a name until 2002. Residents chose a name that combined elements of the names "Neepaulin" and "Papakating", and submitted a proposal to the United States Board of Geographic Names. The name was approved in 2004.

Itak is a populated place situated in Pima County, Arizona, United States. Itak means "point of mountain" in the O'odham language. European settlers had referred to this place as Rocky Point at least through the early part of the twentieth century. On September 8, 1939, the Office of Indian Affairs petitioned the USGS to officially recognize the name of the location as Itak, as that was the name preferred by the local residents, and was more historical. On April 10, 1941, the Board on Geographic Names rendered its decision, officially naming the place Itak. It has an estimated elevation of 2,297 feet (700 m) above sea level.

References

  1. 1 2 3 4 5 6 Monmonier 2008, p. 30.
  2. 1 2 Monmonier 2008, p. 31.
  3. "United States Census County Based TIGER/Line 2009 Data Dictionary: Entity, Joins, Attributes and Domains". Archived from the original on June 27, 2014. Retrieved June 27, 2014.
  4. Cartographic Users Advisory Council (CUAC) (April 26–27, 2007). 2007 Agency Presentation Minutes. Reston, VA: United States Geological Survey (USGS). Archived from the original on January 11, 2014.
  5. Payne 1983, p. 1.
  6. Payne 1983, pp. 1, 3.
  7. Payne 1985, p. 2.
  8. Payne 1983, p. 18.
  9. Payne 1985, pp. 19–20.
  10. Payne 1983, p. 2022.
  11. Monmonier 2008, p. 32.
  12. 1 2 3 Heard 1986, p. 25.
  13. 1 2 3 Payne 1983, p. 3.
  14. Payne 1985, p. 4.
  15. 1 2 3 Payne 1983, p. 4.
  16. 1 2 Payne 1983, p. 6.
  17. 1 2 3 4 5 Payne 1983, p. 5.
  18. Heard 1986, pp. 4–5.
  19. "Geographic Names Information System (GNIS): Domestic Names - Metadata". U.S. Geological Survey. August 18, 2009. Archived from the original on February 6, 2012. Retrieved July 30, 2023.
  20. "Domestic Names - Frequently Asked Questions (FAQs) #17". U.S. Geological Survey. October 17, 2014. Archived from the original on March 18, 2015. Retrieved July 30, 2023.
  21. "GNIS States, Territories, Associated Areas of the United States Text Format for National tabular digital data". U.S. Geological Survey. 2017. Archived from the original on July 30, 2023. Retrieved July 30, 2023.
  22. Payne 1985, p. 7.
  23. 1 2 Heard 1986, p. 4.
  24. 1 2 3 4 5 6 USGS 1998, p. 1.
  25. 1 2 Payne 1983, p. 8.
  26. Payne 1983, p. 9.
  27. 1 2 Payne 1983, p. 11.
  28. Payne 1983, p. 13.
  29. 1 2 Payne 1983, p. 14.
  30. 1 2 3 USGS 1998, p. 2.
  31. 1 2 Heard 1986, p. 12.
  32. 1 2 McEathron et al. 2001, p. 5.
  33. BLM 1980, p. 31, Lost corner.
  34. BLM 1980, p. 37, Obliterated corner.
  35. BLM 1980, p. 7, Bearing tree.
  36. BLM 1980, pp. 62–63, Witness tree.
  37. BLM 1980, p. 13, Corner.
  38. Bright 2004, p. 3.
  39. Schultz, Isaac (October 15, 2019). "The Brief, Baffling Life of an Accidental New York Neighborhood". Atlas Obscura. Retrieved May 6, 2022.
  40. 1 2 3 4 5 6 Brown, Reznik & Gilat 2015.
  41. MSL.
  42. Smetzer 2012.
  43. Monmonier 2008, pp. 33–34.
  44. 1 2 Haaland 2021.
  45. 1 2 Nuessel 2019, p. 188.
  46. STARL 2017.

Bibliography

Further reading