[GIS] DatabaseError: Coordinate values are out of range [-180 -90, 180 90] for GEOGRAPHY type

geodjangopostgisspatial-database

I am using Django 1.3, PostGIS 2.0 , Postgresql 9.0 and GeoDjango.

I had a database with a table for places. This table had latitude and longitude for places in the US. I enabled this database with PostGIS. I added PointField to my model. Then, updated this table with

SELECT AddGeometryColumn('table', 'poly', 4326, 'POINT', 2)

CREATE INDEX "table_poly_id" ON "table" USING GIST ( "poly" )

UPDATE table
SET poly = ST_PointFromText('POINT(' || longitude ||' '|| latitude ||')', 4326)

Now, I want to make query to find places within 5 miles of given latitude and longitude of a user's location.
So, I did this

ref_pnt = fromstr("POINT(%s %s)" % ("-87.627778", "41.881944"))
records = Table.objects.filter(poly__distance_lte = (ref_pnt,D(mi=5)))

But, I am getting an error

DatabaseError: Coordinate values are out of range [-180 -90, 180 90] for GEOGRAPHY type

I also get an error when I do this

SELECT ST_PointFromText(poly) FROM table 

ERROR:  parse error - invalid geometry
HINT:  "0101000020E61000007E" <-- parse error at position 20 within geometry
CONTEXT:  SQL function "st_pointfromtext" statement 1

What could be the problem?

Best Answer

I had a similar problem, in my case, I was storing coordinates inverted.

In WGS84 and postgis, the order in point is longitude, latitude.

In Django, the point object is like: Point(x=longitude, y=latitude)

Related Solutions

[GIS] PostGIS database to be queried by GeoDjango

After some experiments, I think I've found in django-mutant the solution that fit my needs. With it, you can create a dynamic model in the following way:

from mutant.contrib.geo.models import GeoModel, GeometryFieldDefinition
from mutant.contrib.numeric.models import SmallIntegerFieldDefinition
from mutant.models import BaseDefinition, ModelDefinition

model_def, created = ModelDefinition.objects.get_or_create(
                         app_label='myApp',
                         object_name='myShape',
                         defaults=dict(
                         bases=(BaseDefinition(base=GeoModel),),
                         fields=(GeometryFieldDefinition(name='the_geom', srid=31258),
                         SmallIntegerFieldDefinition(name='cat'),)
                    )
                )

In this way, calling model_def.model_class() would return the same model as if you had declared the following in your models.py:

class myShape(GeoModel):
    cat = models.SmallIntegerField()
    the_geom = models.GeometryField(srid=31258)
    class Meta:
        db_table = u'myApp'

As you run ModelDefinition.objects.get_or_create() method, a table named mutant_myApp_myShape is created into PostgreSQL with a relative row in geometry_colums table. In addition, this model has a proper id entry inside django-mutant table named mutant_modeldefinition.

Further tests need to be made, but this approach seems a good starting point to me.

PostGIS – How to Fix Coordinate Values Out of Range Error for GEOGRAPHY Type

From @Jakub Kania tip :

ALTER TABLE routes ADD temp geometry;
select UpdateGeometrySRID('public', 'routes', 'temp', 4326) ;
update routes set temp = ST_Transform(the_geom,4326);
select UpdateGeometrySRID('public', 'routes', 'the_geom', 4326) ;
update routes set the_geom = temp;
alter table routes drop column temp;

Related Question