Read the shape of the speed trace
Generated from
content/lms/data-interpretation-for-drivers/02-reading-speed-traces/01-speed-trace-anatomy.md; edit the source file, not this page.
Source path: content/lms/data-interpretation-for-drivers/02-reading-speed-traces/01-speed-trace-anatomy.md
Course: Data Interpretation for Drivers
Module: Reading Speed Traces
Estimated duration: 55 minutes
The speed trace is the first story your lap tells. It is not the whole story, and it is not a verdict by itself. It is the shape of your car gaining, losing, holding, or recovering speed across the lap. When you learn to read that shape, you stop treating data as a pile of squiggly lines and start using it like an instructor sitting beside you after the session.
Your goal in this lesson is narrow: learn to look at the speed trace and identify what kind of corner story it is telling. You are not trying to solve the entire lap. You are not trying to become a data engineer. You are learning a driver process: look at the shape, ask why that shape happened, check the answer against other channels if you have them, compare to another lap when useful, then set one objective for the next session.
Start with the basic anatomy. On a distance-based speed trace, the line climbs when the car accelerates, drops when the car decelerates, flattens when speed is nearly constant, and changes slope when the rate of acceleration or deceleration changes. A steep downward slope means a strong rate of speed loss. A shallow downward slope means a lighter rate of speed loss. A steep upward slope means the car is accelerating strongly. A broken, wavy, or interrupted climb after corner exit usually means the car was not cleanly committed to acceleration. That may be throttle hesitation, a lift, a line problem, a vision problem, a late correction, traffic, or a decision to protect the car. The trace tells you where the question is. It does not automatically tell you the final answer.
The central skill is to read shape before chasing numbers. A maximum speed number can be interesting, but it can also distract you. A lap can have one impressive peak speed and still be weak through the sections that matter. A corner can show a higher entry speed and still lose time if the speed trace then collapses, flattens too long, or requires throttle corrections on exit. The shape shows how the speed was made, spent, and recovered.
Use three questions every time. First, what shape is the corner supposed to have? Second, what shape did your trace actually make? Third, why did the trace differ from the expected shape? The answer to the third question is where the learning lives.
For most intermediate driver analysis, the useful first split is U-shaped versus V-shaped. A faster corner, roughly above the 65 mph neighborhood in this corpus, usually wants a U-shaped trace. A slower corner, roughly below that neighborhood, often allows or needs a more V-shaped trace. This is a guideline, not a law. Aero cars may move the high-speed threshold upward, and diamond-style corners are an exception. The point is not to memorize 65 mph as magic. The point is to make a first prediction about the shape a corner should produce, then test whether your trace agrees.
A U-shaped speed trace means the car sheds speed, carries a rounded minimum, and begins building speed again without a sharp point at the bottom. The bottom of the U is not a long coast. It is a controlled transition through the middle of the corner where the car is still loaded, still working, and not being yanked from braking to acceleration. On a high-speed or medium-high-speed corner, this rounded bottom often suggests you are managing the entry, mid-corner, and exit as one connected event. The car is not being stopped, rotated, and relaunched as if it were a hairpin. The driver is asking the tires to stay loaded and the car to keep speed.
A V-shaped speed trace means the car loses speed to a sharper minimum and then begins to accelerate more directly from that point. This shape can be appropriate in slower corners where you need the car to change direction more decisively before you go back to power. The bottom of the V is not automatically good or bad. It is a clue. In a slower corner, a clean V may show that you got the car slowed, turned, and released to throttle. In a faster corner, the same V may show that you over-slowed, pinched the corner, or turned a flowing corner into a stop-and-go event.
That is why the rule always includes the question why. If the speed is in the high-speed range and the trace looks like a hard V, do not immediately tell yourself to carry more speed. First ask why it became a V. Did you brake too hard and too late? Did you finish the brake release too abruptly? Did you wait too long to begin turning? Did traffic force the shape? Did you protect the car because the corner exit felt uncertain? Did the line require a late apex or diamond shape? If the answer is traffic, the next-session objective is different than if the answer is hesitation or over-slowing.
If the corner is in the slower range and the trace looks like a broad U, do the same thing. Maybe that corner rewards rolling minimum speed. Maybe you are coasting through the middle and delaying throttle. Maybe you are carrying too much speed at turn-in and then waiting because the car will not finish the corner. Maybe you are using a line that feels smooth but delays full throttle. The speed trace gives you the shape; your job is to turn the shape into a driving question.
The slope of deceleration is the next layer. When the speed trace drops toward a corner, look at the steepness and whether that steepness changes. A straight, firm deceleration slope often points to a clear brake phase. A downward slope that changes shape as the car approaches the minimum speed can suggest trail braking. In the corpus example, the speed trace alone lets you notice a change in the slope of deceleration and suspect trail braking in one marked area, while another marked area shows little trail braking. Brake pressure then confirms the suspicion: the green-circled area had trail braking, and the red-circled area had very little.
This is an important discipline. The speed trace can suggest trail braking, but it does not prove the complete technique by itself. It can show that the rate of speed loss changed as the car approached the corner. It cannot, alone, tell you exactly how much brake pressure was used, whether the release was smooth, whether the front tires were overloaded, or whether the technique was helpful. If you have brake pressure, use it. If you have longitudinal g, use it. If you have throttle, use it. If you have video, use it. The speed trace starts the investigation.
A good driver-data habit is to separate observation from judgment. Observation: the deceleration slope changes later in the brake zone. Observation: the minimum speed is rounded instead of pointed. Observation: the exit acceleration line has two small interruptions. Judgment comes later: that trail brake was useful, or it was too long; that rounded bottom was appropriate, or it was coasting; that exit hesitation was traffic, or it was uncertainty. If you jump from observation to judgment too quickly, you will fix the wrong thing.
Now look at acceleration shape. After the minimum speed, the trace should generally climb in a way that fits the corner and the available grip. A clean exit does not always mean an instantly steep line. In a powerful car, a low-speed exit may be traction-limited. In a faster corner, you may be unwinding steering while adding throttle. But the climb should tell a coherent story. A clean exit usually looks committed. A hesitant exit often looks broken: the speed rises, pauses, rises again, or the slope weakens unexpectedly.
The corpus calls attention to speed changes exiting a corner onto the front straight and asks what causes them. The listed possibilities are throttle adjustments, line, vision, mental image of track-out, too much mid-corner speed, or too much throttle. That is exactly how you should think. Do not say the car was slow on exit and stop there. Ask what input or decision created the exit shape. If the throttle trace shows you were adjusting the throttle after the corner, the speed trace was not just a speed problem; it was a commitment problem, a line problem, or a corner-exit confidence problem.
Coasting is one of the clearest speed-trace failure modes. If the speed trace flattens or drifts gently downward between the brake release and the throttle application, you may have created a dead zone. The car is not braking hard, not accelerating, and not using the available track to build speed. The corpus repeatedly tells you to look for coasting in the speed and throttle traces. For an intermediate driver, this is often one of the biggest early wins because it turns a vague feeling into a precise place to work. The next session objective is not be faster everywhere. It is remove the dead zone between brake release and useful throttle in one corner.
But coasting is not always visible as a perfectly flat section. Sometimes it appears as a lazy transition: the deceleration slope becomes shallow, the bottom of the trace stretches, and the acceleration slope begins late. Sometimes it shows as a speed trace that looks smooth but is slow compared with another lap. Sometimes throttle confirms it directly. The shape matters because drivers often do not feel small coasts accurately at speed. The trace makes the waiting visible.
Throttle lifts are another speed-trace clue. A lift where it should not happen may show up as a reduced acceleration slope, a small sag, or a speed plateau in a place where the car should be accelerating. The throttle trace can confirm whether there was an actual lift. In fast corners, lifts matter because they can be both a time issue and a stability issue. The corpus specifically calls out lifts in fast corners under both brake and throttle review. If you see a lift in a fast corner, do not treat it casually. Ask whether it was traffic, fear, line placement, too much entry speed, a late apex problem, or a vision problem.
Not full throttle between turns is a different clue. On a short straight between corners, you may assume there is not much to gain. The speed trace may disagree. If the trace climbs weakly between two corners, look at throttle. Were you actually full throttle? Did you delay full throttle because you were still finishing the previous corner? Did you lift early because the next corner arrived faster than expected? Did gear selection or shift timing interrupt acceleration? The speed trace points to the weak climb; throttle, gear, and RPM help explain it.
Shift issues can also appear in speed shape. The corpus lists upshifts and downshifts as speed-trace questions. A shift may show as a temporary softening of the acceleration slope or a disruption around braking and entry. The speed trace will not tell you all the gearbox details by itself, but it can show you where acceleration stopped building or where deceleration rhythm changed. If RPM and gear are available, they become the confirmation channels.
Longitudinal g is the speed trace translated into force. When speed is dropping, longitudinal g helps you see decel rate. When speed is climbing, it helps you see accel rate. The corpus uses longitudinal g to ask whether you are consistently using peak g-loads, whether there are braking issues through decel rate, whether there are acceleration issues through accel rate, and whether behavior is consistent lap to lap. For the speed trace reader, longitudinal g is useful because it makes slope changes more obvious. The speed trace shows the car slowing; longitudinal g shows how hard and how consistently it slowed.
Lateral g gives you the cornering side of the story. If the speed trace shape looks odd through a corner, lateral g can show whether the car was consistently loaded, whether there were spikes, and whether the driver used similar cornering force lap to lap. A rounded U with stable lateral g may tell a different story than a rounded U with spikes or uneven lateral load. A V with a clean lateral g pattern may be a planned slow-corner rotation. A V with ragged lateral g may suggest the driver arrived with too much disturbance or corrected the car mid-corner.
Brake pressure is one of the strongest confirmation channels because it tells you what your foot actually did. The corpus tells you to look at brake pressure shape: initial application, trail, long tail, inconsistent pressure, light-long versus hard-short, and lifts in fast corners. When you see a speed trace that drops gently for a long time, brake pressure can tell you whether you were braking lightly for too long. When you see a speed trace with a late change in slope, brake pressure can tell you whether there was a trail-brake release. When you see a slow exit after a high entry, brake pressure may reveal that the entry phase never ended cleanly.
Throttle is the other major confirmation channel. The corpus tells you to look for coasting, hesitant application, early application leading to a lift, and lifts in fast corners. These are not abstract data items. They map directly to what you feel in the car. Hesitant throttle often feels like you are waiting for the car to accept power. Early application leading to a lift often feels like confidence followed by correction. Coasting often feels smooth in the cockpit, which is why it can survive unnoticed. The trace makes the habit visible.
The basic process should be repeatable enough that you can do it after every session without drowning in data. Pick one track section. Look at the speed trace shape. Decide whether the corner should probably be U-shaped or V-shaped, allowing for speed range, aero, and diamond-style exceptions. Look at the decel slope, the minimum-speed region, and the acceleration slope. Ask why. Then confirm with available channels: brake pressure, throttle, longitudinal g, lateral g, steering, RPM, gear, GPS line, segment times, fastest rolling, theoretical fastest, throttle histogram, or video. You do not need every channel. Speed plus longitudinal and lateral g is a typical basic set. Throttle and brake pressure are ideal because they connect the speed shape directly to your inputs.
The danger is looking at too much at once. You can bury yourself in channels and forget the driving question. Keep the first pass simple. Speed tells you where to look. Brake and throttle tell you what you asked the car to do. Longitudinal and lateral g tell you how the car responded. Segment or compare time tells you whether the difference mattered. GPS line or video helps answer why.
Comparison is useful, but this lesson is not the same as a full compare-laps lesson. Here, comparison is a tool for interpreting shape. Overlay two laps when you need a reference. Look for differences in the speed trace. Use delta or compare time to find the biggest differences and prioritize. Then identify the difference in shape. Did one lap brake later but carry a worse exit? Did one lap have a smoother U through the faster corner? Did one lap make a cleaner V and accelerate earlier from the slow corner? Did one lap contain a throttle lift that the other did not?
Do not compare only your fastest lap. The corpus warns that looking only at the fastest lap can miss important information. One lap may contain the better entry to a corner and another lap may contain the better exit. If the driver had put the red and blue laps together, the lesson suggests there was more performance available. That does not mean you can simply stitch fantasy sectors together and declare a target. It means you should look for repeatable pieces of technique that already exist in your driving and then set an objective to make them appear in the same lap.
Consistency matters because one heroic shape is not yet a skill. The corpus repeatedly asks you to compare with other laps for consistency, other drivers, other cars, or other sessions. If one lap has a beautiful U-shaped high-speed corner and the next five have a sharp V or a lift, the lesson is not that you solved the corner. The lesson is that you have seen what the shape can look like and now need to understand what made it repeat or disappear.
When you calibrate the data to your driving, connect the trace to memory. Look at a section and ask what you remember. Did you feel late? Did you feel patient? Did you feel like you were waiting to see track-out? Did you feel traffic ahead? Did you feel you released the brake smoothly? Did you feel like the throttle came in cleanly? Then check whether the trace agrees. Over time, this improves your internal sensor. You start knowing what a coast feels like, what a late throttle feels like, what a clean high-speed U feels like, and what an over-slowed V feels like.
A useful mental step is to imagine what the ideal would look like before you decide what to change. If you believe a corner should be U-shaped, sketch that shape in your mind. Where should speed begin dropping? How rounded should the minimum be? Where should acceleration begin? If your trace has a sharp point, a flat coast, or a broken exit, the mismatch becomes visible. If you believe a slow corner should be V-shaped, imagine a firm decel, a decisive minimum, and a clean acceleration. If your trace instead has a long sagging bottom, the problem is probably not lack of bravery. It may be that you are waiting too long to finish the corner.
The most important product of this work is the next-session objective. A speed-trace read is not complete until it produces an action. The action should be specific enough that you can attempt it on track. Not go faster in Turn 3. Better: in Turn 3, remove the coast between brake release and throttle by releasing the brake with purpose and beginning maintenance throttle as the car approaches the apex. Or: in West Bend, test a lighter brake application because the data suggests the brake event may be stronger than needed for that corner, while keeping the first two laps conservative. Or: in the Downhill, minimize the throttle lift and confirm afterward whether the speed trace holds a cleaner climb.
Because this is an intermediate lesson, you should also know when not to act. A strange speed shape caused by traffic is not a technique failure. A shape changed by a passing situation is not your baseline. A lap with missing or noisy data may not be worth interpreting deeply. The corpus reminds you to know the limitations of your data tool. Data does not lie in the simple sense that the recorded channel is what the system recorded, but it does not tell you everything. GPS speed, sensor quality, synchronization, and missing channels can all limit what you can conclude. Use the trace as a disciplined question, not as an all-knowing judge.
Worked example one: Lime Rock comparative data. The corpus includes Lime Rock Park overlays in Track Attack with two laps compared, GPS speed, time lost, and marked speeds around 112 mph. The teaching point is not the exact tenth shown on the screen. The teaching point is the workflow. Overlay two laps. Look first for the biggest time difference, not the most dramatic-looking wiggle. Then inspect the speed shape around that distance. If the faster lap has a more appropriate U through a fast section, ask what created it. Was braking earlier but lighter? Was the release smoother? Was there less throttle hesitation? If the slower lap has a similar entry speed but a weaker exit climb, the issue is probably not entry bravery. It may be delayed throttle, a compromised line, or too much mid-corner speed that prevented clean exit commitment. Use throttle and brake pressure if available before you make the driving change.
Worked example two: West Bend and the Downhill. The corpus calls out a lap that looks hesitant and names four observations: good brake pressure trace shape in one place, braking for West Bend could be lighter, throttle lift for the Downhill should be minimized, and a blend of throttle and brake may be causing delay in getting to full throttle. This is a rich example because the speed trace alone would tempt you to say be faster. The better read is more precise. In West Bend, the speed shape and brake pressure suggest the driver may be using more brake than needed for that track-specific corner. In the Downhill, the trace and throttle behavior suggest a lift where the objective is to minimize it. In the blend area, the problem may be overlap or transition timing: the driver is not getting cleanly from the slowing phase to committed acceleration. The note that it looks like a hesitant lap matters. Hesitation often shows up as inconsistent brake traces, lazy throttle release, and hesitant throttle application. The right next-session plan is not one giant correction. It is one selected experiment, with traffic and video checked before blaming technique.
Worked example three: trail braking from speed slope. In the speed-plus-brake example, the first clue is only the change in the deceleration slope. That lets you suspect trail braking in one area and little trail braking in another. Then brake pressure confirms it. This is exactly how to use a speed trace intelligently. You let speed produce a hypothesis, then you test it with the input channel. After that, you still ask whether it was good or bad. Trail braking is not automatically good because it appears in data. Little trail braking is not automatically bad. The question is whether the shape helped the corner: did it support rotation, protect minimum speed, and allow a clean exit, or did it extend the slowing phase and delay throttle?
Common mistake: judging the corner by minimum speed only. A higher minimum speed can be slower if it creates a delayed or broken exit. A lower minimum speed can be faster if it lets the car turn and accelerate earlier. What good looks like is a trace shape that matches the corner type and produces a clean recovery of speed after the minimum.
Common mistake: treating every V as bad. A V-shaped trace can be correct in slower corners. What good looks like is asking whether the corner speed and geometry call for that shape, then checking whether acceleration begins cleanly from the point of the V.
Common mistake: treating every U as good. A broad U can hide coasting. What good looks like is a rounded high-speed trace with purposeful transitions, not a long undecided middle where the car is neither braking effectively nor accelerating.
Common mistake: fixing the speed trace without checking throttle or brake. Speed shows outcome. Brake and throttle show much of the request that created the outcome. What good looks like is forming a hypothesis from speed, then confirming with brake pressure, throttle, longitudinal g, lateral g, gear, RPM, GPS line, or video when those channels are available.
Common mistake: chasing the fastest lap only. The fastest lap may not contain your best technique in every section. What good looks like is finding useful shapes across multiple laps and deciding which repeatable behavior you want to bring into the next session.
Common mistake: ignoring traffic. The corpus explicitly flags traffic as a possible explanation. What good looks like is checking video or session context before making a technique conclusion from a strange shape.
Drill: the three-corner speed-shape audit. Do this after your next event session. Choose three corners only: one fast or medium-fast corner, one slow corner, and one corner that felt uncertain from the cockpit. Spend ten minutes total. For each corner, write the expected shape first: U, V, or exception. Then look at the actual speed trace and describe three parts: deceleration slope, bottom shape, and acceleration slope. Next, ask why the shape happened and check one confirmation channel. Use brake pressure or throttle if available; use longitudinal and lateral g if that is what you have; use video if the trace may involve traffic. The success criterion is not finding a huge mistake. The success criterion is producing one clear next-session objective tied to one corner and one visible trace feature.
Drill progression for three sessions. In session one, only identify shapes and do not change your driving mid-session. Afterward, pick one corner objective. In session two, drive normally for the first few laps, then attempt the one objective for three clean laps if traffic allows. Afterward, compare the speed trace shape before and after the attempt. In session three, test repeatability. If the improved shape appears only once, it is a clue. If it appears lap after lap with no new downside in the exit or next straight, it is becoming a skill.
The final rule is simple: read shape, ask why, confirm, compare, calibrate, and set the next objective. The speed trace is powerful because it is basic. It shows every place the car gained and lost speed. But its real value is not the line itself. Its value is that it gives you better questions: why did I coast here, why did the fast corner become a V, why did the exit climb break, why did the other lap recover speed sooner, why did the trace look hesitant? Better questions lead to better experiments. Better experiments lead to cleaner laps.
Worked example: Lime Rock comparative data
Use the Lime Rock overlay as a prioritization exercise, not a number-chasing exercise. Start with compare time to find where the lap difference matters. Then inspect the speed shape around that distance. If two laps have similar peak speed but one loses time on exit, the shape after minimum speed matters more than the peak. If one lap makes a cleaner U through a faster section, confirm with brake, throttle, and g traces before deciding what to change. The output of the review should be one action for the next session, not a list of every visible difference.
Worked example: West Bend and Downhill hesitation
The West Bend and Downhill notes show how a speed trace becomes a driving diagnosis only after confirmation. The lap is described as hesitant, with brake trace inconsistencies, lazy throttle release, and hesitant throttle application. West Bend may need lighter braking. The Downhill calls for minimizing a throttle lift. A throttle-and-brake blend may be delaying full throttle. The useful lesson is that one weak speed shape can come from several different behaviors, so you isolate the section, check the input channels, and choose one experiment rather than trying to fix the whole lap at once.
Worked example: identifying trail braking from slope
A change in the deceleration slope on the speed trace can suggest trail braking, but the speed trace is only the clue. Brake pressure confirms whether the driver actually trailed the brake in one area and used very little trail braking in another. After confirmation, the final question is whether the technique helped the corner. Trail braking that supports rotation and allows a clean exit is different from a long brake tail that delays throttle and stretches the bottom of the trace.
Common mistakes
The most common mistake is judging by minimum speed alone. Good looks like a trace shape that fits the corner and supports the exit. Another mistake is treating U-shaped as always good and V-shaped as always bad. Good looks like matching the shape to corner speed and geometry, with exceptions for aero cars and diamond-style corners. A third mistake is diagnosing from speed alone when throttle, brake, g, gear, RPM, GPS line, or video are available. Good looks like using speed to ask the question and other channels to confirm it. A fourth mistake is ignoring traffic or context. Good looks like checking whether the shape came from driving technique or from the session situation.
Drill: three-corner speed-shape audit
After the next session, pick one fast or medium-fast corner, one slow corner, and one corner that felt uncertain. For each, predict the expected speed-trace shape before looking closely. Then describe the actual deceleration slope, bottom shape, and acceleration slope. Ask why the shape happened and confirm with one other channel. Limit the drill to ten minutes so it stays driver-focused. The success criterion is one clear next-session objective connected to one visible trace feature.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Data-for-Drivers-PRINT | 66236554-430f-2322-19d8-8c5fc03fe1d7 | 10 | 1 | uio_books_raw_v1 |
| 2 | Data-for-Drivers-PRINT | d623e34d-3ab2-0eeb-73dc-e2b770ccdd05 | 10 | 1 | uio_books_raw_v1 |
| 3 | Data-for-Drivers-PRINT | e6c709c8-5c05-7e78-a657-04f11034ae28 | 10 | 1 | uio_books_raw_v1 |
| 4 | Data-for-Drivers-PRINT | 97d78cee-21f9-2292-7003-64b2df741e57 | 10 | 1 | uio_books_raw_v1 |
| 5 | Data-for-Drivers-PRINT | 0094a453-1c9d-26b3-fb46-7912229586c5 | 5 | 1 | uio_books_raw_v1 |
| 6 | Data-for-Drivers-PRINT | 8b3d290e-b0d8-f5d5-aee7-3cb2aa93adda | 5 | 1 | uio_books_raw_v1 |
| 7 | Data-for-Drivers-PRINT | ec2b5633-0f92-b587-99f2-6f5044efc092 | 1 | 1 | uio_books_raw_v1 |
| 8 | Data-for-Drivers-PRINT | c440bd03-cdb9-90b2-ddf1-f8335740fa28 | 1 | 1 | uio_books_raw_v1 |
| 9 | Data-for-Drivers-PRINT | 6ba94a9e-3b49-804d-875a-5266e6625e49 | 1 | 1 | uio_books_raw_v1 |
| 10 | Data-for-Drivers-PRINT | ba11efce-fa7b-39cf-f1bf-2bbfddb3acaa | 1 | 1 | uio_books_raw_v1 |
| 11 | Data-for-Drivers-PRINT | 27a86c4f-e78b-a3ac-5011-0bb82408d23d | 1 | 1 | uio_books_raw_v1 |
| 12 | Data-for-Drivers-PRINT | ba9a10fd-f74a-5561-6dd6-463e44efe09a | 1 | 1 | uio_books_raw_v1 |
| 13 | Data-for-Drivers-PRINT | bfa5ee09-090f-4951-d7d7-2ffae710b22f | 9 | 1 | uio_books_raw_v1 |
| 14 | Data-for-Drivers-PRINT | 45ae5ff1-23c9-fc57-4bfa-5ae8023b6962 | 9 | 1 | uio_books_raw_v1 |
| 15 | Data-for-Drivers-PRINT | c493f39d-9ba1-5829-3168-d38e471cc061 | 9 | 1 | uio_books_raw_v1 |
| 16 | Data-for-Drivers-PRINT | 95d759bb-9d50-5ef8-90ea-2e92ab2c47b4 | 9 | 1 | uio_books_raw_v1 |
| 17 | Data-for-Drivers-PRINT | 36e668ca-5bb7-9f4d-1af8-a1eac0343197 | 1 | 1 | uio_books_raw_v1 |
| 18 | Data-for-Drivers-PRINT | a6f319de-d741-e8b4-12ab-b099ed06bbc8 | 1 | 1 | uio_books_raw_v1 |
| 19 | Data-for-Drivers-PRINT | cb13d8c3-cc6b-28e9-246f-c3c64ae01efc | 1 | 1 | uio_books_raw_v1 |
| 20 | Data-for-Drivers-PRINT | 849f6d32-91c8-10c7-d758-d545a8a31713 | 1 | 1 | uio_books_raw_v1 |
| 21 | Data-for-Drivers-PRINT | c32e7c50-7d5a-817a-2ca4-6ed348f718aa | 16 | 1 | uio_books_raw_v1 |
| 22 | Data for Drivers | b6b9f68e-51d0-1d4b-6d52-7759e4c723d4 | 16 | 1 | uio_books_raw_v1 |
| 23 | Data-for-Drivers-PRINT | 96a12794-6a20-0aa3-31d3-f6f0a4a1c964 | 15 | 1 | uio_books_raw_v1 |
| 24 | Data-for-Drivers-PRINT | ceb9bbb2-e006-aaf5-239d-61056295ff6f | 4 | 1 | uio_books_raw_v1 |
| 25 | Data-for-Drivers-PRINT | e0021f6a-4d30-84d5-32b4-600c89c6f670 | 9 | 1 | uio_books_raw_v1 |