: rendered at 9,000 X 6,000 :

When the 2005 USGS aerial photography was released to the public in the spring of 2007 there were a few places that were censored through pixilation. On this blog I documented how the White House was censored. I documented how the U.S. Capitol was censored. And I even experimented with a QR-Code to show that the Washington Monument was censored. After doing some exploration within the newly obtained 2008 Washington, DC orthophotography, I discovered that the White House and the U.S. Capitol are STILL censored.

However, now that the construction of the new visitors center at the Washington Monument has been completed, which is the reason, I am told, why the Washington Monument was originally censored in the 2005 imagery, the imagery of the monument is now available without pixilation. Moreover, its the exact same imagery that is being used on Google Maps. While I expect to showcase the censorship of the White House & U.S. Capitol in some future entries, I decided to make make my first map of this new dataset of the Washington Monument because I wasn’t able to make it using the last batch of imagery.

To construct this map, I first rendered a full-size Hexagon Quilt Projection map using the original imagery, then sampled a portion of the resulting map, and used the sampled portion to create this derivative map. I chose to sample the portion in the first map because of two underlying aspects of the map. First, I really liked the way the shadows of the Washington Monument combined together. Secondly, I liked the way the apex of the Washington Monument was combined (see detail below) to create a pyramid. Over the years I have enjoyed playing with the notion of aerial & architectural chiaroscuro, as in, using shadows generated by buildings within the original aerial photography to create a new, larger shadow. This map embodies this ongoing design element perfectly.

View the Google Map of the Washington Monument on the National Mall in Washington, DC.

: detail :

View the rest of the details:

Nearly every printed topographic map I’ve ever looked at has the contour interval, otherwise known as the distance between contour lines, listed in the legend. Depending on the scale of the map, the contour interval ranges from 1 foot to hundreds of feet between each successive contour line. The contour interval allows the map reader to instantly know the relative steepness & flatness of the topography in the map at one quick glance. Because of this crucial information, a topographic map is considered incomplete when it does not disclose this information to the reader.

Enter the Terrain feature of Google Maps. Released to the public in November of 2007, the contour lines were subsequently added in April of 2008. I hadn’t really given the feature much use until last week when I was planning my weekend excursion to the Shenandoah mountains. I was trying to figure out the altitude variation on my friends property by finding where their property line started & ended and calculating the elevation change. Since their property lies on the side of a mountain, I wanted to know the altitude at the bottom of the property and the altitude of the highest portion of the property, and subtract the difference to find the total elevation variance.

What I found out instead was that Terrain function of Google Maps was lacking the contour interval declaration in the legend. As with all their maps, the lower left-hand corner showed the units of distance on the map, but was missing the topographical information provided by the contour interval declaration.

In lieu of ever getting a response from Google Maps after previous queries, I decided to send a tweet to Google Maps:

I wasn’t really expecting a response, but a couple hours later I received this response on Twitter:

I was looking at the Wikipedia entry on Aerial Bombing of Cities and came across the World War Two aerial photograph above. It shows the absolute destruction of the Nagasaki, Japan after the atomic bomb known as “Fat Man” was dropped from the sky and detonated in the heart of the city. Below is a screen grab from Google Maps showing a contemporary view of ground zero:

…from life to death to life… Its rather amazing how much development has taken place since the war ended over 60 years ago. I just hope this type of bombing never happens again.

Back in March of 2008 I discovered that Google Maps was incorrectly displaying the official title of the National Museum of the American Indian on their maps. They had truncated the word museum to MSM. A friend of mine who works at Navteq, the supplier of the data, confirmed that the length of the title was too long, so they shaved off a few characters by truncating the word museum to msm. This lexical error was eventually corrected on Google Maps….

However, last night I had someone in India do a Yahoo! search for National Msm of the American Indian and ended up visiting my page. Upon closer inspection, I discovered that Yahoo! Maps was also doing the same type of truncation with Navteq’s data. I think NavTeq should to change it’s dataset so all the museums names are spelled correctly.

Note: the links in the images in this entry go to the Hirshhorn Museum & Sculpture Garden because it was the closest result for my query “National Msm of the American Indian”

Like the highway collapse of I-35 in Minneapolis, the partial collapse of the MacArthur Maze, the destruction of Hurricane Katrina, and the Columbine shootings, I’ve decided to make a map of the area around yesterday’s Metro crash site. Earlier today I downloaded the imagery of the site and found something I wasn’t expected. Not far from the actual crash site there is a Metro train on the tracks. While its not as interesting as the Ghost Cars on the I-35 bridge, I found it interesting that of all the locations for the Metro train to be when the plane flew over in March of 2005, the Metro train happens to be VERY close to the actual site of the tragedy.

Following up on yesterday’s posting, I stumbled across this interesting Google Map mashup. The Qibla (or Kiblah or Qiblah or Quibla) is the Arabic word for the direction that should be faced when a Muslim prays, otherwise known as the direction of the Kaaba in Mecca. For obedient muslims, the Salah, or formal prayer, is performed five times a day: at dawn (fajr), noon (dhuhr), in the afternoon (asr), at sunset (maghrib) and nightfall (isha’a). The Qibla Locator is a simple Google Map that is designed to automatically orient Muslims toward the direction of the Kaaba. Simply enter your location and the red line that is generated shows the shortest distance to the Kaaba. In the case of the screen grab above I decided to show what direction a Muslim would pray if they were in the White House in Washington, DC. I chose this location because I’ve read about some nutty folks who actually think president Barack Obama is a Muslim. Frankly, I don’t care what religion he practices and to take issue with anyone’s religion is a sign of intolerance and veiled ignorance. What I find most interesting about the Google Map is that the rhumb line toward the Kaaba can be somewhat deceiving. I’m not blaming the author of the mashup, rather, I think the nature of how the Quibla is found is unique. Since its based on the shortest distance to Mecca, sometimes the fastest way seems counter-intuitive, as in, I was thought the path from the White House (above) would be facing South-East instead of North-East. If you have a moment, try it out.

• The head of an animal that is slaughtered using Halal methods is aligned with the Qibla.
• Muslims are buried with their faces in the direction of the qiblah. Thus, archeology can indicate a Muslim necropolis if no other signs are present.

A short history of the Qibla:

Originally, the direction of the Qibla was toward Masjid al-Aqsa, Jerusalem (and it is therefore called the First of the Two Qiblahs). At least since Mishnaic times (AD200), Jews face the Temple Mount in Jerusalem while praying. The Mishnah speaks about this in Berakhot (Talmud) chapter 4, Mishnahs 5 and 6 and this practice is even found as early as I Kings 8:35-36. In Islam, this qiblat was used for over 13 years, from 610 CE until 623 CE. Seventeen months after Muhammad’s 622 CE arrival in Medina, the Qiblah became oriented towards the Kaaba in Mecca. According to accounts from the prophet Muhammad’s companions, the change happened very suddenly during the noon prayer in Medina, in a mosque now known as Masjid al-Qiblatain (Mosque of the Two Qiblahs). Muhammad was leading the prayer when he received revelations from Allah instructing him to take the Kaaba as the Qiblah (literally, “turn your face towards the Masjid al Haram”). According to the historical accounts, Muhammad, who had been facing Jerusalem, upon receiving this revelation, immediately turned around to face Mecca, and those praying behind him also did so.

Related Mecca Entries:

Map courtesy of the Library of Congress

Throughout the week I watched the Senate debate on the District of Columbia House Voting Rights Act of 2009. This bill (which I’ve written about before in its different forms) will give DC residents a token vote in the House of Representatives, while denying us representation in the Senate. (Taxation Without 2/3’s Representation!!) Thursday afternoon the Senate passed the Act after they also voted to add a bogus amendment written by the National Rifle Association to weaken/remove the District of Columbia’s gun laws. The vote showed clearly that the District of Columbia is still Congress’ little colony and even with the Act’s passage, DC residents are no better off than before, except of course, we’ll be governed by 536 unelected officials, instead of 535. Hurrah for continued tyranny masked as progress!

There were two words I heard over and over again during the Senate debate: Founding Fathers. Thomas Jefferson, the third president of the United States, is revered as one of America’s founding fathers and after looking at his map that he drew in 1791 (and attempting to read his nearly illegible text), I’ve come to the conclusion that the Seat of Government that the Constitution gives Congress exclusive jurisdiction over (Article I, Section 8, Clause 17), is also nearly the same geography that was defined as the National Capital Service Area [link to Google Map] when DC statehood was proposed. This area is basically all the federal government buildings around the National Mall and is what I feel Congress should have exclusive control over. So why was the Seat of Government expanded to include the entire District of Columbia when Jefferson clearly drew a smaller vision 218 years ago? I don’t know, but fixing one of the Founding Father’s faux-pas should involve giving DC residents full equality that citizens of the rest of America receive, which means representation in both the House and the Senate.

In continuance of yesterday’s posting, recently Congress changed their rules to allow Senators and Representatives to utilize YouTube to share information with their constituents. Today I noticed a secondary tragic flaw in their layout. Since the residents of Washington, DC are denied representation in the Senate, the coders at YouTube are using the state of the District of Columbia to show videos from different congressional committees. Instead of incorrectly listing DC as a state, they should include a link to “Committees.” Moreover, as you can see above & below, Google maps remove the words District of Columbia at different scales. This further shows how little YouTube/Google cares about the half a million disenfranchised residents of the District of Columbia.

Recently Congress changed their rules to allow Senators and Representatives to utilize YouTube to share information with their constituents. Today I noticed a tragic flaw in their layout. Since the residents of Washington, DC are denied representation in Congress, the coders at YouTube are using the state of the District of Columbia to show videos from different congressional committees, not from my elected “Shadow” Representative Mike Panetta or Congresswoman Eleanor Holmes Norton. Moreover, as you can see below, the Google maps remove the words District of Columbia at different scales. This further shows how little YouTube/Google cares about the people of the District of Columbia:

Back in July of 2007 I found that Google was censoring the imagery of downtown Washington, DC. This discovery lead to an article that was featured on the front page of the Metro section of the Washington Post. In the time since, Google has not updated the imagery, even after the release of Street View for Washington, DC.

The other day they finally decided to update the imagery of Washington, DC. I believe they did this because there were millions of people coming to Washington for the inauguration and they would have been showing them outdated imagery on their maps. Now that the imagery has been updated, you can almost see the message on my rooftop that I installed in the summer of 2006. Since the imagery has a somewhat low spatial resolution, its slightly difficult to make out the words “No War,” and it kinda looks like “No W@R.” Below is the photograph that appeared on the front page of the Style Section of the Washington Post in March of 2007 which shows me standing next to the now-visible rooftop sign.

“The mapmaker on his Washington roof with a message that he hopes will someday be reflected in both government aerial photography and the art he creates from that imagery.” (Photo by Michael Williamson — The Washington Post)

As a cutesy election day surprise, Google announced the release of their Street View feature for the Google Maps of Washington, DC. For the last year and a half I’ve been waiting for Google Maps to include the city I live in, while at the same time planning my next installment of my geopolitical art project Google Street View IED , the first google bomb for Street View.

In June of 2007, around the time Street View was first released, Washington, DC’s imagery was “updated” with newer aerial photography from 2005. However, the central business district of Washington, DC continues to this day being shown using out-dated imagery from 2002, and the rest of the District is being shown using the newer imagery from September 2005. In the time since this”update”, even after I assisted in exposing this passive censorship in the Washington Post, the imagery has not been updated and because of this the new Street View feature suffers.

In the screen grab above you are being shown the massive parking lot known as City Center which was the site of the former convention center. The old convention center was imploded in December of 2004, which makes a gross mismatch. By using outdated imagery the convention center is still being shown on the Google Map, but the Street View imagery shows a completely different temporal view. The disturbing part of all of this is that the USGS imagery is completely available to anyone in the world to download. It’s already being used by Google Maps for the rest of Washington, DC and I’ve been using in my maps as well.

So, Google, when are you going to update your imagery? If its for security reasons, why release Street View? This provides far more “on the ground” information the aerial views profide. Please tell your content providers that the imagery of Washington, DC deserves an update so you can better serve your customers. Maybe you can use your new satellite?

Related Google Maps Entries:

Below are the “slides” used in my presentation for the New York Map Society. Culled from the last four years of entries on this website, the selected maps show the range of my cartographic endeavors. What is missing, however, is my explanation of why I chose each slide.

The presentation was was supposed to go for about 45 minutes and have about 15 minutes of Q&A, instead it went for about 75 minutes and had about 15 minutes of Q&A. In all, I felt it was a very successful presentation and I deeply grateful for the New York Map Society for inviting me and the wonderful staff at the New York Public Library for their assistance.

Sensor Spatial Analysis

Park Circle Quilt – Quicktime Virtual Reality

North, South, East, Westminster – Outdoor Installation

The Republican Party’s vice-presidential candidate Sarah Palin is the former mayor of Wasilla, Alaska. Tonight this website had a visitor from Wasilla, Alaska who looked at this statehood-related map. Upon looking at the city on Google Maps, I found out that Wasilla is a border city where the imagery of the geography shows only a portion of the city using new high-resolution imagery. In some ways, this map proves that Republican Party’s vice-presidential choice was literally off the map.

Related Google Map Entries:

I decided to go to Denver to help a friend shoot video for some different websites.

Below are the photos I took today:

View the rest of the photographs:

I stumbled on to this short video because I trying to find a Wikipedia entry on SmartBike DC (there isn’t one yet). I was originally going to post two Google Maps (see below) showing the number of stations in DC compared to the number of Vélib’ stations in Paris. The point of the two maps was to show that Clear Channel, which was beat out in Paris by JCDecaux, went a little skimpy when planning and implementing DC’s SmartBike program.

Vélib’ was launched just about a year ago on July 15, 2007, with 10,000 bicycles and 750 automated rental stations each with 15 or more bikes/spaces. This number has since grown to 20,000 bicycles and 1,450 stations, about 1 station every 300 m throughout the city centre, making Vélib’ the largest system of its kind in the world. Washington, DC, on the other hand, started with 10 stations, about 120 bikes, and is the first program of its kind in North America.

While Paris is a much larger city, I am disappointed that with all the hype surrounding the SmartBike program, the planners were not as Smart as they could have been. Had they placed racks at *ALL* DC-based Metro stations before launching I would have bought my SmartBike pass immediately and I bet more would-be bicycle riders would have as well. Until then, I don’t see myself purchasing a pass because I can get to all the current locations on my own bike.

Washington, DC’s natural topography features a hill that surrounds the “Federal City,” or the old part of the city below Florida Ave, which was once called Boundary Street because it was the natural line of demarcation. This hill is what stops me from going to some places on my bike versus taking the Metro. Yet the locations of all the SmartBike stations are located below the hill, so why bother using the bikes when mine works fine for this area? For example, I’d rather take the Metro to Tenleytown, hop on a bike there, and take it down the hill to Georgetown.

Anyways, I still want to make a video called “Doing Dumb Things On A Smart Bike,” but I guess I am going to have to wait…

For a comparison of scale, check these two Google Map screen grabs featuring the locations of the Vélib’ stations and the SmartBikeDC stations:

Vélib’

---

---

SmartBike DC

One of the little plugins I installed on this Wordpress blog was a link at the bottom of each post which shows what I had posted the year before. The other day I noticed that my research related to censorship of Washington, DC on Google Maps, which culminated into the lead article in the Metro section of the Washington Post had appeared. I decided to check out Google Maps to see if there had been any updates and to my non-surprise, there hadn’t been. All I can say is: “what gives?” DC residents are still looking at downtown Washington, DC from 6 years ago. People visiting the MSM of the American Indian are still seeing it under construction, the newly built dorms on GWU’s campus are still not being shown, and the list goes on….. So when will the imagery be updated? When will DC residents get to enjoy the benefits of Street View? Google has office in DC to lobby elected officials, but they’ve chosen to keep imagery of their own office outdated. This doesn’t make sense to me.

My next map will feature the area around the 2008 Artomatic venue. On Google Maps, which currently shows the geography in April of 2002, the location is still a parking lot. Since the venue is located within the 12 mile perimeter of passive censorship on Google Maps you don’t see the construction or completion of the office building.

For nearly four years (May 2004 to March 2008) this website was a digital experiment how people find content on the internet. By withholding the contents of this website from search engines I was able to create my own digital island that could be found only by those who knew me or when I would selectively release specific content. Last month, exactly one year after an internationally syndicated article was published about me and my website, I concluded the experiment by lifting the electronic Berlin Wall that prevented search engines from accessing the content on this website. For the last month or so, I’ve begun to watch how people are able to find my content through search engines, and frankly its been nothing short of amazing. In the not-so-distant future I will have a more detailed pre & post search engine analysis posted here.

While this website was unlisted and before the article was published, I used to look at my website IP logs every morning. I would manually trace the IP addresses of every visitor to this website and obtain a decent guesstimate of how the person found my website. This IP analysis would give the location and hosting provider of the visitor, but what it did not give is the digital path that my content traveled.

Data does not travel through the internet in a geographic path of least resistance (like as the crow flies), rather data bounces around the world from server to router to user in a path that can go in multiple directions and routed through multiple servers before finally reaching your computer. A trace route is a means to see what servers the content passes through before reaching you. By clicking on the image above you can explore how content travels to your computer using the Google Maps interface to see exactly where the content travels. For example, data from www.Google.com makes 42 unique hops before finally reaching my computer. A fun experiment would be to trace how content from this website arrives on your computer screen.

Watching the route trace itself looks much like a sped up version of “The 21 Steps by Charles Cumming,” which is a cartographically interactive story told through the Google Maps interface. Each stop becomes a new chapter in the information’s delivery. How many stops did this blog entry take to get to you?

Related GIS:

Federal Triangle Quilt #3 with Chinese signature

Using some of the funds from my DC Commission on the Arts & Humanities 2008 Young Artist Grant, I purchased the first set of prints that will be shown at next month’s Artomatic exhibition.

One of Kodak’s newest products is their fleece blanket, which is 100% polyester, machine washable, and frankly, are a very good deal at about $45 each. I’ve been waiting a long time to print my maps on large media cost-effectively and fortunately the size of these blankets match the aspect ratio of my maps (3:2) so I can upload my 9,000 x 6,000-sized maps (one half the original rendering size) without any extra image manipulation. Or so I thought.

Last night I was using Google Maps and discovered that the label for the National Museum of the American Indian has been truncated to be “National MSM of the American Indian.” This raised alarm because the shorthand for MSM is more recognized as “MainStream Media” not museum. Native Americans have been shortchanged for hundreds of years by the American government, and I found it downright rude that the museum’s name has been cartographically shortchanged as well. So why shorten the name?