Google earth pro license Archives

Google earth pro license Archives

google earth pro license Archives

google earth pro license Archives

Talk:Google Earth/Archive 1

This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

"Persian Gulf" is Persian Gulf for ever not Arabian Gulf!!

There is one question why Google Earth does not want to accept that Persian Gulf has only one name which is "Persian Gulf". In case, Google Earth does not want to remove "Arabian Gulf false name", the Iranian users will boycott the Google Earth which is not good for Google Company.


The article states "Unlike the satellite images, the orthophotography has a perspective from close to the surface, leading to distortions when used in a mosaic." If this is true, then it isn't orthophotography - it's just bog standard aerial photography. --Bazonka 23rd July 2006

Perhaps the distortions mentioned are things like the severe tilt of buildings and the weirdness that can occur when different tilt orientations are mosaicked. The spatial distortions of aerial photos can be corrected and made into orthophotos, but things like tilt remain.Pfly 07:44, 20 January 2007 (UTC)

Ahh, finally

Something I can take the world over with. To be serious, NASA world wind is more of a national threat because of its ability to be opensource. However the terra server connected to google earth could be a problem if someone could enable a live-feed satellite script with a gps tracking device. Skynet terminators all around. How about a nice game of chess?--Cyberman 23:36, 17 February 2006 (UTC)


How did everyone miss the fact that the territory of Nunavut in Canada is missing!? Has this already been discussed or am I missing something here...because I see no mention of it anywhere?

--Scott110 8 February 2006

Nunavut exists today. Maybe it was added with the April 18 update [1]? The text should perhaps be revised/removed? --Strangnet 17:08, 23 April 2006 (UTC)

Google Earth live video feeds?

Some satellites capture live video footage of the ground, so what would it take for Google Earth to give us live video feeds of anywhere we decide to look in the world?

--Shultz 10:50, 4 November 2005 (UTC)

A million satellites that can cover every point on Earth simultaneously? EamonnPKeane 21:25, 18 December 2005 (UTC)

Well it obviously isn't very plausible right now, but in reality a very very wide angled-lense could do just this.. With enough correct algorithms attached to it to be able to display the image on the globe.. and the camera being capable of at least multiple gigapixels or a terapixel.. this is certainly somewhat plausible, just not in the very near future. Check this out. Gigapixel cameras already exist. Drumguy8800 22:31, 18 December 2005 (UTC)

I'm not so sure that would be legal to have live feeds. You can easily carry out immensely accurate espionage and stalk someone as much as you want. Do you think i'm right? (I am extremely open to criticism on that). Ardo 02:29, 8 March 2006 (UTC)

Three words: Indoors; cloud cover. - Kookykman|(t)e 20:59, 12 August 2006 (UTC)

I don't think live feeds would be legal either. Hostile countries could just open their Dell Laptop and spy on the US and other countries. Terrorist could also use it to their advantage.

off topic

This section (Google Earth live video feeds?) is off-topic, because it's about the subject of the article, not about the article itself. I'd like to remove this section, but I will not do that today. --HelgeStenstrom 20:24, 10 September 2006 (UTC)

Wiki GPS References

I think we should create a page to list interesting links to the Lat and Long. Maybe all geographic discussions in Google should have their position in the same format so we can see them easily on Goggle Earth (grin). The other thing is that interesting pictures like the stealth fighter at 34D 38M 14.60 and 118D 04M 55.41 will disappear when the image is updated - sad! Maybe we need to archive the interesting pictures!--Dajuroka 06:36, 8 January 2006 (UTC)

I agree... There's a whole WikiPedia integration in google maps, and I'm trying to figure out how to properly tag things. In my test case, there's a really cool cemetery in Manchester, NH... It's already got a WikiPedia page, and I want to tag the coordinates so it will automatically show up as a wiki-tagged POI in Google Earth. I found that I could tag the coordinates in WikiPedia like this: 42°58′59.56″N71°27′36.42″W / 42.9832111°N 71.4601167°W / 42.9832111; -71.4601167 , but am having trouble figuring out how it would all go together. --DigitalSorceress 18:56, 26 August 2007 (UTC)
Hah! answered my own question - --DigitalSorceress 19:07, 26 August 2007 (UTC)
That works for an article with a single coordinate. If an article has multiple coordinates, such as Arlington National Cemetery, the new |name=Label for Point parameter should also be defined in {{coord}} usage so the labels will appear (after coord gets updated). (SEWilco 20:32, 26 August 2007 (UTC))

Photo sources

Besides the Keyhole images, does Google Earth use USGS U.S. urban aerial photos? I guess so. For example, I found Google Earth's Space Needle (Seattle) (47.620496°, -122.349284°) looks just the same as NASA World Wind's (see the shadow). -- Toytoy 09:14, July 19, 2005 (UTC)

Information on image provider could generally be found at the bottom of the satellite image. It would be specified whether the image comes from EarthSat, DigitalGlobe, Tele Atlas, etc. --Plastictv 07:38, 1 September 2005 (UTC)

Yes, but these are image providers, not satellite platforms. So it is still difficult to determine which platform took a particular image using Google Earth (basic or plus). I've heard the the "pro" version allows users to see metadata. But I have not shelled out the money to verify this.Chunchucmil 17:09, 22 January 2007 (UTC)


It could be faster, my average speed is 12 Kbps, maximum speed is 60 Kbps (on a 10 Mbps connection), it took several minutes for the "Three Sisters" to appear.--Jerryseinfeld 14:24, 20 July 2005 (UTC)

I am an ADSL user living in Taiwan. It took me less than 2 minutes to download the "Three Sisters" on my 1280x800 monitor. Google Earth usualy runs a little faster than NASA World Wind on my connection. -- Toytoy 15:15, July 20, 2005 (UTC)


I might just be a nerd, but this whole idea seems remarkably similar to the Earth program in the cyberpunk novel Snow Crash, by Neal Stephenson. I mean, it's not like its a completely new idea, but still. --_mich 16:21, July 25, 2005 (UTC)

That's because it is like Snow Crash. --Gmuir 18:22, 17 May 2007 (UTC)


How does one add locations that everyone else can see? I've joined the Keyhole Community, found a forum where I seem to have posting rights, but I can't find a button that says "new post". Thought my fellow Wikipedians might know....


I don't think that Taiwan is listed as a province of the People's Republic of China anymore, on Google Earth nor Google Maps].[2]Theshibboleth 21:35, 25 November 2005 (UTC)

It's listed as Taiwan

Mac OS X versione

Link ( mirror ) link for download

Upload a *.kmz

Wikipedia's Upload File function currently does not support *.kmz uploads -- I think that, given the power and influence and wealth of data on the Google Earth program, that it would only be fitting to allow *.kmz uploads on wiki sites.

The *.kmz is Google Earth's placemark (or other addon like 3D render) feature. It would be very instrumental when an encyclopedia article gives an address.. or for all geographic pages. The *.kmz file works just like a link in any browser -- a user clicks, and google earth zooms to that location. You can specify tilt, orientation, etc. Could even be used for a "virtual tour" of the Grand Canyon -- which is very impressive, if anyone hasn't checked it out on Google Earth. Anyway, I'm interested in doing a mass implementation on the Dallas/Fort Worth Metroplex pages.. both for cities and structures in the cities. Drumguy8800 07:30, 16 December 2005 (UTC)

I agree that kmz and kml files should be uploadable - not for the GE page but so geographical locations could have the file at the bootom. Flutefluteflute

Windows versions

It says that this program is available only for Windows 2000 and XP. Is it going to be discontinued for later versions?? Georgia guy 22:47, 4 January 2006 (UTC)

It does seem to be for nt5+ only. Google tends to do this, supporting only NT versions. Much easier for them to maintain. The only Google software that still runs on early systems is Google Toolbar, and maybe picasa -- 02:26, 11 February 2006 (UTC)

Take a look at the Google Earth Community, a forum/bulitin board for GE users. You can could post KMZ files there and link to them from Wikipedia. You can also find out if anyone else is working on (or has already completed) a similar project.

Sea level

The cursor also gives on-screen feedback on the height (above sea level) of all geographical locations. But when the cursor is over the sea surface proper, it can indicate that the sea level falls and rises like a hilly landscape! Also, higher definition views of the sea show it as a hilly area. Any explanation welcome.Politis 17:53, 27 January 2006 (UTC)

From observing the coast off sub saharan africa, I noticed the water looked like a shelf that dropped out into the atlantic ocean. Maybe it shows a rough elevation under the water (like the seabed)...? Ardo 02:33, 8 March 2006 (UTC)

Units of measurement

"Notably, the default setting is to U.S. customary units, despite metric units being the international standard used by every nation but 4 (the U.S, Liberia, Myanmar, and the United Kingdom all using the slightly different British measures), leading to accusations of cultural imperialism."

This should be checked. I don't know about the others, but the UK officially uses metric (is there an exception for beer?) The US doesn't use Imperial in any case; US measurements follow their own standard. Njál 23:44, 8 March 2006 (UTC)
There is a lot of talk on this in the metrication article, which states that only UK, US, Liberia and Myammar have not *fully* converted to the metric system. UK is largely converted, but US is not. I think the phrasing in this article may be misleading.
I love the attempted defence of US-bias. As I read it, much of the web is biased so Google should be also. Although Google is a US corporation, I wonder if the majority of their customers really are American. 23:14, 28 March 2006 (UTC)
Please provide references for this assertion. Smells like editor invention to me. Products made in the US nearly always provide US units as default. A tempest in a teapot over less than ideal defaults, or editor invention? JoshuaRodman 10:19, 4 April 2006 (UTC)

If you use the metric system, you can just change the default. It's not that hard. So I don't see what the big deal is. And although Americans might not be the majority of users of Google Earth, they are at least 45% of the users.

Measurements still default to Imperial at each program launch, regardless of user preference settings. Fehrgo 18:19, 11 September 2007 (UTC)
Are you using linux? Have you given write permission to your user folder's program settings?--Lazer erazer (talk) 17:33, 17 November 2007 (UTC)

External links and definition of 'Google Earth'

Maybe the number of external links should be cut down a little. Some of the titles are POV ("The Best German Google Earth Community") — but there are at least two German forums listed, and I don't know if noe or the other has more claim to Wikipedia linkage. Is there a guideline on what to name external links on Wikipedia? I think it would be good practice to make the name of the website the link, with explanatory comments in brackets if necessary.

A separate article dealing with the Google Earth community would be a good place for these links. It's somewhat unclear whether the article is about the computer program, its data, or the entire project. Njál 23:45, 8 March 2006 (UTC)

The status of Tibet is disputed?

I don't think the current status of Tibet is debatable enough for its inclusion under China on a contemporary map to be considered controversial. It's not recognized as an independent state by any country, nor does it have any de facto sovereignty. There's nothing wrong factually with not labelling Lhasa a national capital, either. So where does the dispute come from? Even if you can't stand the democracy record of Chinese government or the way they took over Tibet, please, leave this political statement out of the article - Google simply stayed neutral.

Tibet is not a recognized nation, at least by the united states, since google is in the united states, their recognition of countries goes mainly by those recognized by the u.s.--Olavid 20:08, 3 September 2007 (UTC)

Images uploaded from google earth

What lisence should we use when uploading an image from Google earth to Wikipedia??????? Please help me, I have to upload images on the Greek Wikipedia. -- 14:16, 19 March 2006 (UTC)

Previously, there used to be a satellite image of Greenvale, Victoria on its page. However, this was taken off because copyright problems with it. I was wondering if there is any way possible to make Google Earth images legal. --DChiuch 01:07, 23 April 2006 (UTC)

Images/screenshots of Google Earth are copyrighted. Therefore, they can only be used if it's fair use. For example, an image of Google Earth used on the Google Earth article depicting Google Earth and/or the Google company would be considered as fair use, but using it to depict other items off-topicly (I.e. The building of a company not related to Google) would not be fair use as far as I know. It would be great to have a source of free satellite images, though... I believe that most NASA images are not copyrighted.—G.He 00:05, 20 May 2006 (UTC)
Just use NASA World Wind. All images are in the public domain. - Kookykman|(t)e 22:56, 14 August 2006 (UTC)
I don't quite understand the legal issue. First, the images on the Google Earth Wikipedia article have a warning that they do NOT have adequate rational for Fair Use. However since Wikipedia has teamed up with Google Earth to create Wikimapia, could we use screenshots of Wikimapia in other articles on Wikipedia? For instance, a Wikimapia screenshot of a city on that city's Wikipedia homepage? Of course, the suggestion to simply use NASA data is a good one. All NASA images are in the public domain. But it would be nice to be able to use some Google Earth or Wikimapia screenshots in the content of various articles on Wikipedia. Any further advice / clarification would be greatly appreciated. Chunchucmil 15:24, 21 January 2007 (UTC)
I think there is a distinction between uploading imagery of the application, and the imagery Google Earth presents (and has licensed). Uploading images where the subject is the application is probably OK (especially if just showing NASA imagery), uploading copies of the images is redistributing images licensed to Google and is not allowed. It makes no difference that you can view it for free in Google Earth. Halsteadk 21:56, 21 January 2007 (UTC)
I have contacted Google Earth for a clarification of its use on Wikipedia. As this will likely take weeks for them to talk with lawyers, I'll post their response when I get it.Chunchucmil 17:03, 22 January 2007 (UTC)
I'm interested to find out what they say Chunchucmil. When we have an authoritive reply, a relevant entry for Google Earth images should be added to Wikipedia:Image_copyright_tags/Fair_use. I personally think it is silly for them not to release the images under the GPL, but who knows what legal minefields they had to negotiate. Aschoeff 21:51, 11 February 2007 (UTC)
Any news on this? Fehrgo 18:22, 11 September 2007 (UTC)
They never responded :-( Chunchucmil 16:57, 16 September 2007 (UTC)

Newer Screenshots?

I think the screenshots on the article are out-dated (Uploaded newer version)—G.He 16:30, 20 May 2006 (UTC) Should it be updated or will it not make much of a difference?—G.He 00:08, 20 May 2006 (UTC)

Given the newest versions of Google Earth and the fact that the 3d abilities are one of its major features, does anybody else think a new image is in order? Nrbelex(talk) 06:11, 13 June 2006 (UTC)

Newer Windows Versions?

Why isi it that Google Earth rleased its last Windows Version on November 18, 2005? We are in June 2006! Please check into this! -- 13:02, 11 June 2006 (UTC)

There's already a new version of Google Earth: version 4 BETA. Please update the article.

Google Earth 4.0

Google Earth 4.0 Beta Is now Available

Download Page

The fallowing is Pritty Close to a Quote from the websight. Please Paraphrase if you want to include it in the article.--E-Bod 02:48, 14 June 2006 (UTC)

Linux Support

Google Earth in French, Italian, German, and Spanish.

improved the terrain

  • peaks and valleys are more realistic

The Fallowing is What i noticed when i used it (remember WP:NOR, I'm not sure if we can use this). I typed this in a rush. Feel free to corect my spelling. I will go back to fix my spelling later.

  • Diffrent look
  • Bookmarks can be Edited Im mutch more Detail like Altitue and lat/longe-itude
  • E-mail Placemartk, View, Image
  • Share post
  • You can show lat/longi-tude on map (I don't know if this is new or not)
  • You can turn of the Atmosphere (The halo around the planet but i don't know if this is new)
    • Usefull if you put a new planet Image overlayy
      • I noticed one of Planet image overlays that work for regualr GE don't work while the Main image file for the planess do--E-Bod 03:17, 14 June 2006 (UTC)


It mentions the critisisms regarding showing of military installations etc. Does anyone know if there are problems between google and the USA due to the detailed pictures of Area 51 and the pentagon etc. available?

Not sure, but I do remember how many other countries around the world were well pissed off though, because sensitive locations (e.g. military bases) were being blanked out by Google for the USA but not other nations. I believe they have started blanking out sensitive locations all around the world now. --Spet1363 19:43, 22 July 2006 (UTC)
Not quite right, one can see all sensitive locations (Airforce bases, Nuclear power plant, big dams etc) of India on GoogleEarth/Wikimapia. Vjdchauhan 11:12, 8 November 2006 (UTC)

Arent there any other criticims which involve the fact that google earth is a very powerful tool, that freely gives any human being the right to view any area of the earth. Almost scary when you actually think about it. My opinion at least, we should never have such information at hand like that.

No, quite right, humans should be locked in the dark, with access to as little information as possible. Of course we should have access to this! It's collectivly our Earth, why shouldn't we be able to see the bits of it we want in the detail we want? --TheIslander 20:36, 20 August 2006 (UTC)

Removed following line: "The imajury of the caribbean is old, and out dated from around 2003. The imagery should be updated in even the smallest parts of the world and not just the larger cities." Sounds more like a personal opinion than a criticism --Cirilobeto 05:39, 7 November 2006 (UTC)

Have removed the reference to Birmingham in the section on US bias. Searching for Birmingham now gives Birmingham, UK, in contrast to what the article said. St. Petersburg, however, still gives the American city, not the Russian one. Have also corrected the spelling of the subtitle here on the talk page, being pedantic. Owl 12:36, 16 December 2006 (UTC)

Iguazu Falls Dispute

The parliament in Argentina is going to debate to ask google to correct argentina-brazil limits since a mayor touristic point, the Iguazu Falls, appear completley in Brazil, when in reality is in the border and even most people prefere visiting them from Argentina Side, non existent in google hearth. Argentina authorities presume that the mistake can lead to people planning the trip to Iguazu choose Brazil instead.[3]--

Google Maps

Is it anything like GoogleMaps? -- 05:32, 21 August 2006 (UTC)

Yes and No. Read the Wikipedia articles Google Earth and Google Maps and tell us what you think! AuburnPilot 02:46, 1 September 2006 (UTC)

National Security and Privacy Issues

This paragraph makes little sense to me. Anyone else think so? Landroo 02:27, 25 August 2006 (UTC)

'The 2006 incidental finding of a large topographical replica in the remote Huangyangtan region of China, purportedly a small-scale recreation of the Karakoram mountain range currently under Indian control. When it was confirmed that the territory modelled corresponded to a politically disputed borderline between the neighboring nations, spectators began to entertain sinister military implications.'

Definitly was poorly written. There are several fragments and grammatical mistakes. I'll attempt to revise it. AuburnPilot 02:51, 1 September 2006 (UTC)
Done. AuburnPilot 03:01, 1 September 2006 (UTC)

Use in media

I think it would be interesting to add some section about the usage of Google Maps images in the media. For example I know about Google Earth images being used in Crank and in some British Airways advertisements in the UK. I would start the section, but these are the only two references I know, I think it would be better to start with some more complete information --NavarroJ 14:22, 17 September 2006 (UTC)

3D Signage Tool

I added a new link in the tool section.

It links to a Google SketchUp Plugin for creating 3D signage in Google SketchUp -> the 3D signage can then be exported as a KML model straight into Google Earth. I believe it belongs in this section for the Google Earth article, as it is just that a tool for getting 3D signage into Google Earth!!!! I use Google Earth alot, and develop tools for Google SketchUp and this tool was specifically developed to do something which couldn't be done before. Look around the internet you won't find much 3D signage in Google Earth. Thats because until now tools haven't really be readily available to do it. Please do you homework on the topic, maybe read this other wiikipedia article I have created on the topic Google SketchUp 3D Text - before making comments.

I don't understand why people on wikipedia actually remove things before discussing edits. Its counter productive to the way a wiki should work. Ashleyjoyce 00:03, 23 September 2006 (UTC)

It’s really quite amazing how 3D buildings are being placed on Google Earth. For example, Seattle has but one textured building in its downtown core, whereas virtually every building in downtown Denver has been rendered.

My quibble lies with some of the comments being attached to these textured structures by their modelers. A pair of examples will illustrate my concerns. In Washington DC, the Capitol building reads “Spent the weekend snowed in so I decided to model the U.S. Capitol Building.” The Vehicle Assembly Building at Cape Canaveral reads, “Not quite done yet, but its something.” Is this appropriate for such a professionalism program? ( 17:36, 2 April 2007 (UTC))

aint none

why does the site blurr out and cannot foscus —The preceding unsigned comment was added by (talk • contribs) 21:24, 28 September 2006 (UTC)

msn messenger plugin

hello my friends just wondering about msn messenger contacts showing where they are with google earth is it a future program just send me a message .User:Jonjoe

google earth with msn messenger

How frequently Google Earth updates its satellite imagery

Do we have this data about how frequently does Google Earth updates its satellite imagery to cover newer areas (e.g. over past 6 months or so I have seen only one (prominent) update of Indian cities and now most of smaller Indian cities (apart from earlier bigger cities) are too having high resolution imagery still large tracts of (including some smaller cities/towns and most of rural area) is not covered with High resolution imagery. Regards, Vjdchauhan 10:45, 8 November 2006 (UTC)

I think from time to time, not faster than once per 1-2 years. Alexandre Koriakine 10:50, 8 November 2006 (UTC)

I can tell you this: images of the Greater Vancouver Regional District were almost certainly taken before the summer of 2005. The state of construction on the Vancouver Convention Center, Simon Fraser’s University, and the Fraser Highway extension between 176 ST. and the Langley border, all correspond neatly with the period. In addition, the Infinity project, which broke ground in June 2005 at the corner of 100 AVE. and King George Highway in Surrey, is not visible on my maps.( 21:39, 4 April 2007 (UTC))

Cyprus Naming Dispute?

"Cyprus is shown only as only belonging to Greece and does not show the Turkish half with its' own capital Lefkose."

I removed the information about the cyprus naming dispute in google earth, because: a) Cyprus is not shown as belonging to Greece in google earth. b) Republic of Cyprus is recognised as being sovereign over the entire island. c) Turkish Republic of Northern Cyprus is a defacto state and is not recognised apart from Turkey.

In essence, the dispute is not a google earth dispute but a political dispute. It doesn't really transcend into google earth. Aggelophoros 08:31, 13 November 2006 (UTC)


why that only is half of Edinburgh, Scotland is only shown on GoogleEarth, User:Jonjoe

please ask Sergey Brin or Larry Page sir :) Ammar 12:43, 28 February 2007 (UTC)

Wikipedia Lat/Long co-ordinates implementation into Google Earth

Hey this is a question which involves Wikipedia and Google Earth. I've just started to update Melbourne railway station articles with lat/long co-ordinates but the articles which I have recently added some to don't show up in Google Earth. Does anyone know how long it takes for articles with new co-ordinates to show up in Google Earth? Thanks. --Lakeyboy 02:07, 11 December 2006 (UTC)

I added a new section to the main article describing this new capability. The section still needs a lot of work. I have the same questions as Lakeboy about how often the data is scraped and confirmation of which coordinate templates to use. Theflyer 13:49, 14 December 2006 (UTC)
I'll email the development team, I have the email. -- Zanimum 14:34, 14 December 2006 (UTC)
Actually, emailed Greg Maxwell, a fellow Wikipedian. He says that Google downloads our database dump. When they do, it figures out which articles are newly updated with coordinates or new pics. From there, the articles are approved, and Google makes sure all of the images are legally okay (and that they're not inappropriate). From there, their posted. Since the dumps only happen, I dunno, every two weeks, and it takes a while I presume to approve pictures, it's not an instant process. For now at least. It sounds like they are actively developing it, that's it's not just a "one-timer" release. -- Zanimum 22:13, 14 December 2006 (UTC)
@Lakeboy, maybe this new KML will help you. -- sk 00:18, 15 December 2006 (UTC)
So we actually have a downloadable file devoted to article coordinates? -- Zanimum 16:34, 15 December 2006 (UTC)
Check in google earth in the bottom leftt in the layers section for "Geographic Content" - open this folder and tick the Wikipedia box. If you can't see it get the latest version of Google Earth from the official website.-- FluteflutefluteTalkContributions 16:48, 15 December 2006 (UTC) -- FluteflutefluteTalkContributions 16:50, 15 December 2006 (UTC)
Does anyone know what application, server, or script is used to scrape for coordinates in Wikipedia? If one had their own mediawiki and their own google earth server, what middleware is needed to achieve the same integration that occurs here? -Mike BW 12 JUN 07

Superimposition vs. Superimposing.

If you look at superimposition it's about pictures whereas superimposing is video. So I changed it. CRouleau 14 December 2006

User Boxes

Here are some user boxes for google earth.


--'•Tbone55•(Talk)(Contribs)(UBX) 17:43, 19 December 2006 (UTC)

Usage by CNN and media

Is it worth mentioning that CNN uses Google Earth in various news reports on their cable network? Gordeonbleu 22:58, 15 January 2007 (UTC)


G'day, I'm new to this google earth, I see in the "help" section that there is a tool called layers, how does one find this tool so I can get street names to appear, I can't find layers on the tool box on the left hand side of the screen, anyhelp would be great thanks... —The preceding unsigned comment was added by (talk) 06:04, 4 February 2007 (UTC).

Removed excess from Specifications section

I removed the following text from the specification section. It was there as an example for the age of images. If it belongs in the article, perhaps a new section is needed. But I think it could just become a long ugly list.

"The San Francisco picture around Octavia Boulevard shows the Central Freeway that was damaged in the 1989 Loma Prieta earthquake partially still standing and with cars on it. The picture must have been taken between 1992, when the freeway north of Fell Street was demolished and the remaining portion reopened, and 2003, when the remainder west of Mission Street was demolished.

For example, the image area around Taipei 101 shows the building before the red construction elevators were removed in 2004 and the new WAPA Path 15power line is still under construction (also in 2004).

When viewing downtown Boston, one can see the old elevated Central Artery as well as the old Charlestown High Bridge with cars passing over both, even though both were demolished and replaced by the Thomas P. O'Neill Jr. Tunnel and the Zakim Bunker Hill Bridge. The Zakim is seen, but is still under construction in the picture."

Mikeeg555 12:07, 7 February 2007 (UTC)

I removed "The minimum (age of the imagery) is 2 years old due to privacy issues." This is obviously false. Most people will be able to verify this. Builings erected much more recently are clearly present. Azate 13:08, 5 May 2007 (UTC)

BBC report

Just found this report titled "Iraqis use internet to survive war". It mentions how people are using Google Earth to avoid being kidnapped by sectarian patrols. —KNcyu38 (talk • contribs) 15:37, 16 February 2007 (UTC)

Google Earth on PS3

Does this software works on the PlayStation 3´s yellow dog linux?


I just found this BBC news report. I definetly think we should include something about this in the article as I don't think Google earth have ever teamed up with human rights groups in this way to actively encourage people to take action. Its too important to ignore. Olockers 12:30, 11 April 2007 (UTC)

Help me!

I just downloaded google earth yesterday and it was fine, but 2day all i can normally is San Fran, which is pointless to me. Everything else is low-res, which it wasn't before. icelandichurricane#12(talk) 19:58, 11 April 2007 (UTC)

Nevermind. Apparently when I check off My Places, it blurs. Wonder y... icelandichurricane#12(talk) 20:38, 11 April 2007 (UTC)

Has Google every attempted a global map of the Earth Using Non-visible Spectra?

Obviously, the Americans have already done this for military purposes so that they can deduce the nature of underground structures (and determine where bunkers are and how deep they might be).

I remember reading once about how they have also experimented (and ARE experimenting with) the use of Neutrino detectors in space that potentially have the ability to see straight through the Earth, but this, I imagine, can only be done at low resolution.

The above paragraph does seem quite useless to most of us (I don't own a bunker), but the point about having access to infrared, UV and other telemetry – perhaps in real time – would be quite useful for agricultural purposes, enabling higher food yields for lower water and fertiliser inputs (it should be possible to determine soil fertility qualities with some precision using visible and non-visible satellite spectra).

Anyhow, it would also be cool to see how different the Earth looks when view in terms of different spectra.

I can also imagine that Earth temperature data would be useful for agricultural purposes too...

I can't think of any other applications of such data other than for more efficient food production (for example, it should be possible to implement computer controlled underground piping networks for thirsty crops, that would be controlled dependent upon temperature and humidity information that would optimise growth and better yields).

Though, knowing my luck, all of this has probably be done before.....

MrASingh 18:34, 14 April 2007 (UTC)

Improved Resolution Via the Use of 'Back-Images'

I believe that someone has mentioned that Google Earth updates it's imagery every 1-2 years. Even with such a long time lag (which I'm guessing is actually a gross over-estimate, as Google ^probably^ receives information that enables it to update Google Earth every month, or less), it should be possible to process the Image information in such a way as to improve the resolution of some structures (for example, the Statue of Liberty doesn't move around often – so 2 separate images of her should enable a better 3-D modelling/Image Processing).

The above also goes for Non-Visual spectra, but I'm not sure how many people out there are smart enough to implement it (that's a joke, there's always someone out there smart enough to implement it).

MrASingh 18:41, 14 April 2007 (UTC)

P.S - The Statue of Liberty DOES move around a little, but not as much as the resolution distance that would satisfy most people.

Addition of overlay link

Anon User: has tried to add a link to [4] to the links section. This is an overlay layer mapping the genocide in Darfur, Sudan. I think this may be a sufficiently significant overlay to add to the overlays section. What do other editors think? I have asked the anon user to stop adding the link until consensus is reached, and stop adding an irrelevant link altogether! Halsteadk 10:45, 4 May 2007 (UTC)

Degree Confluence project

GE useed to link to the Degree Confluence Project but recently stopped. could someone find a place to include this in the article? --Ted-m 20:05, 16 May 2007 (UTC)

Who liaises with Google?

Gregory Maxwell has not posted for over two weeks (I do hope he's OK). Who else has contact with Google, in regard to their use of our coordinates? There are pressing issues needing attention. Andy Mabbett 09:55, 1 June 2007 (UTC)


I am currently looking at Antarctica, and there is a grey square with a mountain with really good resolution. It looks a bit out of place. Codelyoko193 19:47, 7 June 2007 (UTC)

Infrastructure & implementation of wiki integration

Does anyone know what application, server, or script is used to scrape for coordinates in Wikipedia and create the KML code? If one had their own mediawiki and their own google earth server, what middleware is needed to achieve the same integration that occurs here? -Mike BW 13 JUN 07

There is no specific MediaWiki support for coordinates, and I'm not aware of extensions to make them easily available. Coordinates on Wikipedia are just text, and Google downloads the database dumps we provide and parses them following the format explained on the wiki. All parsing and serving is done with their own proprietary methods. The MediaWiki database can be queried, or dumped and parsed in a similar way with any MediaWiki installation, though it might not be the best solution. Google support would probably be happy to help with any of their Enterprise products, but if a less than turnkey-solution is enough, they have published a tutorial called Using PHP and MySQL to create KML. --Para 17:19, 13 June 2007 (UTC)

Censoring malls

I just noticed today that Google Earth is censoring out malls...worth mentioning in the article? —Preceding unsigned comment added by (talk • contribs)

Fictional 3-d buildings

I found it interesting that a fictional bridge from Bungie's Halo 2 was included as a 3D bulding in Mombasa, Kenya. Are any other buildings fictional and should it be mentioned?

ThePheonix9 21:30, 20 June 2007 (UTC)

Portable version

What if you want to use GE on a library computer where it is not installed? Are there any pure web interfaces for accessing the GE images without installation of any program? Is there a portable version that could be used without requiring installation?- 21:50, 6 July 2007 (UTC)

Google Maps uses some of the same imagery. 06:43, 7 July 2007 (UTC)

Google Middle-Earth

Idea: What about something like Google Earth combined with a community process like the Wikipedia-one, where everybody shall be able to add info to the landscape, like self-made "aerial photography" (drawn or whatever), designed buildings etc.?
Christian Storm 17:30, 11 July 2007 (UTC)

You can pretty much already do that with Google Earth. Check out the Add -> Image Overlay. -- trlkly 20:20, 16 July 2007 (UTC)

The Globe Icon

Do you guys/gals think that the google earth blue globe icon should be uploaded? --Jackl 13:02, 20 August 2007 (UTC)

how about camera feeds

would be nice if one could get real cameras placed around the earth and get them via google earth peer to peer, govt laws not withholding :) the images look like they are unreal.. —The preceding unsigned comment was added by (talk) 14:40, August 22, 2007 (UTC)

We discuss the article, not Google Earth. (SEWilco 04:12, 23 August 2007 (UTC))


i've lived for 30 years in the US, and never seen the "p.a." abbreviation. "per annum", "per year", "/year" are all common. "pa" is used for pascals and other things. 03:14, 23 August 2007 (UTC)


Are All Those Cars Real or Just There For Decoration? HIYO—The preceding signed but undated comment was added at 19:22, August 23, 2007 (UTC).

Hi. IMO the cars are all real. Remember that most of the images were taken several years ago by satellite. The satellite captured images of cars (as well as a few people). So the cars are real. How would they be able to place so many cars in all those directions? Hope this helps. Thanks. ~AH1(TCU) 14:28, 24 August 2007 (UTC)
When Will They Take New Pics? HIYO 16:55, 24 August 2007 (UTC)
Look on the Google Earth web site for forums to discuss the product. (SEWilco 02:14, 25 August 2007 (UTC))

sky viewing feature

discuss--Olavid 20:10, 3 September 2007 (UTC)

Um.. It's not so much sky as stuff in the sky? (SEWilco 03:56, 4 September 2007 (UTC))

Google Earth Image Use

Exactly how many Google Earth images do we need so the reader is able to understand what Google Earth is? I'm of the opinion that this article is getting flooded with Google Earth images that add little or nothing to the reader's understanding of the topic. Obviously, I feel that important features should remain, but this page has become a repository or gallery for all these copyrighted images and it begins to question the validity of their fair-use rationales. I propose we begin deleting images that are redundant or add almost nothing to the article substance. For example, we have three images of the 3D city look from New York, Denver and L.A. Certainly, one image is sufficient to present this feature. Another example is the "glitches" section explaining the "bumps" that appear across the map. We don't need the Eiffel Tower and the Straight of Gibraltar to illustrate this problem. One or the other. Also, the "flight simulator" is already in a 3D city environment. We can illustrate both features for the reader in this one pic. We are not supposed to be advertisers for Google, but writers of a decent encyclopedia entry. I want to hear what the editors of this page have to say. -- VegitaU 14:32, 11 September 2007 (UTC)

What the fuck

Is with the nazi-ism deleting like every picture on the article? Seriously, the program is ****ing free, whats wrong with a picture (much less low resolution) demonstrating certain things. God Im getting sick of this site. RoyalAbidi 01:15, 5 October 2007 (UTC)

First of all, calm down! Second of all, your comment is on the fringe of being a personal attack. I'll let you slide here, but be careful who you're calling a nazi. As I explained above (and there are many discussions on), Google Earth images are copyrighted. Period. Dot. Regardless of its free availability, all screengrabs and images from there are copyrighted (for the trillionth time). I'm sure someone down the road will ask again. Third (or whatever number I'm on), most of these screenshots, if you take the time to look at them, are high resolution. 1100 X 800 px is not low-resolution. And when you say "certain things" it draws on the next point. There needs to be a reason, a rationale, for why a copyrighted image needs to be used and "certain things" just doesn't quite wash. There has to be an aspect that so requires this copyrighted image that, without it, the user would be left absolutely stupefied about the article in its entirety. So if you're getting sick of this site, I suggest you click here, close the window and tab you're currently viewing, and never come back; because these policies are here to stay and I've deleted enough Google Earth and Google Maps images to know what washes and what doesn't. Happy editing! ;)-- VegitaU 01:37, 5 October 2007 (UTC)

How much of a five-page essay is one expected to have to write for a 'fair use rationale'? I've been asked to provide one for Image:Google Scilly.jpg, but it already has one, pointing out that it is to demonstrate the very low resolution of some areas. If you think more is needed, how about providing some guidelines for what to put? - MPF 08:30, 5 October 2007 (UTC)

No prob. WP:FURG. Again. Enjoy. -- VegitaU 17:12, 5 October 2007 (UTC)
Godwin's law --Lazer erazer 21:15, 7 October 2007 (UTC)

3D buildings

"Google has provided a layer allowing one to see 3D buildings for many major cities."

The section "Google Earth%3D Buildings" does no longer exist, unfortunately. I've taken out the link, someone may insert it with the proper wikilink --Lazer erazer 14:21, 7 October 2007 (UTC)


when I opened up google earth a window came up saying that there was a update available for download and I just closed the that window thinking that I could download it later but now when I open google earth the window Isn't coming up, so does anyone now where I can get the update. 17:05, 7 October 2007 (UTC)

This is not a forum but, under "help" third from bottom "Check for updates online". --AxG@talk 17:08, 7 October 2007 (UTC)

Thank you very much for your help. 15:34, 8 October 2007 (UTC)


I've changed the screenshot... If anyone have any problem, reply to this thread. Reason for change: Original image was of too high resolution, which is not "fair use" since google earth snapshots are copyrighted. Moreover, why snapshot of Manhattan in specific? Replaced it with a generic image of Google Earth software showing Googleplex campus. Mugunth 15:04, 8 October 2007 (UTC)

The image is much better, actually showing the GE nav tools. Although you should rm the Vista task bar from it. --AxG@talk 15:52, 8 October 2007 (UTC)
Not to mention shrinking it to 300 px or less and adding a fair use rationale. -- VegitaU 16:08, 8 October 2007 (UTC)

-- Removed Vista Takbar from image.. oops.. missed it the first time..! -- Made the thumbnail larger (300 px)

Mugunth 17:51, 8 October 2007 (UTC)

That's nice. Now you need to make the actual image smaller and get a fair use rationale up for it. Please, don't make me tag it. -- VegitaU 17:56, 8 October 2007 (UTC)

I've added a "fair use rationale" to the image. But I'm not sure whether it's correct. Can someone please check it out? The image was created on my PC... Mugunth 18:17, 8 October 2007 (UTC)

Zoom limit and Dates

First of all how up to date are the photos in Google Earth?? How come you can't zoom in clear enough to see the actual ground. These are powerful datelites that can see for light-years but, you can't zoom in to even see the bare groung clear enough. Last of all you know how the in the movies people use like an earth viewer but, it's not pictures but live video from space an exsample of this is from the movie Enemy of the State is there really such a thing as real-time video spy satellites?? Please answer if you can.

The photos are usually no less than 3 years old. The images couldn't be high-resolution without destroying Google Earth's bandwidth. There are such things as real-time spy satellites, but they are more often than not hampered by cloud cover. - Kookykman|(t)e
For an example of dating, take a look at Lincoln in the United Kingdom. Following the A15 north you pass the County Showground, as the current coverage shows that the County Show is running, which means one of two days in late June. Less obviously, from my own knowledge as a farmer, the area was photographed in the summer of 2003--I can check crop patterns against records, and I know some buildings are visible which were demolished in early 2004. So the high-res imagery can be dated to the 18th or 19th June 2003, with the sun roughly south-east. —Preceding unsigned comment added by (talk) 17:01, 13 February 2008 (UTC)

How recent are photos?

When does Google Earth usually update their satellite photos? If today is June 12, 2008, then how many days from then will the new pics be taken? I wanna know! Wikiboy12 (talk) 20:28, 12 June 2008 (UTC)wikiboy12

Only Google knows, and it also depends on how the weather is, and if they think it's worth the cost. In other words, it's mostly spontaneous, but large cities receive more updates more frequently. --FlagFreakTALK 16:29, 14 June 2008 (UTC)
Well, actually as of today New York City is shown as it was in 2002, that's a whole 6 years delay. Paris
Источник: []
, google earth pro license Archives

Google Earth Pro for UK Higher Education

Update: Google have made GE Pro free for all users – thanks Google. The post below is now obsolete.


Recently I had a few inquiries from students, academics and IT staff who had heard that as a member of a UK university you can get Google Earth Pro for free. This is to clarify:

Google grant Google Earth Pro licenses to UK HE institutions through their Google Earth Pro Grants programme.
This is for institutional licenses, meaning the university is the license holder, not the individual student or academic. There is no grant for personal licenses. If you want a personal Google Earth Pro license your only option is to purchase one from Google.

If you act on behalf of the university and want to apply for a grant, read on:

The Google Earth Pro grant is for 30 licenses, for one year.

First time application process:

  1. Download and install a trial of Google Earth Pro from You will need to leave your details and Google sends you a trial license key.
  2. Check your eligibility for a free license grant: go to, and go through the wizard to determine your eligibility for a new grant.
  3. At the end of the wizard you are taken to a grant application form. Fill it out. You will need to make a case for the grant. Then wait for response from Google. This can take up to a three months.
  4. If you get the grant, Goggle convert your trial license key to a Goggle Earth Pro license key.
  5. On clients: install Google Earth Pro and enter your license key and the email address that you had used to apply for the grant. The license key and the email address will be visible to end users.


  1. After one year the license expires, to renew it go to the application/renewal page (, enter your previous license key (even if it says to enter a trial key!), and go through the wizard to apply for a renewal of the grant.
  2. You will need to make a case again, Google asks:
    1. Provide a URL or description of any student created content. (This could be a contribution to the Google Earth Community or Google Earth for Educators message boards)
    2. How have you used Google Earth Pro in the past year? (Ie. research for a paper/thesis, teaching tool, curriculum planning, presentation tool, etc.)
    3. How are you planning to use Google Earth Pro in the upcoming year? (Ie. research for a paper/thesis, teaching tool, curriculum planning, presentation tool, etc.)

I applied for and received a grant for Manchester University in 2013, had it for a year, but did not renew due to little interest from users.
Hope this helps someone.

Like this:

Источник: []
google earth pro license Archives

Google Enterprise Geo Master License

Google Earth Pro

This Google Enterprise Geo Master Agreement for the licensing of Google Enterprise Maps and Earth Products and Services (the "Agreement") is made and entered into by and between Google Inc. ("Google") and the customer identified below and/or on the Ordering Document(s)("Customer"). This Agreement, each accompanying addendum and each accompanying Ordering Document governs Customer's access to and use of the Products and Services.

1. Product and Services Terms and Conditions.

1.1 The Agreement is a Master Agreement. The Customer must have the Agreement in effect to obtain Products and Services. Customer may obtain Products and Services by entering into a corresponding Addendum. The parties will execute the Agreement first and are subject to an agreed term. An Addendum is entered separately and is subject to its own terms.

1.2 Generally Applicable Product and Services Terms. Except as otherwise permitted by the Product or Service in the Documentation, Customer will not, and will not allow others to: (a) copy Software except as explicitly authorized; (b) use the Products and Services for High Risk Activities; (c) use the Product and Services to create a substantially similar products or services; or (d) extract any Google Content for use outside of the Products.

1.3 Separate Use. Unless otherwise authorized by Google, Customer will not: (a) distribute or sell Google Content; (b) incorporate or embed Google Content or components of the Products and Services into any of Customer's products or services that it makes available to third parties; or (c) offer the Services, or any Customer products and services based upon the Services, on a subscription basis to third-parties.

1.4 Third-Party Components. Any third party component embedded, included or provided for use with the Software may only be used in conjunction with the Software, and this use is subject to this Agreement and any applicable Addendum and Documentation. However, to the extent Software includes components governed by open source licenses with provisions inconsistent with this Agreement, those components are instead governed solely by the applicable open source licenses. To the extent Software includes components covered by open source licenses requiring the provision of corresponding source code, Google hereby offers such source code consistent with those licenses.

1.5 Restrictions. Customer, except as expressly permitted in an Addendum, will not (and will not allow any third party to): (a) use or reproduce, modify, create derivative works, decompile, disassemble, or otherwise reverse engineer the Products and Services or attempt to reconstruct or discover any source code, underlying ideas, algorithms, file formats or programming interfaces of the Products and Services by (except and only to the extent that applicable law prohibits or restricts reverse engineering restrictions), or incorporate the Products and Services into or with other technology; (b) distribute, sell, sublicense, rent, lease to third parties or otherwise make the Products and Services functionality available to third parties except as set forth herein; or (c) remove or in any manner alter any Products and Services identification, proprietary, trademark, copyright or other notices.

1.6 Customer Data.

a. Services Use. Customer may upload Customer Data into the Systems via the methods described in, and this Customer Data will be stored in accordance with, the Documentation.

b. Risk of Loss. Customer Data will not be returned to Customer, whether the Customer Data is physically provided to Google, or entered by Customer or Google into the Systems. Customer is solely responsible for backing up its Customer Data. Google will not bear any risk of loss for any data.

c. Customer Rights in Customer Data. Customer is solely responsible for having, or obtaining, any necessary rights, licenses, or authorizations necessary for Customer to provide the Customer Data to Google, and for Google to use the Customer Data as stated in this Agreement to provide the Services to Customer. Customer is solely responsible for determining the scope of its notification obligations to Customer Data and any other persons whose tracked data and other information is included in Customer Data.

d. Customer Data Transfer. As part of providing the Service, Google may store, process, and serve Customer Data in the United States or any other country in which Google or its agents maintain facilities. By using the Services, Customer consents to this transfer, processing and storage of Customer Data.

e. Applicable Products and Services. This section is not applicable to Maps API for Business and Google Earth Enterprise.

2. Technical Support Services.

2.1 Technical Support Service (TSS). Subject to Customer's payment of all due and payable Fees and its compliance with this Agreement and its applicable Addendum's terms, Google will provide TSS for Products and Services in accordance with the applicable TSSG for the term agreed in an Ordering Document. Unless otherwise agreed in writing, to receive TSS Customer must provide Google with reasonable access to the Products and Services. Customer's failure to provide access will be at Customer's own risk. If the Ordering Document does not identify a support level, then Google will provide standard or Basic TSS as defined in the TSSG. Google may, from time to time, change the TSS.

2.2 Updates. TSS includes Updates, to the extent available, to the given Product or Service. Customer will only receive Updates if Customer is receiving TSS. Customer's access to and use of TSS is subject to this Agreement's terms, the applicable Addendum and the Ordering Document. Customer will implement Updates in accordance with the TSSG. Customer may, if possible, make an Update copy to facilitate installation and will destroy the copy after use.

3. Term and Termination.

3.1 Agreement Term. Subject to Customer's payment of all due and payable Fees and compliance with this Agreement's terms, the Agreement begins on the Effective Date and will continue until the end of the last Addendum term(s) unless terminated earlier as set forth below ("Initial Term"). An Addendum's term is set forth in the respective Addendum.

3.2 Auto-Renewal. At the end of the Initial Term, and unless otherwise indicated in an Addendum, the Agreement will automatically renew for consecutive twelve month renewal terms. If a party does not want the Agreement to automatically renew, then it must provide the other party a written termination notice at least 15 days prior to the then current term's expiration date. A party's timely non-renewal notice will be effective upon the then current term's expiration. Google will invoice Customer, and Customer agrees to pay, for the renewal of Products and Services as set forth in the applicable Ordering Document. An Addendum's renewal term, if any, will be set forth in the respective Addendum.

3.3 Termination for Breach. Either party may terminate this Agreement or an Addendum if: (a) the other party is in material breach of the Agreement or an Addendum and fails to cure that breach within 30 days after receipt of written notice; (b) the other party ceases its business operations or becomes subject to insolvency proceedings and the proceedings are not dismissed within 90 days; or (c) the other party materially breaches this Agreement or an Addendum more than two times notwithstanding any cure of these breaches.

3.4 Effect of Termination.

a. Termination for Google's Breach.

(i) Agreement Termination. If the Agreement is terminated for Google's breach, the rights granted hereunder may, at Customer's option, continue for the remainder of all then effective Addendum(s)'s term(s), subject to Customer's continued compliance with this Agreement and the corresponding Addendum(s). If Customer elects not to continue under the Agreement, then the Agreement and all accompanying then-effective Addendum(s) will terminate. Customer must make its election to proceed or not proceed under the Agreement upon the Customer's declaration of Google's Agreement breach. If Customer elects to continue the Agreement it further commits to continue all Addendum(s).

(ii) Addendum Termination. If an Addendum is terminated for Google's breach, the rights granted under the Addendum may, at Customer's option, continue for the remainder of the breached Addendum's term, subject to Customer's continued compliance with this Agreement and the continued Addendum. If Customer elects not to continue under the breached Addendum, then the Addendum will terminate. Customer must make its election to proceed or not proceed under the Agreement upon the Customer's declaration of Google's Addendum breach.

b. Termination for Customer's Breach. If the Agreement or an Addendum is terminated for Customer's breach then: (i) the License Term and all other rights and licenses granted by Google to Customer under the Agreement and its Addendum(s) for the Products and Services will cease immediately and (ii) all payments owed by Customer to Google are immediately due and payable.

3.5 Effect of Expiration. If the Agreement expires, the Addendum(s) does not expire until the expiration of its respective term(s). If an Addendum survives Agreement termination or expiration, the Agreement will remain in effect with respect to that Addendum until the Addendum expires. If an Addendum expires the Agreement will stay in effect and any other Addendum in Effect with stay in effect unless otherwise provided.

4. Orders and Payment.

4.1 Purchase Process. Google will provide Customer an Ordering Document for each transaction to confirm the acquired Products and Services and their respective quantities and Fees. The Ordering Document is incorporated into and governed by this Agreement.

4.2 Payment. All Fees are due 30 days from the invoice date. Customer's obligation to pay Fees is non-cancellable. All payments due are in U.S. dollars. Payments made via wire transfer must include the following instructions:

Wells Fargo Bank
Palo Alto, California USA
ABA# 121000248

Google Inc.
Account # 4375669785

4.3 Taxes. Customer is responsible for any applicable Taxes without reduction. If Google is obligated to collect or pay Taxes, the Taxes will be invoiced to Customer, unless Customer provides Google with a valid tax exemption certificate. If Customer is required by law to withhold any Taxes from its payments to Google, Customer must provide Google with an official tax receipt or other appropriate documentation to support this withholding.

4.4 Invoice Disputes. Any invoice disputes must be submitted prior to the invoice due date. If the parties determine that certain billing inaccuracies are attributable to Google, Google will not issue a corrected invoice, but will instead issue a credit memo specifying the incorrect amount in the affected invoice. If the disputed invoice has not yet been paid, Google will apply the credit memo amount to the disputed invoice and Customer will be responsible for paying the resulting net balance due on that invoice.

4.5 Delinquent Payments. Delinquent payments may bear interest at the rate of one-and-one-half percent per month (or the highest rate permitted by law, if less) from the payment due date until paid in full. Customer will be responsible for all reasonable expenses (including attorneys' fees) incurred by Google in collecting delinquent amounts, except where these delinquent amounts are due to Google's billing inaccuracies.

4.6 Purchases and Orders.

a. Orders. Product and Service order requirements will be set forth in this Agreement and each accompanying Addendum.

b. Purchase Orders. If Customer's Ordering Document is a quote, then a Purchase Order is required. If Customer's Ordering Document is an order form, and Customer wants a Purchase Order number on its invoice, Customer will inform Google and will issue a Purchase Order number to Google. If Customer requires a Purchase Order, and fails to provide the Purchase Order number to Google, then Google will not be obligated to provide the Products and Services until Google receives the Purchase Order. Any terms and conditions on a Purchase Order do not apply to this Agreement or any Addendum and are null and void.

c. Delivery. The Products and Services will not be made available until Google receives either: (i) a complete and duly executed Purchase Order referencing a quote and this Agreement; or (ii) a complete and duly executed order form.

4.7 Usage Limits. Customer may not exceed Usage Limits. In order for the Products and Services to continue functioning in excess of the Usage Limits, Customer must enter into a new Ordering Document for the additional Products and Services.

5. Intellectual Property Rights Ownership and Publicity.

5.1 Intellectual Property Rights Generally. Except as expressly stated in this Agreement or in an Addendum, this Agreement does not grant either party any rights, implied or otherwise, to the other's content or any of the other's Intellectual Property Rights. Intellectual Property Rights in and to the content accessed through the Products and Services are the property of the applicable content owner and may be protected by applicable laws.

5.2 Brand Features. If, to the extent possible, Customer wants to display Google Brand Features in connection with its use of the Products and Services, Customer will comply with the Trademark Guidelines. Customer will not alter any images generated by the Products or Services to remove any Brand Feature or proprietary notice of Google or its licensors. Any use of a party's Brand Features will inure to the benefit of the party holding rights in those Brand Features. Each party agrees not to: (a) challenge or assist others to challenge the other party's Brand Features or registration thereof (except to protect that party's rights with respect to its own Brand Features) or (b) attempt to register any Brand Features that are confusingly similar to those of the other party.

5.3 Publicity. Customer agrees that Google may include Customer's name or Brand Features in a list of Google customers, whether online or in offline promotional materials. Customer also agrees that Google may verbally reference Customer as Google client.

6. Export Compliance.

Customer will comply with and will obtain all required authorizations from applicable government authorities under all applicable export and reexport control laws and regulations with respect to its Product and Services use, including the Export Administration Regulations ("EAR") maintained by the U.S. Department of Commerce, trade and economic sanctions maintained by the Treasury Department's Office of Foreign Assets Control, and the International Traffic in Arms Regulations ("ITAR") maintained by the Department of State. This section will survive Agreement termination or expiration.

7. Confidentiality.

7.1 Obligations. Each party will: (a) protect the other party's Confidential Information with the same standard of care it uses to protect its own Confidential Information, but in no event less than reasonable care; and (b) not disclose the Confidential Information, except to Affiliates, employees and agents who need to know it and who have agreed in writing to keep it confidential. Each party (and any Affiliates, employees and agents to whom it has disclosed Confidential Information) may use Confidential Information only to exercise rights and fulfill obligations under this Agreement, while using reasonable care to protect it. Each party is responsible for any actions of its Affiliates, employees and agents in violation of this section. Either party may demand the return of Confidential Information at any time upon written notice to the other party.

7.2 Exceptions. Confidential Information does not include information that: (a) the recipient already knew; (b) becomes public through no fault of the recipient; (c) was independently developed by the recipient; or (d) was rightfully given to the recipient by another party.

7.3 Required Disclosure. The recipient may disclose Confidential Information when required by law after giving reasonable notice to the discloser if allowed by law.

7.4 Product and Services Confidentiality. The Products and Services functionality and pricing is Google's Confidential Information.

8. Warranty Disclaimer.


9. Limitation of Liability.



9.3 Exceptions to Limitations. These limitations of liability do not apply to breaches of confidentiality obligations or violations of a party's Intellectual Property Rights by the other party.

10. Indemnification.

10.1 By Google. Google will indemnify, defend, and hold harmless Customer from and against all liabilities, damages, and costs (including settlement costs and reasonable attorneys' fees) arising out of a third party claim that the Products or the technology used to provide the Services infringes or mis-appropriates any patent, copyright, trade secret or trademark of that third party.

10.2 Exceptions. The obligations set forth in Section 10.

10.3 By Customer. Unless prohibited by applicable law and without waiving sovereign immunity, Customer will indemnify, defend, and hold harmless Google from and against all liabilities, damages, losses, expenses and costs (including settlement costs and reasonable attorneys' fees) arising out of (a) a third party claim made against Google for infringement of the third party rights listed in Section 10.1 based on conduct by Customer as described in Section 10.2; (b) Customer's breach of Section 6 (Export Compliance); or (c) Customer's use of the Software or Services in violation of an End User's privacy.

10.4 Infringement Remedies. If Google reasonably believes the Products or Services infringes a third party's Intellectual Property Rights, then Google will: (a) procure for Customer the right to continue to use the Products or Services; (b) replace the infringing Products or Services; or (c) modify the infringing Products or Services to avoid the alleged infringement. If Google determines the options in this Section are not commercially reasonable, Google may terminate the license for the allegedly infringing Products or Services and will provide a pro-rata refund of the paid but unearned Fees applicable to the period following the Products or Services termination.

10.5 General. The party seeking indemnification must promptly notify the other party of the claim and cooperate with the other party in defending the claim. The indemnification in Sections 10.1 and 10.2 is limited to the payment by the indemnifying party of all damages and costs finally awarded for the claim, or settlement costs approved in writing by the indemnifying party. The indemnifying party has full control and authority over the defense, except that: (a) any settlement requiring the party seeking indemnification to admit liability or to pay any money will require that party's prior written consent, which will not be unreasonably withheld or delayed; and (b) the other party may join in the defense with its own counsel at its own expense. THE INDEMNITIES ABOVE ARE A PARTY'S ONLY REMEDY UNDER THIS AGREEMENT FOR VIOLATION BY THE OTHER PARTY OF A THIRD PARTY'S INTELLECTUAL PROPERTY RIGHTS.

11. Verification and Audit.

At Google's written request, not more than once per calendar year, Customer will provide Google with a certification signed by a Customer officer verifying the Products or Services are being used in compliance with this Agreement. Furthermore, Google will have the right, no more than once per calendar year, and upon at least 30 days prior written notice, to appoint a nationally recognized certified public accountant or independent auditor to examine and verify Customer's Agreement compliance. Audits will be conducted during regular business hours at Customer's facilities and will not unreasonably interfere with Customer's business activities. Customer will provide Google with reasonable access to the relevant Customer records and facilities. If an audit reveals that Customer has underpaid fees to Google during the period audited, then Google will invoice Customer, and Customer will promptly pay Google, for the underpaid fees based on the higher of the price specified in this Agreement or Google's price list in effect at the time the audit is completed. If the underpaid fees exceed five percent of the license fees paid by Customer for the Products or Services during the preceding six-month period, then Customer will also pay Google's reasonable audit costs.

12. Miscellaneous.

12.1 Notices. All notices of termination or breach must be in writing and addressed to the attention of the other party's legal department and primary point of contact. The email address for notices being sent to Google's Legal Department is All other notices must be in English, in writing and addressed to the other party's primary contact. Notice will be treated as given on receipt, as verified by written or automated receipt or by electronic log (as applicable).

12.2 Integration. This Agreement and its accompanying Addendum(s) and Ordering Documents are the parties' entire agreement relating to its subject and supersedes any prior or contemporaneous agreements on that subject. The terms located at a URL and referenced in this Agreement or any Addendum are hereby incorporated by this reference. If there is a conflict between the documents that make up this Agreement, the documents will control in the following order: the Ordering Document, the Agreement, the Addendum(s) and the terms located at any URL.

12.3 Amendment. Any amendments to this Agreement must be in writing and expressly state that is amending this Agreement.

12.4 Assignment. Neither party may assign any part of this Agreement or and Addendum without the written consent of the other, except to an Affiliate where: (a) the assignee has agreed in writing to be bound by the terms of this Agreement; (b) the assigning party remains liable for obligations under the Agreement if the assignee defaults on them; and (c) the assigning party has notified the other party of the assignment. Any other attempt to assign is void.

12.5 Change of Control. Upon a change of Control (for example, through a stock purchase or sale, merger, or other form of corporate transaction) other than in the context of an internal restructuring or reorganization of it Affiliates: (a) that party will provide written notice to the other party within 30 days after the change of Control; and (b) the other party may immediately terminate this Agreement any time between the change of Control and 30 days after it receives the written notice. "Control" means control over greater than fifty percent of the voting rights or equity interests of a party.

12.6 Force Majeure. Neither party will be liable for failure or delay in performance to the extent caused by circumstances beyond its reasonable control.


12.8 No Agency. This Agreement does not create an agency, partnership or joint venture between the parties.

12.9 Additional Terms. Neither party will be treated as having waived any rights by not exercising (or delaying the exercise of) any rights under this Agreement. IIf any term (or part of a term) of this Agreement is invalid, illegal or unenforceable, the rest of the Agreement will remain in effect. There are no third-party beneficiaries to this Agreement. Nothing in this Agreement will limit either party's ability to seek equitable relief. Those provisions that by their nature should survive termination of this Agreement, will survive termination of this Agreement. Customer may not subcontract any of its obligations under this Agreement without Google's written consent. If such permission is granted, Customer will remain liable for all subcontracted obligations and all acts or omissions of its subcontractors.

12.10 Counterparts. The parties may execute this Agreement in counterparts, including facsimile, PDF, and other electronic copies, which taken together will constitute one instrument.

12.11 Acceptable Use Policy. Customer will use all Products and Services in compliance with their applicable Acceptable Use Policy.

12.12 Services Modifications. To the extent to which an Addendum includes Services, Google may make commercially reasonable changes to the Services from time to time. If Google makes a material change to the Services, Google will inform Customer either via a TSS portal or using the email address Customer has provided to Google in order to be notified of such changes.

12.13 URL Modifications. Google may make commercially reasonable changes to the URL Terms from time to time. If Google makes a material change to the Services, Google will inform Customer either via a TSS portal or using the email address Customer has provided to Google in order to be notified of such changes. If Google makes a material change to the URL Terms (except TSS terms) and Customer demonstrates that the change has a material adverse impact on Customer, Customer may notify Google within 30 days of the change and remain subject to the noticed URL Terms (except if the URL was changed to reflect applicable law or a court order). If the License Term is subsequently renewed, it will renew under all the updated URL Terms.

12.14 Other Applicable Terms and Conditions. Customer will only use the Services and Software in compliance with the Agreement and its applicable Addendum(s), the Legal Notices, the applicable Documentation, the Acceptable Use Policy and the Ordering Document. Customer may only use the Services in accordance with the SKUs specified in the applicable Ordering Document.

12.15 Google Content Terms. If Customer receives Google Content, then Customer must not obscure, alter, or remove any included terms or the applicable Legal Notices. If Google Content includes static maps or HTTP services, Customer must incorporate a link to the Earth Terms and Legal Notices in a license agreement governing End Users' use. Customer must notify Google if Customer becomes aware of any End User's non-compliance with the Earth Terms, Legal Notices, or the AUP. "Earth Terms" mean the terms for Google Maps/Earth set forth at the following URL, or other such URL as Google may provide.

13. Definitions.

The Agreement definitions are used in the Agreement and one or more applicable Addendum(s).

"Acceptable Use Policy" or "AUP" means the means the acceptable use policy for the Products and Services as set forth in the applicable Addendum.

"Addendum" means a document entered into by both parties to an Agreement that is incorporated into the Agreement and describes the specific terms and conditions applicable to the Addendum's Products and Services.

"Affiliate" means any entity that directly or indirectly controls, is controlled by, or is under common control with that party.

"Brand Features" means the trade names, trademarks, service marks, logos, domain names, and other distinctive brand features of each party or its respective Affiliates, respectively, as secured thereby from time to time.

"Confidential Information" means information that one party (or an Affiliate) discloses to the other party under this Agreement, and which is marked as confidential or would normally under the circumstances be considered confidential information. It does not include information that the recipient already knew, that becomes public through no fault of the recipient, that was independently developed by the recipient, or that was lawfully given to the recipient by a third party.

"Customer Data" means the data (including data owned by third-parties that is in Customer's possession) Customer loads, or which is loaded on Customer's behalf, into the Systems. Customer Data must be owned or licensed by Customer. The Documentation contains information on the types and formats of Customer Data that may be entered into the Systems.

"Documentation" means the Google proprietary documentation in the form generally made available by Google to its customers for use with the Products or Services as set forth in the applicable Product's or Service's Addendum.

"Effective Date" means the date this Agreement or any accompanying Addendum is entered into by Google.

"End Users" mean the individual human end users who use Products and Services, subject to the requirements of this Agreement, any applicable Addendum and the Documentation.

"Fees" means the Agreement's applicable Product and Services fees and applicable Taxes as set forth in an Ordering Document.

"Google Content" means any content provided through the Products and Services (whether created by Google or its third party licensors) as further defined in each applicable Addendum.

"High Risk Activities" means uses like the operation of emergency services, nuclear facilities, air traffic control or life support systems, where the use or failure of the Services could lead to death, personal injury, or environmental damage.

"Intellectual Property Rights" means current and future worldwide rights under patent law, copyright law, trade secret law, trademark law, moral rights law, and other similar rights.

"Legal Notices" mean the legal notices set forth at the following URL: (or such other URL as may be provided or updated by Google).

"License Term" means the period of time during which Customer is authorized to use the Products and Services under the Agreement or an applicable Addendum, and will be further described in the said Addendum and any applicable Ordering Document.

"Maps" means the maps created by Customer processing Customer Data and, if applicable, Google Content, using the Services. The different types of Maps are described in the Documentation.

"Ordering Document" means either an order form or quote, issued by Google to provide the Products and Services to Customer, subject to this Agreement and the applicable Addendum. The Ordering Document will incorporate this Agreement and will contain: (i) a SKU (including the License Term, if applicable); (ii) a description of the licensed configuration; (iii) price; and (iv) other information as provided on the form.

"Overage" means when Customer's use of the Services exceeds a particular Usage Limit.

"Overage SKU" means a Google SKU that lists the price Customer will pay for its use of the Services in excess of a particular Usage Limit.

"Products" means the Google products (excluding Google Content) as set forth in this Agreement and any accompanying Addendum. The term "Product" may have an additional more detailed supplementary definition in an Addendum.

"Prohibited Territory": means the list of countries where Customer may not use or actively target Product, Software or Service received under the Agreement and any applicable addendum. Each Addendum will have a specific definition of Prohibited Territory.

"Privacy Policy" means the Google privacy policy set forth at the following URL (or such other URL as may be provided or updated by Google).

"Purchase Order" means a Customer issued purchase order.

"Sensor" means the use of any technology to automatically determine an End User's or Asset's location.

"Services" means the Google services as set forth in this Agreement and any accompanying Addendum. The term "Service" may have an additional more detailed supplementary definition in each respective Addendum and the Documentation accompanying the Service.

"Service Level Agreement" or "SLA" means the Google Service Level Agreement, if any, for the Products and Services described in this Agreement and any accompanying Addendum.

"Software" means the Google software, in object code form, or related technologies provided by Google to Customer pursuant to an Ordering Document and as further provided in each applicable Addendum and the Software's accompanying Documentation.

"Systems" means the Google computer, processing, and network systems used to provide the Services to Customer.

"Taxes" means any duties, customs fees, or taxes (other than Google's income tax) associated with Product and Services transactions, including any related penalties or interest.

"Trademark Guidelines" means Google's Guidelines for Third Party Use of Google Brand Features, located at the following URL: (or other URL as may be provided or updated by Google).

"TSS" means the technical support services provided by Google, in accordance with Google's TSSG, for the applicable Products or Services, and for a mutually agreed (in writing) time period.

"TSSG" means Google's then current Product or Service specific Technical Support Services Guidelines, which may be may be accessed at the URL set out in each respective Addendum (or other URL as may be provided or updated by Google).

"Updates" is defined in the TSSG.

"Usage Limits" means the limits for use of the Products and Services, which will be as listed on the Ordering Document or as provided to Customer with the Documentation.

"URL Terms" are those uniform resource locator addresses as identified by Google in the Agreement or any Addendum that refer to Google policies, services descriptions of other Product and Services related terms.

By signing this Agreement, each party represents and warrants that (i) it has read and understands this Agreement and the Ordering Document that is incorporated by reference herein and agrees to be bound by its terms, and (ii) it has full power and authority to accept this Agreement and the Ordering Document.

IN WITNESS WHEREOF, this Agreement has been executed by persons duly authorized as of the date signed by the last party below ("Effective Date").

Google Earth Pro Terms of Service Addendum

1. Integration into Agreement.

This Addendum provides for the licensing of Google Earth Pro products and related services. This Addendum is incorporated into the Agreement by this reference. Capitalized terms not defined in this Addendum will have the meaning ascribed to them in the Agreement. This Addendum is effective upon the Effective Date.

2. Services.

2.1 Generally. Subject to Customer's compliance with the Agreement and this Addendum's terms, and in consideration of Customer's payment of all Fees, Google will provide the Services to Customer during the License Term. Customer's use of the Services is subject to the Usage Limits. Customer agrees not to use Products and Services in the Prohibited Territory.

2.2 Licenses from Google to Customer.

a. To use the Software. Subject to Customer's compliance with the Agreement and this Addendum's terms, and in consideration of Customer's payment of all Fees, Google grants to Customer, and Customer agrees to comply with a non-sublicensable, non-transferable, non-exclusive, terminable, limited license to use the Software during the License Term to use the Services.

b. To use Google Content. Subject to this Agreement and in consideration of Customer's payment of all Fees, Google grants to Customer, and Customer agrees to comply with, a non-sublicensable, non-transferable, non-exclusive, terminable, limited license to access the Google Content via the Services during the License Term for purposes as described in the Documentation.

2.3 License from Customer to Google. By entering Customer Data into the Systems, or if Google enters Customer Data into the Systems on Customer's behalf, Customer grants to Google a limited, irrevocable, royalty-free, and non-exclusive license during the License Term, to reproduce, adapt, modify, translate, publicly perform, publicly display and distribute the Customer Data solely as required to enable Google to provide the Services to Customer.

3. Customer Obligations.

3.1 Access and Use Rights. Customer may specify particular rights regarding the access, viewing, editing, or consuming of its maps to a specific set of End Users.

3.2 Unauthorized Use. Customer will use all commercially reasonable efforts to prevent unauthorized use of the Service, and to terminate any unauthorized use. Customer will promptly notify Google of any unauthorized use of, or access to, the Services of which it becomes aware.

3.3 End User Consent. Customer will obtain and maintain all required consents from End Users to allow: (a) Customer's access, monitoring, use and disclosure of this data and Google providing Customer with the ability to do so and (b) Google to provide the Services.

4. Renewal Terms.

Upon each auto-renewal pursuant to Section 6.2, Google will invoice Customer, and Customer agrees to pay, for the renewal of the Services as set forth in the applicable Ordering Document.

5. Restrictions.

5.1 General. Unless otherwise provided in the Documentation or agreed in advance and in writing by Google, Customer will not, and will not allow others to: (a) display any advertising in connection with its use of the Services; (b) extract any Google Content to be used outside of the Services; (c) use, distribute, or sell any Google Content outside of the Maps; (d) incorporate or embed Google Content or components of the Services into any of Customer's products or services that it sells to third parties; (e) permit the sharing of End User accounts between End Users or (f) offer the Services, or any Customer products, services, or solutions based upon the Services, to End Users directly or embedded in another such product for a fee. Section 5.1(f) does not prohibit Customer from offering professional services to its customers in support of its Software implementation.

5.2 Development and Evaluation Accounts. Development and Evaluation Accounts may only be used for development, evaluation, educational purposes, or some combination thereof. Services from a Development and Evaluation Account may be evaluated in a production environment but not for commercial purposes. A Development and Evaluation Account is an admin account for the Services with the License Term specified on the applicable Ordering Document or, if a License Term is not specified on the Ordering Document, then for a period of twelve months.

5.3 Customer Data and Maps. Google will not provide Customer with a copy of the Customer Data or of any Maps upon the conclusion or termination of the Agreement. Maps may only be used within the Services except as specifically allowed in the Documentation. If Customer wants a copy of its Customer Data, Customer must copy the Customer Data prior to entering the Customer Data, or having the Customer Data entered, into the Systems.

6. Addendum Term and Termination.

6.1 Addendum Term. Subject to Customer's payment of all due and payable Fees and compliance with the Agreement's terms and this Addendum's terms, this Addendum begins on the Effective Date and will continue for the term as set forth in the Ordering Document unless terminated earlier as set forth below ("Initial Addendum Term").

6.2 Additional Term and Termination Conditions. All other terms and conditions pertaining to Addendum term and termination are set forth in the Agreement.

7 Technical Support Services.

The Agreement terms notwithstanding, technical support services are not offered for this Product.

8. Definitions.

"Acceptable Use Policy" or "AUP" means the acceptable use policy for the Product at this or other such URL as Google may provide.

"Prohibited Territory": means the list of countries where Customer may not use or actively target Product, Software or Service received under the Agreement and this Addendum. (or such other URL as may be updated by Google).

"URL Terms" for the purposes of this Addendum means the following URL terms: AUP, SLA, and the TSSG.

Источник: []

What’s New in the google earth pro license Archives?

Screen Shot

System Requirements for Google earth pro license Archives

Add a Comment

Your email address will not be published. Required fields are marked *