Download the PHP package heartsentwined/zf2-geoname without Composer

On this page you can find all versions of the php package heartsentwined/zf2-geoname. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package zf2-geoname

zf2-geoname

Build Status

Maintain a local copy of the Geonames (places) database.

This module will install a self-updating local copy of the Geonames (places) database. It covers the location information, as available from the official database dump. It does not cover the "add-ons", e.g. earthquake, weather data, etc, as available from their webservices.

Attention: the Geonames database is around 1.5GiB - 2GiB in size, when installed in a MySQL database. Are you sure you need a local copy, instead of the official webservices?

Installation

Composer:

Then add Yalesov\Geoname to the modules key in (app root)/config/application.config.*

Geoname module will also hook onto your application's database, through DoctrineORMModule. It will create a number of tables with the prefix he_geoname_*, and will use the default EntityManager doctrine.entitymanager.orm_default. If your settings are different, please modify the doctrine section of config/module.config.yml as needed.

Geoname module makes use of the Cron module, so make sure you follow its settings, and have set up your cron job properly.

Finally, you need to update your database schema. The recommended way is through Doctrine's CLI:

Config

Copy config/geoname.local.php.dist to (app root)/config/autoload/geoname.local.php, and modify the settings.

How frequent should cron be? The recommended setup is every 15 minutes, which is also the default. However, you can make your own adjustments:

At present (18 Sep 2012), it will take 820 cron jobs to install the database. At 15-minute intervals, that would take ~8.5 days to install the database. As for the updates, only 1 cron job per day is needed. However, setting more than one per day is highly recommended to provide redundancy - just in case the geonames server is temporarily unreachable, for example.

You can also adjust to a less frequent cron after install. The status field of the Meta entity, or the he_geoname_meta table, will be Yalesov\Geoname\Repository\Meta::STATUS_INSTALL_* during installation, and Yalesov\Geoname\Repository\Meta::STATUS_UPDATE afterwards.

Usage

Database sync

Just follow the installation instructions. Geoname module will install and update its database in your cron jobs.

Note: when the sources indicate a "delete", Geoname module will not actually delete the corresponding record from your database; it will only mark it as deprecated (by setting the isDeprecated field to true in the entities Place and AltName). This is to ensure that you can rely on the primary IDs set up by Geoname module in your ZF2 app.

Querying the database

You can use the Doctrine 2 ORM API directly. Mapping files are located at (zf2-geoname)/src/Yalesov/Geoname/Entity/Mapping. All places' hierarchy, from continent, country, to the various administration levels, have been properly captured in the parent and children fields of the Place entity.

TODO: add a set of API for common tasks, e.g. finding a place by name, listing all places in a country, etc.

All versions of zf2-geoname with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3.3
yalesov/yaml Version 2.*
zendframework/zendframework Version 2.*
yalesov/arg-validator Version 2.*
yalesov/zf2-doctrine Version 2.*
yalesov/zf2-cron Version 3.*
yalesov/zf2-cli Version 2.*
yalesov/file-system-manager Version 2.*
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package heartsentwined/zf2-geoname contains the following files

Loading the files please wait ....