Download the PHP package sparefoot/geocoder without Composer

Geocoder

Important: You are browsing the documentation of Geocoder 4.x (not released yet).

Documentation for version 3.x is available here: Geocoder 3.x documentation.

Documentation for version 2.x is available here: Geocoder 2.x documentation.

Geocoder is a PHP library which helps you build geo-aware applications by providing a powerful abstraction layer for geocoding manipulations.

• Installation
• Usage
  • Address & AddressCollection
  • The ProviderAggregator
  • TimedGeocoder
  • HTTP Adapters
  • Providers
  • Address-based Providers
    • ArcGISOnline
    • GeoIP2
    • GoogleMaps
    • GoogleMapsBusiness
    • Mapzen
    • MaxMindBinary
    • Nominatim
    • TomTom
    • Yandex
  • IP-based Providers
  • Locale Aware Providers
  • The Chain Provider
  • Dumpers
  • GPS eXchange Format (GPX)
  • GeoJSON
  • GeoArray
  • Keyhole Markup Language (KML)
  • Well-Known Binary (WKB)
  • Well-Known Text (WKT)
  • Formatters
• Extending Things
• Versioning
• Cookbook

Installation

The recommended way to install Geocoder is through Composer:

Usage

Geocoder and its companion Geocoder Extra provides a lot of providers.

Choose the one that fits your need first. Let's say the GoogleMaps one is what you were looking for, so let's see how to use it. In the code snippet below, curl has been chosen as HTTP layer but it is up to you since each HTTP-based provider implements PSR-7.

The Provider interface has three methods:

• geocodeQuery(GeocodeQuery $query):AddressCollection
• reverseQuery(ReverseQuery $query):AddressCollection
• getName():string

The Geocoder interface extends the Provider interface and exposes two additional methods. They will make migration from 3.x smoother.

• geocode($streetOrIpAddress)
• reverse($latitude, $longitude)

Address & AddressCollection

Both geocode() and reverse() methods return a collection of Address objects (AddressCollection), each providing the following API:

• getCoordinates() will return a Coordinates object (with latitude and longitude properties);
• getLatitude() will return the latitude value;
• getLongitude() will return the longitude value;
• getBounds() will return an Bounds object (with south, west, north and east properties);
• getStreetNumber() will return the street number/house number value;
• getStreetName() will return the street name value;
• getLocality() will return the locality or city;
• getPostalCode() will return the postalCode or zipcode;
• getSubLocality() will return the city district, or sublocality;
• getAdminLevels() will return an ordered collection (AdminLevelCollection) of AdminLevel object (with level, name and code properties);
• getCountry() will return a Country object (with name and code properties);
• getCountryCode() will return the ISO country code;
• getTimezone() will return the timezone.

The AddressCollection exposes the following methods:

• count() (this class implements Countable);
• first() retrieves the first Address;
• slice($offset, $length = null) returns Address objects between $offset and length;
• get($index) fetches an Address using its $index;
• all() returns all Address objects;
• getIterator() (this class implements IteratorAggregate).

The ProviderAggregator

The ProviderAggregator is used to register several providers so that you can decide which provider to use later on.

The ProviderAggregator's API is fluent, meaning you can write:

The using() method allows you to choose the provider to use by its name. When you deal with multiple providers, you may want to choose one of them. The default behavior is to use the first one but it can be annoying.

The limit() method allows you to configure the maximum number of results being returned. Depending on the provider you may not get as many results as expected, it is a maximum limit, not the expected number of results.

TimedGeocoder

The TimedGeocoder class profiles each geocode and reverse call. So you can easily figure out how many time/memory was spent for each geocoder/reverse call.

We use the symfony/stopwatch component under the hood. Which means, if you use the Symfony framework the geocoder calls will appear in your timeline section in the Web Profiler.

HTTP Adapters

In order to talk to geocoding APIs, you need HTTP adapters. While it was part of the library in Geocoder 1.x and 2.x, Geocoder 3.x and upper now relies on the PSR-7 Standard which defines how HTTP message should be implemented. You can use any library to send HTTP messages that implements php-http/client-implementation.

To use Guzzle 6 you should run the following command:

Providers

Providers perform the geocoding black magic for you (talking to the APIs, fetching results, dealing with errors, etc.) and are highly configurable.

Address-based Providers

Below, you will find more information for these providers.

ArcGISOnline

It is possible to specify a sourceCountry to restrict result to this specific country thus reducing request time (note that this doesn't work on reverse geocoding).

GeoIP2

It requires either the database file, or the webservice - represented by the GeoIP2 , which is injected to the GeoIP2Adapter. The geoip2/geoip2 package must be installed.

This provider will only work with the corresponding GeoIP2Adapter:

GoogleMaps

Locale and/or region can be specified:

GoogleMapsBusiness

A valid Client ID is required. The private key is optional. This provider also supports SSL, and extends the GoogleMaps provider.

Mapzen

A valid API key is required. This provider also supports SSL.

MaxMindBinary

This provider requires a data file, and the geoip/geoip package must be installed.

It is worth mentioning that this provider has serious performance issues, and should not be used in production. For more information, please read issue #301.

Nominatim

Access to a Nominatim server is required. See the Nominatim Wiki Page for more information.

TomTom

The default language-locale is en, you can choose between de, es, fr, it, nl, pl, pt and sv.

Yandex

The default language-locale is ru-RU, you can choose between uk-UA, be-BY, en-US, en-BR and tr-TR. This provider can also reverse information based on coordinates (latitude, longitude). It's possible to precise the toponym to get more accurate result for reverse geocoding: house, street, metro, district and locality.

IP-based Providers

Important: the Geocoder Extra library contains even more official providers!

Locale Aware Providers

Providers that are locale aware expose the following methods:

The Chain Provider

The Chain provider is a special provider that takes a list of providers and iterates over this list to get information. Note that it stops its iteration when a provider returns a result. The result is returned by GoogleMaps because FreeGeoIp and HostIp cannot geocode street addresses. BingMaps is ignored.

Everything is ok, enjoy!

Dumpers

Geocoder provides dumpers that aim to transform an Address object in standard formats.

GPS eXchange Format (GPX)

The GPS eXchange format is designed to share geolocated data like point of interests, tracks, ways, but also coordinates. Geocoder provides a dumper to convert an Address object in an GPX compliant format.

Assuming we got a $address object as seen previously:

It will display:

GeoJSON

GeoJSON is a format for encoding a variety of geographic data structures.

GeoArray

Simple PHP array format for using with your own encoders.

Keyhole Markup Language (KML)

Keyhole Markup Language is an XML notation for expressing geographic annotation and visualization within Internet-based, two-dimensional maps and three-dimensional Earth browsers.

Well-Known Binary (WKB)

The Well-Known Binary (WKB) representation for geometric values is defined by the OpenGIS specification.

Well-Known Text (WKT)

Well-known text (WKT) is a text markup language for representing vector geometry objects on a map, spatial reference systems of spatial objects and transformations between spatial reference systems.

Formatters

A common use case is to print geocoded data. Thanks to the StringFormatter class, it's simple to format an Address object as a string:

Here is the mapping:

• Street Number: %n

• Street Name: %S

• City: %L

• City District: %D

• Zipcode: %z

• Admin Level Name: %A1, %A2, %A3, %A4, %A5

• Admin Level Code: %a1, %a2, %a3, %a4, %a5

• Country: %C

• Country Code: %c

• Timezone: %T

Extending Things

You can write your own provider by implementing the Provider interface.

You can provide your own dumper by implementing the Dumper interface.

Versioning

Geocoder follows Semantic Versioning.

End Of Life

1.x

As of December 2014, branch 1.7 is not officially supported anymore, meaning major version 1 reached end of life. Last version is: 1.7.1.

2.x

As of December 2014, version 2.x is in a feature frozen state. All new features should be contributed to version 3.0 and upper. Last version is: 2.8.1.

Major version 2 will reach end of life on December 2015.

Stable Version

Version 3.x is the current major stable version of Geocoder.

Cookbook

We have a small cookbook where you can find examples on common use cases:

• Caching responses
• Configuring the HTTP client

Contributing

See CONTRIBUTING file.

Unit Tests

In order to run the test suite, install the development dependencies:

Then, run the following command:

You'll obtain some skipped unit tests due to the need of API keys.

Rename the phpunit.xml.dist file to phpunit.xml, then uncomment the following lines and add your own API keys:

You're done.

Credits

• William Durand [email protected]
• All contributors

Contributor Code of Conduct

As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, age, or religion.

Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. Project maintainers who do not follow the Code of Conduct may be removed from the project team.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.

This Code of Conduct is adapted from the Contributor Covenant, version 1.0.0, available at http://contributor-covenant.org/version/1/0/0/

License

Geocoder is released under the MIT License. See the bundled LICENSE file for details.