Add GeoJSON Export

[radh21301]

Reitti currently has GeoJSON imports, but no exports. It would be great if that can be supported in addition to GPX. Looks like GeoJSON can store extra info for each point, like tracker_id, topic, battery etc.

For example, in Dawarich GeoJSON exports I can see:

tracker_id: "google-maps-timeline-export", topic: "Google Maps Timeline Export"
"tracker_id":"AR","topic":"owntracks/ar/iphone13pro"

So, if Reitti can also preserve all the original information in the exports, that would be great.

[dgraf-gh]

Hello @radh21301,

this will probably not happen. Reitti does not store any information which we do not need. At the moment I do not see any use case for this. It would also complicate the storage and implementation. Since GeoJson is rather flexible in the metadata section we would need a column in the db to store this as text, but then the question arises what to do when gpx is imported.

If you need to preserve all the data, there are probably better solutions for this.

[radh21301]

Hey. Thanks, that makes sense. The main use case I had in mind was cleanup. Sometimes I import bad data by mistake, and it would help to know which points came from which source so I can remove just those. For example, if some bad points came from a file like export_xxx_Jan2021_Dec2025.gpx, I could filter and delete them easily.

It could also be useful for people using multiple devices, since a bit of metadata helps keep sources separate (or at least have the data of Reitti ever decides to use that in the future). And sometimes it’s just helpful to know which file something came from after the fact.

If this is out of scope for Reitti, no problem at all. Just wanted to share the thought.

[dgraf-gh]

I understand your concerns and can relate to them.

Right now, Reitti does not provide any cleanup features, there is no way to delete a point through the app. Technically, you can remove points directly from the database and trigger a recalculation, but there is no official, supported method for removing points.

This stems from my philosophy of building an app that requires as little manual intervention as possible. From my perspective, if I have to babysit it, I wouldn't use it.

Reitti also does not support multiple devices per user. This is intentional: Reitti is designed to track one person's movements, and since you can only be in one place at a time, there isn't a need to support multiple devices per user. You can, however, add a separate user for each device and stitch them together via Settings > Share Access.

There’s no right or wrong approach here, it’s simply a design decision about the direction Reitti should take. For me, it’s meant to be a way to bring back memories, not a 100% accurate tracker. Other apps handle strict accuracy better.

I hope this clarifies things a bit.

[radh21301]

Totally understand. And honestly, I appreciate that you have a strong vision for the app and stick to it without letting scope creep in. It gives me confidence that Reitti will stay focused and do its job well.

In reality, I’ve never actually needed to bulk delete data. It’s more just my instinct to preserve everything “just in case.” But you’re right, that’s not always the right approach, and Reitti’s simplicity is part of what makes it great.