Download the PHP package xlvis7/geonames without Composer
On this page you can find all versions of the php package xlvis7/geonames. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download xlvis7/geonames
More information about xlvis7/geonames
Files in xlvis7/geonames
Package geonames
Short Description A Laravel (php) package that interfaces with the geolocation services on geonames.org.
License MIT
Informations about the package geonames
geonames v2.x
A Laravel (php) package to interface with the geo-location services at geonames.org.
Notes
Forked by xlvis7 to support Laravel7
There is still a lot that needs to be done to make this package "complete". I've gotten it to a point where I can use it for my next project. As time allows, I will improve the documentation and testing that comes with this package. Thanks for understanding.
Installation
And then add geonames
provider to providers
array in app.php
config file:
After that, Run migrate command:
Want to install all of the geonames records for the US, Canada, and Mexico as well as pull in the feature codes definitions file in English?
Want to just install everything in the geonames database?
Maintenance
Now that you have the geonames database up and running on your system, you need to keep it up-to-date.
I have an update script that you need to schedule in Laravel to run every day.
Some info on how to schedule Laravel artisan commands:
https://laravel.com/docs/5.6/scheduling#scheduling-artisan-commands
You can read this notice at: http://download.geonames.org/export/dump/
The "last modified" timestamp is in Central European Time.
It looks like geonames updates their data around 3AM CET.
So if you schedule your system to run the geonames:update artisan command after 4AM CET, you should be good to go.
I like to keep my servers running on GMT. Keeps things consistent.
(Central European Time is 1 hour ahead of Greenwich Mean Time)
Assuming your servers are running on GMT, your update command would look like:
The update artisan command will handle the updates and deletes to the geonames table.
Gotchas
Are you getting something like: 1071 Specified key was too long
@see https://laravel-news.com/laravel-5-4-key-too-long-error
Add this to your AppServiceProvider.php file:
A quick word on indexes
This library contains a bunch of migrations that contain a bunch of indexes. Now not everyone will need all of the indexes.
So when you install this library, run the migrations and delete the indexes that you don't need.
Also, Laravel doesn't let you specify a key length for indexes on varchar columns. There are two indexes suffering from this limit. Instead of creating indexes on those columns the "Laravel way", I send a raw/manual query to create the indexes with the proper lengths.
All versions of geonames with dependencies
ext-intl Version *
ext-pdo Version *
ext-curl Version *
laravel/framework Version ^7.0
michaeldrennen/remote-file Version ^2.0
michaeldrennen/local-file Version ^2.0
curl/curl Version ^2.2
fabpot/goutte Version ^4.0
nesbot/carbon Version ^2.28
illuminate/routing Version ^7.0
illuminate/support Version ^7.0
illuminate/database Version ^7.0