Since the whole file is always in the metric system, the altitude is expressed in meters MSL (above sea level, also known as ASL in some countries). Positive values are toward the north and east directions. Notice that Latitude and Longitude are expressed in degrees. For now, let's just focus on this case which is: T = Longitude | Latitude | Altitude. We will see later which syntaxes are supported for T. The first property T (which stands for Transform) is a special property used to define the object coordinates in space. To save space, Object ids are expressed in hexadecimal without any prefix or leading zeros. This line defines two properties for the object 3000102. In that case, this means that the following events or properties happened at ReferenceTime + 47.13 seconds ⇒ + 47.13 ⇒ T05:00:47.13Z
This line defines a time-frame in seconds relative to ReferenceTime. To understand better what this means, let's have a look at the following line: #47.13 In other words: This line defines the base/reference time used for the whole flight recording. This line assigns the value to the property ReferenceTime of the global object always designated by its id zero 0. Let's see in detail each line syntax: 0,ReferenceTime= The third possibility – not shown here – is a line which starts with the minus sign - followed by the id of an object we want to remove from the battlefield (could be destroyed or simply out of recording range).Each property will be assigned a new value using the equal sign =. An object id (in this example 102) followed by as many properties as you want separated by commas.The sharp sign # introducing a new time frame in seconds relative to ReferenceTime.To better understand this structure, we need to know that – apart from its header – each line of the file can be either: Let's be rational: Even if Tacview will gracefully load this empty file, we need a bit more data to make it useful! Here is a file which makes more sense: FileType=text/acmi/tacviewģ000102,T=41.6251307|41.5910417|2000.14,Name=C172
This header tells Tacview which format to expect. These are the only two mandatory lines you must put first in any ACMI file. Without further ado, let's start with the simplest file possible: FileType=text/acmi/tacview
Freeplane export as bulleted list free#
If you think that an important data should be natively supported and displayed by Tacview, feel free to contact us. It is important to note that data which are not yet supported by Tacview are preserved and visible in the raw telemetry window. For instance, it is now possible to change the coalition, the color, even the type of an object, on the fly! In the same way, you can easily assign and change global properties, like the weather for example. This new format is so simple that it could even be written by hand if the amount of data was not astronomic!ĭespite its simplicity, the new format offers a very powerful way to set and change – in real-time – any property of any object on the battlefield. Its syntax is very easy to read by humans and, with the debug log introduced in Tacview 1.4.3, it is now very easy to diagnose any exporter issues. That way, it is possible to easily export flight data from the simplest programming language. Like its predecessor, the new file format is written in plain UTF-8 text. The goal was to overcome the complexity of the previous format while making it much more powerful at the same time. With Tacview 1.5 a new universal public file format has been introduced.
0 kommentar(er)
