Page 3 of 7
Re: Integrated ATIS for Pilotedge
Posted: Thu Nov 09, 2017 9:01 pm
by Matthias Geiss
kullery wrote:
In many places (especially within ZLA) the “nearest airport” would be the wrong airport when picking up the arrival ATIS. I experimented wih something like that when I attempted to build a web page that would “auto select” the ATIS based on your reported position.
That's a problem, of course, it would only work fine for the departure airport...
Another idea then: We could introduce three frequencies:
1. Nearest airport for checking the departure ATIS and for updates enroute
2. Arrival airport
3. Alternate airport
2. and 3. would of course require that the pilot has filed a flight plan.
Re: Integrated ATIS for Pilotedge
Posted: Mon Jan 15, 2018 11:49 pm
by sono
Is there any further thoughts on an ETA for feature improvement in this area.
For me it is the only weakness of the system..
thank you.
Re: Integrated ATIS for Pilotedge
Posted: Tue Jan 16, 2018 10:53 am
by Keith Smith
Not at the moment. I'll advise when I'm able to work on it. There is one significant technical challenge to overcome.
Re: Integrated ATIS for Pilotedge
Posted: Fri Jan 19, 2018 7:18 am
by uncertifiedpilot
+1
Re: Integrated ATIS for Pilotedge
Posted: Fri Jan 19, 2018 9:24 am
by onevim
+1
Re: Integrated ATIS for Pilotedge
Posted: Sat Feb 03, 2018 4:38 pm
by Frank White
I'm stumbling through threads that captures my interest. Just wondering if the development Roadmap is public and published somewhere?
VERBOSE stuff (that you might as well skip):
The answer about the Roadmap is probably posted in another thread but I if don't ask hear and now, I'll get distracted and forget to look.
Frank,
Pilot wannabe (sigh)
Re: Integrated ATIS for Pilotedge
Posted: Mon Feb 05, 2018 7:32 am
by Keith Smith
Matthias Geiss wrote:kullery wrote:
In many places (especially within ZLA) the “nearest airport” would be the wrong airport when picking up the arrival ATIS. I experimented wih something like that when I attempted to build a web page that would “auto select” the ATIS based on your reported position.
That's a problem, of course, it would only work fine for the departure airport...
Another idea then: We could introduce three frequencies:
1. Nearest airport for checking the departure ATIS and for updates enroute
2. Arrival airport
3. Alternate airport
2. and 3. would of course require that the pilot has filed a flight plan.
There is 0% chance of introducing an ATIS system that involves the use of frequencies other than the ones published for the airport. Similarly, 0% chance of implementing a system that requires the user to file a flight plan when wouldn't be required in real life. The idea of PilotEdge is to reinforce real world procedures, not to introduce new ones.
Re: Integrated ATIS for Pilotedge
Posted: Mon Feb 05, 2018 7:34 am
by Keith Smith
Frank, we published a road map for the addition of airports to the Western US service area, but not for the software development side of the house. This is intentional, and it's not because we like to be mysterious.
Re: Integrated ATIS for Pilotedge
Posted: Mon Feb 05, 2018 1:56 pm
by Frank White
Okay. I'd asked because of the many developmental nuggets you've dropped. Thanks!
PS. keep the nuggets coming...
Re: Integrated ATIS for Pilotedge
Posted: Tue Feb 06, 2018 10:15 pm
by Matthias Geiss
Keith Smith wrote:
There is 0% chance of introducing an ATIS system that involves the use of frequencies other than the ones published for the airport. Similarly, 0% chance of implementing a system that requires the user to file a flight plan when wouldn't be required in real life.
Copied, fair enough.
Keith Smith wrote:The idea of PilotEdge is to reinforce real world procedures
Sounds not too bad, I should try it some time!