This seems to be caused by robot passing by the origin or world. Which probably robot_localization interpret as , robot has changed the poles, causing the yaw_offset in navsat_transfrom_node tobe incorrect.
One possible solution; initialize the world and robot somewhere far from this origin e.g (100, 100).
Adressed by ; 57bbb7a79ff7a003da9ffdd185bfd8890ed0a701
The hector GPS plugin is more consistent with real data. After the above commit things seems to work as expected.
This seems to be caused by robot passing by the origin or world. Which probably
robot_localization
interpret as , robot has changed thepoles
, causing theyaw_offset
innavsat_transfrom_node
tobe incorrect.One possible solution; initialize the world and robot somewhere far from this origin e.g (100, 100).