Google Earth 'timeline' now only goes back as far as 2002?

page: 1
1
<<   2 >>

log in

join

posted on Dec, 29 2012 @ 06:31 PM
link   
Anyone else experiencing this? Or is it just me?

And more specifically, in the Nevada Test Site region??





posted on Dec, 29 2012 @ 06:46 PM
link   
It worked for me all the way back to 1937
edit on 29-12-2012 by Infi8nity because: (no reason given)



posted on Dec, 29 2012 @ 06:49 PM
link   
How far back you can view the timeline will depend on what areas are currently displayed... So for that particular spot, that is as far back as they can go (have images for).



posted on Dec, 29 2012 @ 06:50 PM
link   
It depends on where you are. Some areas have older imagery than others.

Edit: Sek82 beat me to it...
edit on 29-12-2012 by SilentKoala because: (no reason given)



posted on Dec, 29 2012 @ 07:15 PM
link   
wow i didn't know this thanks for the share now that i really think about it ya it would!!!



posted on Dec, 29 2012 @ 07:25 PM
link   
reply to post by BobSacamano
 


We should probably prepare for the day that google decides not to store all the old imagery. It is a bit of a research project, but my understanding is there is a program that slowly moves the Google Earth view, which in turn puts the data in your cache. Then you archive the cache.



posted on Dec, 29 2012 @ 08:19 PM
link   
I've able to 'rewind' the timeline all the way back to the 60's and 70's in the NTS area, in the past. I haven't fired up Google Earth in a couple months, and get on today to see that it's capped at 10 years back (2002) in that region.

Kinda upset by this actually


*puts on tin foil hat* Maybe they're becoming wise that we were catching on to the apparent/totally obvious new construction and expansions that have been going on for the last 4 decades.. lol?



posted on Dec, 30 2012 @ 01:00 AM
link   
reply to post by gariac
 


There's no way you would be able to store that much data. Every single piece of imagery from every historical date from every location on the globe at every zoom level couldn't fit on all the hard drives at your local Fry's. That's why the data has to be streamed and isn't included as a standalone program.



posted on Dec, 30 2012 @ 01:31 AM
link   
reply to post by SilentKoala
 


I meant storing the data just for the Nevada Test and Training range, i.e. not storing everything Google has on GE. Certainly this would make sense for Groom Lake at the very least.

Sometimes the older data is clearer than the new data, or there were interesting aircraft on the ground in older imagery.



posted on Dec, 30 2012 @ 03:57 AM
link   
reply to post by gariac
 


That makes more sense. Funny you should mention GE and Groom Lake, I was just browsing around there for kicks earlier.



posted on Dec, 30 2012 @ 11:08 AM
link   
reply to post by SilentKoala
 


In theory, Google determines where to buy new imagery based on where people look. So look at Groom Lake , the TTR, etc often. Here is a list of interesting spots:

TTR: 37°47'53.71"N 116°46'18.36"W
Base Camp: 38°18'39.77"N 116°16'43.96"W
Groom Lake: 37°14'14.26"N 115°48'27.61"W
Creech: 36°35'2.78"N 115°41'4.30"W (this is the Predator with shadow that Virtual Globetrotting found)
AOF: 36°55'37.48"N 116° 0'27.35"W
China Lake: 35°41'22.58"N 117°41'27.32"W
Honda test track (OK, not really spooky): 35°16'28.03"N 117°57'8.64"W
Kia Test track (ditto): 35° 3'32.65"N 118° 1'57.42"W
Edwards: 34°54'27.72"N 117°52'53.32"W
Mojave: 35° 3'8.03"N 118° 8'41.06"W
Tejon RCS (new imagery 2011): 34°55'39.27"N 118°31'56.69"W
(flying triangles at Tejon ;-) : 34°55'33.81"N 118°31'39.86"W and 34°55'31.66"N 118°31'38.41"W
General Atomics Gray Butte: 34°33'54.78"N 117°40'50.58"W
General Atomics El Mirage and El Mirage junk yard: 34°37'19.28"N 117°36'12.71"W
Helendale RCS (marker on new pad): 34°48'38.34"N 117°17'55.68"W



posted on Dec, 30 2012 @ 09:44 PM
link   

Originally posted by gariac
reply to post by SilentKoala
 
I meant storing the data just for the Nevada Test and Training range, i.e. not storing everything Google has on GE. Certainly this would make sense for Groom Lake at the very least.Sometimes the older data is clearer than the new data, or there were interesting aircraft on the ground in older imagery.


There IS "Google Earth Voyager (GEV)" for offline cache storage. I use it to store GE cache(s) to use offline when I am "down on the range" and don't have internet access. I guess myself or someone else should take the time to archive the NTTR. Never used it with the history tool though.

I see the historical images of Area 51 only go back to 6/6/2002 now. GE is acting very strangely tonight as well, a lot of lowres mosaic of sections of NTTR.



posted on Dec, 31 2012 @ 12:43 AM
link   
reply to post by FosterVS
 


37°13'46.34"N 115°48'38.95"W
This corner of the new hangar has been modified based on the time machine.

At one point in time, the southwest side of the new hangar was visible. There were what looked like electrical breaker boxes on it. That person that was doing the 3D modeling would know for sure.

The first images of Groom Lake were done in 2000 by the FAS. I don't think it is too weird that GE only starts at 2002. That is the imagery that is misaligned.



posted on Jan, 1 2013 @ 01:49 AM
link   
reply to post by gariac
 

I clearly remember GE displaying black and white 60's or 70's satellite imagery, in the timeline feature.

I'll look through my screenshots from over the years and try to verify that.



posted on Jan, 1 2013 @ 02:17 AM
link   
reply to post by weavty1
 


Certainly not the 60s or 70s. There is an old Soviet B&W Groom Lake image, but it was never on Google Earth. The old B&W imagery on GE is from the USGS, and that didn't cover Groom Lake.



posted on Jan, 1 2013 @ 02:20 AM
link   


The change to the corner of the new hangar can be seen in the above image. It is just a box of sorts sticking out at the corner. It doesn't go all the way to the ground.

I initially thought the black spot on the side of the building is a door, but looking at a few of the shots taken that day, I believe the black area is just a shadow.



posted on Jan, 1 2013 @ 03:17 PM
link   

Originally posted by gariac
reply to post by FosterVS
 


37°13'46.34"N 115°48'38.95"W
This corner of the new hangar has been modified based on the time machine. At one point in time, the southwest side of the new hangar was visible. There were what looked like electrical breaker boxes on it. That person that was doing the 3D modeling would know for sure. The first images of Groom Lake were done in 2000 by the FAS. I don't think it is too weird that GE only starts at 2002. That is the imagery that is misaligned.


I compiled a picture of the different images of that spot on GE. Almost looks to me like they added something to that corner of the building.


Higher res:
www.topsecretbases.com...
edit on 1-1-2013 by FosterVS because: (no reason given)



posted on Jan, 1 2013 @ 05:17 PM
link   
OT - speaking of the big "new" hangar - maybe you can address this gariac.

I have seen the "berm" aka large blocking pile-o-dirt on the east side of this hangar on the panorama's. I haven't seen this discussed, maybe I missed it, but I see more than this berm on the imagery. It appears to me that these berm(s) were placed to block viewing of this hangar from the runways i.e. Janet flights, and possibly other areas of the base, and weren't particularily placed to block the view from Tikaboo?




posted on Jan, 1 2013 @ 05:42 PM
link   
reply to post by FosterVS
 


You probably missed the image link.



I cranked up the contrast a bit more. It looks to me like a landing of some sort, then perhaps stairs to the ground. The solid part doesn't go all the way to the ground. It could be a fire escape or some sort of service access.



posted on Jan, 1 2013 @ 06:49 PM
link   
reply to post by FosterVS
 


It looks to me like they have a small detention basin east of hangar 18.
37°14'8.45"N 115°48'43.60"W
So there could be a berm there where you indicated. I don't know enough about desert construction to comment with any authority, nor do I have a degree in CE. But I have paid for such engineering. In more "normal" places (as in not the desert), they put a detention basin to catch the dirt (silt) that is carried off with the water, then there is a drainage path to dump the water into a stream. [By retaining some water before allowing it to flow, it reduces the storm surge.] But in the desert, they just dig the basin and that is that. I assume they figure the water will just evaporate and/or flow into the ground.

They have a detention basin near the TTR "mancamp".
37°53'14.24"N 116°45'28.50"W
It is actually on the BLM property. To get to Mt. Diablo (which is just a small hill, not to be confused with California's 4000ft Mt. Diablo), you drive the edge of this detention basin.

When you grade for construction, you have to do something with the dirt. [Too bad the infamous nuclear tunnel bore machine that vaporizes dirt doesn't exist.] Whatever you do with the dirt, you can't leave it in a state where it will erode away. [Assuming Groom isn't using the "we don't need no stinkin' badges philosophy.] One solution is to fill a hole. The other is to pile the dirt with a 2:1 slope, which is very stable. [Think of the sands in an hour glass. It wasn't the Vulcan mind meld that made so many civilizations build pyramids.] Since that dirt pile doesn't accomplish much of anything, I think they just piled the dirt there because it was the cheapest disposal solution. The third choice is to off haul the dirt, which eats up a lot of diesel.

Though we don't have a view of the north side of the new hangar, it is pretty obvious there are doors on both sides. Most of the time, I assume they use the door we can't see from Tikaboo.

That berm isn't long enough to block much of the view from the runway. I suppose as a counter argument to the berm being used to block a view, we know the base does put up fences.
37°14'3.78"N 115°48'16.41"W
In the case of this structure, then blocked the Tikaboo view and the view from the base. In security, they often speak of TNO (trust no one).





top topics
 
1
<<   2 >>

log in

join