changed coordinates order convention

Since this version the order of coordinates convention has been changed. Now the order is longitude, latitude. This change has been caused by support for spatial databases. But more user friendly is order latitude, longitude(google maps uses it). That's why coordinates are falsely swapped in frontend and then after POST request in form field are swapped back into longitude, latitude order and saved to database.
My conclusion is that the location is falsely swapped in frontend and if you create location without our custom form field or just operate on raw model in backend, you will have to use the longitude, latitude order.
Versions before always uses latitude, longitude order.

fixed geodjango support

v1.3.0

included spatial directory

fixed overriding center point

v1.2.0

fixed overriding center point

fixed plain usage, separed spatial definitions

v1.1.0

updated setup.py

Geodjango support

Added SpatialLocationField and now can work with spatial databases.

added support for spaceless format of coordinates

v0.2.7

updated setup.py

Reverse Geocoding

Added reverse geocoding, AddressAutoHiddenInput, AddressAutoHiddenField

v0.2.3

fixed get_prep_value

v0.2.2

fixed rendering outside the map

v0.2.1

fixed initial value`s format