The previous test terrain contained only one mesh which worked fine with
the processTerrain() method in decodeGoogleEarthEnterprisePacket.js
because it wasn't requiring the correct number (5). Now that the
parsing code has been updated to expect all meshes, the test data needs
to be updated.
This file was downloaded directly from a Google internal enterprise
server. The location was somewhere near Hawaii so that it would contain
terrain above and below sea level, plus contain water surface meshes.
The URL path of the downloaded file was: flatfile?f1c-0300022-t.899
These water surface meshes are not currently used by CesiumJS. They
were added to the terrain packet format after the processTerrain()
method was first written which explains why it started failing with
a later packet format.
Mark Aubin
Tom Fili