Which out-the-window databases can be correlated to the MMRS?
OpenFlight is the standard SERF input data format. However, the
distributed features (areals) and 3D features in this data must have usable
radar attribution such as some sort of feature type identification code
and/or surface material type identification. It also needs to have
enough areals and 3D features to present a reasonably cluttered image.
Completely geo-specific textured databases where there is no surface
material identification provided with the imagery require augmentation
from other sources for a realistic scan.
What other source formats can be used to create an MMRS database?
Optional out-the-window correlated input sources include anything that
can be exported into DTED/DFAD, SIF, or SEDRIS formats. If the
out-the-window database does not fall into any of these categories,
a custom import option can be developed by the Tsunami Tsoftware
Is the database stored in geodetic coordinates?
There is a choice between geodetic and flat earth database coordinate
systems. Larger databases will be geodetic.
How many Levels of Detail (LOD's) are used?
The number and resolutions of the LOD's are configurable. The standard
MMRS configuration supports up to 9 LOD's. It is not necessary to
have a contiguous set of LOD's; missing resolutions are texel-replicated
What resolution of SAR is supported?
Each texel at LOD 0 represents 8x8 feet in the default configuration.
The MMRS and SERF will support finer resolutions, limited only by the
availability of source data at those resolutions.
Are there limits to database gaming area size?
Gaming area is limited by available disk storage and for geodetic databases,
by latitude (no higher than 80 degrees latitude).
What are the disk storage requirements per square nautical mile?
Storage size may vary as a function of feature density and active
resolutions, but a typical average is approximately 10KB per square
What if the customer is just replacing an older radar simulator and does
not want to spend a lot of money redeveloping their database?
For correlation purposes, the MMRS database is built from the out-the-window
database so that most of the development effort and budget is spent on
the IG database. If the image generator is not being replaced and no
back-transformed or exported source is available, Tsunami Tsoftware can
add a custom import of the old radar database to SERF. Beware that old
radar databases may be too sparse to show to advantage on the MMRS without
augmentation from other sources.
Do you provide the source data for radar simulation databases?
To ensure correlation with the rest of the trainer's visual cues, the
radar database should be built from a common source that is normally
provided by the visuals subcontractor. In the case where an
application does not require correlation, it is the customer's
responsibility to provide the database source to Tsunami Tsoftware for
the desired areas of coverage.
What database development support is included with the basic system?
A basic database analysis is part of the proposal process. Tsunami will
evaluate your requirements in the context of available source data and
the basic SERF formatting capabilities. Recommendations will be made on
storage requirements and special formatting needs.
What optional database development services are available?
Optional Database Services include planning and coordination with the
visuals subcontractor to gain access to database source, test and
evaluation of sample areas. When the customer is satisfied with the
test area, Tsunami will coordinate the formatting, delivery, and
acceptance testing of the remainder of the database.