KML Scenario Visualization

Description

Parses a FERS XML scenario file and generates a KML (Keyhole Markup Language) file. This KML file allows visualizing the defined scenario elements like platform positions, motion paths, and basic antenna footprints in geographical viewers (e.g., Google Earth). It is a standalone tool (ferskml) and requires separate execution from the main FERS simulation.

Assumptions

• Assumes the input FERS XML scenario file conforms to the structure expected by the ferskml parser's logic.
• Assumes the user has access to software capable of rendering KML files (e.g., Google Earth, Marble).
• Assumes the reference Latitude, Longitude, and Altitude provided to the tool (or defaulted) accurately represent the origin (0,0,0) of the FERS local coordinate system in the real world for geo-referencing.

Limitations

• Standalone Execution: The tool is separate from the main FERS simulator and must be run manually, typically before or after a simulation run. It is not integrated into the FERS runtime environment.
• Dependency Divergence: Uses the Xerces-C library for XML parsing, which is a different dependency than the one used by the core FERS simulator (libxml2). This adds an extra external dependency requirement solely for this tool.
• Static Visualization: The generated KML represents the scenario definition (platform paths, initial positions, basic antenna shapes) based on the input XML configuration. It does not visualize dynamic simulation results like detected signals, signal power levels, Doppler shifts over time, or the outcome of signal processing.
• Limited Scope: Visualization focuses primarily on platform kinematics (position and movement) and very basic representations of antenna footprints. It does not visualize other detailed simulation aspects like specific radar parameters (PRF, waveform type), target RCS values, or environmental effects directly.

Related Components

• XML Scenario Loading (Defines the input format)
• KML Platform Position and Track Mapping (Uses the parsed data)
• KML Antenna Footprint Visualization (Uses the parsed data)
• KML Standalone XML Parsing (Describes the parsing implementation)
• External KML viewers (e.g., Google Earth)

Validation Status

• Needs Verification: The tool's output needs systematic verification against various FERS scenario configurations to ensure it parses correctly and generates geometrically reasonable KML representations for the defined elements.
• Key Areas for Validation:
  • Accuracy of the local Cartesian (X, Y, Altitude) coordinate conversion to geographical (Latitude, Longitude, Altitude) based on the provided reference point.
  • Correct visualization of different platform motion path types (e.g., linear, potentially cubic) as defined in the XML.
  • Robustness in parsing different valid FERS XML scenario structures without crashing or producing nonsensical output.
  • Correct interpretation and rendering of parameters used for the supported antenna footprint visualizations (e.g., sinc parameters, isotropic representation).
• Priority: Medium (Important for usability and scenario understanding, but not core simulation physics).