Geo APIs Summer Learning Series

 

Google has one of the world’s most comprehensive databases of Places information, including over 50M business listings and points of interest worldwide. The Google Places API lets your applications tap into that database, to find the Places your app needs, so that users can indicate the Place they are at, or discover new Places nearby.

Following the introduction of the Places API at Google I/O last year, we worked with developers in a limited preview to understand what was needed to ensure the Places API is as powerful and easy to use as possible. In the “Connecting People with Places” session at this year’s I/O I was very happy to announce that having implemented the feedback we received during the preview, the API is now accessible to all:

 

The Places API is provided in two ways, a set of XML and JSON web services, and a set of corresponding classes in the Maps API v3.

The web services are ideal for mobile app developers, and can be queried from the developer’s own infrastructure, or directly from the app running on the smartphone. The Places API Search service focuses on location-based search, delivering up 20 Places in the vicinity of a user’s location. Search results can be filtered by Place name, or by one of over 90 categories, such as ‘restaurant’, ‘night_club’ or ‘spa’. The Places API Autocomplete service focuses on text based search, providing autocompletions of Places near the user as they type.

The Places API Report services also allows apps to submit new Places provided by users, which are instantly added to subsequent search results, and also delete them at a later date if required. Apps that allow users to identify the Place they are in at the time can also pass this “check-in” signal back to the Places API Check-in service which factors this real time popularity signal into the ranking of subsequent searches, so that the Places popular with users of the app are ranked higher in real time.

The Engineering Lead for the Places API, Marcelo Camelo, dove into how to get started with the Places API web services, and the structure of requests and responses in the “Location Based App Development using Google APIs” session:

 

For web based applications the Places API has also been integrated into the JavaScript Maps API v3. The PlacesService class provides access to Places API Search directly from the web based Maps applications, while the Autocomplete class enables a HTML text field to predict autocompletions of Places as the user types:

 

To use the Places API classes in your Maps API applications you simply need to request the new places library when you load the API into your web page. To use the web services, you must first create a new project in the Google APIs Console, and then enable the Places API on that project. You can then use the APIs Console key for that Project to access the Places API.

Initially your key will offer courtesy quota of 1,000 requests per day. Once you are ready to launch the next great location based app, simply “Enable billing” on the project. You will be prompted to provide credit card details, in order to verify your identity. Once you have done so, your quota will increase to 100,000 requests per day, but the API will remain free to use. Note that you may be charged if you use the same key for other APIs, which you can avoid by creating a separate project for accessing other APIs.

For more information on how to use the Places API, check out the documentation for the Search and Autocomplete web services and Maps API v3 places library. You can also discuss the API with other developers on the Google Maps API Web Services forum, and request additional features you would like to see the API offer, or report any problems you find, using the Places API section of the Google Maps API Issue Tracker.

Our launch at Google I/O this year was just the beginning of the Google Places API story. We are looking forward to bringing you many more features in the future to help you build more innovative and compelling location based applications. So do get started developing your apps, but keep an eye on this blog for more to come!

 

TripsQ and Foursquare Data

TripsQ

TripsQ is a data visualisation application that aims to help people make full use of the data they’ve generated through Foursquare. It uses all the data you have gathered while travelling, by turning your check-ins at airports into useful travel statistics.

Everyone who uses Foursquare can easily sign in to tripsQ and visualise their trips and travel itineraries. TripsQ also provides users with detailed statistics on the distance they’ve travelled, the amount of CO² they’ve produced during each trip and other information about their travels.

The site uses Google Maps to visualise your travels around the world. The map has been beuatifully styled with the Styled Maps feature to create a map that complements the overall design of the tripsQ website.

There are some other cool features coming soon as well. One planned feature is to show the tips left by your friends in each of the cities you visit. Another planned feature will be to show the distance you have walked during each of your trips.

Secrets and Surprises in Geo APIs Summer Learning Series

The second session of the Geo track at Google I/O was “Secrets of the Surprises of the Google Geo APIs.” Going into I/O we wanted to have a session that could serve as a foundation for later sessions and one where we can feature some of the latest launches leading up to Google I/O. We covered features of the Maps API v3, the Earth API, Fusion Tables, the Maps API Web Services and the Static Maps API in this one session.

What we hope that you take away from this talk is that there is more to the Maps API than just putting markers on a map – we’ve been actively adding many cool features that can really enhance your mapping application and create a better experience for your users.

Here’s a small subset of the features discussed in the talk:

  • With an ever-growing list of cities with 45° imagery available you’re now able to give your users a new perspective of what a place looks like.
    Don’t forget that there are several easy to enable layers available to quickly add content to your map.
  • Developers have frequently requested the ability for API applications users to drag direction routes around the map in a similar manner to Google Maps, so as you might have guessed, enabling draggable directions in the Maps API is now as simple as a one line code change.
  • A favorite feature of the Maps API is the ability to style the base Google map. With the power to change not only the features shown on the map but the color scheme of those features you have tremendous ability to theme your map to fit a look or brand or remove features that are relevant to your users.
  • Street View in the Maps API v3 is implemented entirely in HTML and Javascript so it’s usable on mobile devices with capable browsers without the use of a plugin. This also gives you the power to provide your own custom panoramic imagery and link it to our standard Street View imagery. Don’t let the experience end at the front door – take your users indoors!
  • We’ve added a Distance Matrix service that lets you quickly and easily get travel time and distance between many origins and destinations in one call.

    • In addition to providing driving, walking and bicycling directions the directions service will even optimize the route, determining the best order to visit several destinations.

We talked about a lot more – including AdSense integration, the Places API, useful open source libraries, Fusion Tables and historical imagery, trees and 3D buildings in the Earth API – check out the video or review the slides to learn more!