Download as PDF, PPTX
Uploaded byRyan Sarver
W3C Geolocation API - Making Websites Location-aware
The document discusses the W3C Geolocation API, which allows websites to detect the user's location. It provides an overview of the API and location technologies, examples of how to use the API, and upcoming geo events. The API allows websites to get the user's location either once or periodically with callbacks that return position and error objects. Common location technologies discussed are IP geolocation, GPS, Wi-Fi, and cell tower triangulation.
More Related Content
Similar to W3C Geolocation API - Making Websites Location-aware
Editor's Notes
- #2 - who here runs a website? - who here uses location of some kind on their website? - mobile?
- #3 - who here already knows Skyhook?
- #4 - its important that you can leave here
- #5 - leave lots of time for questions at the end
- #6 - location is a proxy to lots of metadata - rich demographic data - context about the physical surroundings of the user - events they might be at - nearby POIs - time of day, weather
- #7 - the more context you have the more relevant the experience you can delivery
- #8 - deliver the most highly relevant experience to your users - use most accurate location available
- #9 - so lets define “location” - what does that mean?
- #10 - going to become important that sites can work with lat/lon - w3c api will always deliver you a lat/lon - start to architect your apps to store lat/lon as well
- #16 - anyone here use brightkite or foursquare? - disambiguate lat/lon into something meaningful. business names are great - also consider using custom place names
- #18 - some location information is only relevant to nearby users - placenames, neighborhoods - add higher-level context for other users
- #19 - maps can be a misnomer bc users dont always want to share exact location - EXAMPLE: user is in San Francisco -- where do you put the marker? - consider text display
- #20 - Here is a video of BrightKite using auto-location - gives you a feel for how other sites are doing it
- #21 - relevancy. too much noise, not enough signal - location is a piece of metadata that can make the entire web more relevant - better user experience - geotag photos, share location on social networks, local search, local news
- #22 - Lets take a store finder as an example - each dot represents a Dunkin Donuts in Boston - if you ask a user to tell you where they are, they will say “boston” or “02218” - using precise location allows you to instantly show them the correct location and start to route them there
- #23 - A lot has changed in one year, since i was here last - last year i was talking about the how it was coming together and some tools - now, W3C working group and 3 major browser vendors you can download today
- #24 - Loki was launched at Where 2.0 in 2006 - toolbar to get skyhook’s technology into the browser - eventually made a javascript API to the toolbar
- #25 - May 2006 - i realized the only way for this to grow was to get consensus among browser vendors - needed to evangelize the idea of location on the web - no one knew you could make a laptop a gps-like device - pre iPhone
- #26 - google picked it up, added it to Gears - started with cell positioning for mobile devices - created their own Javascript API
- #27 - June 2008 - standardize the way geolocation is exposed through the browser
- #28 - all major vendors are involved - already getting to draft - KISS
- #29 “its all coming together”
- #30 - bold proclamation - location was always the technology of next year, well its finally next year - desktops, laptops and netbooks will all be location enabled
- #37 - accuracy is directly proportional to cell size - gps, wps = street address accuracy - cell = neighborhood / city accuracy
- #41 - instead of waiting for all the browsers, add it now - cross platform, cross browser - on MapQuest.com/findme
- #43 - Wi-Fi positioning is primary, IP as a fallback
- #45 - REALLY this simple to add location to your website
- #50 enableHighAccuracy will probably change
- #51 do this to save a new location request. power friendly position <= 5 minutes timeout:0 = return cached position
- #52 do this to save a new location request. power friendly position <= 5 minutes timeout:0 = return cached position
- #53 - if you are looking to get more involved in geo, there are some great events to attend