It seems like this problem is still here: https://github.com/michaeldrennen/Geonames/issues/18 PHP constant DIRECTORY_SEPARATOR on Windows system is backslash: "\" On MySQL query running it make a troubles:

# php.exe artisan geonames:install --country=EN --language=en
.............................................................
Inserting via LOAD DATA INFILE: D:\OpenServer\domains\project\storage\geonames\iso-languagecodes.txt
SQLSTATE[HY000]: General error: 7890 Can't find file 'D:OpenServerdomainsprojectstoragegeonamesiso-languagecodes'.

PDO::exec("LOAD DATA LOCAL INFILE 'D:\OpenServer\domains\project\storage\geonames\iso-languagecodes.txt'
    INTO TABLE geonames_iso_language_codes_working IGNORE 1 LINES
        (   iso_639_3,
            iso_639_2,
            iso_639_1,
            language_name,
            @created_at,
            @updated_at)
    SET created_at=NOW(),updated_at=null")

When i'm running

php artisan geonames:install --country=ru --language=ru

i get error :

SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'isHistoric' at row 1 (SQL: insert into geonames_alternate_names_working (alternateNameId, geonameid, isolanguage, alternate_name, isPreferredName, isShortName, isColloquial, isHistoric, updated_at, created_at) values (9528154, 472757, en, Volgograd, 1, 0, 0, 1961, 2018-05-04 09:19:35, 2018-05-04 09:19:35))
/var/www/zdravproduct-app/vendor/laravel/framework/src/Illuminate/Database/Connection.php:664

Looks like isHistoric tinyint but trying insert value '1961'

Change DIRECTORY_SEPARATOR to environment variable with default value.

See issue #43: Problems with backslash (Windows, DIRECTORY_SEPARATOR)

It's important to merge pull request to LocalFile package at first: https://github.com/michaeldrennen/LocalFile/pull/5

Hello Michael and thank you for your contribution! Will be any updates about latest Laravel?

Log file: Problem 1 - Conclusion: remove laravel/framework v7.9.2 - Conclusion: don't install laravel/framework v7.9.2 - michaeldrennen/geonames v3.0.0 requires illuminate/database ^6.8 -> satisfiable by laravel/framework[6.x-dev], illuminate/database[6.x-dev, v6.10.0, v6.11.0, v6.12.0, v6.13.0, v6.13.1, v6.14.0, v6.15.0, v6.15.1, v6.16.0, v6.17.0, v6.17.1, v6.18.0, v6.18.1, v6.18.10, v6.18.11, v6.18.2, v6.18.3, v6.18.4, v6.18.5, v6.18.6, v6.18.7, v6.18.8, v6.18.9, v6.8.0]. - michaeldrennen/geonames v3.0.1 requires illuminate/database ^6.8 -> satisfiable by laravel/framework[6.x-dev], illuminate/database[6.x-dev, v6.10.0, v6.11.0, v6.12.0, v6.13.0, v6.13.1, v6.14.0, v6.15.0, v6.15.1, v6.16.0, v6.17.0, v6.17.1, v6.18.0, v6.18.1, v6.18.10, v6.18.11, v6.18.2, v6.18.3, v6.18.4, v6.18.5, v6.18.6, v6.18.7, v6.18.8, v6.18.9, v6.8.0]. - Can only install one of: laravel/framework[6.x-dev, v7.9.2]. - don't install illuminate/database 6.x-dev|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.10.0|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.11.0|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.12.0|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.13.0|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.13.1|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.14.0|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.15.0|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.15.1|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.16.0|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.17.0|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.17.1|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.0|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.1|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.10|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.11|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.2|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.3|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.4|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.5|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.6|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.7|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.8|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.18.9|don't install laravel/framework v7.9.2 - don't install illuminate/database v6.8.0|don't install laravel/framework v7.9.2 - Installation request for laravel/framework (locked at v7.9.2, required as ^7.0) -> satisfiable by laravel/framework[v7.9.2]. - Installation request for michaeldrennen/geonames ^3.0 -> satisfiable by michaeldrennen/geonames[v3.0.0, v3.0.1].

The problem

I'm testing ^2.0 version of this package and found to install exactly the version 2.0.2 after requiring it through Composer.

When I ran the php artisan migration I'm getting the following error:

Illuminate\Database\QueryException :
SQLSTATE[42000]:
Syntax error or access violation:
1071 Specified key was too long; max key length is 1000 bytes
(SQL: alter table `geonames_alternate_names` add index `geonames_alternate_names_alternate_name_index`(`alternate_name`))

Digging through the migration code I found that it was thrown into 2017_02_11_145951_create_geonames_alternate_names_table.php line 70:

$table->index( 'alternate_name' );

If we comment this line the Artisan's migration command will run without any errors. But I went even deeper into the problem:

Some explanation

The error says that the max key length is 1000 bytes and the above highlighted line is trying to create an index key for the alternate_name column. This column is defined in the same migration file at line 37 as a VARCHAR with length 400 (!!!). When we define the length of a column explicitly how it is done at this line, the code Schema::defaultStringLength(191) may be inserted into boot method of AppServiceProvider.php and will just be ignored (at least by this line) resulting on the same error because the basic Laravel collation is utf8mb4 which uses 4 bytes to each char on a VARCHAR column and 400 * 4 = 1600 bytes which is much greater than the maximum size of 1000 bytes to a key (like specified by the error).

What I recommend to solve it

I understand that creating an index to alternate_name column is useful to make filters when querying geonames_alternate_names table. But this table isn't important to everyone using this package (also depending on how and why we are using it there may have more tables which will not be important though). Also, this column stores something like a CSV data, so it could be parsed and stored in another way to avoid creating a VARCHAR(400).

Also, why not let us publish the migrations and commands and change them as we need?

Don't misunderstand me, the package is awesome, it just need a bit of improvement

./artisan route:cache gives that result :

Route cache cleared!

In Route.php line 917:
Unable to prepare route [geonames/examples/vue/element/autocomplete] for serialization. Uses Closure```

Hi! I'm trying to install your package and I am getting stuck on the migration. I have tried the appservice provider fix

use Illuminate\Support\Facades\Schema;
use Illuminate\Support\ServiceProvider;


class AppServiceProvider extends ServiceProvider
{
    /**
     * Register any application services.
     *
     * @return void
     */
    public function register()
    {
        //
    }

    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        Schema::defaultStringLength(191);
    }
}

Ive even tried changing the database engine to innodb

'mysql' => [
            'driver' => 'mysql',
            'url' => env('DATABASE_URL'),
            'host' => env('DB_HOST', '127.0.0.1'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'unix_socket' => env('DB_SOCKET', ''),
            'charset' => 'utf8mb4',
            'collation' => 'utf8mb4_unicode_ci',
            'prefix' => '',
            'prefix_indexes' => true,
            'strict' => true,
            'engine' => 'InnoDB',
            'options' => extension_loaded('pdo_mysql') ? array_filter([
                PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
            ]) : [],
        ],

I was hoping maybe you might have an idea?

alternate_name should have its index. Maybe with isPreferredName ? Usefull if we want to propose cities from a postcode. (Postcodes are stored in alternate_name of table geonames_alternate_names)

Problem 1
    - The requested package phpunit/phpunit (locked at 6.5.6, required as ~7.0) is satisfiable by phpunit/phpunit[6.5.6] but these conflict with your requirements or minimum-stability.
  Problem 2
    - Installation request for michaeldrennen/geonames ^1.0 -> satisfiable by michaeldrennen/geonames[v1.0.0].
    - michaeldrennen/geonames v1.0.0 requires ext-intl * -> the requested PHP extension intl is missing from your system.
  Problem 3
    - Installation request for sebastian/diff (locked at 2.0.1) -> satisfiable by sebastian/diff[2.0.1].
    - phpunit/phpunit 7.0.0 requires sebastian/diff ^3.0 -> satisfiable by sebastian/diff[3.0.0].
    - phpunit/phpunit 7.0.1 requires sebastian/diff ^3.0 -> satisfiable by sebastian/diff[3.0.0].
    - phpunit/phpunit 7.0.2 requires sebastian/diff ^3.0 -> satisfiable by sebastian/diff[3.0.0].
    - Conclusion: don't install sebastian/diff 3.0.0
    - Installation request for phpunit/phpunit ~7.0 -> satisfiable by phpunit/phpunit[7.0.0, 7.0.1, 7.0.2].

Running, "php artisan geonames:install" on a homestead installations eventually runs out of memory. PHP memory usage increases until all available memory is consumed. Not sure is this a system configuration issue or an issue with the alternate names command.

Split file #289 of 2583 has 5000 rows. Inserting alternate names 1359/5000 [▓▓▓▓▓▓▓░░░░░░░░░░░░░░░░░░░░░]  27%

mmap() failed: [12] Cannot allocate memory

mmap() failed: [12] Cannot allocate memory PHP Fatal error:  Out of memory (allocated 4495486976) (tried to allocate 16384 bytes) in /vagrant/dr-services/vendor/laravel/framework/src/Illuminate/Database/Connection.php on line 330

mmap() failed: [12] Cannot allocate memory

mmap() failed: [12] Cannot allocate memory PHP Fatal error:  Out of memory (allocated 4495486976) (tried to allocate 65536 bytes) in /vagrant/dr-services/vendor/laravel/framework/src/Illuminate/Auth/SessionGuard.php on line 18

I'm getting error as following when I execute php artisan geonames:install --country=TR --country=US

File: /home/forge/app/storage/geonames/TR.txt

Combining TR.txt 10669811/10669811 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%
File: /home/forge/app/storage/geonames/US.txt

Combining US.txt 302388147/302388147 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%
Num Lines: 2323203

Starting to insert the records found in /home/forge/app/storage/geonames/master.txt
We are going to try to insert 2323202 geoname records.
Dropping the temp table named geonames_working (if it exists).
Creating the temp table named geonames_working
Running the LOAD DATA INFILE query...
SQLSTATE[HY000]: General error: 1300 Invalid utf8 character string: ''Iowa,Aioua,Aiova,Ajov,Ajova,Ajovae,Ajovo,Ayova,Ayowa,Hawkeye St'

First of all, thank you for this package that makes life easier!

My question is in the title: Is it possible to add countries without deleting existing ones ?

I've already installed US and Canada records
php artisan geonames:install --country=US --country=CA
and I'd like to add Brazil without reinstalling US and Canada ~~php artisan geonames:install --country=US --country=CA --country=BR~~ php artisan geonames:add --country=BR equivalent?

This commit is part of a campaign to reduce the amount of data transferred to save global bandwidth and reduce the amount of CO2. See https://github.com/Codeception/Codeception/pull/5527 for more info.

I was just thinking geonames could be laravel-ized and low and behold... !

I don't need the full database of geonames. For example in a current project i need cities with their countries, administrative areas, continents etc for cities with a population over 10,000.

Is there a reason why there is no foreign keys from geonames table to the admin tables, alternate names, hierarchy (parent and child)?