Right now footprint data has only lat/lon whereas it would be useful for DataView if it had enriched that with city/state/country as users won't be able to decipher where a lat/lon represents by looking at it in table view. This could be done through geocoding or some other method and could be done on initial save_timeline API or done through scheduled enrichment e.g. using a Cloudwatch event that checked for any new entries in DB since last check and enriched them based on their lat/lon using geocoding.

Right now get_footprints returns all footprints in the DB. Add the ability to query the DB for a specific date range of footprints, use SQL query either:

SELECT * FROM footprints WHERE date >= '2020-04-01' AND date <= '2020-04-03';

or

SELECT * FROM footprints WHERE date BETWEEN >= '2020-04-01' AND '2020-04-03';

both should work, pick one.

Should take in a username and password send from client through API, and add new user + account/membershp to the DB, generate a json web token and send it back to the client. If email already exists in DB then disallow the new register -> signing up multiple account memberships should be through a different route.

Takes in email and password, hashes the password, retrieves the password and other details from the DB, compares the two password hashes and if they match, sends back a json web token to the client, and if they don't (if either email not exist in DB or password not match, sends back error to client).