When we were designing the GeoSMS standard we looked around for other examples of SMS geotagging to see if it had already been done. It turns out there were quite a few previous applications, but nothing with a published standard.
In early 2007 the E-TEN Glofish M700 was launched, one of the first GPS-equipped smart phones to hit the market. Bundled with the phone was an application called Location SMS that let you send your GPS coordinates in human-readable form.
Based solely on the screen shot, it seems to use the reader-friendly B DD:MM‘SS.SS“ format to represent the location.
The TrekBuddy application, which runs on Java-enabled GPS devices, has had an SMS capability since September 2006. The SMS format wasn’t officially published, but it was mentioned in a forum post -
- Header $TBMYT or $TBIAH – TrekBuddy My You There or I Am Here
- Timestamp in secs (currentTimeMillis / 1000)
- Coordinates in the same format as in NMEA
- User message (ie. “Be quick” in this example)
- And end as NMEA (*00), but checksum is not implemented
The GeoSMS service was established by Coldbeans Software, a Moscow-based company, in November 2007. If you send an SMS of the form *location* message to +7909 921 3670 your message will be displayed on their on-line Google map at the specified location.
Although this is technically a published standard, the definition of location is “anything understood by the Google Geocoding API”. This means the receiving application needs an internet connection. It’s also not that accurate, unless you want to specify your location down to the street number. In which case, why bother with geotagging?
From the same group of Muscovites came another GeoSMS service in September 2009, part of their Geo Messages suite. This is an HTML5 application that lets you send your current location, formatted as a bit.ly-compressed Google Maps URL.
Google Maps URLs, to be honest, are probably the best way to send a location to another person given the currently-deployed handsets, since they have the best chance of being displayed correctly. But they aren’t suitable as a geotagging standard because they require the receiving device to have internet access, and they rely on a proprietary Google interface. The use of bit.ly has similar problems, plus it’s at the mercy of the Libyan government.
Finally, there’s the GeoSMS Android application, released by Geeksville Industries in March 2010. This application also uses Google Maps URLs to encode the location.