Technial stop Limitations
Posted: Tue Feb 13, 2024 7:02 pm
I was just working with a pilot who has a problem with the client where the app was crashing when it tried to load the flight from the server. Turns out the flight in question had nine technical stops defined and when the client tried to load all the airports related to the flight it was overflowing the data buffer used and causing the client app to stop working. Now I either need to increase the buffer size in the client and/or reduce the number of airports returned from the server but it got me thinking, what limitations should we put on technical stops in a route. Right now there really is no limitation, because up till now the only thing they were used for was in the client when you land at the airport and you did not push divert it used that list to determine if you were doing a tech stop or landing at the wrong airport. But now we are caching the airports in the client and I am working on some logic for the automated pilots that uses the technical stops to determine how the bot going to determine where they will actually land, a long list of tech stops makes that logic very complex so I was thinking of adding some limitations to the list of technical stops which I think would be:
Thoughts?
Edit: This has been implemented.
- No more that four
- The distance from the technical stops to either the departure or arrival airport must be less than the distance between the departure and arrival
- The distance from the departure to the technical stops and then to the arrival airport must be less than 150% the distance between the departure and arrival airport
- The distance between the technical stops and the arrival and departure airport and the distance between each technical stops must be at least 100 nm
Thoughts?
Edit: This has been implemented.