MVM is now compatible with the Google Earth!
This
service allows clients to view their vessel and vehicle locations on the
Google Earth application. This is an alternative to the maps that we
normally supply on the client pages of this website.
The client may download Google Earth directly from http://earth.google.com/download-earth.html
Google Earth operation is pretty-well self-explanatory & beyond the scope of this page. Basically it consists of a series of maps on a globe, which the operator may manipulate through zooming & panning. In some places the map quality is excellent, with individual berths clearly visible, while in other locations the map quality is not so good. However, new maps are being added constantly, and the presentation & ease of use make this a very interesting way to view vessel information.
MVM integrates with Google Earth through the use of a *.KML file for each client. This KML file is emailed to each client. It is a static file which doesn't change, and in fact is only a pointer to the dynamic data file which is located on the Meridian web server. The data file on the web server is updated every 5 minutes (though the data from the actual vessel/vehicle will usually update less often than this).
All the client needs to do (assuming they have Google Earth already
installed) is to extract the *.KML attachment from the email
and then put it in a folder on their computer somewhere. Then they can
double-click on the *.KML file which will open Google Earth with the KML file in
"Temporary Places" and show the vessel/vehicle data. Google Earth will
periodically refresh the data from the server, at an interval described below.
NOTE: When closing Google Earth, the application will give the client an
opportunity to save the data from "Temporary Places" to "My
Places". If this is done, the data will automatically appear in Google
Earth any time it is opened - after the user enters the username & password
when requested.
Note that the KML given to each client is a plain text file that can be
edited by the user. There is really only 1 parameter that a client would want to
change:
<refreshInterval>120</refreshInterval>
This value is in seconds, and represents how often Google Earth will try to grab
data from the web server. The default is 120 seconds or 2 minutes but this can
be changed by the client to a value that suits their available Internet
bandwidth. For example, if bandwidth is expensive or limited, and the client's
vessels only update every 6 hours, then a value of 600 seconds (10 minutes)
would probably be ample.
The system is very secure. Although a client is given the KML file, they may not actually access the data on the web server without knowing the username & password. This is the same username & password that the client uses to access their own sub-website on the Meridian main website. If the client doesn't know the username & password they are welcome to contact us.
Note that as well as the background maps provided by Google, and the dynamic vessel information provided by Meridian, static information can also be included in the maps. The example below shows a no-go border line around Aceh in North Sumatra. Items such as working limits, platforms, fishtrap or seismic survey runlines, etc can be included in the presentation, delivered to the client as extra KML files so they do not need to be downloaded every time the dynamic data is automatically refreshed.
| Examples of vessel/vehicle icons | Example of Google Earth presentation (vessel labels removed) |
| Example of a stationary vessel - red colour (Note the trail behind the vessel)
|
![]() |
| Example of a moving vessel - green colour (Note the trail behind the vessel)
|
|
| Example of a vessel that hasn't updated for 24 or more hours
|
If the client requires extra KML files to show working boundaries or fish-trap/seismic run-lines, these files will be left on the sub-webs on the Meridian main website so that the client can access them when required. We welcome all comments & suggestions from our clients as to how we can improve the presentation.
NOTE: An error message may appear every so often, as this example below
shows. This error is caused by the server updating the data just at the time the
client is trying to refresh from the server. If this occurs, just press the
Ignore button & the error will no longer occur for that session of Google
Earth.

visits since