1) I create a flight plan at http://onlineflightplanner.org/ and download the flightgear compatible file. The file is attached to this ticket.
2) I confirm that the waypoint names are correct by entering them into a plan at https://skyvector.com/
3) I load the plan in my fg 3.4 route manager
4) Because fg has old and incorrect data for waypoint SIGUL, my flightplan is now about 12000 nm longer
I consider this a bug because waypoints loaded from a plan file should take precedence over the default fg data. If you edit the attached plan changing "SIGUL" to "SIGUL-plan" you will see that the desired route is set. This confirms that the file correctly specifies desired longitude and latitude for the waypoint. The loaded file should take precedence because it can serve as a workaround for incorrect fg data (SIGUL in nav.dat.gz in this case)
Confirmed.
Pushed a fix to next in commit 1cbcae9795ff15de4513f19581. Testing / verification is appreciated, then I will cherry-pick to the stable branch