[Feature] Allow user to load vATIS files from URL to support auto-update

[fcooper94]

I constantly see members in our division running ATIS files made for vATIS v1 and they never update their files, even when new updates are available. It would be great if you could load a vATIS file from a Github URL for example allowing the division to update the ATIS file remotely.

With a notification when the file has been updated.

[justinshannon]

I’m currently working on revamping vATIS. I have disclosed much about it, but I am considering some sort of “data admin” site that facility staff can use to create and modify ATIS profiles. This will allow vATIS users to easily download the ATIS profiles and they will automatically update with any changes.

[ml0130]

I’m currently working on revamping vATIS. I have disclosed much about it, but I am considering some sort of “data admin” site that facility staff can use to create and modify ATIS profiles. This will allow vATIS users to easily download the ATIS profiles and they will automatically update with any changes.

Are you looking at data admin like what vNAS has, where the day-to-day controller can't edit or make changes to their atis files?

[justinshannon]

I’m currently working on revamping vATIS. I have disclosed much about it, but I am considering some sort of “data admin” site that facility staff can use to create and modify ATIS profiles. This will allow vATIS users to easily download the ATIS profiles and they will automatically update with any changes.

Are you looking at data admin like what vNAS has, where the day-to-day controller can't edit or make changes to their atis files?

No, not necessarily. Maybe more of just a central repository? It would just be nice to have some sort of functionality to allow controllers to easily download and update their ATIS profiles without having to manually download them from their facility's website, similar to how CRC works in that regard.

If you have any suggestions, please feel free to share!

[ml0130]

Until then, the "data admin/repository" takes more shape. At this point, if the user already has a profile set up for a facility, they can locally upload it and choose what it keeps up to date within the file. For example, in most of the facilities I run, I have added additional NOTAMs and Conjugations, and those would be details that I wouldn't want to be overwritten when the facility decides to update.

Additionally, an interesting back-end functionality, at least for CRC/vNAS, is if, say, both CRC and ATIS are running and you install a new facility in CRC and Set up a profile for that facility, then ATIS starts downloading the respective files as well, if they are available.

Example: Take ZDV (Denver) once you install the CTR in CRC and you set up a profile for COS (Colorado Spring), Regardless of position, then ATIS auto downloads the ATIS Files for that facility

[fcooper94]

I’m currently working on revamping vATIS. I have disclosed much about it, but I am considering some sort of “data admin” site that facility staff can use to create and modify ATIS profiles. This will allow vATIS users to easily download the ATIS profiles and they will automatically update with any changes.

Excellent - Having a central repo is what we need.

[ml0130]

Until then, the "data admin/repository" takes more shape. At this point, if the user already has a profile set up for a facility, they can locally upload it and choose what it keeps up to date within the file. For example, in most of the facilities I run, I have added additional NOTAMs and Conjugations, and those would be details that I wouldn't want to be overwritten when the facility decides to update.

Additionally, an interesting back-end functionality, at least for CRC/vNAS, is if, say, both CRC and ATIS are running and you install a new facility in CRC and Set up a profile for that facility, then ATIS starts downloading the respective files as well, if they are available.

Example: Take ZDV (Denver) once you install the CTR in CRC and you set up a profile for COS (Colorado Spring), Regardless of position, then ATIS auto downloads the ATIS Files for that facility

To add to the last suggestion I had. If this data admin/database is followed through, this is more of a QoL addition from the user side, having ATIS files auto-sorted based on the CTR they fall into first.

For example, look below and have it sorted by CTR drop-down and then by alphabetical facility. Also, for the bigger Tracons like SCT NCT N90 A80 and a couple of others, you can work individual areas and consolidate that area into a drop-down for the overall terminal. I would say the only exception for this rule would be for the Consolidated Tracon since those would be most frequently use in the CTR. For example in LA have L30 and SCT listed alphabetically first then alphabetically list all other terminals.

ZAU-Chicago ARTCC
C90
Champaign Terminal
CID Terminal
Fort Wayne
Great Lakes West
Madison Terminal
MILWAUKE Terminal
ZDV-Denver ARTCC
D01
COS Terminal
CPR Terminal
ZLC-Salt Lake City ARTCC
Big Sky Terminal
ZNY-New York ARTCC
N90-New York Tracon
N90 CatSkil
N90 EWR
N90 ISP
N90 LGA
ABE TERMINAL
AVP TERMINAL
ELM Terminal
MDT/RDG Terminal