We're also aware of a "target" database that would be worth releasing, and at the moment, we're not there - or near for that matter - so maybe we need to gauge peoples opinions as to what is acceptable, before any new Navdata file is released?
It might help to look at it this way:
A customer who goes out tomorrow and buys a brand new RadarBox, and plans to operate it without an Internet connection (which is a perfectly legitimate mode of use, Internet isn't listed as a requirement) will basically be getting a database that's more than 2 years out-of-date, and the updaters team might just as well not exist as far as he/she is concerned.
And the argument that "OK, our current database is cr*p, but at least we've got one whereas the competition hasn't" doesn't really hold water, does it ?
After we discuss some of the suggestions above with our Updaters team we will be back with more information.
One might have hoped that, at the same time the updaters team started work all those months ago, AirNav would have also started work on an architecture that would support the new database.
Instead, it would seem, months later, we haven't got past the "discussing suggestions" stage.