Timeline feature

[Outlet2048]

Would it be possible to add something similar to a timeline similar to what Googles location history offers?

Id be totally fine with manually confirming where I was and don't expect the data to be accurate enough for all of this to work without any user input. For me this would be an amazing feature to have but i have no idea how hard an implementation would be.

Cheers!

[linusg]

Googles location history

I'm not familiar with that, my Google account has location history saving turned off - can you provide a screenshot or additional explanation?

[Outlet2048]

I have disabled that feature as well but I can describe what I remember At the bottom of the page there's a bar that lists all the places you've been that day. I assume staying somewhere for an extended period of time causes Google to add an entry Ive noticed that owntracks also sets a lot of points when you stay somewhere for a longer period of time so this might be the best way to identify whether or not the user has stopped somewhere for an extended period of time.

The screenshot i've attached is somewhat outdated but its enough to get the idea of it. Basically a list of all stops organized in a timeline. Admittedly i have no idea how difficult it would be to get the data from openstreetmap to see what place the user has stopped at.

[linusg]

Oh, that would be pretty awesome! I'll think about how we could approach this - basically there are three options:

• Do it all client side (detection of individual locations from raw data points, look up their name)
• Add this functionality to the recorder itself
• Add a secondary service that reads data from the recorder and adds metadata like this, the frontend would then need to communicate with both, or it proxies the recorder and serves as an enhanced replacement

Great idea though, would love to have this :)

[Outlet2048]

I'm really happy to hear that you like the idea!

Sadly i have no programming experience and have no idea what approach would be best. But let me know if you have any questions regarding the user experience :P

[growse]

Oh, that would be pretty awesome! I'll think about how we could approach this - basically there are three options:

* Do it all client side (detection of individual locations from raw data points, look up their name)

* Add this functionality to the recorder itself

* Add a secondary service that reads data from the recorder and adds metadata like this, the frontend would then need to communicate with both, or it proxies the recorder and serves as an enhanced replacement

Great idea though, would love to have this :)

One challenge with (2) and (3) would be in persisting metadata. It's been a while since I looked at it, but I believe that some Geocoding services (e.g. Google) specifically prohibit storage of the reverse geocode result - it's for point in time display only.

Seems like an ideal thing to do client-side, as it's fundamentally a display/UI problem, rather than something tha should leak upstairs to data storage?

[jpmens]

Google specifically prohibit storage of the reverse geocode result

That's one of the reasons we're fond of OpenCage who specifically permit it: Cache results as long as you like is prominently displayed on their landing page. :-)

[Outlet2048]

Hello again!

Another idea that came to mind is the ability to "create" places. Example: I visit a friend. This wont show up with any name since its just an address and not a shop etc. So it would be great if the user could geofence an area and give it a name. Entering it will display the given name on the timeline

Cheers!

[Outlet2048]

I heard you can add a "bounty" to issues via the issuehunt website. Assuming that you'd have to enable this for your repo first, would you be interested in doing so?