The trace_splitter.py script can parse that JSON format and it has to show charts of the duration.
More specifically the tdur (aka thread duration) parameter should be plotted.

• add controls on the screen to move the map
• keyboard bindings

• select 3D/flat terrain tiles
• place initial point near some 3D building

• split a trace at every bindBuffer call producing multiple csv files (starting from a bindBuffer until the call before the next bindBuffer)
• given a trace file, draw a chart showing the elapsed time between every bindBuffer call

NB: trace export in CSV file has to be done from the web gui querying for the webgl keyword.

The WTF traces graphs between the bindBuffer functions has to be divided into the 3 groups. Highlight how much time is spent in each group with respect the overall time elapsed between two subsequent bindBuffer calls.
Consider to show the bar chart with 3 different colors matching the 3 groups.

Capture a trace like the previous ones, but re-drawing a point without moving it. Do like the other traces sending only one "position", but it is the same as the original one without any modification.
Check if there is still a bufferSubData call, even though the object is not moved but just repainted on the screen.

Point's camera should rotate properly in order to simulate the user's view

Catch WTF traces from the following scenarios:

• old man moving on the map with all the tiles
• map with all the tiles moving without the old man (move only the camera)
• empty map with old man moving

Compare all the traces above to see what's in common and what not.

• use google's web tracing framweork to get insights about what is really going on frame-by-frame
• trace analysis script to see some meaningful timing chart between WrbGL function calls (#7)
• identify which WebGL functions are used to render a single frame (#6, #7, #8)

Just some random links:

• Terrain builder
• Terrain server
• 3D Tiles/pointcloud server