The Daily Render

by

A Digital Scrapbook for the Past, Present, and Future

| FRONT PAGE | GEOSPATIAL ART | DC HISTORY / TIMELINE | NEWS | COLONIST | FOUND MAPS | FRACTALS |
| PHOTOGRAPHY | ANTIQUE | DESIGN | VIDEO | PRICE LIST | RANDOM | CONTACT |


i'm currently on daily blogging sabbatical, but i'll be back very soon.

A new change in Washington, DC’s imagery on Google’s servers
|| 7/10/2007 || 9:42 am || 2 Comments Rendered || ||

For the last 3 years I have followed how the aerial & satellite imagery of Washington, DC has been released, redacted, and remixed. This entry marks another important observation and a new discovery in Google Maps.

washington dc 2007 A new change in Washington, DCs imagery on Googles servers

Last week I discovered the extent to which Google has updated their servers with the 2005 USGS aerial photography. My findings suggest that Google has censored much of downtown Washington, DC by not using a substanial amount of newer imagery.

Continue reading:

When Google Maps was first released, Washington, DC was displayed using USGS aerial photography taken in April of 2002. This is the same aerial photography that I’ve used for most of my DC maps. I am under the impression that public input requesting the White House be redaction-free forced Google to change the imagery for Washington, DC.

This resulted in slightly new imagery of Washington, DC from Sanborn. When I state “slightly newer” I mean, only a couple months at most. The construction of the World War Two Memorial and the Mandarin Oriental Hotel show that the two were taken only months apart. Google kept both sets of imagery on their servers, which explains the nature of the two toned diamond of the Washington, DC metropolitan area. The brown edge was 2002 imagery and the central diamond was 2002 imagery from Sanborn.

Screenshot from 8/17/2005
new dc mosaic A new change in Washington, DCs imagery on Googles servers
: Imagery Analysis :
new dc mosaic 2005 update A new change in Washington, DCs imagery on Googles servers

It was like this until June 2nd, 2007 when Google added the USGS 2005 imagery. I had been beating google to the map since March of 2007 when the imagery was first released to the public. I made a total of 8 maps in before Google got around to updating their servers.

Screenshot from 7/2/07
google change in dc A new change in Washington, DCs imagery on Googles servers
: Imagery Analysis :
google change in dc map A new change in Washington, DCs imagery on Googles servers

There were four known areas of redaction by the National Geospatial-Intelligence Agency
• the White House
• the U.S. Capitol
• the Washington Monument
• the U.S. Naval Observatory

But now you can see below much of DC’s central business district has been purposely outdated by Google. This method of keeping the old imagery and surrounding it by new imagery Google is actually censoring MORE than the NGIA! This is a de-facto form of censorship being done by Google.

Close-Up of 2007 imagery
google dc 2007 A new change in Washington, DCs imagery on Googles servers

The three areas below in yellow are already redacted in the 2005 aerial photography dataset by the NGIA. The area in red is the outline of the area which Google is censoring, which, as you can see, is larger.

washington dc 2007 redacted A new change in Washington, DCs imagery on Googles servers

The perimeter of censorship is roughly 12 miles around:

google censorship perimeter3 A new change in Washington, DCs imagery on Googles servers

….How I discovered the censorship….
On June 28th DCist had a feature on someone who was caught joyriding in a field on Google Maps. I had a pretty decent idea of when the imagery was taken and wrote a comment that I never posted. Later that evening the blog entry was covered by the Fox News affiliate in Washington, DC. It wasn’t until last week when I was about to start to publishing the new Adams Morgan maps did I discover that Google had updated their servers. As I was zooming into Adams Morgan for the blog link I noticed that the imagery was now the same for Adams Morgan, but not for the entire DC area…..

I had read before that Google Maps had an easter egg that allowed users to zoom-in even further than what the built-in zoom feature allows. This is done by adjusting the zoom level in the link to the google map (below).

Example at the line of redaction at 16th & S Street, NW, Washington, DC:
http://maps.google.com/maps?f=q&hl=en&geocode=&q=washington,+dc
&ie=UTF8&t=h&om=1&ll=38.914083,-77.036259&spn=0.001029,0.002489&z=19&iwloc=addr

By adjusting the “z=19″ to “z=20″ one can see the line of redaction because the old imagery becomes blurry:
http://maps.google.com/maps?f=q&hl=en&geocode=&q=washington,+dc
&ie=UTF8&t=h&om=1&ll=38.914083,-77.036259&spn=0.001029,0.002489&z=20&iwloc=addr

What I discovered was that Google has kept the original .16 meters per pixel imagery on their servers! The difference between the USGS 2002 & 2005 imagery is of spatial resolution at .3 meters per pixel and .16 meters per pixel, respectively (roughly 1 foot vs 6 inches per pixel, a 4X increase).

I believe this change in spatial resolution is why Google has chosen to censor parts of Washington, DC, but I don’t understand the extent. The censorship is more than what should be required for national security- like the White House, U.S. Capitol, Washington Monument, or the U.S. Naval Observatory.

The 2005 USGS aerial photography is available for anyone in the world to download, which Google had to do to in order populate their servers. Yet a large portion central Washington, DC is being withheld by Google. Thus Google is placing priority over old proprietary imagery instead of public domain government sponsored imagery.

Questions:
1) Is it okay for Google to censor Washington, DC?
2) If National Security is the reason for the censorship, why are some areas still available to be viewed in .16m resolution?
3) Will the central business district of Washington, DC be updated soon?
4) Could Google have redacted Washington, DC to highlight the historical nature of DC’s maps by moving the line up censorship north to the area historical defined as the Federal City? (this is the area south of Florida Ave, once known as Boundary St. This area contains most of the historic homes of Washington, DC.)
5) Since I can obtain the imagery that Google has withheld from the general public, will the maps I make in the hidden area be more valuable?

Related Maps:
• The U.S. Capitol is Off-Limits To the Public
• The White House is Off-Limits To the Public

Related Analysis:
Comparitive Meta-Data of the USGS Orthoimagery of Washington, DC

This blog entry has made it’s way to the Washington Post:
Google’s View of D.C. Melds New and Sharp, Old and Fuzzy

####UPDATE – 7/29/07 #####

– The area that was not updated is also the exact same area that shows the 3D buildings:
3D buildings nadir A new change in Washington, DCs imagery on Googles servers

– I made a MyGoogleMap of the 12 mile perimeter that shows the 2002 imagery:
dc update map A new change in Washington, DCs imagery on Googles servers




####UPDATE – 1/21/2009The imagery was finally updated in January of 2009.


Related



Post Title: A new change in Washington, DC’s imagery on Google’s servers
Post Tags: , , , , , , , , , , , , , , , , , , , , , , , , , ,
Posted in: Activism, Building, Cartography, Censorship, DC, Found Map, GIS, Google, Google Earth, Google Maps, history, Location, News, orthophotography, visualization, Washington Post
Last edited by Nikolas Schiller on 11/30/2009 at 1:06 pm



  1. You mention how you found the censorship, but I don’t see why you think Google would censor/how they would benefit……………….

    Comment by Tom — 7/23/2007 @ 4:04 pm

  2. Frankly, I don’t know how Google would benefit from the censorship. It goes against their philosophy.

    The NGIA already censored the 2005 imagery (maps above), so why is Google censoring more than the NGIA?
    Thats my central question. I don’t have the answer, and the article in the Washington Post did not answer it.

    I’d rather have Google come out and say “We were asked to censor downtown DC.” or just have them update the rest of DC with the new imagery and keep the old imagery for the places that the NGIA censored.

    Comment by Nikolas Schiller — 7/23/2007 @ 4:24 pm

+ RSS feed for comments on this post.

Sorry, the comment form is closed at this time.





The Daily Render By
A Digital Scrapbook for the Past, Present, and Future.

©2004-2014 Nikolas R. Schiller - Colonist of the District of Columbia - Privacy Policy - Fair Use - RSS - Contact




::SUBSCRIBE::


+ Facebook
+ Twitter
+ YouTube
+ MySpace
+ Google
+ Vimeo

::LAST 51 POSTS::

Fair Use


12 queries. 0.687 seconds.
Powered by WordPress


Photo by Charlie McCormick
Nikolas Schiller is a second-class American citizen living in America's last colony, Washington, DC. This blog is my on-line repository of what I have created or found on-line since May of 2004. If you have any questions or comments, please contact:

If you would like to use content found here, please consult my Fair Use page.

::LOCATIONS & CATEGORIES::





thank you,
come again!

::THE QUILT PROJECTION::

Square
Square

Diamond
diamond

Hexagon
hexagon

Octagon
octagon

Dodecagon
Dodecagon

Beyond
beyond

::OTHER PROJECTIONS::

The Lenz Project
Lenz

Mandala Project
Mandala

The Star Series


Abstract Series
abstract

Memory Series
Memory

Mother Earth Series
Mother Earth

Misc Renderings
Misc

::RENDERS BY YEAR::

+ 95 in 2008
+ 305 in 2007
+ 213 in 2006
+ 122 in 2005
+ 106 in 2004

::POPULAR MAPS::

- The Los Angeles Interchanges Series
- The Lost Series
- Terra Fermi
- Antique Map Mashups
- Google StreetView I.E.D.
- LOLmaps
- The Inaugural Map
- The Shanghai Map
- Ball of Destruction
- The Lenz Project - Maps at the Library of Congress
- Winner of the Everywhere Man Award

::ARCHIVES BY YEAR::

+ 2011
+ 2010
+ 2009
+ 2008
+ 2007
+ 2006
+ 2005
+ 2004


::MONTHLY ARCHIVES::

:: LAST VISITORS ::