TO-DO Checklist

• Python server connect to SteemData and location retrieval (done)
• Python server connect to Geopy and get free/unlimited realtime user coordinates(done)
• Javascript-Python API between webclient and python backend (on progress, currently being tested locally)
• Map population (to be done, only tested using dummies)

** Please find below the current main changes/updates since last report. **

---

Updates

#1. Using google maps service entirely not feasible.

It would had been very convenient just utilizing google map service entirely for both geolocation and map generation. My first concern was overloading the geolocation API with multiple and redundant calls (different users calling for same users coordinates).

Good enough, Google Maps has the possibility to cache the searches so that you dont need to duplicate calls. However, regardless of the search result saving option, the API calls have a daily limit. On top of that, for more than 100.000 geolocation calls a premium google account would be needed.

---

#2. Geopy as a solution

Geopy is an open-source Python3 library that enables real-time unlimited geolocation of addresses. Therefore, by creating a Geopy data routing bypass in between the Webclient Google Map and the Python User location server ( See chart below) we can get free geolocation service for the Steemit community.

---

#3 Using Presentation Posts for improving the location Database

Since only around 50% of users have locations enabled, I will improve the database by searching for location-related keywords in every user presentation post (e.g. I live in **** // I work in ***). I believe this will both greatly expand the datababase while being relatively accurate.