GeoDjango's "Point" class expects the constructor arguments to be (longitude, latitude) rather than the more traditional (latitude, longitude). Inverting them results in some unexpected behaviour & validation errors.
Fix is likely just to switch the arguments in fixture_algorithms/default_fixture.py:
class GeoDjangoDataFixture(object):
def create_point(self, x=None, y=None):
# latitude: [-90,90], longitude: [-180,180]
latitude = x or random.randint(-90, 90)
longitude = y or random.randint(-180, 180)
return Point(longitude, latitude)
GeoDjango's "Point" class expects the constructor arguments to be (longitude, latitude) rather than the more traditional (latitude, longitude). Inverting them results in some unexpected behaviour & validation errors.
Fix is likely just to switch the arguments in fixture_algorithms/default_fixture.py: