
My guess is that the software thinks the trip log skips the third intersection.
Right-click on the Network View and choose "Layout Grid with GPS". Then right-click again and choose "Show Intersection Extents". Make sure your trip log is visible in the Network View. (To make it visible, check its box in the list of trip logs in the GPS Status View).
You should see the trip log and some small red circles around each node. The trip log should pass through each red circle. If it doesn't, the software thinks the trip log bypasses that intersection.
You may have to zoom in the Network View and the scroll to see the third intersection, but I'm expecting you'll see that the trip log passes outside the red circle.
If that's the case, then either the red circle is in the wrong location, or the red circle is not wide enough.
To solve the first problem, make sure your geographic coordinates are correct. If you got them from the GPS, make sure they're in pairs that straddle the center of the intersection. (If you took just one GPS reading, traveling in the east-bound direction, then the "center of the intersection" (red circle) will be too far south (in right-hand drive rule countries).
To solve the second problem, either (1) make sure you've got multiple readings for the geographic coordinates taken on diagonal opposites of the center of the intersection -- the farther the readings are apart, the larger the circle, or (2) make sure you've declared the correct number of lanes and lane widths at the intersection. You can cheat if necessary: declare a large number of lanes to artificially enlarge the red circle. Cheating on the number of lanes will adversely affect a platoon-progression diagram, but it won't harm a time-space diagram, a TT&D report, or a trip-log plot.
There's a topic in the Frequently Asked Questions section of the online help that deals with this problem, but from the wording of the question, you might not recognize its applicability at first:
"The TT&D report says that my recorded trip log stops before an intersection then resumes at the next intersection downstream." or "The TT&D report says that my trip log started at intersection X but it actually started at the previous intersection upstream."
Let me know if this doesn't solve it.
Regards.
Greg