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

Login with username, password and session length
 


Author Topic: Database Update Requests  (Read 832536 times)

0 Members and 1 Guest are viewing this topic.

Chris11

  • Hero Member
  • *****
  • Posts: 1052
Re: Database Update Requests
« Reply #300 on: December 06, 2010, 08:16:30 PM »
Looks like it - deleted A320C9 off my local database and it popped up again with the same corruption - B350

Chris11

  • Hero Member
  • *****
  • Posts: 1052
Re: Database Update Requests
« Reply #301 on: December 07, 2010, 01:35:59 AM »
Not populating 4249AB Flight ID UTABIC

ACW367

  • Guest
Re: Database Update Requests
« Reply #302 on: December 07, 2010, 03:45:25 AM »
Not populating 4249AB Flight ID UTABIC

Appears to be B734 VQ-BIC on delivery ex OK-FGS (28478/3132)

ACW367

  • Guest
Re: Database Update Requests
« Reply #303 on: December 07, 2010, 05:27:19 AM »
Looks like it - deleted A320C9 off my local database and it popped up again with the same corruption - B350

Chris - that will occur until Airnav fix the bugs.  I do not know when this fix will occur as it is now over two months since Airnav communicated with us updaters on this.  

Any data that appears in your Navdata in the fields AT, PT,PT2,LK and LK2 does NOT currently come from our updating team.  From what I understand and Airnav can clarify, is that the photos are still individually interrogated by each user direct with Airliners net. The AT field still reaches back to the old 2 year out of date Navdata, and if it can't find an entry on that Navdata info held on the airnav server it tries to formulate a code utilising the information in the AN long name field.  

In our updater for every record, we have correct ICAO codes and photo links, but our database is just not interrogated for these fields during a user update. Until Airnav provide the necessary fixes, the only fields that the Airnav server successfully interrogates and pulls from our work is the AR, AN,AC and CN.  Therefore until Airnav fix the bugs, these are the only fields that you need to report anomalies to us.

We know this has become very annoying but it is completely outwith the control of the updating team and in the hands of Airnav Dev.

-------------------

To confirm the following is what we have had for N300R in our DB for a number of months

MS A320C9

AR N300R

CN 50500031

AT E55P (due to bug your navdata will reachback to original Airnav data, which for this airframe is from previously registered B350. Our DB is currently not interrogated for this field).

AN Embraer EMB 505 Phenom 300

AC Twin Palms II LLc

The PT and LK fields remain empty as there have been no photos uploaded to Airliners Net.

--------------------

Another example that I know has caused users consternation. French Sentry with tail number 202

In our DB since edited by updaters in the Summer as follows:

MS 3B77DC

AR 202

CN 24116/1003

AT E3CF (due to bug navdata will reachback to original Airnav data, however as this code was correct as E3CF on the original 2 year old Navdata, users should still receive this code.  But it was not sourced from the updater info)

AN Boeing E-3F Sentry

AC France - Air Force

PT Pablo Ignacio Blanco [BUT SEE NOTE BELOW]

LK http://www.airliners.net/photo/France---Air/Boeing-E-3F-Sentry/1504088/L/ [BUT SEE NOTE BELOW]

PT2 Ricardo Aysa Calahorra [BUT SEE NOTE BELOW]

LK2 http://www.airliners.net/photo/France---Air/Boeing-E-3F-Sentry/1525519/L/ [BUT SEE NOTE BELOW]

NOTE Due to bug, the PT and LK fields are not sourced from the updater DB. On receiving the aircraft the bug means users boxes will individually interrogate ANet for photos using the old Airnav modus of searching for the most popular picture for that tail number.  Consequently despite the update team having correct photo links for the Sentry, users may get pictures of an Antonov scrapped in the 1990s or a Mirage gate guardian.

Hope this all helps clarify what you get from us and what gets corrupted or incorrectly downloaded due to long standing bugs.

Regards ACW367
« Last Edit: December 07, 2010, 11:23:53 AM by ACW367 »

ACW367

  • Guest
Re: Database Update Requests
« Reply #304 on: December 07, 2010, 05:45:20 AM »
To further clarify, on our updater we have the ability to provide the LK fields with the 'photo not available' holding JPEG when a registration is re-used by authorities, with new aircraft currently registered with a registration, but ANet only has links for pictures of an older aircraft that previously used that same tail number.  The idea being that as new photos for the currently registered aircraft are uploaded to ANet, we can change that holding placard to the correct link to the picture of the new airframe.  

An example would be M-ARIE. It is on our DB with full details for the currently registered PC-12.  However previously the registration was carried on a Challenger.  ANet only has a photo of the Challenger, no pictures of the PC-12 have yet been uploaded.  As us updaters would not want users to recieve the picture of the Challenger, our DB is set up so that users could get the holding 'photo not available' JPEG instead.  Once a PC-12 pic is put on ANet we could change the link in our DB from the holding JPEG to the ANet PC-12 link, enabling users to recieve only the correct new picture of the currently registered airfram.  

However the bug means our DB is not interrogated for these fields, so no matter what we have entered, users boxes will still individually interrogate ANet and get the previously registered Challenger pic.

Hope that also makes sense.

Regards
ACW367

AirNav Support

  • AirNav Systems
  • Hero Member
  • *****
  • Posts: 4124
Re: Database Update Requests
« Reply #305 on: December 07, 2010, 09:41:00 AM »
Just a note about the bugs.

This is being worked on and we apologise once again for the delay, as you are probally aware there a few products which are being worked on at the moment.

We are hoping all these of including the bug fixes will be ready in the next couple of months.
Contact Customer/Technical support via:
http://www.airnavsystems.com/contact.html
[email protected]

Chris11

  • Hero Member
  • *****
  • Posts: 1052
Re: Database Update Requests
« Reply #306 on: December 07, 2010, 10:48:05 AM »
ACW367 - thanks for that detailed explanation.  I am most appreciative of the work being done by the updating team. The number of aircraft that do not populate has reduced dramatically and tends to be new aircraft or re-registrations. There are also some gaps with Indian aircraft.

ANav - surely some of these bugs should be easy to fix, and some must have been fixed - is it not possible for an interim release. There is no need for the big bank approach.

The modern method of software release (perfected by Microsoft) is to release something with big holes and then issue minor bug fixes on a regular basis.

Runway 31

  • Moderator
  • Hero Member
  • *****
  • Posts: 33508
Re: Database Update Requests
« Reply #307 on: December 07, 2010, 11:08:09 AM »
Chris, I think you will find that the Indian gaps have been plugged to a large extent but as always, if anyone finds something unknown let us know and we will find it if possible and include it in the database, same with any corrections that you find to be required.

knight01

  • Sr. Member
  • ****
  • Posts: 298
Re: Database Update Requests
« Reply #308 on: December 07, 2010, 11:47:37 AM »
Hi,
These two have no info: 343541, 4249BB

Runway 31

  • Moderator
  • Hero Member
  • *****
  • Posts: 33508
Re: Database Update Requests
« Reply #309 on: December 07, 2010, 12:49:55 PM »
343511 = EC-LII Eclipse Aviation EA 500 c/n 000184, Jet Ready Europe
4249BB - VQ-BIJ Dassault Falcon 2000LX, c/n 214 operator unknown.

Both into Luton from mode-s forum.

Alan
« Last Edit: December 07, 2010, 01:25:45 PM by Runway 31 »

54901 - Jim

  • Hero Member
  • *****
  • Posts: 566
    • N9JHB.com
Re: Database Update Requests
« Reply #310 on: December 07, 2010, 01:41:46 PM »
Missing from this morning's log -->

A21CEA / N235UW / Eurocopter Deutschland GMBH EC 135 T2+ / CFS Air LLC / 0548

Thanks!
KOSH - Oshkosh, Wisconsin USA

Runway 31

  • Moderator
  • Hero Member
  • *****
  • Posts: 33508
Re: Database Update Requests
« Reply #311 on: December 07, 2010, 01:47:09 PM »
Thanks Jim, its operated by the UW Med Flight.

Alan

54901 - Jim

  • Hero Member
  • *****
  • Posts: 566
    • N9JHB.com
Re: Database Update Requests
« Reply #312 on: December 07, 2010, 01:56:23 PM »
This just appeared -->

A9AC28 / N722NB / Hawker Beechcraft 390 Premier 1 / Cool Stream LLC / RB-280

Thanks!
KOSH - Oshkosh, Wisconsin USA

Runway 31

  • Moderator
  • Hero Member
  • *****
  • Posts: 33508
Re: Database Update Requests
« Reply #313 on: December 07, 2010, 02:08:37 PM »
Its already in the d/b Jim, thanks anyway.

Alan

Chris11

  • Hero Member
  • *****
  • Posts: 1052
Re: Database Update Requests
« Reply #314 on: December 07, 2010, 03:43:55 PM »
343559 PT-XUG - fields AN and AC blank - is this the bug?