Opened 5 years ago

Closed 5 years ago

#5962 closed defect (fixed)

GeoTicketPlugin should store lat/lon if available

Reported by: k0s Owned by: k0s
Priority: high Component: GeoTicketPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.11


Currently, the lat/lon is derivative from the ticket location string, mainly because it was easy to do the way it is done. In several cases (clicking on a map, clicking on one of multiple locations, etc), the exact lat/lon is available and technically the location string is the derived quantity.

If the lat/lon is the canonical location, then the DB should be updated with this location.

Attachments (0)

Change History (3)

comment:1 Changed 5 years ago by k0s

  • Status changed from new to assigned

comment:2 Changed 5 years ago by k0s

(In [6688]) adding latitude and longitude hidden fields and storing them directly in the DB instead of another geo lookup. refs #5962

comment:3 Changed 5 years ago by k0s

  • Resolution set to fixed
  • Status changed from assigned to closed

should mostly be fixed. There may be AJAX race conditions, but should be dealt with upon diagnosis

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.