Database Update Requests

[DaveReid]

Unless they manually update the data now that the information is available.

Hopefully you're not really suggesting that the many thousands of RadarBox users are all supposed to be monitoring this thread, capturing updates and entering them one at a time into their DB Explorer, all because AirNav can't get their act together and ship an updated database ?

[Runway 31]

Do you update your database Dave?  I update mine as do many others.

Even after the new navdata is released, updates will be required, aircraft come and go all the time are you really suggesting owners do nothing to update their boxes.

[DaveReid]

Do you update your database Dave?  I update mine as do many others.

No argument there.

Even after the new navdata is released

That's precisely my point, there is still no sign of it, and no way for users to know how much longer they're going to be left to their own devices.

[Hawkeye]

In reply#356 Alan asks:-

"Do you update your database Dave?  I update mine as do many others.

Even after the new navdata is released, updates will be required, aircraft come and go all the time are you really suggesting owners do nothing to update their boxes"

After all the sterling work you and the others are doing with updates, surely it is not too much to expect AirNav to regularly release updates. I wouldn't have thought once a month would take too much effort or would be too much to ask seeing as the data gathering and revisions to the 'Master Database 'has been done for them. 
Presumably you undertook the task expecting this to happen, otherwise what's the point of the exercise. Individual users have always been able to do tie ups through Airframes  to update their own data anyway if they were capable of doing so.

Just another point Alan, and I'm not at all being critical or pedantic. There seems to be a mix up between 62-3582 and 62-3852. I assume it's just a typo and it is -3582 you've done the entry for.

Keep up the good work, hopefully we'll all benefit from it eventually.

Oh, and just as a matter of interest, (or not,) 62-3852 is on record as being a Beech U8 the last of which was  withdrawn from service in 1992

Regards,

Syd

[Marpleman]

After all the sterling work you and the others are doing with updates, surely it is not too much to expect AirNav to regularly release updates. I wouldn't have thought once a month would take too much effort or would be too much to ask seeing as the data gathering and revisions to the 'Master Database 'has been done for them. 
Presumably you undertook the task expecting this to happen, otherwise what's the point of the exercise. Individual users have always been able to do tie ups through Airframes  to update their own data anyway if they were capable of doing so.

Just another point Alan, and I'm not at all being critical or pedantic. There seems to be a mix up between 62-3582 and 62-3852. I assume it's just a typo and it is -3582 you've done the entry for.



Regards,

Syd

Hi Syd

We've been screaming for this for a long time now,as we as a team see this as the best way forward.

If we suddenly stop after the release of a new updated database , then frankly without a suitable mechanism to continue, we've been wasting our time!

Most other "enthusiast" packages on the market seem to operate under a similar system,and as we've discussed on here, given the fluidity of record changes/deletions/inceptions etc, the more frequent the release of a revised database, then the better it will be for all!

Unfortunately we as a team are not able to make that decision as I'm sure you'll appreciate.

The initial hurdle was to correct and capture as much "known" information as we could, hence why at the moment, no "new" file has been released.


As regards your second point - this is exactly the sort of stuff we want to receive, be it input error or error with the existing data!!


Cheers

Rich

[Runway 31]

Syd I can confirm it is on the database as 62-3582.  Glad I made the typo here and not on the d/b.

Alan

[Hawkeye]

Thanks for your reply Rich.

I can understand your frustration.
To be honest, if I was a member of 'TheTeam' I'd feel like chucking it in as a waste of time if having put so much effort into it, AirNav hadn't even acknowledged it and informed me what if anything they intended to do with it, as seems to be the case.
I would have thought that providing databases as up to date as possible would be considered essential as a selling point and they couldn't wish for anything better than to have people not associated with the company supplying such information at no cost.
I would like to add that I think the Logos, Outlines, Silhouettes etc produced by Rod and others must also be of benefit to the company and I'm sure that all RB users appreciate the time they put into producing them.

Syd

[neroon79]

AR:RA-10202    AN:Gulfstream Aerospace GV-SP (G550)   AT:GLF5   CN:5119    MS: 1427DA  AC:Surgutneftegaz   didn't populate

[neroon79]

D-EASA (3D0680) populates with obsolete Data: Morane-Saulnier... Actually it's a Cirrus Design Corp SR-20...

The same is valid for D-HAUL (3DD4B3) which is now a AN: Eurocopter AS-355N Ecureuil 2 (AS55) CN: 5742 AC: Meravo

[neroon79]

five further:

1st: D-MIDI (3FEB41) PNR2 ALPI Pioneer 200
2nd: D-MFBS (3FEA9A) FK9 B & F Technik  FK-9
3rd: D-KEDK (3E66D8) DISC Schempp-Hirth Discus bT CN:81/414
4th: D-KGRH (3E6D89) SF25 SCHEIBE SF-25c "Rotax Falke" (LSV Grambeker Heide e.V.)
5th: D-EWTT (3D40C1) C182 Cessna T182T   CN:T18208877    

[neroon79]

And another one:

D-ELIC (3D2286) AT: C82R AN:Cessna TR182 Turbo Skylane RG AC: Luftsportverein Rietberg eV  CN:R18201847   

D-MOMB (3FEEA2) AT: ? AN: TL Ultralight TL-96 Star AC: Flugschule Bielefeld CN: ?

[Runway 31]

Ingo, all updated, many thanks

BTW, received your email

Alan

[neroon79]

I just added D-MOMB...

[Runway 31]

Thanks Ingo, got it

Alan

[neroon79]

If the acquired information is correct I just got a rarity:

D-IEAG (3E21DE) JU87 Junkers Ju87 A07 ("Stuka" or "Dive Bomber")
well, at least once D-IEAG was a J87...