Well, that's legacy. Changing it means making all recorded plots invalid - which would be a pity... From a timing PoV, the problem is not too severe - both triggers are ahead of the real point and the difference in distance is compensated by the different speeds (at least I am a lot faster at 'Gate' compared to 'Bridge'). The reason for the split trigger at Aremberg is optimization for the internal GPS's typical behavior in corners: iOS seems to apply some smoothing which leads to 'wide bends':
Setting the trigger somewhat outside, increases the detection rate.
- Harry