KML Platform Position and Track Mapping

Description

This feature within the standalone KML visualizer tool (ferskml) translates the local Cartesian coordinates (X, Y, Altitude) of platform initial positions (Transmitters, Receivers, Targets) defined in the FERS XML scenario into geographical coordinates (Latitude, Longitude, Altitude). It also visualizes the defined motion paths for platforms using KML Tracks (<gx:Track>), attempting to represent Linear and Cubic interpolation paths based on the XML waypoints.

Assumptions

• Assumes the input FERS XML file contains <platform> elements.
• Assumes these <platform> elements contain <positionwaypoint> elements for initial position and optionally a <motionpath> element for movement.
• Assumes the simple equirectangular projection (using a constant factor like 111319.9 meters per degree for both Latitude and Longitude changes) provides sufficient accuracy for converting local X/Y coordinates to Lat/Lon changes relative to the defined origin, adequate for the scale of the simulation scenario being visualized.
• Assumes the <positionwaypoint> tags contain readable child elements for x, y, altitude, and time.

Limitations

• Approximate Coordinate Conversion: The conversion from local X/Y coordinates to Latitude/Longitude changes uses a simple equirectangular projection. This method does not account for the true curvature of the Earth and its accuracy degrades over larger geographical distances from the defined origin.
• Non-functional Hyperbolic Path Visualization: The code includes logic attempting to visualize hyperbolic motion paths, but this is explicitly marked as non-functional in comments and likely does not produce correct or useful KML output for this path type.
• Potentially Inaccurate Cubic Path Visualization: The KML visualization for cubic spline paths appears to use hardcoded control points or a simplified interpolation method within the KML generator. This may not accurately reflect the path calculated by FERS's internal cubic spline interpolation logic defined in the core simulator.
• No Rotation Visualization: This feature only visualizes the positional track of platforms (changes in location over time). It does not visualize changes in platform orientation (rotation).

Related Components

• Standalone ferskml tool executable.
• FERS XML Scenario file format (specifically <platform>, <positionwaypoint>, <motionpath> elements).
• KML Standalone XML Parsing (Wiki page detailing the XML parsing within the KML tool).
• Platform Motion (Wiki category page for the FERS components defining the motion being visualized).

Validation Status

• Needs Verification: The accuracy and correctness of the generated KML paths require verification against known inputs and potentially FERS internal state data for the same scenario.
• Key Areas for Validation:
  • Accuracy of the Latitude/Longitude conversion for platforms at different distances and directions from the reference origin.
  • Visual comparison of generated KML tracks (Linear, Cubic) against expected paths or paths plotted directly from FERS internal position data for the same simulation scenario.
  • Confirmation that Hyperbolic path visualization is indeed non-functional or produces incorrect output.
  • Behavior with various edge cases (e.g., platforms crossing the origin, scenarios spanning larger geographical areas, sparse waypoints).
• Priority: Medium (Correct visualization aids usability and scenario understanding, but core simulation physics accuracy is likely higher priority).