coderholic / django-cities Goto Github PK

This is likely to have been caused by recent changes, when doing syncdb:

Traceback (most recent call last):
File "./manage.py", line 20, in
execute_from_command_line()
File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/core/management/init.py", line 429, in execute_from_command_line
utility.execute()
File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/core/management/init.py", line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/core/management/base.py", line 191, in run_from_argv
self.execute(_args, *_options.dict)
File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/core/management/base.py", line 219, in execute
self.validate()
File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/core/management/base.py", line 249, in validate
num_errors = get_validation_errors(s, app)
File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/core/management/validation.py", line 35, in get_validation_errors
for (app_name, error) in get_app_errors().items():
File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/db/models/loading.py", line 146, in get_app_errors
self._populate()
File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/db/models/loading.py", line 61, in _populate
self.load_app(app_name, True)
File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/db/models/loading.py", line 78, in load_app
models = import_module('.models', app_name)
File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module
import(name)
File "/srv/art_dev/art_dev_env/src/cities/cities/models.py", line 4, in
from conf import settings
File "/srv/art_dev/art_dev_env/src/cities/cities/conf.py", line 129, in
settings = create_settings()
File "/srv/art_dev/art_dev_env/src/cities/cities/conf.py", line 107, in create_settings
res.files.update(django_settings.CITIES_FILES)
File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/utils/functional.py", line 277, in getattr
return getattr(self._wrapped, name)
AttributeError: 'Settings' object has no attribute 'CITIES_FILES'

Error is the following

INFO Importing district data
WARNING District: Fier-Cifci: Cannot find city in hierarchy, using nearest

AttributeError: 'DatabaseOperations' object has no attribute 'mysql'

I am using Postgres for my backend.
'ENGINE': 'django.contrib.gis.db.backends.postgis'

All other tables [ie. city, regions, etc.. ] loaded properly into the database. Districts however fails to import with the above error. Stuck?

I am on ubuntu 12.x.x using bitnami djangostack 1.5.4 dev

Warning: Incorrect string value: '\xC5\xAB Z\xCC\xA7...' for column 'name' at row 1

Not sure what is causing this.

Hi,

Could it be that Django-Cities does not allow for abbreviations of locations? e.g. "Northrhein-Westphalen" (a German state) is commonly abbreviated as "NRW". The abbreviation can be found in Geonames for that state but we can't get it out on our end.

Hi, is it possible to download also cities with population less than 1000?

I've been reading through the import scripts and have found multiple places where the import scripts were set to silently fail when the data was not in the exact correct format. among other problems:

1. There NEEDS to be a transaction around the import process. At the very least have @method_decorator(transaction.commit_on_success) on the handle() method. This one line cuts my import time in half and ensures my db is never incomplete.

2. tab delimited files are not opened with csv.Reader, cannot take advantage of header names, entire file is read into memory instead of iterated over. I'd imagine this to introduce a reasonable performance penalty....

3. There is also a LOT of magic numbers everywhere:

   country.name = items[4]
   country.code = items[0]
   country.population = items[7]
   country.continent = items[8]
   country.tld = items[9][1:]
   

   needs something more like this:

   country.name = row[HEADER_COUNTRY_NAME]
   

4. There needs to be some effort put in to explicitly define what happens when data does not line up:

   try: country.id = int(items[16])
   except: continue
   

   This fails any country that does not have a column 16. What is column 16? why would it be missing? what does this mean for the rest of the imported data?

I'm happy to work on this code if someone is happy to go through what all the table columns are with me, because I don't have a clue....

I use django 1.7 and python 3.4

./manage.py migrate
I get this:
Traceback (most recent call last):
File "./manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/home/cosmin/.v/gasit/lib/python3.4/site-packages/django/core/management/init.py", line 385, in execute_from_command_line
utility.execute()
File "/home/cosmin/.v/gasit/lib/python3.4/site-packages/django/core/management/init.py", line 354, in execute
django.setup()
File "/home/cosmin/.v/gasit/lib/python3.4/site-packages/django/init.py", line 21, in setup
apps.populate(settings.INSTALLED_APPS)
File "/home/cosmin/.v/gasit/lib/python3.4/site-packages/django/apps/registry.py", line 108, in populate
app_config.import_models(all_models)
File "/home/cosmin/.v/gasit/lib/python3.4/site-packages/django/apps/config.py", line 197, in import_models
self.models_module = import_module(models_module_name)
File "/home/cosmin/.v/gasit/lib/python3.4/importlib/init.py", line 109, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 2254, in _gcd_import
File "", line 2237, in _find_and_load
File "", line 2226, in _find_and_load_unlocked
File "", line 1200, in _load_unlocked
File "", line 1129, in _exec
File "", line 1471, in exec_module
File "", line 321, in _call_with_frames_removed
File "/home/cosmin/.v/gasit/lib/python3.4/site-packages/cities/models.py", line 1, in
from django.utils.encoding import force_unicode
ImportError: cannot import name 'force_unicode'

Hey,

Can you upload 0.4 release on PyPI, 0.3 is latest..

In cities.models.create_geo_alt_names:

name_format = geo_type.name + '{}' + locale.capitalize()

..requires a positional value in the replacement field '{}', i.e. '{0}'

I am getting the following:

cities.CityAltNameEn.is_preferred: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more
information.
cities.CityAltNameEn.is_short: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more
information.
cities.CityAltNameUnd.is_preferred: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more
information.
cities.CityAltNameUnd.is_short: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more
information.
cities.CountryAltNameEn.is_preferred: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more
information.
cities.CountryAltNameEn.is_short: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.

    HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.

cities.CountryAltNameUnd.is_preferred: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.CountryAltNameUnd.is_short: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.DistrictAltNameEn.is_preferred: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.DistrictAltNameEn.is_short: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.DistrictAltNameUnd.is_preferred: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.DistrictAltNameUnd.is_short: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.RegionAltNameEn.is_preferred: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.RegionAltNameEn.is_short: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.RegionAltNameUnd.is_preferred: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.RegionAltNameUnd.is_short: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.SubregionAltNameEn.is_preferred: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.SubregionAltNameEn.is_short: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.SubregionAltNameUnd.is_preferred: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
cities.SubregionAltNameUnd.is_short: (1_6.W002) BooleanField does not have a default value.
HINT: Django 1.6 changed the default value of BooleanField from False to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.

Currently the optional postcode and alternative name models are dynamically generated based on configuration details provided in settings.py, and a separate model is created for each of the different configuration options. I think the code would be much more readable and maintainable if this magic is removed.

@kometes sorry for not flagging this at the time you issued your pull request - I should have been paying closer attention but was super busy at the time. It'd be great it you could give me some insight into why you took this approach, and why you feel it works better than having single PostalCode and AltName models that have a country and locale field respectively, instead of a model for every country and locale?

Somehow (some django magic involved) moving the admin registration call into an admin.py file resolved some weird import dependencies we could not resolved in our project.

We're forking it an will send a pull request. No change to code, just moved 5-6 lines to another file, the way it should be done.

At least in Django 1.2.3, this plugin will not run without installation of the libgeos C library. A mention of this in the documentation should be made.

Hello,

On runing command :
./manage.py cities --flush=all

when is flushing alt_names error:

File "/home/aliona/hpn.aksprendimai.lt/aruodai/cities/management/commands/cities.py", line 517, in flush_alt_name
[geo_alt_name.objects.all().delete() for locales in geo_alt_names.values() for geo_alt_name in locales.values()]
NameError: global name 'geo_alt_names' is not defined

All another date flushing pass OK.

It appears that mysql backend doesn't have distance() function, which is called during import process in some cases

Could we have a workaround to handle it ?

because of that, we can't sanely use mysql....

There is a lot of quebec cities in wrong regions

For example :
Laval (id:6050610) appears to be located in Northwest Territories,
Lavaltrie (id:6050650) appears in Nunavut,

We noticed at least 50 errors like those.

The lat-long are ok (but for Lasalle, there is indeed a lasalle located at those lat-long but the population is for another Lasalle(near of Montreal))

Hi There,

First of all, thanks for sharing the app! I got the following output after running syncdb (I am using a PostgreSQL db with PostGIS 2.0 and Django 1.4.1):

Syncing...
Creating tables ...
Creating table cities_country
Creating table cities_region
Creating table cities_subregion
Creating table cities_city
Creating table cities_district
Creating table cities_country_alt_name_en
Creating table cities_country_alt_name_und
Creating table cities_region_alt_name_en
Creating table cities_region_alt_name_und
Creating table cities_subregion_alt_name_en
Creating table cities_subregion_alt_name_und
Creating table cities_city_alt_name_en
Creating table cities_city_alt_name_und
Creating table cities_district_alt_name_en
Creating table cities_district_alt_name_und
Installing custom SQL ...
Installing indexes ...
Failed to install index for cities.City model: AddGeometryColumn() - invalid SRID
CONTEXT: SQL statement "SELECT AddGeometryColumn('','',$1,$2,$3,$4,$5, $6)"
PL/pgSQL function "addgeometrycolumn" line 5 at SQL statement

Failed to install index for cities.District model: AddGeometryColumn() - invalid SRID
CONTEXT: SQL statement "SELECT AddGeometryColumn('','',$1,$2,$3,$4,$5, $6)"
PL/pgSQL function "addgeometrycolumn" line 5 at SQL statement

Any help would be great, thanks!!

Fei

I get this error when running syncdb as soon as i install the app. Not sure if there are dependencies for the app and what they are in order to get it running. Appreciate the help. Thanks.

Is this a bug, or do we have a migration / South problem?

When we add places without cities, we get the error column cities_city.subregion_id does not exist.

I have fixed it with ALTER TABLE cities_city ADD COLUMN subregion_id integer; but wonder if there's a by the book way of doing it?

http://download.geonames.org/export/dump/admin1Codes.txt is no longer available as it been removed due to all the encoding error it had. now everything is available in http://download.geonames.org/export/dump/admin1CodesASCII.txt.

changing line 79 of update_cities_geodata.py with the new url made the import proccess work.

thought midway it has encoding problems that i'm still trying to figure out.

I have run

./manage.py cities --import=all

it does not write a single line.

I have following settings:

CITIES_LOCALES = ['en', 'cs', 'LANGUAGES']

# Postal codes will be imported for all ISO 3166-1 alpha-2 country codes below.
# See cities.conf for a full list of country codes.
# See download.geonames.org/export/dump/countryInfo.txt
CITIES_POSTAL_CODES = ['US', 'CA', 'CS']

# List of plugins to process data during import
CITIES_PLUGINS = [
]

Import seems to be fine but when I try to look for anything it does nothing:

>>> from cities.models import Country, Region, City, District
>>> City.objects.filter()
[]
>>> 

What should I do?

Is it normal to have this behavior while importing datas ?

(lot of)
City: Henstedt-Ulzburg: Cannot find region 2: DE.10.00
City: Wesenberg: Cannot find region 2: DE.10.00
City: Moraas: Cannot find region 2: DE.12.00
City: Fargau-Pratjau: Cannot find region 2: DE.10.00
City: Admannshagen-Bargeshagen: Cannot find region 2: DE.12.00
City: Bartenshagen-Parkentin: Cannot find region 2: DE.12.00
City: Borgerende-Rethwisch: Cannot find region 2: DE.12.00
City: Diensdorf-Radlow: Cannot find region 2: DE.11.00
City: Bruchhausen: Cannot find region 2: DE.08.00
City: Brohl-Lutzing: Cannot find region 2: DE.08.00
City: Schmedeswurth: Cannot find region 2: DE.10.00
City: Barnitz: Cannot find region 2: DE.10.00
City: Peterswald-Loffelscheid: Cannot find region 2: DE.08.00
City: Stadecken-Elsheim: Cannot find region 2: DE.08.00
City: Dannstadt-Schauernheim: Cannot find region 2: DE.08.00
City: Rodersheim-Gronau: Cannot find region 2: DE.08.00
City: Billigheim-Ingenheim: Cannot find region 2: DE.08.00
City: Bohl-Iggelheim: Cannot find region 2: DE.08.00
City: Hochdorf-Assenheim: Cannot find region 2: DE.08.00
City: Dittelsheim-Hessloch: Cannot find region 2: DE.08.00
City: Hochborn: Cannot find region 2: DE.08.00
City: Heuchelheim-Klingen: Cannot find region 2: DE.08.00
and so on

Title says it all!

Traceback (most recent call last):
File "../manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/home/django/virtualenvs/site1/src/django/django/core/management/init.py", line 427, in execute_from_command_line
utility.execute()
File "/home/django/virtualenvs/site1/src/django/django/core/management/init.py", line 391, in execute
django.setup()
File "/home/django/virtualenvs/site1/src/django/django/init.py", line 21, in setup
apps.populate(settings.INSTALLED_APPS)
File "/home/django/virtualenvs/site1/src/django/django/apps/registry.py", line 112, in populate
app_config.ready()
File "/home/django/virtualenvs/site1/src/django/django/contrib/admin/apps.py", line 22, in ready
self.module.autodiscover()
File "/home/django/virtualenvs/site1/src/django/django/contrib/admin/init.py", line 23, in autodiscover
autodiscover_modules('admin', register_to=site)
File "/home/django/virtualenvs/site1/src/django/django/utils/module_loading.py", line 74, in autodiscover_modules
import_module('%s.%s' % (app_config.name, module_to_search))
File "/usr/lib/python2.7/importlib/init.py", line 37, in import_module
import(name)
File "/home/django/virtualenvs/site1/src/django-cities/cities/admin.py", line 29, in
class CityAdmin(CityBaseAdmin):
File "/home/django/virtualenvs/site1/src/django-cities/cities/admin.py", line 30, in CityAdmin
raw_id_fields = Region.levels
AttributeError: type object 'Region' has no attribute 'levels'

Hi, I'm using Django1.5 and django-cities0.4 (zip downloaded from this repo) and I'm getting the following error when trying to make "python2.7 manage.py cities --force --import=all" on a fresh install:

KeyError: 'fields'

this is after a long time (around 20mins). After that, the following tables are populated (I'm not sure if all the data that should be loaded is loaded): cities_country, cities_country_neighbours, cities_region and cities_subregion. Also, the follogin tables are empty: cities_city, cities_district, cities_postalcode.

Hi, Thanks for creating a great django module. After installing via pip, I noticed that there is no PostalCode model in the pypi version, while there is in the git version. Both versions say they are 0.2, which led to some confusion for me. I ended up using the git version and it works great. Thanks!

Loading data does not work with the new django-cities version on PostgreSQL 9.1.1 with PostGIS 1.5.3

time ./manage.py loaddata geonames_dump
Problem installing fixture '/srv/art/art_env/src/cities/cities/fixtures/geonames_dump.json': Traceback (most recent call last):
File "/srv/art/art_env/lib/python2.7/site-packages/django/core/management/commands/loaddata.py", line 174, in handle
obj.save(using=using)
File "/srv/art/art_env/lib/python2.7/site-packages/django/core/serializers/base.py", line 165, in save
models.Model.save_base(self.object, using=using, raw=True)
File "/srv/art/art_env/lib/python2.7/site-packages/django/db/models/base.py", line 553, in save_base
result = manager._insert(values, return_id=update_pk, using=using)
File "/srv/art/art_env/lib/python2.7/site-packages/django/db/models/manager.py", line 195, in _insert
return insert_query(self.model, values, **kwargs)
File "/srv/art/art_env/lib/python2.7/site-packages/django/db/models/query.py", line 1436, in insert_query
return query.get_compiler(using=using).execute_sql(return_id)
File "/srv/art/art_env/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 791, in execute_sql
cursor = super(SQLInsertCompiler, self).execute_sql(None)
File "/srv/art/art_env/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 735, in execute_sql
cursor.execute(sql, params)
File "/srv/art/art_env/lib/python2.7/site-packages/django/db/backends/util.py", line 34, in execute
return self.cursor.execute(sql, params)
File "/srv/art/art_env/lib/python2.7/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 44, in execute
return self.cursor.execute(query, args)
DatabaseError: invalid byte sequence for encoding "UTF8": 0x00

./manage.py loaddata geonames_dump 13.49s user 0.59s system 85% cpu 16.390 total

Please let me know if I can provide any other information.

Postgresql: 9.1.1
Postgis: 1.5
Geos: 3.3.0-1
Proj: 4.7.0
Django: 1.3,1
Distro: Arch

Settings:

CITIES_FILES = {
    'city': {
       'filename': 'cities5000.zip',
       'urls':     ['http://download.geonames.org/export/dump/'+'{filename}']
    },
}

CITIES_POSTAL_CODES = ['US','CA', 'FR']
CITIES_LOCALES = ['en', 'fr']
CITIES_PLUGINS = [
    'cities.plugin.postal_code_ca.Plugin',
]

Error when running "cities" command:

Traceback (most recent call last):
  File "./manage.py", line 20, in <module>
    execute_from_command_line()
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/core/management/__init__.py", line 429, in execute_from_command_line
    utility.execute()
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/core/management/__init__.py", line 379, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/core/management/base.py", line 191, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/core/management/base.py", line 220, in execute
    output = self.handle(*args, **options)
  File "/srv/art_dev/art_dev_env/src/cities/cities/management/commands/cities.py", line 68, in handle
    func()
  File "/srv/art_dev/art_dev_env/src/cities/cities/management/commands/cities.py", line 494, in import_postal_code
    pc.save()
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/db/models/base.py", line 460, in save
    self.save_base(using=using, force_insert=force_insert, force_update=force_update)
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/db/models/base.py", line 553, in save_base
    result = manager._insert(values, return_id=update_pk, using=using)
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/db/models/manager.py", line 195, in _insert
    return insert_query(self.model, values, **kwargs)
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/db/models/query.py", line 1436, in insert_query
    return query.get_compiler(using=using).execute_sql(return_id)
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 791, in execute_sql
    cursor = super(SQLInsertCompiler, self).execute_sql(None)
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 735, in execute_sql
    cursor.execute(sql, params)
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/db/backends/util.py", line 34, in execute
    return self.cursor.execute(sql, params)
  File "/srv/art_dev/art_dev_env/lib/python2.7/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 44, in execute
    return self.cursor.execute(query, args)
django.db.utils.DatabaseError: invalid byte sequence for encoding "UTF8": 0x00

Also here are some errors from shell_plus command:

Failed to import 'CountryAltNameFr' from 'cities' reason: 'module' object has no attribute 'CountryAltNameFr'
Failed to import 'CountryAltNameEn' from 'cities' reason: 'module' object has no attribute 'CountryAltNameEn'
Failed to import 'RegionAltNameFr' from 'cities' reason: 'module' object has no attribute 'RegionAltNameFr'
Failed to import 'RegionAltNameEn' from 'cities' reason: 'module' object has no attribute 'RegionAltNameEn'
Failed to import 'CityAltNameFr' from 'cities' reason: 'module' object has no attribute 'CityAltNameFr'
Failed to import 'CityAltNameEn' from 'cities' reason: 'module' object has no attribute 'CityAltNameEn'
Failed to import 'DistrictAltNameFr' from 'cities' reason: 'module' object has no attribute 'DistrictAltNameFr'
Failed to import 'DistrictAltNameEn' from 'cities' reason: 'module' object has no attribute 'DistrictAltNameEn'
Failed to import 'PostalCodeCA' from 'cities' reason: 'module' object has no attribute 'PostalCodeCA'
Failed to import 'PostalCodeFR' from 'cities' reason: 'module' object has no attribute 'PostalCodeFR'
Failed to import 'PostalCodeUS' from 'cities' reason: 'module' object has no attribute 'PostalCodeUS'

The import seems to run for a long while but after about an hour and half it craps out as per the below error, any suggestions before I start tearing into the issue? Me thinks it might be Spatialite setup, Super thank you!

#python manage.py cities --import=all --settings=settings_development
...
DEBUG cities cities.py@304: Added city: Banket, Mashonaland West Province, Zimbabwe
DEBUG django.db.backends util.py@51: (0.000) SELECT (1) AS "a" FROM "cities_city" WHERE "cities_city"."id" = 1106542  LIMIT 1; args=(1106542,)
DEBUG django.db.backends util.py@51: (0.001) INSERT INTO "cities_city" ("id", "name", "slug", "name_std", "location", "population", "region_id", "subregion_id", "country_id") VALUES (1106542, Chitungwiza, chitungwiza, Chitungwiza, GeomFromText(POINT (31.0755499999999998 -18.0127400000000009),4326), 340360, 1105844, None, 878675); args=[1106542, 'Chitungwiza', u'chitungwiza', 'Chitungwiza', <django.contrib.gis.db.backends.spatialite.adapter.SpatiaLiteAdapter object at 0x19112e4c>, 340360, 1105844, None, 878675]
DEBUG cities cities.py@304: Added city: Chitungwiza, Harare Province, Zimbabwe
INFO cities cities.py@112: Downloading: hierarchy.zip
INFO cities cities.py@312: Building hierarchy index
INFO cities cities.py@328: Building city index
DEBUG django.db.backends util.py@51: (0.074) SELECT "cities_city"."id", "cities_city"."name", "cities_city"."slug", "cities_city"."name_std", AsText("cities_city"."location"), "cities_city"."population", "cities_city"."region_id", "cities_city"."subregion_id", "cities_city"."country_id" FROM "cities_city"; args=()
INFO cities cities.py@333: Importing district data
WARNING cities cities.py@347: District: Fier-Cifci: Cannot find city in hierarchy, using nearest
DEBUG django.db.backends util.py@51: (0.001) SELECT "spatial_ref_sys"."srid", "spatial_ref_sys"."auth_name", "spatial_ref_sys"."auth_srid", "spatial_ref_sys"."ref_sys_name", "spatial_ref_sys"."proj4text" FROM "spatial_ref_sys" WHERE "spatial_ref_sys"."srid" = 4326 ; args=(4326,)
DatabaseError: no such table: spatial_ref_sys

python ./manage.py cities --settings=bookingpal.settings.staging --import=region --force

INFO File up-to-date: admin1CodesASCII.txt
INFO Building country index
INFO Importing region data
Traceback (most recent call last):
  File "./manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/var/www/bookingpal.com/releases/20140622112133/virtualenv/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
    utility.execute()
  File "/var/www/bookingpal.com/releases/20140622112133/virtualenv/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/var/www/bookingpal.com/releases/20140622112133/virtualenv/local/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/var/www/bookingpal.com/releases/20140622112133/virtualenv/local/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "/var/www/bookingpal.com/releases/20140622112133/virtualenv/local/lib/python2.7/site-packages/cities/management/commands/cities.py", line 68, in handle
    func()
  File "/var/www/bookingpal.com/releases/20140622112133/virtualenv/local/lib/python2.7/site-packages/cities/management/commands/cities.py", line 222, in import_region
    self.logger.warning("{0}: {1}: Cannot find country: {2} -- skipping".format(class_.__name__, region.name, country_code))
NameError: global name 'class_' is not defined

Hi,

I have installed django-cities in one of my geo-spatial projects (postgis works fine). The installation of django-cities was effortless and the dbsync worked fine as well.

However, when I try to execute "./manage.py cities --import=all", the import function throws the following error message after 20 seconds. Can you please give me an understanding what might cause this error? Thank you!

./manage.py cities --import=all
Traceback (most recent call last):
File "./manage.py", line 23, in
execute_from_command_line()
File "/Users/h/Development/v/lib/python2.7/site-packages/django/core/management/init.py", line 429, in execute_from_command_line
utility.execute()
File "/Users/h/Development/v/lib/python2.7/site-packages/django/core/management/init.py", line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/Users/h/Development/v/lib/python2.7/site-packages/django/core/management/base.py", line 191, in run_from_argv
self.execute(_args, *_options.dict)
File "/Users/h/Development/v/lib/python2.7/site-packages/django/core/management/base.py", line 220, in execute
output = self.handle(_args, *_options)
File "/Users/h/Development/v/lib/python2.7/site-packages/cities/management/commands/cities.py", line 70, in handle
func()
File "/Users/h/Development/v/lib/python2.7/site-packages/cities/management/commands/cities.py", line 233, in import_subregion
if not self.call_hook('subregion_pre', items): continue
File "/Users/h/Development/v/lib/python2.7/site-packages/cities/management/commands/cities.py", line 73, in call_hook
for plugin in settings.plugins[hook]:
AttributeError: type object '' has no attribute 'plugins'

Hi :)

We are using your Library and we face a multipleobject with some of the cities.

=> select slug, count(*) from cities_region group by slug, country_id having count(*) > 1;
    slug      | count 
---------------+-------
daugavpils    |    2
lima          |    2
ash-sharqiyah |    2
vientiane    |    2
al-batinah    |    2
(5 rows)

What do you think it could be ?

Hi,

I experience an tricky problem with creating forms with contain a dropdown menu with foreignkeys to django-cities. When the form is supposed to be created, the DB is hit with a large number of requests for 'cities_region' and 'cities_country'. Normally, I restrict the DB requests with select_related, but I do not seem to have luck with django-cities in this matter.

The model for my Item class contains the following code:

from cities.models import City
class Item(models.Model):
name = models.CharField(...)
location = models.ForeignKey(City, blank = True, null = True)
...

and the views.py contain the class based view code:

from django.views.generic.edit import CreateView, UpdateView, DeleteView
from project.models import Project
class ItemCreate(CreateView):
queryset = Item.objects.select_related('city', 'city__country', 'city__region').all()
template_name = 'item_create_form.html'

When I now request the view class, I see an unlimited number of sql requests like below hitting the db and the page is not loading. It seems that the requests are created to fill the drop down box in the form menu.

SELECT "cities_country"."id", "cities_country"."name", "cities_country"."slug", "cities_country"."code", "cities_country"."population", "cities_country"."continent", "cities_country"."tld" FROM "cities_country" WHERE "cities_country"."id" = %s
(2077456,)
SELECT "cities_region"."id", "cities_region"."name", "cities_region"."slug", "cities_region"."name_std", "cities_region"."code", "cities_region"."country_id" FROM "cities_region" WHERE "cities_region"."id" = %s
(2147291,)

How are you restricting the requests to the DB when you include foreignkeys to the django-cities app?

Thanks for your thoughts.

Hi Ben,
Thanks for this project -- the import script especially is very useful!

I think I've spotted one small bug: the import script seems to be switching latitude and longitude for both City and District locations.

Lines 86 and 145 of import.py construct City and District Point objects as: Point(float(items[4]), float(items[5]), where I think it should be Point(float(items[5]), float(items[4]). In GeoNames cities1000.txt, col 5 (Items[4]) is Latitude and col 6 (items[5]) is Longitude. The Point constructor takes the arguments Point(x, y) or Point(Lon, Lat) instead of point Point(Lat, Lon) (see http://groups.google.com/group/django-users/browse_thread/thread/80dae95ee8f76361?pli=1).

Thanks again and keep up the good work!

Kevin

i have got this trace when i want to import datas

Downloading: countryInfo.txt
Importing country data
Downloading: admin1CodesASCII.txt
Building country index
Importing region 1 data
Traceback (most recent call last):
File "./manage.py", line 14, in
execute_manager(settings)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/core/management/init.py", line 438, in execute_manager
utility.execute()
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/core/management/init.py", line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/core/management/base.py", line 191, in run_from_argv
self.execute(_args, *_options.dict)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/core/management/base.py", line 220, in execute
output = self.handle(_args, *_options)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/cities/management/commands/cities.py", line 65, in handle
func()
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/cities/management/commands/cities.py", line 164, in import_region
self.import_region_0()
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/cities/management/commands/cities.py", line 218, in import_region_0
region.save()
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/db/models/base.py", line 460, in save
self.save_base(using=using, force_insert=force_insert, force_update=force_update)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/db/models/base.py", line 526, in save_base
rows = manager.using(using).filter(pk=pk_val)._update(values)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/db/models/query.py", line 491, in _update
return query.get_compiler(self.db).execute_sql(None)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 869, in execute_sql
cursor = super(SQLUpdateCompiler, self).execute_sql(result_type)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 735, in execute_sql
cursor.execute(sql, params)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/db/backends/util.py", line 34, in execute
return self.cursor.execute(sql, params)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/db/backends/mysql/base.py", line 86, in execute
return self.cursor.execute(query, args)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/MySQLdb/cursors.py", line 176, in execute
if not self._defer_warnings: self._warning_check()
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/MySQLdb/cursors.py", line 92, in _warning_check
warn(w[-1], self.Warning, 3)
_mysql_exceptions.Warning: Incorrect string value: '\xCA\xBCs al...' for column 'name_std' at row 1

thank you for help

I want to be able to use the Place model in its own right - ie one model that combines all the rest. But, with abstract=True it doesn't let me.

I get programming error when taking out abstract=True (and the Place model doesn't have a table associated with it and migrating doesn't create them).

Is there any way to use the Place model within an already set up django-cities app?

Cheers!

When I merged in one of Kometes pull requests I missed that it breaks the fixed hierarchy. It's now possible to have either one or two regions per city. That makes it much harder to work out the target model, eg:

/united-kingdom/england/hemsworth -> City
/united-kingdom/england/borough-of-swindon -> Region

It also adds a lot of complexity when creating place directories, because you need to check the region hierarchy. The hierarchy was originally fixed by design, and I'd like to return it to a fixed hierarchy. It'd be great to get some input on the best way to return to one while causing minimum disruption and still supporting all required use cases. I'm currently thinking of a new SubRegion class, and having a ForeignKey to both region and subregion on City. That way you could completely ignore SubRegions should you choose to.

Please be advised, I get the following traceback upon a syncdb of the "cities" app alongside the "geodjango" pre-requisite:

(funretire) C:\Users\code\workspace\funretire\src>python manage.py syncdb
Traceback (most recent call last):
File "manage.py", line 10, in
execute_from_command_line(sys.argv)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management__init__.py", line 399, in execute_from_command_line
utility.execute()
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management__init__.py", line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management\base.py", line 242, in run_from_argv
self.execute(args, *options.dict)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management\base.py", line 284, in execute
self.validate()
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management\base.py", line 310, in validate
num_errors = get_validation_errors(s, app)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management\validation.py", line 34, in get_validation_errors
for (app_name, error) in get_app_errors().items():
File "C:\Users\code\Envs\funretire\lib\site-packages\django\db\models\loading.py", line 196, in get_app_errors
self.populate()
File "C:\Users\code\Envs\funretire\lib\site-packages\django\db\models\loading.py", line 78, in populate
self.load_app(app_name)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\db\models\loading.py", line 99, in load_app
models = import_module('%s.models' % app_name)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\utils\importlib.py", line 40, in import_module
import(name)
File "C:\Users\code\Envs\funretire\lib\site-packages\cities\models.py", line 2, in
from django.contrib.gis.db import models
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\db\models__init.py", line 8, in
from django.contrib.gis.db.models.manager import GeoManager
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\db\models\manager.py", line 2, in
from django.contrib.gis.db.models.query import GeoQuerySet
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\db\models\query.py", line 6, in
from django.contrib.gis.db.models.fields import get_srid_info, PointField, LineStringField
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\db\models\fields.py", line 4, in
from django.contrib.gis import forms
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\forms__init.py", line 2, in
from .fields import (GeometryField, GeometryCollectionField, PointField,
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\forms\fields.py", line 11, in
from django.contrib.gis.geos import GEOSException, GEOSGeometry, fromstr
ImportError: cannot import name GEOSException

(funretire) C:\Users\code\workspace\funretire\src>python manage.py syncdb
Traceback (most recent call last):
File "manage.py", line 10, in
execute_from_command_line(sys.argv)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management__init__.py", line 399, in execute_from_command_line
utility.execute()
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management__init__.py", line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management\base.py", line 242, in run_from_argv
self.execute(args, *options.dict)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management\base.py", line 284, in execute
self.validate()
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management\base.py", line 310, in validate
num_errors = get_validation_errors(s, app)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\core\management\validation.py", line 34, in get_validation_errors
for (app_name, error) in get_app_errors().items():
File "C:\Users\code\Envs\funretire\lib\site-packages\django\db\models\loading.py", line 196, in get_app_errors
self.populate()
File "C:\Users\code\Envs\funretire\lib\site-packages\django\db\models\loading.py", line 78, in populate
self.load_app(app_name)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\db\models\loading.py", line 99, in load_app
models = import_module('%s.models' % app_name)
File "C:\Users\code\Envs\funretire\lib\site-packages\django\utils\importlib.py", line 40, in import_module
import(name)
File "C:\Users\code\Envs\funretire\lib\site-packages\cities\models.py", line 2, in
from django.contrib.gis.db import models
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\db\models__init.py", line 8, in
from django.contrib.gis.db.models.manager import GeoManager
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\db\models\manager.py", line 2, in
from django.contrib.gis.db.models.query import GeoQuerySet
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\db\models\query.py", line 6, in
from django.contrib.gis.db.models.fields import get_srid_info, PointField, LineStringField
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\db\models\fields.py", line 4, in
from django.contrib.gis import forms
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\forms__init.py", line 2, in
from .fields import (GeometryField, GeometryCollectionField, PointField,
File "C:\Users\code\Envs\funretire\lib\site-packages\django\contrib\gis\forms\fields.py", line 11, in
from django.contrib.gis.geos import GEOSException, GEOSGeometry, fromstr
ImportError: cannot import name GEOSException

When I remove the Django-cities app from INSTALLED_APPS, manage.py syncdb seems to work just fine:

(funretire) C:\Users\code\workspace\funretire\src>python manage.py syncdb
Creating tables ...
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)

Hi,

I can't import=postal_code. The file allCountries.zip is downloaded but the script doesn't add a single line and nothing is displayed even with full verbose.

Tried with --force, no more luck.

Please note that my system killed the import script while importing alt_name when I first tried import=all.

I'm using PostGIS.

Any idea ?

EDIT: The module is not up to date on pip. I installed it from github. Still no postal_code after a clean install of 0.4 :(

Hi

I have the following issue when importing GB postal codes

FYI, line is 472 because i use the fork posted by kometes which handle mysql distance workaround ; i don't know if there is any link between this issue and fork version

Thanks

Traceback (most recent call last):
File "./manage.py", line 14, in
execute_manager(settings)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/core/management/init.py", line 438, in execute_manager
utility.execute()
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/core/management/init.py", line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/core/management/base.py", line 191, in run_from_argv
self.execute(_args, *_options.dict)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django/core/management/base.py", line 220, in execute
output = self.handle(_args, *_options)
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django_cities-0.18-py2.7.egg/cities/management/commands/cities.py", line 68, in handle
func()
File "/Users/odin/Developer/Projects/Django/MA/venv/lib/python2.7/site-packages/django_cities-0.18-py2.7.egg/cities/management/commands/cities.py", line 472, in import_postal_code
pc.location = Point(float(items[10]), float(items[9]))
ValueError: could not convert string to float:

I tried to run the command on a server running with 500mb of ram, and it just fails saying "killed".

Don't know how to check the looger, but when I tried to import only the country data it worked like it should. Probably fails due to lack of memory.

Just before the author name.

Hi, Thanks again for the great package. However, I havent been able to import PostalCode data from the commands:

./manage.py cities --import=postal_code

Also, running ./manage.py cities --import=all imports data for every field except PostalCode. What is the problem with this? How can I get the data for postal codes into my database?

What could be going wrong here?

column cities_city.location does not exist
LINE 1: ..., "cities_city"."slug", "cities_city"."name_std", "cities_ci...
^

I'm trying to use django-cities with the new version of Django (1.7) and when I try to run the python manage.py syncdb command to create django-cities tables I got the following error (full traceback):

Operations to perform:
  Synchronize unmigrated apps: cities
  Apply all migrations: admin, contenttypes, auth, sessions
Synchronizing apps without migrations:
  Creating tables...
    Creating table cities_country_neighbours
    Creating table cities_country_alt_names
    Creating table cities_country
    Creating table cities_region_alt_names
    Creating table cities_region
    Creating table cities_subregion_alt_names
    Creating table cities_subregion
    Creating table cities_city_alt_names
Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
    utility.execute()
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/core/management/__init__.py", line 377, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/core/management/base.py", line 338, in execute
    output = self.handle(*args, **options)
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/core/management/base.py", line 533, in handle
    return self.handle_noargs(**options)
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/core/management/commands/syncdb.py", line 27, in handle_noargs
    call_command("migrate", **options)
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/core/management/__init__.py", line 115, in call_command
    return klass.execute(*args, **defaults)
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/core/management/base.py", line 338, in execute
    output = self.handle(*args, **options)
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 128, in handle
    created_models = self.sync_apps(connection, executor.loader.unmigrated_apps)
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 228, in sync_apps
    sql, references = connection.creation.sql_create_model(model, no_style(), seen_models)
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/db/backends/creation.py", line 82, in sql_create_model
    col_type = f.db_type(connection=self.connection)
  File "/Users/cristianrojas/.virtualenvs/bbintlcargo/lib/python2.7/site-packages/django/contrib/gis/db/models/fields.py", line 220, in db_type
    return connection.ops.geo_db_type(self)
AttributeError: 'DatabaseOperations' object has no attribute 'geo_db_type'

Wouldn't it be useful to be able to specify the countries that you want to import the cities for ? Maybe it's not necessary to import all cities of all countries in all projects.

Getting the output below when running manage.py cities.
Could it be a problem with python versions?

INFO Downloading: allCountries.zip
INFO Importing country data
INFO {'code': '2986043', 'postalCodeRegex': '0', 'name': '42.64991', 'codeNum': 'Pic de Font Blanca', 'area': 'T', 'geonameid': '2860', 'currencyCode': '00', 'tld': '', 'languages': '', 'phone': '', 'neighbours': 'Europe/Andorra', 'code3': 'Pic de Font Blanca', 'fips': 'Pic de Font Blanca,Pic du Port', 'capital': '1.53335', 'postalCodeFormat': '', 'currencyName': '', 'continent': 'AD', 'equivalentFips': '2014-11-05\n', 'population': 'PK'}
Traceback (most recent call last):
File "manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/home/vagrant/env/local/lib/python2.7/site-packages/django/core/management/init.py", line 399, in execute_from_command_line
utility.execute()
File "/home/vagrant/env/local/lib/python2.7/site-packages/django/core/management/init.py", line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/vagrant/env/local/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv
self.execute(_args, *_options.dict)
File "/home/vagrant/env/local/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute
output = self.handle(_args, *_options)
File "/home/vagrant/env/local/lib/python2.7/site-packages/cities/management/commands/cities.py", line 68, in handle
func()
File "/home/vagrant/env/local/lib/python2.7/site-packages/cities/management/commands/cities.py", line 179, in import_country
country.area = int(float(item['area'])) if item['area'] else None
ValueError: could not convert string to float: T

I ask this because I get a memory error during import. Do 'import all' import every city from every country? I was hoping a workaround would be to only import united states information.

The other work arounds to the memory issue seem very complicated.

Please advise.

Maybe I'm wrong, but I can't find any trace of south migration in django-cities so far. It would be inconvenient for those who want to upgrade from earlier version. Also, I suggest that timezone field is added to each city model.