Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Foreflight import should support tail number as an optional column for easier sim import, should map out/in to block instead of engine, add TimeOff TimeOn for flight times #1308

Closed
ericberman opened this issue Sep 15, 2024 · 1 comment

Comments

@ericberman
Copy link
Owner

No description provided.

@ericberman
Copy link
Owner Author

E.g., you could put the "SIMxxxx" tail numbers in and have them import correctly.

@ericberman ericberman changed the title Foreflight import should support tail number as an optional column for easier sim import Foreflight import should support tail number as an optional column for easier sim import, should map out/in to block instead of engine Sep 17, 2024
@ericberman ericberman changed the title Foreflight import should support tail number as an optional column for easier sim import, should map out/in to block instead of engine Foreflight import should support tail number as an optional column for easier sim import, should map out/in to block instead of engine, add TimeOff TimeOn for flight times Sep 17, 2024
ericberman added a commit that referenced this issue Sep 17, 2024
 - Add TailNum as a synonym for AircraftID
 - Map out/in to block time instead of engine.
 - Map on/off to flight start/stop
 - Move three static regex expressions into lazy-load RegexUtility
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant