Skip to main content

Posts

Showing posts from January, 2013

The mystery of the "Vanishing Island"

    A 60 square mile land mass know as the Sandy island or the Sable Island has vanished without a trace from the Pacific Ocean. This island was supposed to be located between Australia and New Caledonia and can be seen in the older versions of Google Maps and several other scientific and nautical maps. The original location of the Sandy Island     Just recently a research vessel sailed to the location to find nothing but deep blue Pacific more than 4,500 feet deep. The researchers and doctoral students overboard the ship saw this mysterious island on all the scientific maps and weather maps but not on  one  navigational chart that was on their ship. There was no indication of any land mass at the exact location where the Sandy Island was shown.     If Sandy Island did exist, it would sit in the French territorial waters. But the French government denies that any of its official maps ever listed the invisible island. If such an island never existed, how did it find its way on

Ground Truth - How Google Builds Maps

    Todays's article is cross posted from The Atlantic 's Tech section. The article was posted by Alexis Madrigal who is a senior editor at The Atlantic , where he oversees the Technology channel. So, thanks to The Atlantic and Alexis Madrigal, we will have an exclusive look inside Ground Truth , the secretive program to build the world's best accurate maps.     Behind every Google Map, there is a much more complex map that's the key to your queries but hidden from your view. The deep map contains the logic of places: their no-left-turns and freeway on-ramps, speed limits and traffic conditions. This is the data that you're drawing from when you ask Google to navigate you from point A to point B -- and last week, Google showed me the internal map and demonstrated how it was built. It's the first time the company has let anyone watch how the project it calls GT, or "Ground Truth," actually works.     Google opened up at a key moment in its evo

The Jquery Mobile Multiple titles problem

    What is this "Multiple Title" problem? In JQuery Mobile, we have the multi-page structure which causes this problem. In case you want to check out what multi-page structure in Jquery Mobile is, please check out this post. The problem:     When you load the first page of a jQuery Mobile based site, then click a link or submit a form, Ajax is used to pull in the content of the requested page. Having both pages in the DOM is essential to enable the animated page transitions, but one downside of this approach is that the page title is always that of the first page, not the subsequent page you're viewing. The solution:      jQuery Mobile automatically parses the  title  of the page pulled via Ajax and changes the title  attribute of the parent document to match. For the multi-page documents, we handle this using the data-title attribute which is added   to each page container within a multi-page template to manually define a title. The title of the HTML document w

Jquery Mobile - Multi-page structure

    In this post today, we will have a look at the multi-page Jquery mobile architecture. We have discussed the single page architecture in detail in the previous post . In case you have missed it, I recommend you to have a look at it first, before you proceed to the Jquery Mobile Multi-page architecture.     Jquery multi-page architecture is nothing but a collection of DIVs stacked together in a single HTML page linked to each other using the div IDs. Let's take a look at the example below and then discuss it in detail.  The example shows a three "page" site built with 3 jQuery Mobile divs navigated by linking to an id placed on each page wrapper. Note that the id's on the page wrappers are only needed to support the internal page linking, and are optional if each page is a separate HTML document. Here is what three pages look inside the  body  element.     You must have observed that each of the page div has an attribute data-role="page" and a