organicmaps/organicmaps

Fork 18

Option to allow user to set accuracy for track recording (recording interval/frequency) #9342

New issue

Open

opened 2024-09-21 15:02:04 +00:00 by Aurareus · 8 comments

Aurareus commented

2024-09-21 15:02:04 +00:00

(Migrated from github.com)

Currently the track recording feature in Organic Maps is less accurate than the app I am currently using to record tracks (Trekarta) because the frequency at which points are recorded is lower.

To give an example, I recorded a track using both Organic Maps and Trekarta simultaneously and in the following screenshot the section of track in grey was what Organic Maps recorded and the section of track in blue is what Trekarta recorded:

One solution would simply be to increase the frequency of recorded points during track recording, but I think it would be preferable to add an option in the settings that allows the user to set their own point recording frequency.
That way users who require more precisely recorded tracks can increase the value to meet their needs without potentially impacting battery usage for users who don't need more precision, and users who don't need very precise tracks at all can reduce the value to potentially reduce battery usage.
Though I would imagine that most users would leave the setting at its default.

Currently the track recording feature in Organic Maps is less accurate than the app I am currently using to record tracks (Trekarta) because the frequency at which points are recorded is lower. To give an example, I recorded a track using both Organic Maps and Trekarta simultaneously and in the following screenshot the section of track in grey was what Organic Maps recorded and the section of track in blue is what Trekarta recorded: ![Screenshot_20240921-154236](https://github.com/user-attachments/assets/b2a04a31-4ed1-404d-a914-c31bdc40ba2f) One solution would simply be to increase the frequency of recorded points during track recording, but I think it would be preferable to add an option in the settings that allows the user to set their own point recording frequency. That way users who require more precisely recorded tracks can increase the value to meet their needs without potentially impacting battery usage for users who don't need more precision, and users who don't need very precise tracks at all can reduce the value to potentially reduce battery usage. Though I would imagine that most users would leave the setting at its default.

RobfromVI commented

2024-09-22 18:24:34 +00:00

(Migrated from github.com)

I emailed the following about this subject:

Testing the latest track recorder below

It does not appear to record the point at which I start recording. The first recorded point is after I have walked one interval. After that it works fine. I think the exact starting point should be recorded.
The points are a bit too far apart for hiking.apparently about 16m apart. Pretty sure the earlier version was closer. Some kind of time vs distance formula might be good. IE If I move more than 3m in say 3 seconds set a point but if I move 50 m in 5 seconds still only set one point. Some relationship where if I am going fast, I probably need lower point density. Customizable point spacing would of course be best ie set one point after configurable time or distance whichever comes first.

Another great option and possible solution regarding above might be to record an additional point if I tap on the cursor. That way for example if I am turning a sharp corner on a hike I can mark the apex of the trail.

I emailed the following about this subject: Testing the latest track recorder below 1) It does not appear to record the point at which I start recording. The first recorded point is after I have walked one interval. After that it works fine. I think the exact starting point should be recorded. 2) The points are a bit too far apart for hiking.apparently about 16m apart. Pretty sure the earlier version was closer. Some kind of time vs distance formula might be good. IE If I move more than 3m in say 3 seconds set a point but if I move 50 m in 5 seconds still only set one point. Some relationship where if I am going fast, I probably need lower point density. Customizable point spacing would of course be best ie set one point after configurable time or distance whichever comes first. **Another great option and possible solution regarding above might be to record an additional point if I tap on the cursor. That way for example if I am turning a sharp corner on a hike I can mark the apex of the trail.**

Aurareus commented

2024-09-22 18:34:29 +00:00

(Migrated from github.com)

I am also seeing the behavior mentioned in your first point, perhaps worth checking to see if someone has opened an issue about it already and opening a separate issue if nobody has?

To your second point, my assumption is that the the interval between recorded points is purely a timer, irrespective of distance? I should probably look at the code to check and update this issue accordingly.

I am also seeing the behavior mentioned in your first point, perhaps worth checking to see if someone has opened an issue about it already and opening a separate issue if nobody has? To your second point, my assumption is that the the interval between recorded points is purely a timer, irrespective of distance? I should probably look at the code to check and update this issue accordingly.

RobfromVI commented

2024-09-22 19:24:02 +00:00

(Migrated from github.com)

I tried standing still for a while and pacing about in a narrow radius, and no point got set. My recorded points seem to be quite consistently 16m apart.

Thus my idea of adding manually set points at important junctions etc.

I tried standing still for a while and pacing about in a narrow radius, and no point got set. My recorded points seem to be quite consistently 16m apart. Thus my idea of adding manually set points at important junctions etc.

RobfromVI commented

2024-10-02 14:54:17 +00:00

(Migrated from github.com)

These issues still both exists on latest beta Oct 01.

If nothing else, please reduce point spacing to 10m

Also, please make sure a point is recorded at the location where I start recording, and not have the first point set 16m afterwards. Also please make sure another point is set at the exact location where I stop recording.

These issues still both exists on latest beta Oct 01. If nothing else, please reduce point spacing to 10m Also, please make sure a point is recorded at the location where I start recording, and not have the first point set 16m afterwards. Also please make sure another point is set at the exact location where I stop recording.

Aurareus commented

2024-10-03 00:36:08 +00:00

(Migrated from github.com)

I personally think time-interval based recording is preferable to distance based as time based would result in tracking precision being dependant on the speed that you're moving.
With time-interval based recording the slower you're moving the more precise the tracking is, and typically that's what you'd want.

I personally think time-interval based recording is preferable to distance based as time based would result in tracking precision being dependant on the speed that you're moving. With time-interval based recording the slower you're moving the more precise the tracking is, and typically that's what you'd want.

RobfromVI commented

2024-10-03 02:57:19 +00:00

(Migrated from github.com)

It gets tricky, because you do not want repeated points set while you are standing still, looking at the view, or having lunch.

So we need a minimum amount of movement first, and then a minimum amount of time, like maybe minimum 2m or 3m of movement, and at about 8 seconds of time to set another point. I would like it to set points at about 10m intervals on a fast walk.

It gets tricky, because you do not want repeated points set while you are standing still, looking at the view, or having lunch. So we need a minimum amount of movement first, and then a minimum amount of time, like maybe minimum 2m or 3m of movement, and at about 8 seconds of time to set another point. I would like it to set points at about 10m intervals on a fast walk.

RobfromVI commented

2024-10-04 16:30:56 +00:00

(Migrated from github.com)

No hints of progress on this in latest beta Oct 4th

Aurareus commented

2024-10-25 20:15:19 +00:00

(Migrated from github.com)

mentioned in issue #9554