Artyom Maslyonkin 1099699 Posted March 14, 2011 at 07:42 PM Posted March 14, 2011 at 07:42 PM Hello! I have a proposal to insert an automatical count for magnetic declination to ES-client. It may be usefull for control big sectors, different FSS, where declination may change from point to point for several degrees and its not comfortable because controller see different planes flying with different degrees.. I have a fortran program which automatically counts declination depends on coordinates of point. This program could even work as selfmodule. Link to comment Share on other sites More sharing options...
David Zhong Posted March 15, 2011 at 08:30 AM Posted March 15, 2011 at 08:30 AM Many (real world) area control centres will simply orientate system maps to true north to avoid this problem. If vectoring is required, controllers would use a relative heading rather than a specific heading (e.g., "ABC123, for separation, turn left 30 degrees, report new heading" "Left 30 degrees onto heading 324, ABC123") David Zhong Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted March 15, 2011 at 10:06 AM Posted March 15, 2011 at 10:06 AM I'm not sure a multiple magnetic variation can be used in one sector, you would have to distortions on the screen. The best solution I see is to use a average variation for the entire sector. EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Jean-Frederik Dion 819740 Posted March 15, 2011 at 09:09 PM Posted March 15, 2011 at 09:09 PM In Canadian systems (NARDS, RSiT, CSiT and GSiT), such variation calculation is done on each and every panning. You can actually see the rotation occur if centering the map on a far away point. Coupled with a more realistic map projection this feature would give us a professional grade software for sure. Artyom, how big is the database which holds the variation info? And how often does the data get updated? Can you tell us what source is used? Jean-Frederik Dion VATCAN10 - CZUL Chief EuroScope Beta Tester / Board of Designers GVCCS Beta Tester Link to comment Share on other sites More sharing options...
Jonas Eberle Posted March 19, 2011 at 12:54 PM Posted March 19, 2011 at 12:54 PM Problem is, it is not in the .sct/.sct2 file format so another approach would have to be taken. Link to comment Share on other sites More sharing options...
Jean-Frederik Dion 819740 Posted March 24, 2011 at 06:24 PM Posted March 24, 2011 at 06:24 PM Artyom? Jean-Frederik Dion VATCAN10 - CZUL Chief EuroScope Beta Tester / Board of Designers GVCCS Beta Tester Link to comment Share on other sites More sharing options...
Ross Carlson Posted March 24, 2011 at 06:44 PM Posted March 24, 2011 at 06:44 PM Problem is, it is not in the .sct/.sct2 file format so another approach would have to be taken. The sector file format is just lat/lon .... the magnetic variation has no impact on that. The same sector file data could be used, it would just have to be rotated on screen by a different amount depending on where the scope is centered. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Jonas Eberle Posted March 27, 2011 at 08:57 PM Posted March 27, 2011 at 08:57 PM Problem is, it is not in the .sct/.sct2 file format so another approach would have to be taken. The sector file format is just lat/lon .... the magnetic variation has no impact on that. The same sector file data could be used, it would just have to be rotated on screen by a different amount depending on where the scope is centered. Yes, that's how I meant it: Don't count on sector files because they won't help. You need to choose another approach. Sector files don't stop you from implementing it somehow different, but they won't help. Link to comment Share on other sites More sharing options...
Recommended Posts