We have local navi software, wich can update onscreen image as many times per second as hardware can recalculate. Looks helpful, because while driving I cannot look directly to the monitor, but using high fps I can "feel" right turns, distances, work of "autozoom" realtime option etc.
There are some problems in programming such software due to 1Hz gps sygnal. For missing frames we use interpolation and a little bit extrapolation algorythms. Later fps was limited by 5 because streets naming flips too often. Their position was not blocked to leave nice effect of "names follows the streets". It looks like liquid texts dynamically bends along the viewable fragment of the street while driving with closest zooms.
That was good idea (2k1Toaster) to use gyro-odometer sygnals to avoid extrapolation in real-tame navigation software. For example in ublox DR chipsetst you can set custom period of calculation speedimpulses, gyro is sampled by 40Hz and their UBX-protocol is not ASCII, its binary, with flags, crc's etc. The question of adequate navi-software, supported such things is opened for most areas.