Task import
| Platform | Status | Where |
|---|---|---|
| iOS | done | vulture-ios/Packages/TaskScreens/Sources/TaskScreens/ImportTasksvulture-ios/Packages/CompetitionScreens/Sources/CompetitionScreens/SoaringSpotvulture-ios/Packages/WeGlide/Sources/WeGlide/Requests/WeGlideTaskRequest.swift |
| Android | done | vulture-android/feature/taskmapvulture-android/data/weglidevulture-android/data/soaringspot |
| Web | done | vulture-web/app/api/soaring_spot_tasks.rb |
Behaviour
Section titled “Behaviour”- WeGlide: pick one of your own WeGlide tasks or enter a task ID.
- Competition: take a Soaring Spot day’s task (AAT, AST, Bailleau and the British variants, parsed by the Vulture backend).
- A task from a service keeps its source (
externalURL,externalVersion), so Update fetches the new version when the day’s task changes. - Tasks inside a CUP waypoint file are imported with the file.
Platform differences
Section titled “Platform differences”- Android opens WeGlide and Soaring Spot tasks on the read-only task map and can save and update them. Picking from your own WeGlide task list is not verified on Android.
- iOS keeps an analytics event for uploading a task to WeGlide (
uploadTaskFromTaskListToWeGlide), but no task upload request exists inPackages/WeGlide, so that upload looks unbuilt. Not verified further.