Daneel Polakoff Posted August 23, 2020 at 01:14 AM Posted August 23, 2020 at 01:14 AM Hello, I am the FE at PCF (we cover ZAN, HCF, and ZUA) and I was recently attempting to add the ZAN Oceanic Sector (ZAP) to our file. The ZAP boundary crosses over the international date line and creates a strange result. The boundary on the other side of the date line is moved very far away from its intended location. I understand this a very unique issue but I was wondering if there was any fix for this or any possible solutions to make the file work. (Picture is taken in VRC so I can zoom out to show the problem, issue is the same in vERAM) Thanks, Daneel Polakoff PCF FE Link to comment Share on other sites More sharing options...
Ross Carlson Posted August 23, 2020 at 01:31 AM Posted August 23, 2020 at 01:31 AM I'm not 100% sure this will work, but could you try subtracting 360 from the longitude values for those points that are on the other side of the IDL? Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Daneel Polakoff Posted August 23, 2020 at 02:00 AM Author Posted August 23, 2020 at 02:00 AM Amazing! It worked, thanks for the help! Link to comment Share on other sites More sharing options...
Daneel Polakoff Posted August 23, 2020 at 05:28 AM Author Posted August 23, 2020 at 05:28 AM Hello Ross, I have continued to develop the sector file. Although the file might work across the IDL, the traffic on VATSIM does not. The traffic appear where the boundary used to. Is there a fix to this? I would assume not. Link to comment Share on other sites More sharing options...
Ross Carlson Posted August 23, 2020 at 05:48 AM Posted August 23, 2020 at 05:48 AM Nope, no fix for that. I'm not sure what other facilities near the IDL do, but one possibility is to open another window centered on the other side of the line. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Kyle Sanders Posted November 1, 2020 at 02:24 AM Posted November 1, 2020 at 02:24 AM Daneel, Nikolas Boling and I are working on a Script to fix this. We have it done already but just piecing it all together. It will automatically and accurately handle East longs (at least in VRC). At the time of this comment, I am waiting to hear back if a W180.00.00.001+ coordinate will be accepted by vERAM. If so, then we are good to go and will be putting an .exe or something together to get these coordinates converted. Watch this project for updates: https://github.com/KSanders7070/NASR_2_SCT Kyle SandersVATUSA ZLC ARTCC Link to comment Share on other sites More sharing options...
Ross Carlson Posted November 1, 2020 at 04:20 AM Posted November 1, 2020 at 04:20 AM 1 hour ago, Kyle Sanders said: Nikolas Boling and I are working on a Script to fix this. Kyle, it sounds like you're referring to a script to convert coordinates in a sector file or video map. Daneel has already done that. The issue is that radar data coming in from the VATSIM server would need to be similarly converted so that the traffic appears on the correct side of the antimeridian. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Dominic Nguyen Posted November 5, 2020 at 03:09 PM Posted November 5, 2020 at 03:09 PM Useful, nonetheless for those who wants to maintain or develop sector files. The last time I tried to manually convert them by just adding the amount of degrees to the other side of the IDL, it turned out like this.... Link to comment Share on other sites More sharing options...
Recommended Posts