The Geographic Names Information System (GNIS) is the Federal standard for geographic nomenclature. The U.S. Geological Survey developed the GNIS for the U.S. Board on Geographic Names, a Federal inter-agency body chartered by public law to maintain uniform feature name usage throughout the Government and to promulgate standard names to the public. The GNIS is the official repository of domestic geographic names data; the official vehicle for geographic names use by all departments of the Federal Government; and the source for applying geographic names to Federal electronic and printed products of all types. See http://geonames.usgs.gov for additional information. This is an update to the gnis_jul16 layer.
The Geographic Names Information System contains information about physical and cultural geographic features of all types in the United States, associated areas, and Antarctica, current and historical, but not including roads and highways. The database holds the Federally recognized name of each feature and defines the feature location by state, county, USGS topographic map, and geographic coordinates. Other attributes include names or spellings other than the official name, feature designations, feature classification, historical and descriptive information, and for some categories the geometric boundaries. The database assigns a unique, permanent feature identifier, the Feature ID, as a standard Federal key for accessing, integrating, or reconciling feature data from multiple data sets. The GNIS collects data from a broad program of partnerships with Federal, State, and local government agencies and other authorized contributors. The GNIS provides data to all levels of government and to the public, as well as to numerous applications through a web query site, web map and feature services, file download services, and customized files upon request.
The U.S. Board on Geographic Names was created in 1890 and established in its present form by Public Law in 1947 to establish and maintain uniform geographic name usage throughout the Federal Government. The Board serves all government agencies and the public as the central authority to which name inquiries, name issues, and new name proposals can be directed. It is comprised of representatives of Federal agencies associated with land management and cartography. Sharing its responsibilities with the Secretary of the Interior, the Board develops principles, policies, and procedures governing the use of both domestic and foreign geographic names as well as undersea and Antarctic feature names.
publication date
None. Acknowledgement of the U.S. Geological Survey would be appreciated in products derived from these data.
523 National Center
The Geographic Names Information System was developed by the U.S. Geological Survey in cooperation with the U.S. Board on Geographic Names.
GeoPlan relied on the integrity of the attribute information within the original data.
GeoPlan relied on the integrity of the original data.
GeoPlan relied on the integrity of the original data. During Phase I data compilation, a random sample of 10% of the entries in the system were visually verified against the compilation source data (large-scale USGS topographic maps) to ensure logical consistency of locative references (geographic coordinates, topographic map, and county. Subsequent data compilation and input processes include programmed validation checks for logical consistency, visual examination, and spot checks of data.
This dataset contains information about United States physical and cultural geographic features of all types and classes, with the exception of most roads and highways. Subsequent to the original data compilation process, which was taken primarily from Federal maps, the GNIS has become dependent on input from Federal, State, county, and local government agencies and other approved sources. The completeness, currency, and accuracy of the data varies by area depending on the quality and timeliness of that input. Accordingly, the Geographic Names Project actively seeks to expand partnerships with Government agencies at all levels and other interested organizations. The latest tools and methodologies are being applied, including web map and feature services, and joint or linked web applications, to ensure that local data are properly represented in the GNIS and through the GNIS to all Federal agencies and to the public. Feature additions or corrections are accepted for consideration from any source, and when validated by appropriate agencies, will be entered into the database. Local and State agencies are encouraged to submit data and to participate in the GNIS partnership program. Non-government organizations with valuable data are considered on a case basis. Authorized partners have access to web based transaction entry and edit forms, which submit data directly to the GNIS for review and inclusion in the database. Partners also submit batch files in most standard formats, and coordinate with the Geographic Names Project to develop joint services, processes, and applications for greatest efficiency. Data entered into the GNIS immediately is available to all web services and applications dependent on it. For additional information or to request user accounts for entry and edit of production data and web seminar training, contact gnis_manager@usgs.gov.
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan. Accuracy of these digital data is based upon the use of printed or electronic source graphics which are compiled to meet National Map Accuracy Standards. Comparison to the graphic source is used as control to assess digital positional accuracy.
GeoPlan relied on the integrity of the original data.
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan.
Spatial and Attribute Information
GNIS Phase I data compilation and edit - Feature name and attribute data were collected from the largest-scale USGS topographic maps available. These data are compared to the records of the U.S. Board on Geographic Names.
523 National Center
GNIS Phase II data compilation and edit - Feature name and attribute data are collected from official state and local sources and other approved sources including historical maps and documents.
523 National Center
GNIS Maintenance program - Federal and state maintenance cooperators submit new and corrected data in conjunction with their mapping and geographical information system data maintenance programs. The GNIS has an active data gathering and maintenance program. A web-based data entry and edit application allows authorized users to submit transaction data directly for validation and entry into the database, where it immediately becomes available to all web services and applications. A test and demonstration site with no connection to production data is available for review, training, and familiarization. Batch files will be accepted in most standard formats. Government agencies at all levels are encouraged to join this program. Other organizations and individuals will be considered on a case basis. For additional information or to request user accounts for entry and edit of production data and web seminar training, contact gnis_manager@usgs.gov or the individual below.
523 National Center
Partnerships - the Geographic Names Project enters into partnerships with State names authorities and State and local GIS agencies to integrate name, location, and attribute data in the GNIS with State and local datasets. These partnerships utilize GIS and web technology to automate and simplify data maintenance, ensure data consistency, integrity, and accuracy, and meet the requirements of the Board on Geographic Names for national names standardization. Government agencies at all levels are encouraged to join this program. Other organizations and individuals will be considered on a case basis. For additional information contact the individual below.
523 National Center
GeoPlan downloaded the data on January 9, 2018 from the United States Geological Survey at http://geonames.usgs.gov/domestic/download_data.htm in text format. Metadata was imported from https://geonames.usgs.gov/domestic/download_data.htm. The original data extent was limited to the State of Florida. NOTE: This layer must be created in a file geodatabase as to keep correct field length. Please create a geodatabase before working on this layer. Geoplan completed the following process steps during QA/QC: -Modified original text file in a text editor to change delimiters to commas -Saved as a .csv and then exported into file geodatabase as a geodatabase table -Created an XY event layer from fields "PRIM_LONG_DEC" and "PRIM_LAT_DEC" -Selected NAD_83 as source projection -Exported event layer to file geodatabase feature class -Deleted all points with no spatial extent and points not within the extent of Florida (218 points). -Projected to Albers using NAD_83_to_HARN_Florida transformation -Uppercased all fields -Added field DESCRIPT based on FEATURE_NAME -Added field FGDLAQDATE based on date downloaded from source -Restructured table
Dataset copied.
Internal feature number.
ESRI
Feature geometry.
ESRI
A permanent, unique number assigned to a geographic feature for the sole purpose of uniquely identifying that feature as a record in any information system database, dataset, file, or document and for distinguishing it from all other feature records so identified. The number is assigned sequentially (highest existing number plus one) to new records as they are created in the Geographic Names Information System. The number, by design, carries no information or association to the content of the feature record and therefore is not subject to change as attribute values change. Once assigned to a feature, the number is never changed or withdrawn, and never reassigned. The Feature ID can be applied in conjunction with system-unique record identifiers in any database or system, thus providing a national standard common reference identifier across multiple datasets. The Feature ID is stored in the GNIS database as an integer with a maximum of ten digits.
USGS
A geographic feature name and its written form and application approved or recognized as official by the United States Board on Geographic Names for use throughout the Federal Government. The official name is established either by policy or by decision of the Board on Geographic Names. It is the proper name, specific term, or expression by which a particular geographic entity is, or was, known. A geographic feature may have only one official name, which must be the name applied to the feature on all Federal products, electronic or printed.
USGS
A feature class is a designation for a group of features in a broadly defined descriptive category. All features are assigned to one and only one class. They do not individually classify all kinds of cultural and natural features. By design, there are no Federal or industry standards or guidelines for feature classification. These classifications originally were developed for mainframe file structure search purposes. Although the terms are generally consistent with dictionary definitions, they may not conform exactly and are not always intuitive.
USGS
The unique two letter alphabetic state code containing the geographic feature as specified by the American National Standards Institute (ANSI) Codes. Note: Some feature records in State files will display State Alpha and Number Codes for a State other than that requested. This is not an error. It indicates that the primary coordinates for the feature reside in another State, but that the feature crosses into and is included in the specified State. This also means that the feature record is included in both State files.
USGS
The unique numeric state code containing the geographic feature as specified by the American National Standards Institute (ANSI) Codes. Note: Some feature records in State files will display State Alpha and Number Codes for a State other than that requested. This is not an error. It indicates that the primary coordinates for the feature reside in another State, but that the feature crosses into and is included in the specified State. This also means that the feature record is included in both State files.
USGS
The name for the county or county eqivalent containing the geographic feature.
USGS
The unique three number code for the county or county equivalent containing the geographic feature as specified in the American National Standards Institute (ANSI) Codes.
USGS
Official feature latitude location, NAD 83 DMS-degrees/minutes/seconds.
USGS
Official feature longitude location, NAD 83 DMS-degrees/minutes/seconds.
USGS
Undefined by source.
GeoPlan
Undefined by source.
GeoPlan
Official feature latitude location, NAD 83 DEC-decimal degrees.
USGS
Official feature longitude location, NAD 83 DEC-decimal degrees.
USGS
Source latitude coordinates of linear feature only (Class = Stream, Valley, Arroyo), NAD 83; DMS-degrees/minutes/seconds.
USGS
Source longitude coordinates of linear feature only (Class = Stream, Valley, Arroyo), NAD 83; DMS-degrees/minutes/seconds.
USGS
Undefined by source.
GeoPlan
Undefined by source.
GeoPlan
Source latitude coordinates of linear feature only (Class = Stream, Valley, Arroyo), NAD 83; DEC-decimal degrees.
USGS
Source longitude coordinates of linear feature only (Class = Stream, Valley, Arroyo), NAD 83; DEC-decimal degrees.
USGS
Elevation in meters: The elevation above sea level of the feature at the primary point (positive number) or depth of a feature at the lowest point below sea level (negative number). By default, elevations are provided in meters. For custom data extracts, elevations can be provided in either feet or meters depending on user requirements. Elevation figures are not official and do not represent precisely measured or surveyed values. The data are extracted from the National Elevation Dataset (http://ned.usgs.gov/) for the primary coordinates and may differ from elevations cited in other sources. The differences will be most evident for features such as summits where precision is of more concern and where the local relief (rate of change of elevation) may be more prominent. However, the elevation figures are within tolerances for the data for most points and sufficiently accurate for purposes of general information.
USGS
Elevation in feet: The elevation above sea level of the feature at the primary point (positive number) or depth of a feature at the lowest point below sea level (negative number). By default, elevations are provided in meters. For custom data extracts, elevations can be provided in either feet or meters depending on user requirements. Elevation figures are not official and do not represent precisely measured or surveyed values. The data are extracted from the National Elevation Dataset (http://ned.usgs.gov/) for the primary coordinates and may differ from elevations cited in other sources. The differences will be most evident for features such as summits where precision is of more concern and where the local relief (rate of change of elevation) may be more prominent. However, the elevation figures are within tolerances for the data for most points and sufficiently accurate for purposes of general information.
USGS
The name of the standard USGS 7.5x7.5 minute quadrangle map(s) containing the representation of the feature
USGS
The date the geographic feature record was initially committed to the database and made available through GNIS products and services.
USGS
The date one or more attributes of an existing geographic feature record were last edited. The attributes edited are not specified.
USGS
Based on FEATURE_NAME.
GeoPlan
Date when data was downloaded from source.
GeoPlan
Unique ID added by GeoPlan
GeoPlan
Principles, Policies, and Procedures: Domestic Geographic Names, By Donald J. Orth, Executive Secretary, Domestic Geographic Names (emeritus) and Roger L. Payne, Executive Secretary, United States Board on Geographic Names and Domestic Geographic Names, Third printing (revised) and Preliminary Online Edition, 1997 (http://geonames.usgs.gov/docs/pro_pol_pro.pdf).
431 Architecture PO Box 115706
The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist. Furthermore, the GIS data available in the FGDL are provided 'as is'. The University of Florida GeoPlan Center makes no warranties, guaranties or representations as to the truth, accuracy or completeness of the data provided by the data sources. The University of Florida GeoPlan Center makes no representations or warranties about the quality or suitability of the materials, either expressly or implied, including but not limited to any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. The University of Florida GeoPlan Center shall not be liable for any damages suffered as a result of using, modifying, contributing or distributing the materials. A note about data scale: Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data. 1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: http://geoplan.ufl.edu/education.html.
All GNIS data may be queried, displayed, and/or printed from the public web site
Datasets of under 2000 records may be queried and displayed from the public web site and downloaded
Primary attributes are available from the names layers served through an ESRI ArcGIS web map service. The following are instructions for access by ESRI ArcMap. For other tools, please adjust accordingly. 1) Click Add Data, 2) expand drop-down to GIS Servers, 3) select Add WMS Server, 4) enter the following full URL, 5) click Get Layers, then click OK, (The service is added to the list of available servers), 6) select service if not already highlighted, 7) click Add, 8) select the service again in pop up box, 9) click Add. The layers should appear in the ArcMap table of contents. No data will appear until you zoom in far enough over continental the US. The layers display at varying resolutions. See these same layers in The National Map viewer under the Names category in the layer list. The names layers do not include all attributes. Customized files of large data sets also can be provided on request in most standard formats including shape files. The data is presented in format Arc SDE.
Primary attributes are available from the GNIS XML service. Instructions: Insert desired parameter value(s) in single quotes following the equals sign. Do not change or delete unused parameters. Parameter definitions: fname = feature name. (Exact match. Not case sensitive.) state = state name. (Exact match. Case sensitive.) cnty = county name. (Exact match. Not case sensitive.) cell = USGS standard topographic map name. (Exact match. Not case sensitive.) ftype = feature type (class). See the GNIS public query page (http://geonames.usgs.gov/pls/gnispublic/). The pick list for feature class contains the values. Note that the value (populated place) in the pick list is abbreviated (ppl) in the data. See question 14, How can I acquire GNIS data?, of our FAQ (http://geonames.usgs.gov/domestic/faqs.htm) for more details and sample URLs. As currently implemented, it is for relatively small data set queries not for mass downloads. It does not include all attributes. Customized files of large data sets also can be provided on request in most standard formats. The data is presented in format XML.
Data extract files for States and territories are available for download via web browser. Topical extracts of the data base are also available: the U.S. Populated Places File lists information about all communities throughout the United States that are described in the database; the U.S. Concise File lists information about major physical and cultural features throughout the United States that are described in the database; the Historical Features File lists information about features which are no longer in existence and/or no longer serve their original purpose; the All Names File lists all names, both official and nonofficial (variant), for all features in the nation; and the Antarctica File contains entries throughout the continent of Antarctica as approved for use by the United States Government. The data is presented in format ASCII, UTF-8, or UTF-16.
Custom data sets may be requested in most standard formats including ASCII, UTF-8, UTF-16, shape, .xls, and Oracle extract. Contact gnis_manager@usgs.gov.
523 National Center