Continuing on from my last post regarding new client-side storage options, I decided to keep the trend of HTML5-related posts coming

So unless you haven’t visited the web in the last 3 years, you know that location-based services are super-hot right now.  If social networking was the final result of Web 2.0, wiring-in people’s browsers (both position-locked and mobile) to geolocation is easily Web 3.0 and beyond.  For example, with few exceptions, the vast majority of my iPhone apps have some geo-location component.  Whether it’s my RedBox app finding me the closest kiosk, or FourSquare letting me “check in” to new (and not so new) locations, nearly everything I do on the web is able to be tagged with a location.  Every tweet, every Facebook wall post, heck, even this blog post have geolocation data attached to them.  In every possible way, the web is no longer just about “what” you are doing–it’s where you’re doing it as well.

To help make this more of an integrated reality, HTML5 will come fully-loaded with baked-in geolocation support.  As with client-side storage, dealing with the geolocation options is quite easy.

Let’s take a look at a simple example.  In what follows, I simply want to More >