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

Login with username, password and session length
 


Author Topic: Inclusion of Hex Code File Within Radarbox  (Read 15129 times)

0 Members and 1 Guest are viewing this topic.

spotter70

  • Jr. Member
  • **
  • Posts: 65
Inclusion of Hex Code File Within Radarbox
« on: September 17, 2007, 11:36:39 AM »
Hello
I wish to know if there is going to be an Inclusion of a Hex code file within the Radarbox program???
As a spotter and logger the ability to log and see your perspective aircraft is Priority 1 as i am concerned.
I use a database program to log all my sightings its a commercial product readily available .
Is Airnav looking to tie up the Radarbox with an existing commercial product???
From what source and how does the Radarbox update the hex codes???
Regards
Spotter70


Allocator

  • RadarBox24.com Beta Testers
  • Hero Member
  • *
  • Posts: 3568
Re: Inclusion of Hex Code File Within Radarbox
« Reply #1 on: September 17, 2007, 12:05:47 PM »
Spotter70,

RadarBox uses the Gatwick Aviation Society (GAS) database for looking up the aircraft details when a new Mode S hex code is received.  If you click on an aircraft in the aircraft list that only has the hex code, you see the photos being downloaded and the aircraft details are inserted if the aircraft is in the GAS database.  However, the current Beta12 has the photo download disabled for testing, so the GAS database lookup is probably also disabled.

I'm not aware of a third-party comercial database tool that is compatible with RadarBox at the moment.

You can extract the log for yesterday and today in txt format from the MyReports option.  These txt files can be imported into MS Excel, but this is not a straightforward job.  You can view all aircraft received too, but there is no way of exporting the data at the moment.

I know that AirNav are aware that users such as you and me want to be able to see aircraft recieved in more detail and to be able to manipulate that data outside RadarBox.  I think that the current priority is to overcome the existing snags before moving on to the database issue.

spotter70

  • Jr. Member
  • **
  • Posts: 65
Re: Inclusion of Hex Code File Within Radarbox
« Reply #2 on: September 17, 2007, 03:25:15 PM »
The GAS Database is hardly up to date and if new Hex codes arrive or if they are incorrectly transmitted you have no way of knowing .
As a spotter the information has to be correct and visible.
It seems to me that at the moment the Rbox is of greater value to the People who track aircraft than those who log .
Because i log aircraft i see of my Rbox i do not track them my view is changing daily .Sbs-1 has in place the facilities and the commercial database .
Will Airnav look at this???
I apprieciate that Airnavs priority at the moment is to get the bugs out of the system and get a stable program for all its members and users.
But this requires a greater interest and further devolpment.
Regards
spotter70

Allocator

  • RadarBox24.com Beta Testers
  • Hero Member
  • *
  • Posts: 3568
Re: Inclusion of Hex Code File Within Radarbox
« Reply #3 on: September 17, 2007, 03:35:33 PM »
The GAS Database is hardly up to date .......

.Sbs-1 has in place the facilities and the commercial database .
Will Airnav look at this???


I've always used the GAS database with the SBS-1 using SBSPlotter - it's pretty much up to date as far as I'm concerned, but you may have more exacting standards.

Not sure what you mean about the SBS-1 commercial database.  The SBS-1 comes with no data in the database at all, all the records I have in BaseStation have been populated by SBSPopulate.  Basestation only records the Mode S Codes and position information, not aircraft details.

I agree that RadarBox needs better database data extraction and data manipulation, but as I said, AirNav are aware of this.
« Last Edit: September 17, 2007, 03:41:24 PM by Allocator »

spotter70

  • Jr. Member
  • **
  • Posts: 65
Re: Inclusion of Hex Code File Within Radarbox
« Reply #4 on: September 17, 2007, 03:58:38 PM »
At the moment when i log an aircraft off the Rbox Screen and then visibly see it
It then gets put into a Commercial Database specifcally designed for the logging of Aircraft.
There are 2 Commercial databases that i know of that facilitate that use but only on Sbs-1.
Are there any plans to make provision for this facility??
Or will it remain a flight tracking software program only??
Regards
Spotter70

AirNav Support

  • AirNav Systems
  • Hero Member
  • *****
  • Posts: 4127
Re: Inclusion of Hex Code File Within Radarbox
« Reply #5 on: September 17, 2007, 08:36:13 PM »
Hi spotter70,

What is it you exactly require. The GAS database is great so far and we see no reason to change it. You mention a commercial database but don't understand what you mean.

RadarBox 2007 does provide a output port so any developer can connect to this and any aircraft which is logged at that time they can then add it into there application or database. In terms of being able to extract information from the database we are looking into this.
Contact Customer/Technical support via:
http://www.airnavsystems.com/contact.html
[email protected]

spotter70

  • Jr. Member
  • **
  • Posts: 65
Re: Inclusion of Hex Code File Within Radarbox
« Reply #6 on: September 17, 2007, 09:08:31 PM »
Hello Airnav
There are subscription based Aviation databases out there on the market.
These facilitate in the logging process .As a sighting is made i enter it as a seen aircraft on the day i saw it and where i saw it .
Where Radarbox fits in is that it helps me locate aircraft either as a Trail or a Low pass into LCY as thats my Nearest Airport.
The Database program i use is ADU SOFTWARE.
There is another software product which is AVDB
Other Aviation enthusiasts out there probaly use a deriatve of their own probaly an Excel spreadsheet.
These Software programs are run by Aviation Enthusiasts with a string of Editors that are experts in certain field from Jet Aircraft to Biz-Prop and General Aviation including Mlitary.
As the world of aviation is changing all the time these people keep the databases updated at regular intervals from fleet changes to hex code changes to registrations being changed as aircraft move between airlines .
I hope this answers your question.
Also both the aformentioned database companies supply software that allows intergration with mode S but only for SBS-1 at the moment.

My question is the same is Radarbox going to go down the same route with modes S and A/b intergration or is it going to be a stand alone flight tracking software only????
Regards
Spotter70

AirNav Support

  • AirNav Systems
  • Hero Member
  • *****
  • Posts: 4127
Re: Inclusion of Hex Code File Within Radarbox
« Reply #7 on: September 17, 2007, 09:19:33 PM »
Hi spotter70,

Not fully sure what you are trying to say especially when you say is RadarBox only going to be a flight tracking software.

RadarBox 2007 uses its own centralised database which also gets queries from GAS. While it does not provide any support to pass on the hex codes to another company if they are not found, this can be done via external software using the data port or if they contact us we may be able to sort something out.

However as they subscription based we may not integrate with them as there could be costs involved which we do not want to pass on to our customers. Those database you mention have not been integrated by SBS but more like the those companies have created software for the SBS not the other way round.
Contact Customer/Technical support via:
http://www.airnavsystems.com/contact.html
[email protected]

spotter70

  • Jr. Member
  • **
  • Posts: 65
Re: Inclusion of Hex Code File Within Radarbox
« Reply #8 on: September 17, 2007, 09:30:23 PM »
People who have the logging databases or purchase this type of software already pay for the facility .
If you have the AVDB software intergrated within it is a program (snoopy) which they create and design to run along side the sbs-1.
ADU has its own software privately devolped to run alongside sbs-1


Can someone help me out her or am i not making my point clear enough.
Someone out there who has a logging program please me out .

Respectful regards
Spotter70

prbflight

  • Sr. Member
  • ****
  • Posts: 328
Re: Inclusion of Hex Code File Within Radarbox
« Reply #9 on: September 20, 2007, 12:40:51 AM »
I'm trying to get integration with AirNav Suite. 

I've been logging into the All Heard Management part of this program for over 4 years.  I would love to be able to import my RadarBox contacts, including 'heard' and 'seen' into All Heard Management but so far Airnav Support has not developed the software to do this.

I just keep hoping...


Paul

spotter70

  • Jr. Member
  • **
  • Posts: 65
Re: Inclusion of Hex Code File Within Radarbox
« Reply #10 on: September 20, 2007, 07:29:47 AM »
The thing is i am a spotter.
I log aircraft i see to complete fleet listings.
I was hoping that Radarbox would facilitate in this use.
Its plainly obvious that this software is designed to track aircraft from one destination to another.
I am only interesred in what i can see within a 50 mile radius.
The attraction for Radarbox was its size and portability .
If i go to an airport a quick setup and i can recieve traffic .
The GAS Hex code network is not 100% correct as it is run on a volunteer basis so if queries arrive they will take more time to be corrected .
Correct data is the absolute top priority.
Hex codes are being transmitted incorrectly all the time where the Aviation Databases come in (as long as you are a subscriber) is that queries will be dealt with quicker and correct information used.People that run such databases are on the case all the time specialist editors and so on.
so it looks like i will use my Sbs-1 until such time things change and Airnav look at this .
Regards to all members
Spotter70

b744

  • Full Member
  • ***
  • Posts: 147
Re: Inclusion of Hex Code File Within Radarbox
« Reply #11 on: September 20, 2007, 07:58:43 AM »
I fully understand your point regarding GAS and a bought and paid for program such as AVDB or ADU. I've been an SBS user for a couple of years and also use one of the data programs you mention but do not integrate it with SBS. These programs are as accurate/inaccurate as GAS so all have mistakes. For that reason I choose to check any tie ups being made by such systems and will manually enter data where I see fit. Takes a bit more time but means my system has what I want in it.
If you then join and contribute to online user groups such as Mode-s forum,you will get ACTUAL tie ups plus any logs sent in are scanned for mistakes and you can then correct them. I travel alot and the absolute rubish that some have for tie ups in Asia and South America is quite amazing. Without checking yourself you'll have a nice full database...with everybody elses errors and assumptions.
Also try Airframes.org which is very accurate.
This is why I'd like Airnav to make the database more easy to edit while the ARB is working. Try to edit it now and the data jumps around as the system uses it.
Just my take on the subject
Rgds

Question on the GAS populate...does it work for network flights and if so are they also written to the database ?
« Last Edit: September 20, 2007, 08:02:57 AM by b744 »

spotter70

  • Jr. Member
  • **
  • Posts: 65
Re: Inclusion of Hex Code File Within Radarbox
« Reply #12 on: September 20, 2007, 08:47:28 AM »
At last someone who understands
I agree the hex code business is a problem at times with incorrect tie ups.
I am on the verge of joining AVDB as the network tie ups queries are sorted out very quickly With the dedicated team that is in place.
I do use Airframes.org as well just in case.
Radarbox could have the same by having a fully functional editable database for sightings and record sessions.
Regards
spotter70

AirNav Support

  • AirNav Systems
  • Hero Member
  • *****
  • Posts: 4127
Re: Inclusion of Hex Code File Within Radarbox
« Reply #13 on: September 20, 2007, 05:47:31 PM »
GAS:

Yes it does work for network flight so those aircraft are added to the database (note that's the aircraft database not your MyLog Database)

We will be looking into making the database easier to maintain and understand your points about other databases. However at the moment we are sticking with GAS.

One important point to all customers:

While we want to include every request we receive this is not possible. Some require too much time to develop and  are only asked by one person while others may not actually be possible or cost too much. Or some may be detrimental to others.

As you can see from the beta one post we have already added a large amount of requests and will continue to do so. Please bear this in mind when requesting a development as we do not guarantee all will be done. This is not aimed at this post as this post has been interesting and does make valid points. 
Contact Customer/Technical support via:
http://www.airnavsystems.com/contact.html
[email protected]

Allocator

  • RadarBox24.com Beta Testers
  • Hero Member
  • *
  • Posts: 3568
Re: Inclusion of Hex Code File Within Radarbox
« Reply #14 on: September 20, 2007, 07:33:38 PM »
Try to edit it now and the data jumps around as the system uses it.

It's not very tidy, but you can stop the database jumping around to edit it by deselecting both "Process Hardware Flights" and "Get Flights From RadarBox Network" at the bottom of the two aircraft lists.

Of course, this does stop data reception, but at least the Database Explorer actually allows you to explore the database :-)