On 01/16/2007 12:57 PM, daveluff wrote:
> The best way to keep the data updated would be to feed improvements to
> Robin Peel (http://x-plane.org/home/robinp/) and then pull his updated
> data periodically.
An excellent suggestion.
In the meantime,
1) I pulled the data from the x-plane site.
2) I merged that with the data from the FG cvs tree.
3) This "grand unified" result can be found at
http://www.av8n.com/fly/fgfs/fix-grand.dat.gz
It has 87191 fixes with 84746 distinct IDs.
4) My merge procedure condenses clones i.e. groups of fixes
that have the same name _and_ are situated very close
together; it keeps only one representative of such a
clone. Ideally we would keep only the most up-to-date
member of such a clone, but since we don't know the
provenance of the data it is hard to be fastidious about
this.
5) I haven't yet done anything with the navaid or runway
databases. I suspect they need attention, too.
6) FWIW there were some 5279 fixes known to x-plane but not
to FG.
Of more concern, there were some 2703 fixes known to FG but
not known to x-plane.
It remains to be seen if Robin Peel is interested in
incorporating these 2703 fixes into his database. If
not, it's no big deal to merge them back in every time
we pull a copy of the x-plane database.
AFAICT there is nothing to lose by pulling it rather
frequently. Maybe even a cron job that runs every 56 days
or something like that.
Questions? Comments?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
