Misplaced Pages

#610389

37-615: The U.S. Board on Geographic Names settled on "Ounce River" as the stream's name in 1938. According to the Geographic Names Information System , it has also been known historically as the "Ounse River", "Owense River", shortened from "Totacaticonce River" and "Totogaticanse River", thereby meaning "Small Totagatic River", where "Totogatic River" ( Doodoogaatig-ziibi in the Ojibwemowin ) means "River of Boggy Riverway"; thus, Dootoogaatigoons-ziibi means

74-495: A "Concise" subset of the NGNDB that listed "major features", and a "Historical" subset that included the features that no longer exist. There is no differentiation amongst different types of populated places. 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 ". In comparing GNIS populated place records with data from

111-552: A "River of a Small and Boggy Riverway." The suffix ens on a consonant stemmed word or oons on a w-stemmed word in Ojibwemowin indicates "little" or "small". 46°10′05″N 91°41′38″W  /  46.16800°N 91.69380°W  / 46.16800; -91.69380 This article about a location in Bayfield County, Wisconsin is a stub . You can help Misplaced Pages by expanding it . This article about

148-588: 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". 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

185-694: 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". 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. Prior efforts had included

222-422: A later phase). 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". The primary geographic coordinates of features which occupy an area, rather than being a single point feature, were

259-537: A location in Douglas County, Wisconsin is a stub . You can help Misplaced Pages by expanding it . This article related to a river in Wisconsin is a stub . You can help Misplaced Pages by expanding it . Geographic Names Information System The Geographic Names Information System ( GNIS ) is a database of name and location information about more than two million physical and cultural features throughout

296-399: A permanent, unique feature record identifier, sometimes called the GNIS identifier. The database never removes an entry, "except in cases of obvious duplication." 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

333-412: A second Alaska file) data from the 1:100000 and 1:250000 scale USGS maps. Map names were recorded exactly as on the maps themselves, with the exceptions for diacritics as with the NGNDB. 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. The TMNDB was later renamed

370-425: A third phase was considered, which would have handled name changes where local usages differed from maps, it was never begun. 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

407-405: Is almost universally employed when storing data to 9-track magnetic tape , NAND flash memory , and rotating media such as floppy disks , hard disks , and optical discs . Most file systems are based on a block device , which is a level of abstraction for the hardware responsible for storing and retrieving specified blocks of data, though the block size in file systems may be a multiple of

SECTION 10

#1732787813611

444-410: Is called blocking , while deblocking is the process of extracting data from blocks. Blocked data is normally stored in a data buffer , and read or written a whole block at a time. Blocking reduces the overhead and speeds up the handling of the data stream . For some devices, such as magnetic tape and CKD disk devices , blocking reduces the amount of external storage required for the data. Blocking

481-472: Is normally abstracted by a file system or database management system (DBMS) for use by applications and end users. The physical or logical volumes accessed via block I/O may be devices internal to a server, directly attached via SCSI or Fibre Channel , or distant devices accessed via a storage area network (SAN) using a protocol such as iSCSI , or AoE . DBMSes often use their own block I/O for improved performance and recoverability as compared to layering

518-443: 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 ). Mountain features would fall into "ridge", "range", or "summit" classes. A feature class "tank" was sometimes used for lakes, which was problematic in several ways. This feature class

555-561: The Geographic Cell Names database (GCNDB hereafter) in the 1990s. 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. 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

592-714: 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. 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". In surveying in

629-703: 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. Data were collected in two phases. Although

666-548: The 1990s (still including tape and paper) to floppy disc , over FTP , and on CD-ROM . 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. The FTP site included extra topical databases: a subset of the NGNDB that only included the records with feature classes for populated places,

703-572: The GNIS web site and can review the justifications and supporters of the proposals. The usual sources of name change requests are an individual state's board on geographic names, or a county board of governors. 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. Conversely, a group of middle school students in Alaska succeeded, with

740-466: The United States , with the coördinates published in the latter substituted for the coördinates from the former. 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 . Elevation and location data followed

777-905: 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" or "obliterated" ), marked in various ways including with trees known as "bearing trees" ("witness trees" in older terminology ) or "corner monuments". 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". Such false classifications have propagated to other geographical information sources, such as incorrectly classified train stations appearing as towns or neighborhoods on Google Maps. 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

SECTION 20

#1732787813611

814-574: The broadcasting masts for radio and television stations, civil divisions, regional and historic names, individual buildings, roads, and triangulation station names. 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 . The feature classes for association with each name included (for examples) "locale" (a "place at which there

851-426: 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; these coordinates are called the "primary point". Secondary coordinates were only an aid to locating which topographic map(s) the feature extended across, and were "simply anywhere on

888-424: 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. The files were compiled from all of the names to be found on USGS topographic maps, plus data from various state map sources. In phase 1, elevations were recorded in feet only, with no conversion to metric, and only if there

925-423: The feature and on the topographic map with which it is associated". River sources were determined by the shortest drain, subject to the proximities of other features that were clearly related to the river by their names. The USGS Topographic Map Names database (TMNDB 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

962-439: 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. 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. It excluded several classes of feature because they were better documented in non-USGS maps, including airports,

999-585: 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. Likewise, in researching

1036-425: The location of the feature's mouth, or of the approximate center of the area of the feature. 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. alluvial fans and river deltas counted as mouths for this purpose. For cities and other large populated places,

1073-717: The most such names being Arizona. 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. 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". There were 828 names containing "squaw", including 11 variations on "Squaw Tit" and "Squaw Teat", contrasting with

1110-483: The physical block size. This leads to space inefficiency due to internal fragmentation , since file lengths are often not integer multiples of block size, and thus the last block of a file may remain partially empty. This will create slack space . Some newer file systems, such as Btrfs and FreeBSD UFS2 , attempt to solve this through techniques called block suballocation and tail merging . Other file systems such as ZFS support variable block sizes. Block storage

1147-604: The point where a dam is thought to be". The National Geographic Names database (NGNDB 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. The second Alaska file was an earlier database, the Dictionary of Alaska Place Names that had been compiled by the USGS in 1967. A further two files were later added, covering

Ounce River - Misplaced Pages Continue

1184-412: The same rules as for the NGNDB. So too did names with diacritic characters. Phase 2 was broader in scope than phase 1, extending the scope to a much larger set of data sources. 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

1221-455: The sources to use. 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 . The actual compilation was outsourced by the U.S. government, state by state, to private entities such as university researchers. The Antarctica Geographic Names database (AGNDB hereafter)

1258-464: The use of "Nipple" in names with non- Native American allusions such as "Susies Nipple". Block (data storage) In computing (specifically data transmission and data storage ), a block , sometimes called a physical record , is a sequence of bytes or bits , usually containing some whole number of records , having a maximum length; a block size . Data thus structured are said to be blocked . The process of putting data into blocks

1295-757: 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 . It only contained records for natural features, not for scientific outposts. The media on which one could obtain the databases were extended in

1332-449: Was an actual elevation recorded for the map feature. They were of either the lowest or highest point of the feature, as appropriate. Interpolated elevations, calculated by interpolation between contour lines , were added in phase 2. 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

1369-568: 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". 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

#610389