Get a compact treenode representation of a list of skeletons

Get a compact treenode representation of a list of skeletons

The returned data can optionally with the history of individual nodes and connectors.

Returns, in JSON, [[nodes], [connectors], {nodeID: [tags]}], with connectors and tags being empty when 0 == with_connectors and 0 == with_tags, respectively.

Each element in the [nodes] array has the following form:

[skeleton_id, id, parent_id, user_id, location_x, location_y, location_z, radius, confidence].

Each element in the [connectors] array has the following form, with the third element representing the connector link as 0 = presynaptic, 1 = postsynaptic, 2 = gap junction, 3 = desmosome, 4 = mitochondria, -1 = other:

[treenode_id, connector_id, 0|1|2|-1, location_x, location_y, location_z]

If history data is requested, each row contains a validity interval. Note that for the live table entry (the currently valid version), there are special semantics for this interval: The upper bound is older than or the same as the lower bound. This is done to encode the information of this row being the most recent version and including the original creation time at the same time, plus it requires less queries on the back-end to retireve data. This requires the client to do slightly more work, but unfortunately the original creation time is needed for data that was created without history tables enabled.