Track recording does not record exact starting and ending points #9685

New issue

Open

opened 2024-11-18 19:19:17 +00:00 by RobfromVI · 5 comments

RobfromVI commented

2024-11-18 19:19:17 +00:00

(Migrated from github.com)

⚠ Have you searched for similar, already existing issues?

I think I saw someone other than me mention this once, but I cant find it now. I first raised this issue in my summary of track recording issues #9554

Describe the issue

The track recorder misses recording the exact starting and ending points of a recorded track.

Steps to reproduce

Go to a known point and start the track recorder,
Start walking, and observe the first recorded point some distance from where you started.
Walk until some point gets recorded, ie a new line segment appears. Then walk some additional distance until you can see clear separation between last recorded point and your position, and stop recording, save the track.
See error that no additional point is recorded for your final position

Expected behaviour
A clear and concise description of what you expected to happen.

Each track should set a recorded point immediately upon start recording, and another point when stop recoding is selected, even if you are only halfway to the next normal recoded point spacing.

Screenshots
If applicable, add screenshots or screen recordings to help explain your problem.

System information:

Operating system and its version: [iOS 12, Android 10, Ubuntu 22, MacOS Big Sur, etc.]
Organic Maps version: [you can find it by tapping the button with the green Organic Maps logo]
Device Model: [e.g. iPhone 6, Samsung S22]

Android system on Samsung S20FE - using latest Organic maps Nov 2024 release

Additional context
Please add any other context or comments here that may be useful.

⚠ Have you searched for similar, already existing issues? I think I saw someone other than me mention this once, but I cant find it now. I first raised this issue in my summary of track recording issues #9554 **Describe the issue** The track recorder misses recording the exact starting and ending points of a recorded track. **Steps to reproduce** 1. Go to a known point and start the track recorder, 2. Start walking, and observe the first recorded point some distance from where you started. 3. Walk until some point gets recorded, ie a new line segment appears. Then walk some additional distance until you can see clear separation between last recorded point and your position, and stop recording, save the track. 4. See error that no additional point is recorded for your final position **Expected behaviour** A clear and concise description of what you expected to happen. Each track should set a recorded point immediately upon start recording, and another point when stop recoding is selected, even if you are only halfway to the next normal recoded point spacing. **Screenshots** If applicable, add screenshots or screen recordings to help explain your problem. **System information:** - Operating system and its version: [iOS 12, Android 10, Ubuntu 22, MacOS Big Sur, etc.] - Organic Maps version: [you can find it by tapping the button with the green Organic Maps logo] - Device Model: [e.g. iPhone 6, Samsung S22] Android system on Samsung S20FE - using latest Organic maps Nov 2024 release **Additional context** Please add any other context or comments here that may be useful.

RobfromVI commented

2024-11-18 19:22:19 +00:00

(Migrated from github.com)

mentioned in issue #9554

RobfromVI commented

2024-11-18 19:23:04 +00:00

(Migrated from github.com)

changed title from Track recording does not record exac{-g-}t starting and ending points to Track recording does not record exact starting and ending points

changed title from **Track recording does not record exac{-g-}t starting and ending points** to **Track recording does not record exact starting and ending points**

kavikhalique commented

2024-12-22 21:26:46 +00:00

(Migrated from github.com)

The track recorder misses recording the exact starting and ending points of a recorded track.

Thanks for your feedback.

You are correct. Track recorder should instantly show the start point as track recorder is started but there is a little bit of gap and the reason behind this is that when we start the track recording our system starts storing all the gps co-ords, but it keeps only those co-ords for track which are precise enough which some times discards the exact start point because during walking of car drive precision decreases due to speed.

My solution -> To remove this issue there should be a loading shown for track recording until we don't get the first precise point, so that users will be aware that track recording has not yet started.

> The track recorder misses recording the exact starting and ending points of a recorded track. Thanks for your feedback. You are correct. Track recorder should instantly show the start point as track recorder is started but there is a little bit of gap and the reason behind this is that when we start the track recording our system starts storing all the gps co-ords, but it keeps only those co-ords for track which are precise enough which some times discards the exact start point because during walking of car drive precision decreases due to speed. My solution -> To remove this issue there should be a loading shown for track recording until we don't get the first precise point, so that users will be aware that track recording has not yet started.

RobfromVI commented

2024-12-22 21:47:24 +00:00

(Migrated from github.com)

Now if so, then your solution still leaves out the part about the ending point.

According to my tests so far, it will not record another point unless I move at least 13m from the previous point, and thus if my walk ends at say 10m from the previous point, no additional point will be recorded when I stop and save, no matter how long I stand at the final destination before stop and save.

Stop and save should record one more point wherever I am at that time.

So, you are saying if I stand still on my starting point for some amount of time, or possibly move about in a small circle, it should record a point at the map cursor location? I will test this and see if that works for me. Now if so, then your solution still leaves out the part about the ending point. According to my tests so far, it will not record another point unless I move at least 13m from the previous point, and thus if my walk ends at say 10m from the previous point, no additional point will be recorded when I stop and save, no matter how long I stand at the final destination before stop and save. Stop and save should record one more point wherever I am at that time.

kavikhalique commented

2024-12-22 21:59:29 +00:00

(Migrated from github.com)

So, you are saying if I stand still on my starting point for some amount of time, or possibly move about in a small circle, it should record a point at the map cursor location? I will test this and see if that works for me.

Yes, absolutely

Now if so, then your solution still leaves out the part about the ending point.

For end point i think it would be better if we wait for some time (eg. 5-10 sec) before disabling the track recording, to get the last precise point.

Scenario - suppose you are walking/driving and you disabled the track recorder then instead of getting disabled instantly it will wait for around maximum of 10 seconds (loading on track icon will be shown) and if in between those 10 seconds we get precise point then it will disable the track recorder and save it but if it dont gets any precise point in next 10 seconds also then it will save with last precise point.

According to my tests so far, it will not record another point unless I move at least 13m from the previous point, and thus if my walk ends at say 10m from the previous point, no additional point will be recorded when I stop and save, no matter how long I stand at the final destination before stop and save.

If that is the case then we need to deal with it too, although 10 meter is not a very big distance and gps cant accurately determine that small gap IMO, because in core part we accept all those points which have accuracy of around 50-60 meters.

> So, you are saying if I stand still on my starting point for some amount of time, or possibly move about in a small circle, it should record a point at the map cursor location? I will test this and see if that works for me. > Yes, absolutely > > Now if so, then your solution still leaves out the part about the ending point. > For end point i think it would be better if we wait for some time (eg. 5-10 sec) before disabling the track recording, to get the last precise point. Scenario - suppose you are walking/driving and you disabled the track recorder then instead of getting disabled instantly it will wait for around maximum of 10 seconds (loading on track icon will be shown) and if in between those 10 seconds we get precise point then it will disable the track recorder and save it but if it dont gets any precise point in next 10 seconds also then it will save with last precise point. > According to my tests so far, it will not record another point unless I move at least 13m from the previous point, and thus if my walk ends at say 10m from the previous point, no additional point will be recorded when I stop and save, no matter how long I stand at the final destination before stop and save. > If that is the case then we need to deal with it too, although 10 meter is not a very big distance and gps cant accurately determine that small gap IMO, because in core part we accept all those points which have accuracy of around 50-60 meters.