GeoNames: Global Gazetteer Data for GIS, Geocoding, and Place-Based Analysis
GeoNames is an open geographical database and gazetteer covering countries and named features around the world. Its records include geographical names, alternate names, coordinates, feature classes and codes, country and administrative references, population, elevation, timezone, and modification dates. The project publishes daily database extracts, country-specific files, city subsets, alternate-name tables, hierarchy data, and separate postal-code files. It also provides REST web services for name search, reverse geocoding, nearby-feature discovery, country and timezone lookup, hierarchy traversal, and related location queries. GeoNames is particularly useful as a place-name and geographic-reference layer, but it should not be treated as a complete street-address database, authoritative cadastral layer, turn-by-turn road network, or universally current representation of every physical feature.
GeoNames is one of the foundational reference datasets in the open GIS and location-data ecosystem. It gives software a consistent way to represent named places and geographic features across countries, languages, administrative hierarchies, and feature types. A typical GeoNames record is point-based and includes a stable geoname identifier, a primary name, alternate names, WGS84 latitude and longitude, feature classification, country and administrative codes, population, elevation-related fields, timezone, and a modification date. The project also publishes supporting tables for alternate names, administrative codes, feature codes, country information, time zones, hierarchies, and daily modifications. (geonames.org)
How EDK fits
For: GeoNames is suited to GIS analysts, cartographers, geocoding and search engineers, researchers, data journalists, public-sector analysts, and developers who need a broad geographic-name index. It is especially useful when an application must recognize place names, connect multilingual names to coordinates, search for nearby named features, or attach other datasets to countries, administrative areas, cities, mountains, waterways, roads, and other gazetteer categories.
GeoNames is relevant to the broader problem of finding and understanding the physical world because names are one of the primary interfaces people use to refer to places. The dataset can provide a geographic-name layer that helps connect a user query such as a city, mountain, lake, road, administrative area, or alternate-language name to a coordinate and a structured feature type. That makes it useful as a reference or discovery layer alongside richer representations of buildings, roads, infrastructure, imagery, environmental features, and public records. GeoNames does not itself provide a complete world model: its records are primarily gazetteer features and associated attributes, often represented as points, and it does not replace detailed geometry, current imagery, authoritative addresses, or specialized transport and infrastructure datasets. In a world-model and computation context, GeoNames can help normalize names, resolve geographic references, filter candidate features by country or feature class, traverse place hierarchies, and connect human language to spatial computation.
- •Use GeoNames as a multilingual place-name index when interpreting searches for cities, villages, mountains, lakes, streams, roads, administrative areas, or other named geographic features before joining the result to more detailed spatial layers.
- •Use the geoname identifier, country codes, administrative codes, feature classes, and coordinates to group, rank, filter, or aggregate other geographic records by named place or geographic hierarchy.
- •Use GeoNames search and nearby-feature services as a reference step in workflows that locate a place, then compute distances, coverage, proximity, regional comparisons, or changes using additional roads, buildings, imagery, environmental, or public-data layers.
Dataset profile
Formats
UTF-8 tab-delimited text
ZIP archives
JSON web-service responses
XML web-service responses
RDF for selected semantic-web services
CSV, TXT, RSS, and KML for selected services
GeoJSON-like simplified country-shape products
Access methods
Download the worldwide allCountries extract
Download country-specific gazetteer files
Download city subsets such as cities500, cities1000, cities5000, and cities15000
Download alternate names, hierarchy, administrative-code, feature-code, country, and timezone files
Download separate postal-code files
Query the REST web services for search, reverse lookup, nearby features, hierarchy, country, timezone, and postal-code operations
Use daily modification and deletion files to synchronize a local copy
Quality and limits
GeoNames states that its data is provided as-is without warranty of accuracy, timeliness, or completeness.
Coverage, precision, naming conventions, and update behavior vary by country, feature class, and contributing source.
The main gazetteer is primarily point-based and should not be mistaken for authoritative feature geometry.
Population, elevation, postal-code, and administrative attributes may have different source dates and meanings.
Postal-code coverage and coordinate accuracy vary by country; some countries provide partial codes or estimated coordinates.
Free web services have usage limits and are intended differently from professional commercial services.
Legal, cadastral, emergency, navigation, property, and other high-consequence workflows require validation against appropriate authoritative sources.
Analysis workflows
Load the core tab-delimited extract into a spatial database using geonameId as the stable primary identifier and latitude/longitude as WGS84 point geometry.
Join featureCodes, administrative lookup files, country information, language codes, and time-zone tables before publishing derived layers.
Index name, ASCII name, alternate names, country code, administrative codes, feature class, and feature code for fast search and filtering.
Use alternateNamesV2 for multilingual, historic, preferred, colloquial, and time-bounded name matching instead of relying only on the convenience alternate-name field.
Use GeoNames web services for interactive autocomplete, place search, nearby-feature queries, and reverse geographic lookup; use local extracts for repeatable batch analysis.
Apply daily modification and deletion files to maintain a synchronized local gazetteer and record the source date for every derived analysis.
Join GeoNames features to roads, buildings, administrative polygons, imagery, environmental layers, public assets, or service records using identifiers, codes, spatial proximity, or validated name matching.
Validate coordinates, duplicates, country assignments, feature codes, null values, and source dates before using the results in decision-support or public-facing applications.
Value inside EDK
What GeoNames contains
The core GeoNames gazetteer is organized around named geographic features with stable numeric identifiers. The official extract documentation lists fields for the name, ASCII name, alternate names, WGS84 latitude and longitude, feature class, feature code, country code, alternate country codes, administrative codes, population, elevation, digital elevation model value, timezone, and modification date. The feature taxonomy includes administrative areas, hydrographic features, area features, populated places, roads and railroads, spot features, terrain features, undersea features, and vegetation features. (download.geonames.org)
GeoNames also distributes supporting datasets. These include alternate names with language and historical-name fields, administrative-code lookup files, ISO language codes, feature-code descriptions, country information, time zones, hierarchy relationships, user tags, and simplified country shapes. Separate city extracts such as cities500, cities1000, cities5000, and cities15000 provide smaller subsets based on population or administrative importance. Postal-code data is distributed separately and has country-specific coverage and precision constraints. (download.geonames.org)
- •Primary and alternate place names, including multilingual and some historic or colloquial variants.
- •Point coordinates in WGS84 decimal degrees.
- •Feature classes and feature codes for geographic interpretation.
- •Country, administrative, population, elevation, timezone, and modification-date attributes.
- •Hierarchy, country, language, time-zone, and feature-code reference files.
- •Separate postal-code data and simplified country-boundary products.
Geography, temporal coverage, and update cadence
GeoNames is intended to cover all countries and a wide range of named geographic features. Coverage is broad, but it is not uniform in meaning or precision. A populated place, mountain, stream, road, building, administrative unit, and postal-code record may be represented differently and may originate from different source materials. The main gazetteer coordinates are geographic WGS84 coordinates, while postal-code coordinates can be estimated or derived from nearby records, centroids, or other country-specific methods. (geonames.org)
The project describes the worldwide extract as a daily database export. Its dump documentation also lists modifications and deletion files for the previous day, enabling a local database to be synchronized incrementally rather than rebuilt from the complete archive each time. The existence of daily files does not mean every feature is independently verified or that every source attribute is updated daily; users should track the modification date and retain the dataset date used in each analysis. (geonames.org)
- •Geographic scope: global, with country-specific files and worldwide extracts.
- •Coordinate reference: WGS84 latitude and longitude for the main gazetteer.
- •Update cadence: daily extract and daily modification/deletion files are documented by the project.
- •Temporal meaning: modification dates identify record changes; they do not necessarily describe when a place existed or when an attribute was measured.
- •Completeness and accuracy: variable and not guaranteed across countries, feature types, or source inputs.
Formats and access methods
The principal download workflow is file-based. The main gazetteer is supplied as ZIP archives containing UTF-8, tab-delimited text. Users can download allCountries.zip, country-specific files, city subsets, alternate-name files, hierarchy data, administrative lookup tables, and other reference files. This structure is practical for batch loading into PostgreSQL/PostGIS, SQLite, DuckDB, Python, R, Spark, or a cloud data warehouse. The official readme documents the field order and semantics needed to build an importer. (download.geonames.org)
For interactive applications, GeoNames provides REST web services. Documented services include full-text place-name search, nearby-place and nearby-toponym queries, reverse country lookup, hierarchy and children queries, country information, timezone lookup, postal-code search, and retrieval of a feature by geonameId. Most services support XML and JSON, while additional service formats include RDF, CSV, TXT, RSS, and KML in the broader service catalog. A registered username is required for the web services, and the documentation distinguishes free services from commercial services intended for professional or mission-critical use. (geonames.org)
- •Batch files: ZIP archives containing UTF-8, tab-delimited text.
- •Common subsets: worldwide, country-level, city-population subsets, alternate names, hierarchies, and postal codes.
- •API formats: XML and JSON for many services; RDF, CSV, TXT, RSS, and KML are available for selected services.
- •Access pattern: registered free web-service account for API use; commercial services are available for higher-availability professional requirements.
- •Recommended import practice: preserve geonameId, source vintage, modification date, original codes, and attribution metadata.
Suitable GIS and spatial-analysis workflows
GeoNames works well as a gazetteer and reference layer in GIS. A common workflow is to load the core file into a point layer, join feature-code descriptions and administrative lookup tables, and index the name, alternate-name, country, feature-code, and coordinate fields. Analysts can then search for candidate places, map feature distributions, select only populated places or hydrographic features, and connect records to other datasets using geonameId, country code, administrative codes, or spatial proximity.
For multilingual search, load alternateNamesV2 rather than relying only on the convenience alternatenames field in the main table. The separate table retains language codes and additional attributes such as preferred, short, colloquial, historic, and temporal name indicators. This supports workflows such as matching a local-language query to a canonical feature, building search indexes, or comparing historical and current names. (download.geonames.org)
- •Gazetteer search and multilingual name matching.
- •Point-layer mapping by feature class and feature code.
- •Spatial joins between named places and roads, buildings, imagery, environmental features, or public records.
- •Administrative and hierarchy-based aggregation.
- •Nearby-feature and reverse-geocoding support.
- •Incremental local-database synchronization using modification and deletion files.
License, strengths, and tradeoffs
GeoNames publishes the main data under a Creative Commons Attribution 4.0 license and asks users to give credit to GeoNames when using the data or web services. The project also notes that data comes from multiple sources, and some specialized files, particularly postal-code subsets, have country-specific coverage and copyright-related restrictions or omissions. Review the relevant file documentation before redistributing derived products. (geonames.org)
The strongest use of GeoNames is as a broad, accessible geographic-name index. Its stable identifiers, feature taxonomy, multilingual names, daily extracts, and API services make it useful for place discovery and geographic normalization. Its main tradeoff is that a gazetteer is not a complete physical-world representation. Point coordinates and names are excellent for reference and search, but insufficient by themselves for precise geometry, current road navigation, building-level addressing, property boundaries, or authoritative operational decisions.
- •Strength: broad global coverage across many types of named geographic features.
- •Strength: multilingual and alternate-name support with stable geoname identifiers.
- •Strength: both downloadable extracts and queryable web services.
- •Tradeoff: accuracy, completeness, and update timing vary by country, feature class, and source.
- •Tradeoff: the primary gazetteer is largely point-based and does not provide a complete road, parcel, building, or address geometry layer.
- •Tradeoff: free web services have usage constraints, while professional users may need commercial services or a locally hosted extract.
- •Tradeoff: postal-code data has country-specific limitations, including partial codes or estimated coordinates in some jurisdictions.
Questions teams ask
Is GeoNames an address database?
Not in the sense of a complete, authoritative street-address registry. GeoNames contains geographical names and many place-related attributes, and its services can support place search and some reverse-geographic lookups. However, users needing current address points, parcel-level locations, delivery validation, or official addressing should use an appropriate national, local, or commercial address source and may combine it with GeoNames for name normalization.
How often is GeoNames updated?
GeoNames documents a daily database extract and provides daily modification and deletion files for synchronization. The record modification date indicates when a GeoNames record changed; it does not guarantee that every feature or underlying source was surveyed or independently verified on that schedule.
What file format does GeoNames use?
The principal downloadable extracts are ZIP archives containing UTF-8, tab-delimited text. The project also publishes supporting files such as alternate-name, hierarchy, administrative-code, time-zone, and feature-code tables. Its web services commonly return XML or JSON, with additional formats available for selected services.
Can GeoNames be used commercially?
The project publishes its data under a Creative Commons Attribution 4.0 license, so attribution is required. Users should review the specific file documentation and any source-specific conditions, especially for postal-code data. GeoNames also offers commercial web services and premium data services for professional requirements.
What is the best way to use GeoNames with other GIS data?
Use GeoNames as a name, identifier, and geographic-reference layer. Match names and alternate names, filter by feature class or code, connect records through geonameId or administrative codes, and then use more detailed roads, buildings, boundaries, imagery, environmental, or public datasets for geometry and physical-world analysis.
Keep exploring
gtfs
GTFS complements GeoNames by providing transit stops, routes, trips, schedules, and shapes for transportation and location-based analysis.
gadm
GADM provides polygonal administrative boundaries that can be used with GeoNames points and administrative codes for regional mapping and aggregation.
census acs
Census ACS can be joined to geographic areas and named places for demographic and socioeconomic analysis after GeoNames supports place identification or normalization.
Sources
About GeoNames
Official overview of GeoNames coverage, reported database scale, WGS84 coordinates, data sources, web services, and Creative Commons attribution licensing.
Open sourceGeoNames Gazetteer Extract Readme
Official field definitions, feature classes, downloadable files, UTF-8 tab-delimited format, daily modifications, deletions, and license disclaimer.
Open sourceGeoNames Data Download and Web Services
Official description of the daily worldwide extract, country files, postal-code downloads, and web-service ecosystem.
Open sourceGeoNames Web Service Documentation
Official documentation for search, reverse-geocoding, nearby-feature, hierarchy, postal-code, country, and related REST services.
Open sourceGeoNames Web Services Overview
Official overview of supported service endpoints and available response formats.
Open source