Jump to content

Cardin Pelletier

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Disregard. This has been previously talked about in another thread.
  2. Was wondering if you'd consider adding in functionality to the autotrack feature that would allow autotrack based on airspace configuration. For example, if a facility has an east and west departure position, have the eastbound departure from the primary airport be autotracked by the east departure controller and the west departures tracked by the west departure controller. Maybe autotrack based on scratchpad entry (utilizing the auto scratchpad for departures) or by allowing configuration of autotrack based on their filed DP or initial fix?
  3. This is what immediately came to mind as one of the challenges of having a controller client work in this manner. I would say, a vast majority of the time coordination would not be affected as most of the time we are dealing with the difference between a DAL123 and DELTA123. Regardless of whether the next controller sees "DELTA" or "DAL", we're both going to be on the same page. I'm not sure about how it would work with the SUPS either -- that's another thing. Having the system automatically correct an incorrectly-entered ACID based on squawk code and flight plan correlation sounds like a good
  4. My thoughts are that this is mainly a side-effect of users doing something they shouldn't. They shouldn't connect using callsigns with a hyphen, and they shouldn't connect using callsigns with invalid airline code prefixes. I suppose I could modify the clients so that if you [Mod - Happy Thoughts]ign a code with "QB UAL123" and then later a target appears with some other callsign (such as UNITED123) squawking the [Mod - Happy Thoughts]igned code, and that callsign (UNITED123) doesn't already have a code [Mod - Happy Thoughts]igned, it would grab UAL123's code and [Mod - Happy Thoughts]ign
  5. I have the same problem all of the time when using STARS or ERAM. An aircraft calls up, I attempt to [Mod - Happy Thoughts]ign a beacon code to that aircraft and, in the case of ERAM, I end up not acquiring the aircraft under the callsign I entered because the callsign I entered was different from that which the pilot signed on to the network with. This can get pretty tricky if, for example, you have a "UAL42" call up, but they've signed on to the network as "UNITED42." Or, a CFBDX call up who has signed on to the network as "C-FBDX". If you don't put the dash, you will not get a track. It sho
  6. I've got a GeoMaps.xml file from the FAA and I noticed that the way it is formatted is slightly different than what the XML file vERAM reads. Has anyone converted an FAA GeoMaps to work with vERAM? The file is huge, which makes it pretty comebersome to work with (it would be unfeasible to manually enter the data using the editor). Cheers, Cardin
  • Create New...