weasty/jjs-geonames-bundle

GeoNames.org geographical data and associated functionality

Geonames Bundle

Introduction

Provides access to the data exported by geonames.org into [symfony 2][sf2] applications., _(*1)

What is geonames.org

From the geonames.org website:, _(*2)

The GeoNames geographical database covers all countries and contains over eight million placenames that are available for download free of charge., _(*3)

When to use this bundle

Most useful application for this bundle is to normalize the geograhical information stored in your database such as Countries, States and Cities. Thanks to the extensive geonames.org data almost all cities, towns and suburbs are covered worldwide., _(*4)

Features

• Imports the following geonames.org data:, _(*5)

  • Countries
  • Timezones
  • States & Provences
  • Cities, Towns, Suburbs, Villages etc.

• Provides the following data store implementations:, _(*6)

  • Doctrine ORM

Installation

1. Install the bundle using composer:, _(*7)

   composer require jjs/geonames-bundle:*
   

   Or add it to your composer.json file directly, _(*8)

   {
       require: {
           "jjs/geonames-bundle": "*"
       }
   }
   

2. Add the bundle to your AppKernel.php, _(*9)

   ```php // AppKernel::registerBundles() $bundles = array( // ... new JJs\Bundle\GeonamesBundle\JJsGeonamesBundle(), // ... );, <sub>(*10)</sub>

Install or update database schema

The database schema for he bundle is defined using doctrine migrations. Migration versioning is designed so they can be merged into your application migrations or migrate the schema manually., <sub>(*11)</sub>

Independant versioning

Execute the migrations using the supplied migration configuration, <sub>(*12)</sub>

# Run in your project root directory
app/console doctrine:migrations:migrate --configuration=vendor/jjs/geonames-bundle/JJs/GeonamesBundle/migrations.xml

Application versioning

This schema management stragegy involves more configuration and management, but comes with the benefit of greater control. It is possible due to mapping between incremental database version and semantic bundle version. It involves 'folding' the geonames schema versioning into your own migrations and managing the migration of your database as a whole., <sub>(*13)</sub>

As yet this versioning strategy is undocumented, please contact me if you're interested in using it and I will write the documentation., <sub>(*14)</sub>

Import the data

Note that importing the data from the remote geonames.org repository involves downloading almost 250 MB data from geonames.org., <sub>(*15)</sub>

The following commands can be used in sequence to load all supported data from the geonames.org export (http://download.geonames.org/export/dump), <sub>(*16)</sub>

Import countries

Loads a list of all countries which are refenced by the other imported data such as timezones and localities., <sub>(*17)</sub>

app/console geonames:load:countries

Import timezones

Loads a list of timezones mapped to countries, <sub>(*18)</sub>

app/console geonames:load:timezones

Import localities

There are two options for importing the localities - either the whole world at once or batched by countries. Internally the same import mechanism is used and the import process will download a data file for each country and then process the country files individually., <sub>(*19)</sub>

Note the full load process may take several hours to complete and requires a large amount of memory., <sub>(*20)</sub>

# All countries
app/console geonames:load:localities

# Subset of countries (list the desired contries as arguments)
app/console geonames:load:localities US CA