Changelogs » Django-mapbox-location-field

PyUp Safety actively tracks 263,329 Python packages for vulnerabilities and notifies you when to upgrade.

Django-mapbox-location-field

1.6.3

Fixed few bugs in admin panel integration (19)

1.6.1

Issue 15. Now you can e.g. serialize this field with Django Rest Framework's CharField. Just remember about proper field validation or deal with a build-in db protection mechanism. (Read more 15 )

1.6.0

Feature requested in the 13 issue. Added in cooperation with edgaru (PR 14 )
  
  v.1.5.0
  Just fixed the 10 issue, which is a major bug

1.4.0

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.

1.3.0


        

1.2.0


        

1.1.0


        

1.0.0

Added SpatialLocationField and now can work with spatial databases.

0.2.7


        

0.2.5

Added reverse geocoding, AddressAutoHiddenInput, AddressAutoHiddenField

0.2.3


        

0.2.2


        

0.2.1


        

0.2.0

Added initial marker and browser support checking. Fixed bunch of small bugs.
  Added unit tests on Travis CI

0.1.7


        

0.1.5

It actually works. Or at least I think so.