Feature proposal #8795


Redesign location feature to be single input

Added by krileon about 2 years ago. Updated 7 months ago.

Target version:
Start date:
03 December 2021
Due date:
% Done:


Estimated time:


This should just strictly ask for an address and link that to a map. If map API keys (try to support a few.. e.g. google maps, open maps, etc..) are supplied the map pin icon should expand down a map to select their location and if location api is available the detection location button should use that otherwise use ip address location guessing. If a location is selected on the map AND the location has a name in addition to an address then that also needs to be passed along as a hidden input value. Use localStorage to save their previously used locations so the input can also support autocomplete.

Actions #1

Updated by krileon about 2 years ago

Location should be stored in a separate database. Database structure as follows.

id | user_id | activity_id | name | address | lat | long

Mapping is restricted to activity so there's no reason to worry about dealing with supporting other objects. Having the activity id stored with it is useful for building activity from locations. Having the user id stored with it is useful for providing autocomplete in the dropdown per-user. Name and Address can both be used for autocomplete lookup. lat/long will be what's actually used for mapping.

Actions #2

Updated by krileon 11 months ago

  • % Done changed from 0 to 60
Actions #3

Updated by krileon 11 months ago

This will not be stored to a separate table. It will continue to be stored in activity parameters, but those can be extracted during activity save if anyone needs to utilize them externally.

Actions #4

Updated by krileon 11 months ago

  • Status changed from Assigned to Resolved
  • % Done changed from 60 to 100
Actions #5

Updated by krileon 7 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF