Flight Number Generation - Routes

[AirNav Support]

Hi all,

Seems a lot of the posts at the moment are about Routes in RadarBox and why are they are not updated while there other applications which can do this.

Firstly its very difficult to have database with all the routes of the world as they change so much and very often. Having said that the one in RadarBox has over 100,000+ records.
Maintaining that is impossible task.

You have may have come across other applications which are generating the routes once they are caught and you have asked us why we can't do the same:

A lot of these programs are using a technique where they poll certain web flight tracker sites for the Flight Number and once they find a result they get the route details back and save it.

This is not a nice technique for a software to do as these sites make money via adverts so polling a website like this is not liked by the tracking company as you are getting the information for free. If we were to do this without permission of various companies (you will need a few to get a good number of results) we could get into some legal difficulty.

We will be looking into alernate ways however this is difficult task either way to have a world route database.

Hope that gives you a insight.

[Allocator]

If anybody wants to play with the routes I've gathered using PlanePlotter and Flight Display 6 for the central UK, then I'll make the file available.

However, you will either have to add these routes manually, or will need to know how to import them to the NavData.db3 database as described by tarbat - easy when you know how, but has the potential to go horribly wrong :-0

Here is a small section of the csv file - note the capture of Flight ID's with letters after the numbers.  EZY24 might already be in the RadarBox flight database, but EZY24LC certainly won't be, even though the route is the same as for EZY24

"EZY24LC","EGGW","EGPD"
"EZY265","EGSS","EGAA"
"EZY26QD","EGSS","EGAA"
"EZY27AJ","EGKK","EGAA"
"EZY27VE","EGSS","EGPF"
"EZY28EJ","EGKK","EGAA"
"EZY28ZF","EGSS","EGPH"
"EZY2LN","EGGD","EGAA"
"EZY302T","LSGG","EGGP"
"EZY305K","EGGP","LSGG"
"EZY3075","EGSS","LEAS"
"EZY309U","EGGP","LSGG"
"EZY31WB","EGGW","EGPH"
"EZY32HL","EGKK","EGPF"

I've captured 788 routes so far, but the majority of these will already be in the RadarBox database.

[steveb25]

Allocator

I would be very interested in a copy of your list

[Really]

If anybody wants to play with the routes I've gathered using PlanePlotter and Flight Display 6 for the central UK, then I'll make the file available.

I would love a copy too if that's ok?

Cheers

[Allocator]

I'll try and get it uploaded and post the address tonight.

Allocator

[Allocator]

Here it is:

http://www.ruyton.demon.co.uk/Downloads/data.csv

[Really]

Here it is:

http://www.ruyton.demon.co.uk/Downloads/data.csv

Thank you

[steveb25]

Allocator

a big thank you from myself also

[Roadrunner]

Maybe an enhancement for the next update of RB. Be able to import lists of flight numbers and details direct into the NavData.db3, in a simlilar fashion to importing .SQB files from SBS1 to RB ? ? ?

[Bigyun2000]

Allocator

Thanks.  Can this csv file be imported to the database for RadarBox please?

Thanks

[tarbat]

The problem with sharing routes is that they soon get out of date.  I set FD6 to auto-expire routes after one month.

If anyone wants my 1500+ routes gathered over the last week using FD6, it's attached.  You'll need to use something like SQLite Maestro to import these into the routes table.  Suggest you use the "update or insert" option when importing, to overwrite the out-of-date routes that are already in the routes table, and use FN as the KEY.

In fact, I do an "insert" daily, because it's quick.  And then weekly, I do an "update or insert".

One warning, if you don't understand these instructions, then don't use them, you can seriously mess-up your NavData database.

[attachment deleted by admin]

[Bigyun2000]

tarbat

Thanks for the info.  How about an idiot guide :)

I guess its best to backup the NavData file before hand.