Modify ↓
Opened 15 years ago
Closed 15 years ago
#5962 closed defect (fixed)
GeoTicketPlugin should store lat/lon if available
Reported by: | Jeff Hammel | Owned by: | Jeff Hammel |
---|---|---|---|
Priority: | high | Component: | GeoTicketPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
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 15 years ago by
Status: | new → assigned |
---|
comment:2 Changed 15 years ago by
comment:3 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
should mostly be fixed. There may be AJAX race conditions, but should be dealt with upon diagnosis
Note: See
TracTickets for help on using
tickets.
(In [6688]) adding latitude and longitude hidden fields and storing them directly in the DB instead of another geo lookup. refs #5962