Google Places API Offers Local Data To ‘Check-in’ Developers

Google previously announced (at its I/O developer conference) the creation of a Places API as part of the Google Maps API. That Places API is now open for business and being made available to third party developers. Booyah’s MyTown “check-in” app is one that has already been using it.

In short all the information and data that Google has about a place, say Gramercy Tavern in New York, will become available to developers through the API. This is exciting to many and offers the promise of a kind of open or “free” database of places (an LBS meme of late), though some might prefer a “neutral” database such as the one being developed by OpenStreetMap. As an aside, Mapquest has helped to fund OpenStreetMap and has ambitious plans to build on top of it.

Places API’s terms seem to require use of AdSense on any apps developed: “All developers wishing to use the service must already have an Adsense account, or must create one prior to applying.”

There are also other rules and restrictions regarding how data are to be presented in applications. For example, there’s no caching or storage of data locally — so to speak. (Here’s the technical discussion.)

For the near term Google said it is only going to work with “check-in” applications:

We are going to focus initially on check-in applications. These are the applications that we feel the API currently caters to well, and we are excited to work with developers building these applications to understand their requirements, and ensure that we are offering them the best possible experience.

It appears that third party applications will be able to do two basic kinds of things with the data: enable users to search for places (where they are or nearby) and/or retrieve more detailed information about specific locations (here or near).

The restriction to “check-in” applications (at least at the outset) may result in the development of lots of new check-in apps. Foursquare’s founder Dennis Crowley not long ago said that “check-ins would become a commodity.” The Google Places API would seem to all but guarantee that.

Related Topics: Channel: Mobile | Google: AdSense | Google: APIs | Google: Maps & Local | Google: Mobile


About The Author: is a Contributing Editor at Search Engine Land. He writes a personal blog Screenwerk, about SoLoMo issues and connecting the dots between online and offline. He also posts at Internet2Go, which is focused on the mobile Internet. Follow him @gsterling.

Connect with the author via: Email | Twitter | Google+ | LinkedIn


Get all the top search stories emailed daily!  


Other ways to share:

Read before commenting! We welcome constructive comments and allow any that meet our common sense criteria. This means being respectful and polite to others. It means providing helpful information that contributes to a story or discussion. It means leaving links only that substantially add further to a discussion. Comments using foul language, being disrespectful to others or otherwise violating what we believe are common sense standards of discussion will be deleted. Comments may also be removed if they are posted from anonymous accounts. You can read more about our comments policy here.

Comments are closed.

Get Our News, Everywhere!

Daily Email:

Follow Search Engine Land on Twitter @sengineland Like Search Engine Land on Facebook Follow Search Engine Land on Google+ Get the Search Engine Land Feed Connect with Search Engine Land on LinkedIn Check out our Tumblr! See us on Pinterest


Click to watch SMX conference video

Join us at one of our SMX or MarTech events:

United States


Australia & China

Learn more about: SMX | MarTech

Free Daily Search News Recap!

SearchCap is a once-per-day newsletter update - sign up below and get the news delivered to you!



Search Engine Land Periodic Table of SEO Success Factors

Get Your Copy
Read The Full SEO Guide