Thanks a lot 🙏

Thank you. Would be nice to hear if it works for you or something is missing.

Hi @themadcodger@kbin.earth, thanks for opening the discussion on https://github.com/dedicatedcode/reitti/discussions/176.

As I mentioned there: It depends on your usage. Reitti on its own could probably run with 512MB of RAM. This would probably also work while ingesting data from one of the integrations. I doubt that imports of data, spanning more than one day, will work. We already stream the uploaded data but in the end, it has to go temporally into RAM. Either in Reitti itself or in Redis or in the DB.

For anyone interested. These are the numbers on my host for the stack idling and waiting for data.

ONTAINER ID   NAME                CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS
222a0ed74fe7   reitti-reitti-1     0.10%     392MiB / 30.77GiB     1.24%     221MB / 103MB     2.11MB / 35.4MB   87
76c9317352bc   reitti-postgis-1    0.00%     83.38MiB / 30.77GiB   0.26%     67.7MB / 144MB    66.4MB / 145MB    16
06747b08882d   reitti-rabbitmq-1   0.46%     154.8MiB / 30.77GiB   0.49%     84.7MB / 91.3MB   46MB / 86.4MB     57
5012afdf4688   reitti-photon-1     0.42%     492.6MiB / 30.77GiB   1.56%     124kB / 5.51kB    616MB / 256MB     121
ddbc854a3940   reitti-redis-1      0.50%     4.875MiB / 30.77GiB   0.02%     52.2MB / 232MB    2.34MB / 164kB    6

Thank you very much. Let me know if it fits your need or something is missing

Thank you 🙏

There is an integration for that. You provide the URL, the user and deviceId and Reitti will fetch all new data. There is also a button to import all historical data from the recorder

Hello @chellomere@lemmy.world , totally understandable point. I stated on another thread that I probably won’t add an export function since we discard some points of the raw data before Reitti processes it. So even if I add an export function, it will be less than the original data.

Some solutions to your problem could be:

• post your points into dawarich and update Reitti by hand using the GPX import. That is actually the way I did it in the beginning of development. GPX logger also saves the GPX files on your phone if you use that.
• another user pointed me to the owntracks recorder. Your data would be stored there and Reitti can be attached to the recorder. If there is a integration in dawarich, this could solve your problem for updating two apps.

I also considered writing a proxy like you mentioned which could delegate to two endpoints but then decided at one point it would not be worth the hassle. I stopped using dawarich but I am also biased 😅

To change the password and the user of the db you have to change it in the postgis service but also need to let reitti know that it is not the standard anymore. You need to set the environment for reitti according to the Readme

If you want to start from scratch you probably need to delete the volumes from docker. See here

Normally the volumes are called reitti_postgis and so on.

Let me know if you need further assitance, i am currently on mobile but can provide more info later

Bonus points for having the options not sorted 👍

Someone would need to get that data out of the app. Either as GPX or some other format. I do not think these devices are able to send the position to some configurable endpoint. A quick search for nut tracker and home assistant does not yield any reasonable results.

I think we are out of luck at that point. But maybe someone knows about a more open tracker device which could be configured.

Reitti displays data coming either from an import. You could upload GPX, GeoJson files or export the data from google maps and import that. If you want more up to date data, you could install an app on your phone which pushes your latest locations into Reitti. GPSLogger or Owntracks are at the moment supported for that

No, not really. It just makes it easier to spin up all the needed services and it is at the moment the “documented” way.

On the release there is also jar of Reitti.

If you need any help in starting that, let me know.

You are right, I missed that they are still open for the other services. I have mine running behind traeffik and did removed all port definitions.

I will change the compose file to only expose Reitti.

Thanks for the feedback🙏

If you are running Reitti with Docker, you can set the environment variable DANGEROUS_LIFE to true. This will enable a new section in the Settings. There, you can use the button ‘Clear and Reprocess’. This will delete all visits and trips and set all raw data points to unprocessed. During the next run, everything will be recalculated. In that settings section, you could also press the ‘Start Processing’ button if you don’t want to wait. Make sure to wait until the success message appears. It can take a while until all data is deleted and switched to unprocessed.

Greetings, @Pandoras_Can_Opener@mander.xyz, that sounds like a truly wonderful idea, and as a fellow cat owner, it brings me great joy to hear about it. 😻

In fact, I have recently changed the analysis of data, which is now performed in near real-time as soon as new data becomes available. I am currently working on the functionality to display multiple users (or, in your case, Pandora) on the map, which should be beneficial to your idea.

Now, the primary question is, how can we integrate the data from the tracker into Reitti. Thats something I have no idea at the moment. Do you have any Infos about that?

Hi ada,

yes, this will impact the visit calculation. Visits are calculated in building clusters of at least 5 points in a range of 100m over a duration of at least 5 minutes. If there is only one point logged for example at work or home, Reitti is not able to detect when you left it because every point is just an instant in time and does not carry any duration information with it.

The more points we have to calculate Visits the more accurate it will be. I personally have set up GPSLogger to log every 30 seconds no matter how far I travelled but with at least 40m of accuracy.

Hi LazyToad,

it depends. Reitti on its own does not import any pictures. It only shows fetches them from Immich. For that to work it needs the geolocation where the image was taken in the exif data. You need to check if your expected image has this data in Immich. If it is available it shoud be displayed on the map if you select the day the picture was taken.

Does it show the location in Immich? You can verify this if you open the image in Immich and let it display the Info.

If it is showing, then it still could be that it is a bug in Reitti. Feel free to open an issue then :)

Thank you very much for these kind words. Means a lot to me if my little tool brings value to you :)

Cool, thanks for the feedback.

For: 1: There should be something about downloading in the Photon logs. You can check with docker compose logs photon. I do not remember how long it took to download the index for Germany, but it was noticeable. It depends a lot on how you are connected to the internet and then how long it takes to extract the index.

2: You should also see that in the log of Photon. If the default does not work reliably, you can create an account on Geoapify; it is free, and you get 3000 reverse geocode requests per day. I personally have Photon for DE and then the default service and additional Geoapify.

3: Yeah, I was also thinking about that. In the end, a per-user setting and then the overlay should be disabled, but it could take a while until I can get to it.

I am glad it worked out for you in importing the first file. I am still puzzled why it took that long.

For the new format, did you have Android or iOS? With the timeline export from Google Maps on iOS, we can not do anything at the moment because there is actually no raw data in it. Only information like you stayed in this timeframe at that point and you traveled between these points. It’s actually a little bit funny that it aggregates to the same data Reitti uses in the end.

If you are on Android, it could also be a bug when importing that file. I only had a small one from one of my accounts to test. If you mind creating a bug report, I will have a look. If you do not want to attach the export file there, feel free to send it to daniel@dedicatedcode.com. I will have a look at it then privately. No problem.

For the overlap in exports, it depends. If the points are the same, meaning they have the same timestamp, then Reitti will discard them. If not, they will be handled like every other new data and will end in recalculating visits and trips around that particular time.