This repository is part of the Pelias
project. Pelias is an open-source, open-data geocoder built by
Mapzen that also powers Mapzen Search. Our
official user documentation is here.

Pelias Geonames importer

This Node.js package imports data from Geonames into
Pelias. It includes utilities for downloading and cleaning up the data before
import.

Requirements

Node.js '4.0' or greater

Installation

git clone https://github.com/pelias/geonames

cd geonames

npm install

Configuration

The importer can be configured from your local pelias-config
(defaults to ~/pelias.json) in the imports.geonames object:

{

"imports":{

"geonames":{

"datapath":"/path/to/geonames/data",

"countryCode":"MX"

}

}

}

The following are all optional:

datapath: the path to geonames data. Defaults to a directory inside the importer.

countryCode: the two digit (ISO 3166-1 alpha-2) country code
for the country for which data will be downloaded and imported. Use ALL for all countries.

Admin Lookup

Pelias has the ability to compute the admin hierarchy (county, region, country, etc)
from Who's on First data.
For more info on how admin lookup works, see the documentation for
pelias/wof-admin-lookup. By default,
adminLookup is enabled. To disable, set imports.adminLookup.enabled to false in Pelias config.

Note: Admin lookup requires loading around 5GB of data into memory.

Usage

A list of supported countries and their codes can be viewed with npm run countryCodes

Download the data

The data corresponding to the countryCode in the pelias config file will be downloaded.
npm run download

Import the downloaded data

npm start

Updating Metadata

The metadata is not shipped with the repo, however, during normal usagage running npm install will also trigger a script that updates the metadata.

However this hook will not trigger in non-interactive sessions such as many shell scripts. To explicitly download the metadata or refresh it (it changes very infrequently, perhaps every few months), run:

npm run download_metadata

The metadata is packaged in our Docker images, so using an up to date docker image should guarantee recent enough metadata.