Page 1 of 1

Understanding POI and combined Tracks

Posted: Sun Jun 22, 2025 8:07 am
by vlad4md
Here I am trying to combine 2 different tracks.

The picture is self-explanatory, I hope, the issue I am currently encountering is that in lap analysis it is showing the conflict between T1 and T2.

These are 2 autocross custom tracks that I created myself.
As you can see, one of them 'overlaps' the other, but they have different directions and different start/stop points.

I managed to record the session without any issues. I am just wondering if I've correctly set the 'Info' and 'Danger' zones as per this layout, without actually confusing the Laptimer, so I need confirmation here that what I did makes sense, and I can use the same principle for any other future custom tracks that overlap.

1) What exactly a POI (information) provides? apart from the 'text' that it displays that I define in its description.
Somehow I thought that it should at least display the 'speed' at which I pass this information point, but it seems that it is not the case.

How does the laptimer decide to display the corner/straight speed in the video overlay? Is is done automatically based on G-forces?


2) How do I share the custom-created track with my friends? Is the only way to do this is to share the whole DB backup?

3) How do I create a group/share with them POI, tracks (custom-made) ?

4) Have you considered changing the sync method for an external video with the gps/laptimer data?
I think racechrono approach of having a split screen with the video and map makes it so much easier, compared to setting the 'end' of the lap. I understand this might be easy when you are on a track and you clearly see the finish line in your video, but it's not always the case.
I'm attaching a screenshot and hopefully we can have this thing improved.

5) I have been able to reproduce the bug with the spinning 'video' after the export, I wanted to record my iPhone screen but it even failed to save the recording, so I guess it's more of the OS related than the issue with the laptimer itself, it just makes me confused how an app can 'break' the functionality of the iOS 'Photos' native app :)
A restart has helped, not the biggest concern for me.

6) Please fix the 'drag and drop' of the points in the map view for the iOS for the next release :) I know we discussed it earlier, hopefully we can have it fixed soon.

7) What is the purpose of the 'Track' trigger type of the POI? When and how it should be used?

Attaching the screenshots.



Thank you

Re: Understanding POI and combined Tracks

Posted: Sun Jun 22, 2025 12:24 pm
by Harry
Provided you make sure (in your track definition) LapTimer will not pick up a T1 trigger when started by T2 (and vice versa), this scenario is fine. So from I see in the sketch - you can ignore the warning. The conflict detection is pretty dump. It just creates a rectangular area from all POIs belonging to a track set and checks if this area overlaps with some other track's rectangle. The warning has been added because there are plenty of tracks world wide which are used in multiple configurations. In case one has loaded more than one of these, recordings will get screwed up.

On 1: Information POIs are just illustrative and are displayed in overlays and the map view. Speeds added to a video are not related to information POIs. What LapTimer does is recognizing local min and max speeds. These typically correspond to corner speed before accelerating again, and straight speeds just ahead of the braking point. At least in case you do a perfect lap without obstacles ;-) Straight and corner speeds are the most important indicators for lap quality.

On 2 and 3: You can use the Certify Track function. Usually it is used to submit a track set for inclusion into our track repository. Instead of sending the mail generated to us (tracks@gps-laptimer.de), just send it to your friends. Thy can tap the .hpoil attachment and open / import it with their LapTimer instance.

On 7: we provide POI sets of all tracks we have defined. Every track is represented by such a Track POI. Usually, it is the weighted center of all POIs included in a track. It produces a nice overview in Map View but is ignored otherwise.

Re: Understanding POI and combined Tracks

Posted: Sun Jun 22, 2025 9:56 pm
by vlad4md
Thanks,
finally, is there a mode where the app will simply record the data so i could add the POI’s start/finish lines later?

Re: Understanding POI and combined Tracks

Posted: Mon Jun 23, 2025 6:35 am
by Harry
Yes, you can log data after enabling "Manual Timing" in Settings. This will add "Start" and "Stop" buttons to Timer View.