[Feature request]: Remove default 1,000 waypoint limitation
As explained in #65 (comment 575365172), there is a limitation on the number of airports/waypoints which will be loaded into memory. This is designed to reduce the CPU impact on older phones.
However, this leads to an inconsistent experience, as the user will get different airports depending on where the user is when starting the program. This limitation is opaque, and so the the user is not aware that the program is filtering available airports.
Nor is the user readily able to distinguish an airport missing from https://gitlab.com/ninelima/kwikEFIS/-/blob/master/app/src/main/assets/waypoint/airport.gpx.xml from one simply too distant to find itself sorted into the nearest 1000.
This becomes problematic when the destination airport is not within the filtered list. For instance, from 1B9 to LEX is easily attainable in a single flight, but due to the distance LEX is filtered out of the destinations. (I would need to check to confirm program behavior, but since the cache is loaded at program start possibly the only way to use kwikEFIS to get to LEX is to restart the app once LEX is within range.)
Ideally, the program would give the user all airports, and then let the user decide for him/herself how many airports is appropriate in the cache. So long as the cache doesn't interfere with the smooth running of the program after start-up, then it seems reasonable to think most users will prefer to wait several seconds longer and in return have high confidence in the app.