->GTS


gts encoder conversion
Since v1.2.9
Available on all platforms
See also

The ->GTS function converts an encoder into one GTS per type in the encoder. The result is a map, with key describing the type. If defined, name, labels and attributes are kept in the result. Function also accepts wrapped or raw-wrapped encoders.

An encoder is very similar to a Geo Time Series™, it differs by its ability to store values of all four types (LONG, DOUBLE, BOOLEAN, STRING) and since 2.1 also BINARY content, when a GTS is limited to the type of the first value stored. An encoder can also have a name, labels and attributes.

The set of operations which can be performed on encoders is more limited than those that can be performed on GTS.

Signature

Examples

[ [ 1 48.44218 -4.41427 80000 "v1" ] // ( timestamp, latitude, longitude, elevation, string value ) [ 2 12 3.14 ] // ( timestamp, elevation, double value ) [ 3 42 ] // ( timestamp, long value ) [ 4 -45 0 true ] // (timestamp, lat, long, boolean value) ] ->ENCODER "testname" RENAME { 'id' '23444' } RELABEL ->GTS //MAP-> //if you want to visualize the GTS
[ [ 1 48.44218 -4.41427 80000 "v1" ] // ( timestamp, latitude, longitude, elevation, string value ) [ 2 12 3.14 ] // ( timestamp, elevation, double value ) [ 3 42 ] // ( timestamp, long value ) [ 4 -45 0 true ] // (timestamp, lat, long, boolean value) ] ->ENCODER WRAPRAW //push a byte array on the stack. WRAP pushes a string. ->GTS