Commentary

Stephen Wellman
 

Will The CIA Censor Google Earth?

Controversy surrounding satellite mapping services like Google Earth continues to grow. This week Vice Admiral Robert Murrett, the head of the National Geospatial-Intelligence Agency, told AP that commercial satellite services may need to be edited or censored to protect U.S. interests. Is this just another example of someone who can't deal with the reality of the Web?

Controversy surrounding satellite mapping services like Google Earth continues to grow. This week Vice Admiral Robert Murrett, the head of the National Geospatial-Intelligence Agency, told AP that commercial satellite services may need to be edited or censored to protect U.S. interests. Is this just another example of someone who can't deal with the reality of the Web?Right now the U.S. government could do two things to control what images are shown over the Web. First, it could buy all available satellite images and only release what it wants to. This is what the government did during the early phases of the invasion of Afghanistan, but that also was before services like Google Earth made accessing satellite images so easy. The second thing is to restrict funding to many of the companies that provide satellite imagery services.

While these two solutions might work for U.S. companies they won't stop satellite images coming from international sources. And as developing markets like China and India launch satellites and collect images, it will become harder to control what goes live.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

I think this is another example of an entrenched institution that wishes the Web wasn't there. Just like the RIAA, government leaders who want to control what satellite images go on the Web seek to institute controls that simply are no longer feasible.

What do you think? Does the U.S. government need to censor what images go live on the Web? Or does it need to embrace the radical transparency that Web 2.0 brings to the world?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links