django-mapbox-location-field
Simple in use location model and form field with MapInput widget for picking some location. Uses mapbox gl js, flexible map provider API. Fully compatible with bootstrap framework. Can be used with spatial or plain databases.
MIT License
Bot releases are hidden (Show)
Published by simon-the-shark 7 months ago
There shouldn't be any breaking changes. Routine update, changed few details, fixed testing on github actions, upgraded bunch of versions etc.
Published by simon-the-shark over 2 years ago
BREAKING CHANGES. Proper support for Django 3.x and 4.x. Thanks for #36 #35. Tests migrated to Github Actions.
Read more: https://github.com/simon-the-shark/django-mapbox-location-field#compatibility
https://pypi.org/project/django-mapbox-location-field/2.0.0/
Published by simon-the-shark over 3 years ago
Introduced language and message_404 parameters in map_attrs options. Read more in documentation. Feature upon request #27
Published by simon-the-shark over 3 years ago
Fixed #23
Published by simon-the-shark almost 4 years ago
Finally a proper solution for #20 Proposed by @mjnaylor8 (#22)
Published by simon-the-shark almost 4 years ago
Resolved #21. Solution for the issue is presented in the troubleshooting section
Published by simon-the-shark about 4 years ago
Fixed few bugs in admin panel integration (#19)
Published by simon-the-shark over 4 years ago
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 )
Published by simon-the-shark over 4 years ago
Feature requested in the #13 issue. Added in cooperation with @edgaru (PR #14 )
Published by simon-the-shark over 4 years ago
Just fixed the #10 issue, which is a major bug
Published by simon-the-shark almost 5 years ago
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.
Published by simon-the-shark almost 5 years ago
Published by simon-the-shark almost 5 years ago
Published by simon-the-shark almost 5 years ago
Published by simon-the-shark almost 5 years ago
Added SpatialLocationField and now can work with spatial databases.
Published by simon-the-shark almost 5 years ago
Published by simon-the-shark over 5 years ago
Added reverse geocoding, AddressAutoHiddenInput, AddressAutoHiddenField
