Search the Community
Showing results for tags 'vatspy'.
Hi all, for those of you who are still or again using Qutescoop (this is a link) or who are interested in testing it, download this version . For the time being you also have to install a local proxy-tool to convert VATSIM data from the new format to Qutescoop's legacy format, download the tiny software from Github. We have updated the airspace data of almost the entire world. You will be able to see almost all CTR and FSS stations displayed correctly. You never heard about Qutescoop? It's an old, but really good program, that will show you the current status of ATC and pilots at VATSIM in both graphical, but also in tabular way. You can search, list and display ATC bookings from VATBOOK. You can search for flightplan routes from vroute and then display them on the map. Here are two sample screenshots taken moments ago: By clicking onto one of the ATC station labels you can retrieve all the information about this controller. Zoomed into the London area to check who is online where and responsible for what airspace. It should be rather accurate, at least according to the data sources that I have used. See next chapter for more information on this. Data Sources Most airspace data have been copied and converted from the VatSpy Client Data Update Project. While doing so, I realized that its data is also not 100% accurate in some areas of the world which forced me to download, examine and convert current sector files of vACCs from around the world which was quite time consuming. It would be great if all vACCs would regularly propagate airspace data to the VatSpy Client Data Update Project if they make significant changes. Download Note: You can omit this step if you just newly downloaded and installed Qutescoop! To update an existing installation of Qutescoop: proceed to Qutescoop's GitHub-page, enter the Data-directory and download the following 3 .dat-files: firlist.dat firdisplay.dat airports.dat You may also download all the other .dat-files from this directory and update your own set as described in the next paragraph. Make a backup of the existing files before. Installation proceed to the AppData directory where Qutescoop is storing its basic data. In Windows by default this is C:\Users\UserName\AppData\Local\QuteScoop\QuteScoop\data to make it easy, create a backup of the entire \data\ directory, just in case something goes terribly wrong move the 3 .dat-files that you just downloaded into the \data\ directory. Replace the existing files with the new files Known Issues There are some minor technical limitations of Qutescoop that we cannot correct at this time. Before I will explain them briefly, the good news is that some of the old developers of Qutescoop are again around and may improve the product, personal time and motivation permitting. Qutescoop only looks at the "prefixes" of CTR and FSS stations, but it does not consider the type of station at all. For example, in the Azores there's both LPPO_CTR and LPPO_FSS. The CTR station is a radar control station that is responsible for the islands and TMAs around them, while the FSS station is a non-radar position that controls the entire Oceanic airspace of "Santa Maria". Qutescoop cannot make a difference between LPPO_CTR and LPPO_FSS and will display the airspace of the first one, regardless whether CTR or FSS is actually online. I have resorted to giving priority to the FSS station. As a consequence you have to make sure that you have a look at who is actually online LPPO_CTR or LPPO_FSS (or both). Whatever LPPO station will be online, Qutescoop will be showing the greater of the two airspaces (LPPO_FSS). This is how the sector data looks like with a SectorViewer Tool from DLMN: The same is happening in Canada at CZQX: CTR (domestic) vs. FSS (Oceanic). In this case I have given priority to the CTR station that usually covers both the domestic airspace of Gander (CZQX_CTR) and Moncton (CZQM_CTR). The consequence is now that even if CZQX_FSS is online, Qutescoop will show the combined domestic airspace of CZQX_CTR, not the Oceanic airspace. Again: you have to click on the label of the station and check whether it is actually CZQX_CTR or CZQX_FSS: If you think that it would be better to give priority to FSS over CTR, let me know and I can change it - or you can also change it yourself. AIRAC NavData Updates If you would like to update Qutescoop's NavData, you'll need to download current data for X-Plane 10 (not X-Plane 11!). Qutescoop stores NavData in your main program path: Drive:\xxxxxxx\qutescoop\Resources\default data Extract the files into this directory, you will need earth_awy.dat, earth_fix.dat and earth_nav.dat. Feedback If you spot mistakes, errors or inaccurate airspace data, comment here below and I will try to improve it. If you would like to participate in up keeping the data, let me know - help will always be welcome. Serious offers only, please. Enjoy! Changelog: 29 NOV 2020: own update file removed, link to GitHub inserted, new update instructions inserted 20 JUL 2020: updated airports.dat and new London LTC-sectors 30 JUN 2020: added NavData update instructions
Dear all, If you would like to display the latest information in Korea, please download it from the GitHub (https://github.com/vatsimnetwork/vatspy-data-project) ! You can easily find Korea information in FIRBoundaries.dat with Ctrl + F. The information in Korea is from RKRR to RKDA-C. (RKRR, RKRR-N, RKRR-S, RKDA, RKDA-E, RKDA-C) And it can also be easily found in VATSpy.dat with Cril + F. The information in Korea is from RKJB to RKXX. If you have any question, please fell free to write it in the comments. Thank you. Best regards, VATKOR7B, Hwayong Lee Deputy Event Director, VATSIM Korea Division