Overview of GT7 Telemetry Software

  • Thread starter Thread starter snimat
  • 275 comments
  • 122,624 views
Does anyone know if it’s possible to get track data (left and right boundaries of the track)? I’m trying to create a visualization of the racing line in relation to the track and need track information in order to draw the racetrack beneath the racing line. This would be useful for post-race analysis to see if you’re hitting the apexes.

One idea I had was to drive around each track twice, once along the left edge and once along the right edge, to capture positional data of the track boundaries. I’m wondering if there’s a better way.
For Delta we had to drive around the edges of every track. Took a while!
 
I made my own dashboard if anyone is interested in trying it out.

Edit: It's now out on iOS and Android!
iOS: https://apps.apple.com/us/app/podium-gt7-dashboard/id6752813246
Android: https://play.google.com/store/apps/details?id=io.podium.app

It will be free on iOS and Android when its ready. Let me know if there is any feedback.



IMG_5807.webp


IMG_5809.webp
 
Last edited:
Hi everyone,
Has anyone figured out how the track sector times are achieved? I assume it's not available in pure telemetry and it's in game code. Or is there any way to determine the track sectors?
I was hoping to have a table display of sectors of lap times for easy comparison.
One approach was thinking is just divide the lap track data up into thirds or quarters by lap track distance.

I've forked the great work of gt7dashboard by @snimat and working towards a hopefully more appealing UI (dark theme/ carbon theme).
Still work in progress and bug fixing todo.
Getting accurate sector times takes a lot of work. I’ve managed to get decent results by following this process:

1. Collect map data by driving around the edges of the track

2. Once you have the map data, place sector markers at 33% and 66% along the total track length (for tracks with three sectors). This provides a good initial estimate of where the in-game sectors are located.

3. Next, calibrate your sectors by providing reference laps and recording the sector times from the game. You only need to calibrate once.

Screenshot 2025-10-06 at 12.15.02 PM.webp


4. Adjust your sector locations to minimize the total delta between your estimated sectors and the in-game sector times from the reference laps.

This method has gotten me very close to the in-game sectors, sometimes even spot-on. Its a lot of work but is really worth it because once you have track data it opens up the possibility to do a ton of interesting things like, track detection, live deltas, lap time prediction, pit detection and obviously accurate sector times.

Screenshot 2025-10-06 at 12.10.08 PM.webp
 
Last edited:
Getting accurate sector times takes a lot of work. I’ve managed to get decent results by following this process:

1. Collect map data by driving around the edges of the track

2. Once you have the map data, place sector markers at 33% and 66% along the total track length (for tracks with three sectors). This provides a good initial estimate of where the in-game sectors are located.

3. Next, calibrate your sectors by providing reference laps and recording the sector times from the game. You only need to calibrate once.

View attachment 1483898

4. Adjust your sector locations to minimize the total delta between your estimated sectors and the in-game sector times from the reference laps.

This method has gotten me very close to the in-game sectors, sometimes even spot-on. Its a lot of work but is really worth it because once you have track data it opens up the possibility to do a ton of interesting things like, track detection, live deltas, lap time prediction, pit detection and obviously accurate sector times.

View attachment 1483899
Basically what I’ve been doing, but I have also dabbled a bit with “recording” coordinates for each lap, and comparing to a previous lap, ie not bothering with the track edges at all. It works, but it takes a toll on the device to keep up, cpu-wise. I’m going to look into it more as soon as the iPad version of EzioDash Pro is closer to completion.
 
I made my own dashboard if anyone is interested in trying it out.

Edit: It's now out on iOS and Android!
iOS: https://apps.apple.com/us/app/podium-gt7-dashboard/id6752813246
Android: https://play.google.com/store/apps/details?id=io.podium.app

It will be free on iOS and Android when its ready. Let me know if there is any feedback.



View attachment 1482184

View attachment 1482185


This is great! I'm running on an Android Pixel 9 pro. The only thing that isn't working is the brake/throttle graph. I have just a grey box.
 
This is great! I'm running on an Android Pixel 9 pro. The only thing that isn't working is the brake/throttle graph. I have just a grey box.
Thanks, I'll have to take a look at the logs.

Edit: I pushed an update, just restart the app to get the update.
 
Last edited:
Back