Download the PHP package abivia/geocoding without Composer
On this page you can find all versions of the php package abivia/geocoding. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
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 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.
Informations about the package geocoding
Abivia Geocoding
The Abivia geocoding library provides a caching interface to IP address lookup APIs provided by ipinfo.io and ipstack.com. The library supports both IPv4 and IPv6 addresses and is designed to seamlessly support other IP address geocoding services.
Requirements
Geocoding requires:
- PHP 8.2 or higher
- ext-curl to perform API calls
- abivia/cogs for address support
- mlocati/ip-lib for IP address support
PHP does not need to be built with IPv6 support.
Installation
Via composer:
Caching
Geocoding comes with two cache handlers designed for light use and a database cache for heavier use. The array cache will retain lookup results for the lifetime of the current request (or session if stored in a session variable). The file cache stores cached data in a text file. Neither offers support for concurrent requests.
The PDO Cache takes a connection to a database, optionally with table names to override the
default tables geocoder_cache_ip, geocoder_cache_subnet and geocoder_cache_options.
The cache handler will create these tables if they do not already exist.
Applications can create persistent caches by conforming to the CacheHandler interface. Caches support different retention times for lookup hits and lookup misses. In a file cache, the default retention time for a successful lookup is seven days, the default retention time for a failed lookup is one hour. The PDO cache defaults to 30 days for a successful lookup and one hour for a failed lookup.
Cache Purging
Array caches are expected to be transient, so there is no purge logic.
The file cache runs a purge at the time the cache is loaded.
The PDO cache runs at the interval set by the purgeCacheTime() method, which defaults to 24 hours.
On the first object creation,
the last purge time is loaded from the database and cached in the session to reduce overhead.
Sample Usage
The geocoder normalizes results from different services using the GeocodeResult interface, but applications can retrieve the service's response through the GeocodeResult::data() method to access extended information.
Example using a file cache
Subnet queries
For the most part from a geolocation perspective, only the first 24 bits of an IPv4 and the first 48 of an IPv6 address are significant. Geocoding provides a "subnet" query that will return the last queries result in the v4 or v6 range. This can reduce the number of queries on the lookup service, increasing performance and (in the case of paid services) reducing costs.
Subnet Example
Donations welcome
If you're getting something out of Geocoding, you can sponsor us in any amount you wish using Liberapay
.
Liberapay is itself run on donations and takes no fees beyond bank charges.
All versions of geocoding with dependencies
ext-curl Version *
abivia/cogs Version ^2
mlocati/ip-lib Version ^1
ext-pdo Version *