Replies: 4 comments 5 replies
-
|
This is a great high-level write up. I have a couple of suggestions in terms of implementation:
|
Beta Was this translation helpful? Give feedback.
-
|
This matches my use case quite well. I own a "main" device, which represents "me", typically this is the smartphone I use every day. Then I have a bunch of GPS trackers for all sorts of things, mainly for my curiosity about how all these different GPS trackers work and what I can do with them (for example via LoRaWAN). For them, I don't need full-blown visit detection or trip calculations. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds great! Also it would be great to mark timeslots in which a device does not represent you.
We could also take device types into account: Depending on the device type we could also add more filtering or auto hide modes:
|
Beta Was this translation helpful? Give feedback.
-
|
I will try to pickup your ideas here but as a first impression I think we are on the right track here. Lets assume we somehow get the data from the devices or whatever you want to track. There are a lot of uncertainties here but lets do not look at that. So right now, we have a user with one or more api tokens. This is our baseline and will also be the future way of having your timeline. This is the one you track with your main device for example your phone. Then we add a new feature. Devices associated with this main account. They get their own api key for ingestion and to associate the data to that device. They can have additional attributes like color, name etc. Now everything tracks its data, your main device tracks directly into your user data with the complete visit and trips detection. All others report into their device accounts without any detection. We just store the raw path.
This could be solved when we add the ability to copy data from the tracked smartwatch back to your main account, essentially overriding the data from your phone with your data from the jogging. This would be a manual process for the time but it should solve your usecase by reconstructing your personal journey.
Lets just hope this does not happen again. :D but if so, your best bet is that I at one time decide it would be bice to have the ability to delete points or drop them from the database.
Since we would not merge timelines, there is no real usecase here to assign transportation modes to devices. There was already an idea in having a dedicated app with some algorithms based on the sensors of the phone to detect the certainty of transportation mode. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
After reviewing several incoming feature requests, I realized something interesting: while reitti currently focuses on tracking your personal location, many users might benefit from the ability to track multiple devices they own, such as vehicles, pets, or personal gadgets.
Here's my concept for how this could work:
How It Would Work
Multi-Device Association
Each user account could have multiple devices linked to it, making it easy to manage everything in one place.
Dedicated API Keys
Each device would automatically receive its own API key. This simplifies integration with lighter-weight solutions like GPSLogger, Overland, or the default OwnTracks app. For more advanced setups like MQTT or OwnTracks-Recorder, additional configuration would still be required, but the API key approach provides a solid foundation for all integration methods.
Flexible Map Display
On the map view, you'd have full control over what to show:
Smart Data Storage
Additional device locations would be stored efficiently in the database without the overhead of full user processing:
What This Could Enable
This approach could support real-world scenarios like:
Your Input Matters
Does this concept address any use cases you have in mind? If you already track multiple devices with reitti, I'd love to hear about your specific situation and what would make this feature truly useful for you.
What do you think about this direction? Are there aspects you'd like to see adjusted or features that would make this more valuable for your needs?
Beta Was this translation helpful? Give feedback.
All reactions