Database correlation between different systems is a difficult issue, but sometimes we make it harder than it has to be. For example, imagine someone has a large terrain database built with TerraVista. You want that terrain and since your system can handle OpenFlight, you think, "Great! Let’s try it out. Send me that database." What you get is hundreds of openflight files and one master.flt file that references the hundreds of individual tiles of terrain. When you try to load the master.flt file, your system runs out of memory and crashes. Bummer, that didn’t work. It’s like trying to eat a bag of popcorn without opening the bag first.
To handle this problem, you could choose an approach that would be optimal for your system, but also the hardest and most time-consuming to implement; you would have to reprocess the terrain database into a structure that better suits your system architecture. But many times you don’t have the skills, time, or energy to do that. You just want to load the thing and see if it is a useful database before committing to optimizing it.
Here’s what I recommend: try MetaFlight. Lots of people think MetaFlight is a different kind of database but it’s not. It’s just an XML-based way to reference the many tiles of a terrain. MetaFlight describes the grid of tiles using your database’s coordinate system so that the simulation or visual system can fetch the tiles that it needs and ignore the ones that are not needed or in view. When you use MetaFlight, it’s like reaching into the bowl of popcorn and getting the handful that you want.