Skip to content

Skywatch.brief: support multi-leg routes (route: [...]) #18

Description

@jayrav13

Deferred from the v1 sprint that shipped `from:` / `to:` route input (#5).

The v1 route brief takes a single leg (origin → destination). For real flight planning, a route is often multi-leg (e.g., KCDW → fix → KACK), and the enroute corridor should follow the multi-segment great-circle path through every waypoint.

Acceptance: `Skywatch.brief(route: ["KCDW", "X1", "KACK"], departing_at: ...)` returns a Brief whose enroute slot reflects the union of all leg corridors and whose destination_forecast targets the final waypoint.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions