GeoLocal APIs: unencumbering the geolocal ecosystem

Location Business Summit

GeoLocal APIs

unencumbering the GeoLocal ecosystemTyler Bell

14 September 2010

[email protected]: @twbell

- 2 -

Local Ecosystem

Tyler Bell | [email protected] | @twbell

Interconnected resources that facilitate an informed, real-world consumer experience…

The Local Ecosystem

http://www.flickr.com/photos/leafy/3826214063/

and the value of a product is proportional to how many other products it communicates with

- 3 -

GeoLocal


Built Environment and AR Daily Deals

Places and Listings

Maps Utilities, Routing, Geocoding

Social Location

- 4 -

Obligatory NASCAR Logo Montage

Tyler Bell

- 5 -

Three Ways In


Application

API

CrawledContent

ContributionTo LocalEcosystem

- 6 -

Monday: TechCrunch/SimpleGeo


http://techcrunch.com/2010/09/13/what-is-it-you-do-the-need-for-simplicity/

A: See our API docs….

Q: What is it you do?

This is the only appropriate answer to a developer

- 7 -

Piñata


Marketing (paper maché)

API (candy)

http://www.flickr.com/photos/esquipulas/561125635/

- 8 -Tyler Bell | [email protected] | @twbell

APIs are the soul of a product

- 9 -

Source and Crawled Content


robots.txt is hugely insightful

as is ‘viewing source’

…both make for lousy presentations

- 10 -

Example: Google Places PM

“We are going to focus initially on check-in applications [and] have now begun reaching out to developers”


http://googlegeodevelopers.blogspot.com/2010/07/checking-in-with-places-api.html

- Google Maps API Product Manager

- 11 -

Example: Google Places API TOS

• Applications may not store any Place data permanently except References and IDs.

• Place data cannot be redistributed via your own API

• May only be used in conjunction with displaying results on a Google map

• Using Place data without displaying a map for which Place data was requested is prohibited.

• May only be used in response to end user actions.

• So there.


Paraphrased from http://code.google.com/apis/maps/documentation/places/

- 12 -

Product Design Philosophy


The Hallway

- 13 -

No Doors

http://www.flickr.com/photos/raulc/4429603/

Product does not facilitate new approaches, applications, or

business models

- 14 -

Multiple Product Options

http://www.flickr.com/photos/brentdanley/211734796/

Product creates multiple new opportunities for exploration, integration

and experimentation

- 15 -

A Look into some Local APIs


Short commentary on what APIs reveal

(now, not planned roadmap or intentions)


• Ease of check-in at expense of data accuracy (this is OK, and worked well)

• Massive dupe prob – solvable. Larger issue of traction has been addressed

• Search provides no name-to-venue disambiguation

• Robots.txt: restricts websearchhttp://aboutfoursquare.com/superusers-mislocated-venues/


• Only user names exposed to crawlers

• Massive API presence (of course)

• Does not employ own metadata standards – see API note above

• Robots.txt: heavy restrictions – again, pushing for API use v. crawled content


• No ‘place pages’, therefore no crawled metadata

• Tweets from 4sq check-ins are tied to a Twitter place – done via BD rather than API

• Three geo endpoints in API: nearby, details, and rev. geocode

• Place serves now as tweet-centric hub – more certainly coming


• Hcard encoding on listings (nice)

• FB Like Button

• No venue resolution on search API

• Literally impersonal: no people parameters in API

• robots.txt contains ‘three laws of robotics’ (geek cred)


foursquare:venue=516723

Krohn Conservatory

• Machine tags allow cross-reference into any namespace (incl. OSM)

• Huge API

• But also indexed and discoverable across searchhttp://www.flickr.com/photos/chrisirmo/4560462516/

- 21 -

Wrap Up: Use of Wire

Razorwire v. Datawire


- 22 -

Datawire

Tyler Bell | [email protected] | @twbell http://www.flickr.com/photos/tigerplish/250836258/

Connect and Plumb

- 23 -

Razorwire

Tyler Bell | [email protected] | @twbell http://www.flickr.com/photos/mightyboybrian/113445631/

Partition and Control

- 24 -

Thank You


[email protected]

@twbell

http://radar.oreilly.com/tylerb/

GeoLocal APIs: unencumbering the geolocal ecosystem

Documents

Transcript of GeoLocal APIs: unencumbering the geolocal ecosystem