How to Embed Google Maps on a Website

Instructions

1. 
   
   
   Step 1
   
   Locate the map you wish to embed on your website. Use Google Maps to create a map of a specific location or directions to and from locations (see Resources below). You can embed a set of driving directions in the same way that you would embed a map of a single location.
   
   
2. 
   
   
   Step 2
   
   Click the link labeled "Link to this page." It is located just above the map on Google Maps search results. A box will pop up with both a link and a line of HTML code. Highlight the HTML code and copy it. Google Maps will also give you a link offering the option "Customize and preview embedded map," which you can use to change the size of the map you will embed.
   
   
3. 
   
   
   Step 3
   
   Paste the HTML code into your website's code, if you are using HTML code to design your website. If you are using software that does not require coding, you may need to switch to an HTML editing mode in order to insert the map.
   
   
4. 
   
   
   Step 4
   
   Check the live version of your site to ensure that your map is showing properly. It should be fully functional. For instance, if you click on the map, it should act as a link to Google Maps. If your map is not loading properly, the Google Help Center can provide troubleshooting support.
   
   
5. 
   
   
   Step 5
   
   Check the map that you have embedded on a regular basis. Any changes made to Google Maps, from adding new reviews to a business to moving a location marker, will show up on your version of the map. Since Google Maps is easy to edit for anyone, information that you do not approve can appear on your website.
   
   AardvarkMap website has a feature to create maps in few simple steps. See example below.
   
   
   
   
   

Digicel Digimodem Mobile Tests

18 February 2010
By Matt Temar & Samson Busai

Our objective is to produce data for anyone interested in utilizing the Digimodem. The Digimodem can be useful for tracking systems.

Ouir test equipments:

Hardware

Laptop Notebook - Windows XP
Digimodem (USB) from Digicel
Blackberry Phone
Toyota Bus - Sam's (B 11064) Avg Speed 40km/hr

Software

Windows XP
Digicel application wizard installed.
Facebook Chat
Gmail Chat
DOS command - ping www.google.com -t

Testing real time connection by using chat and ping.

Results

Executing ping command to www.google.com -t.
Time-out as usual with the modem but applications are steady at number 3.
Latency very high in town maybe because of buildings.

Long time-out riding from Unelco to fungkuei

Connection established at Fatumaru Bay.

Long time-out from Tebakor Agriculture Supplies to Tebakor station.

Reply from 66.249.89.147: bytes=32 time=1058ms TTL=48<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Reply from 66.249.89.147: bytes=32 time=2021ms TTL=48
Good connection from Tebakor/Malapoa road to Solwota Club. Low latency.

Ping response
Reply from 66.249.89.147: bytes=32 time=956ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=915ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=872ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=948ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=925ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=943ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=961ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=920ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=920ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=957ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=915ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=951ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=951ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=925ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=942ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=981ms TTL=48<br /> Reply from 66.249.89.147: bytes=32 time=1306ms TTL=48<br /> <br /> Long time out from Tagabe to Mele.<br /> <br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=1525ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=4427ms TTL=48<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.
Mele connection not steady

Reply from 66.249.89.99: bytes=32 time=2362ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2795ms TTL=48<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=2139ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=857ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=875ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=876ms TTL=48<br /> Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=1108ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=874ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=873ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=873ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=969ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=866ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=886ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=882ms TTL=48
Mele-Maat road
Trac
Ping response
Reply from 66.249.89.99: bytes=32 time=2134ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=1596ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=921ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2657ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2621ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=939ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3082ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=957ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2057ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2117ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3598ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=1296ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2678ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2038ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3879ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=935ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2260ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2855ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3260ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2533ms TTL=48
Clems Hill

Ping response
Reply from 66.249.89.99: bytes=32 time=900ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=918ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=937ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=914ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=890ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=909ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=925ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=925ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=944ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2659ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=1663ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=909ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=925ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=908ms TTL=48
Towards Tamate Village

Ping response
Reply from 66.249.89.99: bytes=32 time=886ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3337ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2236ms TTL=48<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=3472ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=1798ms TTL=48<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.Reply from 66.249.89.99: bytes=32 time=923ms TTL=48
Up the hill towards Tamate village

Ping response
Reply from 66.249.89.99: bytes=32 time=2878ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2716ms TTL=48<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=1935ms TTL=48<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=1412ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=996ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=976ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=971ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=951ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=945ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=1203ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=1059ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=939ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2973ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=918ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=918ms TTL=48Request timed out.
Around Tamate Village

Ping response
Reply from 66.249.89.99: bytes=32 time=2973ms TTL=48<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=1952ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=921ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=1021ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=1057ms TTL=48<br /> Request timed out.
Long time-out from junction at Mangaliliu to Tanoliu

Stop at Tanoliu Village. FB chat not steady.

Message: Could not connect to Facebook Chat at this time.
tanoliu now 7:14pm Matt Sending: test 7:16pm Matt test

Ping response
Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=4331ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3644ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=963ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=937ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3482ms TTL=48<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=2719ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3550ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3284ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3121ms TTL=48<br /> Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=1632ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3901ms TTL=48<br /> Request timed out.<br /> Request timed out.
We captured some changes on our return trip. Between Mangaliliu road and Tanoliu, we had some ping responses. We concluded that, our connection depends on the Digicel tower locations.

Ping responses
Request timed out.<br /> Request timed out.<br /> Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=1419ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=1439ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3178ms TTL=48<br /> Request timed out.<br /> Request timed out.<br /> Reply from 66.249.89.99: bytes=32 time=4163ms TTL=48<br /> Request timed out.<br /> Request timed out.<br /> Request timed out.
At Tamate Village, the connection is better than before. There is a tower right next to the village.

Ping response
Reply from 66.249.89.99: bytes=32 time=940ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=920ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=937ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=912ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=912ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=989ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=965ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=924ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=924ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=919ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=937ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=936ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=913ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=911ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=1013ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=913ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=932ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=946ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=1299ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=3599ms TTL=48<br /> Reply from 66.249.89.99: bytes=32 time=2480ms TTL=48

Global Mapper Run Error

After installing Global Mapper, if you come across a lti_dsdk_dll
error, download and place the file in your c:\windows\system32
directory.
That should fix your problem.
The filename LTI_DSDK_DLL.DLL was first seen on Mar 29 2008 in the
following geographical regions of the Prevx community.
download the file here:
http://discuss.corruptedfilerepair.com/post/2008/09/11/GDAL13DLL-Download-File-GDAL13DLL.aspx