VR-Forces Developer's Guide
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Groups Pages
Coordinate Systems in VR-Forces

Table of Contents

Overview

VR-Forces uses coordinates for various purposes throughout the API, and they can be in various different coordinate systems. This section lays out the naming conventions used in the API for coordinates and how they relate to each other.

The main terms used are:

These terms are used in various functions and parameter names. For example:

World Coordinates (ECEF)

World coordinates use an earth-centered-earth-fixed (ECEF) cartesian system. This system, also called geocentric coordinates, has its origin at Earth's center with axes:

This is the coordinate system used by DIS and RPR FOM network standards. API functions may refer to this system as either "geocentric" or "DIS" coordinates.

Local (Database) Coordinates

Local coordinates match the terrain database's native coordinate system. This system varies depending on the loaded terrain:

VR-Forces primarily stores and processes coordinates in this system for efficiency, avoiding frequent coordinate conversions when accessing terrain data. Some API components refer to these as "database" coordinates.

Relative (Parent) Coordinates

Relative coordinates are centered on a specific simulation object, useful for embarked entities or describing points on an object. The axes are:

This system is essential for:

Geodetic Coordinates

Geodetic coordinates use latitude, longitude, and altitude. While VR-Forces can convert to and from this system, it:

Topographic (ENU) Coordinates

Topographic coordinates (also called "topo" or ENU) provide a localized flat-earth approximation at a specific location with axes:

Key characteristics:


Document ID: Generated on Thu Oct 23 22:29:17 EDT 2025 from SVN revision 280951
Copyright © 2005-2024 MAK Technologies. All Rights Reserved (www.mak.com)