I have experienced this exact same problem on my 2013 MS. It seems to be a GPS reception issue and will normally clear up quickly with improved reception. I have also tried resetting the MCU (hoping the GPS subsystem would also reset) with mixed results.