Skip to main content

Titanic mapping - 100th aniversary


    When you hear "Titanic", the first thing that comes to your mind is the 1997 classic, Kate Winslet and Leonardo DiCaprio starer, James Cameron directed epic romantic disaster film "Titanic" which after more than 15 years is re-released in 3D. You must be wondering why I am talking about the movie here on this blog. Well, its not about the movie, but about the mapping of the Titanic that interests me!

    April 15, 2012 will mark the 100th anniversary of the sinking of the Titanic in the North Atlantic Ocean. A century ago the Titanic collided with an iceberg in the north Atlantic and sank. Mapping traveler's hometowns, revels the immigrant status of most people traveling third-class, who also suffered the highest fatality rate. ESRI, has created a map story that will help us look at the geography, class and the fate of the passengers aboard the ship 100 years ago. The online map displays the hometowns of all the passengers aboard the Titanic excluding the crew and identifies them by the type of class they were traveling on whether first, second or third.

    The passenger data was mapped from Wikipedia's list of Titanic passengers. Visit Geography, class and fate: Passengers on the Titanic to see this amazing map story. Click on the menu items to see only the places of origins by a specific class and to view a pie chart showing how many passengers survived and died within that class.  Click on a location to see a list of passengers based from that point.  You can delve further into the lives of the Titanic passenger list to see that person’s hometown, boarding location, intended destination, age, class traveled, and whether or not they survived.


    Hope you all love this map story - Geography, Class and fate: Passengers on the Titanic!

Comments

  1. postingan yang bagus tentang"Titanic mapping - 100th aniversary"

    ReplyDelete

Post a Comment

Please leave your comments here...

Recommended for You

Where does Google get it's live traffic data from?

Referring to a post that I wrote earlier, Google’s - Live traffic Layer , ever wondered how Google collected this data? I was wondering the other day, how Google received live data to display it on their maps as a layer! I looked up the web and found something very interesting and am sharing the same with you all. As we all know, the traffic layer is available most accurately in several states in USA. Most major metro areas in the US have sensors embedded in their highways. These sensors track real time traffic data. Easy to miss at high speeds (hopefully anyway, traffic permitting), more commonly noticed may be the similar sensors that often exist at many busy intersections that help the traffic lights most efficiently let the most amount of people through. The information from these tracking sensors is reported back to the Department of Transportation (DOT). The DOT uses this data to update some of the digital signs that report traffic conditions in many metro areas. They als...

Playing with the markers and info window bubbles...

    In the last few posts, we have seen some marker examples and some information window examples. Now, lets do something interesting combining these two things. Just writing that "This is an info window" in the information bubble is not very interesting! And I know this...Have gone through the same phase!     So, today we will do something interesting! We will display the latitude- longitude co-ordinates of the point that the user clicks on the map! Doing this is not at all complex! Copy paste the following code and you will see for yourself a map coming to life!     The output of the above code looks as seen in the result section above! If you have any queries regarding the above code please comment on the blog post or feel free to contact me at my mail ID .

The mobile meta tag

    If you have ventured into the world of Mobile web development, you would have realized the importance of the viewport meta tag in the head section of your HTML page. Without the proper meta tag included in your HTML, your web page would zoom, move, be dragged around and basically not client acceptable. To avoid all of this, we need to include a viewport meta tag in the HTML in the head section.     Jquery mobile suggests the users to use the following viewport meta tag. <meta name="viewport" content="width=device-width,minimum-scale=1.0,maximum-scale=1.0">     By using the above viewport meta tag, the width would be set to pixel width of the device. This would avoid the resizing of the page and there-by the web page would not be draggable any more. However, this would not disable our zooming issue. The user can still zoom the web page by tapping the screen or by pinching it. Jquery mobile suggests that this is a ...

Hilarious Google Maps

       I came across these simple yet wonderfully done illustrations based on the Google Maps Street style by Christoph Niemann - Illustrator for the Times Magazine. These illustrations are absolutely stunning show of creativity, design, execution and general beauty. All the illustrations show exactly how it is on the roads in New York. Sit back and enjoy the show.

Why this difference?

       Several of you must have observed this like I did, that the Google geocoder returns different results on the Google Maps website and Google Maps API v3 for the same address string. To understand why this difference exists, I dug deeper into the web and came up with the following.        The first and foremost place to look for an answer was the Google Maps API FAQ section. The FAQ section did not let me down of course! The FAQ section says: The API geocoder and Google Maps geocoder sometimes use different data sets (depending on the country). The API geocoder occasionally gets updated with new data, so you can expect to see results changing or improving over time.         What I concluded from the above is that, in a lot of cases Google licenses data from other companies like DigitalGlobe, Infoterra Ltd & Bluesky, GeoEye, Getmapping plc, Tele Atlas, etc. When negotiat...