The Google Latitude API allows for websites and developers to integrate with Google Latitude, which lets users update and read their current location, their location history, and other geo-related information.
In Latitude, a location is a record of where a user was at a given time. A location always contains a latitude, a longitude and a timestamp. It might also contain more details about the position of the user at that time, such as altitude, or metadata about how the position itself was captured, such as accuracy.
A user typically has a current location, which represents the most recent known position of the user. In some cases, however, a user might decide to temporarily hide, making their position invisible to Latitude friends. A hidden user has no current location.
A user can opt to have their locations stored as a time series by Google. This collection of positions is called the user's location history.
The following is a list of historical changes that were made to this asset. Typically, once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change. As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset, we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb. If you spot an error in our data and believe that a record needs to be updated in some way, the ProgrammableWeb team would very much like to hear from you at firstname.lastname@example.org
So far, we don't have a record of any changes to this API