Open sww326 opened 3 months ago
The airport records is possibly from 2decb1d65d5a94f67d217edb60a061bb29f6202f or 7d10661028ccb9ad9b70f8e289e019080f8d03b7
The shortest being 0 miles... Mine actually is a zero mile flight, so shows correctly...
If you edit the flight, is the distance correct? Can you remove the src/dst and re-add them to force it to recalculate?
Hmm. The airport analyse part works fine locally on my dev install...
If you edit the flight, is the distance correct? Can you remove the src/dst and re-add them to force it to recalculate?
That worked. Doesn't explain how the error occurred in the first place (I haven't edited that effected segment since I first entered it years ago), but it resolved the issue for me.
Hard to say exactly.
Depending on how long ago, could've been some calculation bug at point of insert. Or some corruption since.
If it's not replicable, or seemingly widespread, not much can easily be done to try and find out.
Glad that part is fixed at least!
I reviewed the "Analyze" data for my flight log today and found two errors. First, under "Journey records,"my past flight between CLE-PBI is calculated at "0 miles, 00:30" and thus became my shortest flight.
Also, the Airport Records section is blank.