Skip to content

changed coordinates order convention
Compare
Choose a tag to compare
@simon-the-shark simon-the-shark released this 08 Nov 21:54
· 95 commits to master since this release
v1.4.0
caf9efb
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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.

Assets 2