[FIX] crm_partner_assign: more precise geolocation
Google api geolocation service returns a precise latitude and longitude, greater or equal than 5 digits The precision is important as storing 2 digits instead of 5 can lead to an inaccuracy of allmost half a mile.
This commit is contained in:
parent
f833d2eacd
commit
36af222569
|
@ -85,8 +85,8 @@ class res_partner_activation(osv.osv):
|
|||
class res_partner(osv.osv):
|
||||
_inherit = "res.partner"
|
||||
_columns = {
|
||||
'partner_latitude': fields.float('Geo Latitude'),
|
||||
'partner_longitude': fields.float('Geo Longitude'),
|
||||
'partner_latitude': fields.float('Geo Latitude', digits=(16, 5)),
|
||||
'partner_longitude': fields.float('Geo Longitude', digits=(16, 5)),
|
||||
'date_localization': fields.date('Geo Localization Date'),
|
||||
'partner_weight': fields.integer('Weight',
|
||||
help="Gives the probability to assign a lead to this partner. (0 means no assignation.)"),
|
||||
|
|
Loading…
Reference in New Issue