AirNav RadarBox
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 


Author Topic: V2.0 now supports Alphanumerical Callsigns  (Read 23252 times)

0 Members and 1 Guest are viewing this topic.

AirNav Development

  • AirNav Systems
  • Hero Member
  • *****
  • Posts: 2545
    • AirNav Systems
V2.0 now supports Alphanumerical Callsigns
« on: August 19, 2008, 10:06:00 PM »
We are happy to announce that we have just finished a change in our flight data server to enable alphanumerical callsigns to be properly decoded.

So from now on callsigns like EZY67HP will have their origin/destination retrieved from our server.

This is another feature requested by users and immediately developed by AirNav Systems.
Hope you enjoy it.

tarbat

  • ShipTrax Beta Testers
  • Hero Member
  • *
  • Posts: 4219
    • Radarbox at Easter Ross
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #1 on: August 19, 2008, 10:13:04 PM »
That's excellent news - well done in getting this working!!

Allocator

  • RadarBox24.com Beta Testers
  • Hero Member
  • *
  • Posts: 3568
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #2 on: August 19, 2008, 11:07:41 PM »
Yes, that seems to be working - note the last 2 autopopulated routes :-)


Deadcalm

  • Sr. Member
  • ****
  • Posts: 381
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #3 on: August 20, 2008, 08:14:24 AM »
Hello, Airnav.  A leap in the right direction - thanks.
However, how consistent is this change?  I only ask because, again, the majority don't show the route, including current Easyjet flights on screen at the moment:
EZY605F, EZY271L, and TCX535K, TCX269K, etc., etc...

DC
Go around, I say again go around...

Allocator

  • RadarBox24.com Beta Testers
  • Hero Member
  • *
  • Posts: 3568
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #4 on: August 20, 2008, 08:50:41 AM »
Give it time to autopopulate DC - it doesn't all happen at once.

tarbat

  • ShipTrax Beta Testers
  • Hero Member
  • *
  • Posts: 4219
    • Radarbox at Easter Ross
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #5 on: August 20, 2008, 09:33:52 AM »
Not sure which providers Airnav are now using for routes, but this might help explain some of the problems with dealing with alphanumeric callsigns (it's a statement by the author of FD6 that I forwarded on to Airnav last month):

"For info FlightAware does not carry Ryanair, Easyjet or the other non-US low cost carriers. FS & FC do carry most low cost carriers but FS will only accept FlightIDs where the flight number part of the code is numerical so FS will return a route for EZY6521 but it will not return a route for EZY37FN as 37FN is not numeric. FC will accept both EZY6521 & EZY37FN so depending on the lookup site and the format of the flightID you may or may not get a match."

From what I've seen Airnav are doing everything they can to get this working reliably for the myriad of callsign formats, and are now making significant progress.
« Last Edit: August 20, 2008, 09:35:55 AM by tarbat »

Allocator

  • RadarBox24.com Beta Testers
  • Hero Member
  • *
  • Posts: 3568
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #6 on: August 20, 2008, 09:47:32 AM »
Amongst other routes, I've got the following low-cost carrier routes autopopulated today:

EZY80FX EGGD EGPE
TCX104P EGKK EGCC
EZY18LM EGKK EGPH
RYN81LN EGGW EIKN

This is after a quick look at the routes table in Database Explorer, so it does look like they are being populated.

64 routes populated so far this morning :-)

« Last Edit: August 20, 2008, 09:50:24 AM by Allocator »

AirNav Support

  • AirNav Systems
  • Hero Member
  • *****
  • Posts: 4125
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #7 on: August 20, 2008, 11:41:34 AM »
They are being popuplated, but please remember sometimes our source data does not have all the flights. There isn't a magical database out there with all of them so some will be missing :) But this is the closest we can get at the moment.

Contact Customer/Technical support via:
http://www.airnavsystems.com/contact.html
[email protected]

CarlosAbreu

  • Hero Member
  • *****
  • Posts: 2763
  • The sky is not the limit
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #8 on: August 20, 2008, 12:26:59 PM »
This an excelent improvement for ANRB2009 however I would like to know if I can manually update flight codes.
I was using 1.5v with many routes manually updated, however due to a personal decision I decided to fully install the new ANRB version instead of the update because it gave me problems.
The new fully version works fine but after I looked the new route database I checked that many flights I had in my old one are missing.
I have a backup of my 1.5v data If you wish, under your instructions I can provide it for you to pick up missing flights.
These update flights were essencially from low costs and charters with origin/destination from Portugal and Spain and some cruise levels for North Africa an North/South America.

Brgds
CA
« Last Edit: August 20, 2008, 02:25:30 PM by CarlosAbreu »
Station: Primetec PGANRB100514
Antenna: Wimo GP-1090 (AS-1090/BT-1090)
Cable: Ecoflex 10 (15m)

Station: XRange2 PGANRB501386
Antenna: Airnav Systems
Cable: LBC240 00220M (15m)


Roadrunner

  • Hero Member
  • *****
  • Posts: 600
  • Aviation enthusiast since school visit to Heathrow
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #9 on: August 20, 2008, 01:06:46 PM »
Hi AirNav,

On a slightly different tack with route information. I note that the drop down lists available to select from or to airports for data use IATA 3 lettercodes but the data that is in the aircraft list and on the maps uses the ICAO 4 letter codes.

Would it be possible to have a choice as to whether IATA or ICAO codes are displayed in the list and on the maps.

Regards

AirNav Support

  • AirNav Systems
  • Hero Member
  • *****
  • Posts: 4125
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #10 on: August 20, 2008, 01:12:20 PM »
CarlosAbreu,

Contact support direct and we will see whether we can put those routes on the server. However as they won't be updated we probably need to look for a better start source.

You can update the route table if you like, the only difference now is that it has a date time stamp, if this is older than a month in then tries to get the route data again if is available.

Roadrunner,

Suggestion noted, although the drop down filter list can take both 3 and 4 code when entered manually.
« Last Edit: August 20, 2008, 02:26:55 PM by AirNav Support »
Contact Customer/Technical support via:
http://www.airnavsystems.com/contact.html
[email protected]

tarbat

  • ShipTrax Beta Testers
  • Hero Member
  • *
  • Posts: 4219
    • Radarbox at Easter Ross
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #11 on: August 20, 2008, 03:16:56 PM »
You can update the route table if you like, the only difference now is that it has a date time stamp, if this is older than a month in then tries to get the route data again if is available.

Can you please confirm how it handles all the routes that have NULL in the CH (date/timestamp) field.  Do these expire immediately?

AirNav Support

  • AirNav Systems
  • Hero Member
  • *****
  • Posts: 4125
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #12 on: August 20, 2008, 03:35:37 PM »
Yes, however expire is not a nice word.

They don't get removed from the database unless there is route in the online database.
Contact Customer/Technical support via:
http://www.airnavsystems.com/contact.html
[email protected]

CarlosAbreu

  • Hero Member
  • *****
  • Posts: 2763
  • The sky is not the limit
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #13 on: August 21, 2008, 09:44:09 AM »
I have already contact Airnav Support and now waiting for a reply, however I would like to know if I must introduce a date value in the field CH on the manual updates.

Brgds
CA
Station: Primetec PGANRB100514
Antenna: Wimo GP-1090 (AS-1090/BT-1090)
Cable: Ecoflex 10 (15m)

Station: XRange2 PGANRB501386
Antenna: Airnav Systems
Cable: LBC240 00220M (15m)


tarbat

  • ShipTrax Beta Testers
  • Hero Member
  • *
  • Posts: 4219
    • Radarbox at Easter Ross
Re: V2.0 now supports Alphanumerical Callsigns
« Reply #14 on: August 21, 2008, 09:56:27 AM »
I have already contact Airnav Support and now waiting for a reply, however I would like to know if I must introduce a date value in the field CH on the manual updates.

Yes, I'd be interested in the "official" answer to this as well.  In the meantime, I've been using a date/timestamp (today) of "20080821000000".