GE Map offsets

[Approach_Medium]

Hi;
I have been building a prototype route using Google Earth and Transdem.
I have noticed for a long time that often after importing maps from GE into Transdem, that there are offsets where the maps don't exactly line up.
Streets and tracks may be off by a few millimeters, or sometimes more.

I have been careful not to cause GE to rotate, tilt, etc the map during capture, and recently started using the arrow keys instead of the mouse to position the map for the next capture.
I thought that perhaps when the GE captures aren't in-line with each other, there could be displacements, but this is not the case. I still get the offsets regardless of how I move the maps before capture.

Normally, I overlap my maps by about 15-25%.

Has anyone else had this problem, and if so, what is the solution?

Thanks

FW

 

[Dermmy]

I use screen caps from GE for another purpose, overlapping many shots to produce a single image and have never had the images not allign perfectly. Always use the arrow keys to move, always hit 'r' (resets tilt and compass) before capture...

Andy

 

[Approach_Medium]

I use screen caps from GE for another purpose, overlapping many shots to produce a single image and have never had the images not allign perfectly. Always use the arrow keys to move, always hit 'r' (resets tilt and compass) before capture...

Andy

Maybe it's a Transdem issue. The only other program I use to capture from GE is Snagit, but the images are not geo-referenced.
I'm pretty much done with what I need to do in GE, but am curious to fix the problem for my next route.

FW

 

[Dermmy]

Why not just use Ctrl+Alt+S from GE for a screen cap?

 

[Approach_Medium]

Why not just use Ctrl+Alt+S from GE for a screen cap?

That is what I am doing.
First, create a placemark, then Ctl-S, followed by Ctl-Alt-S to save the .jpg file.
There is really no need to use Snagit at all, but I was in the habit of using it for non-georeferenced images from GE.
Also, Snagit allows direct printing, so I don't have to open the .jpg file in another app to print.

This problem I have with offsets seems to occur only when I create geo-referenced maps that are more than one screen wide.
When I want to get in close to a RR route, and need to create images on either side of the track, I would use two captures, creating two georeferenced maps and load them into my DEM in Transdem.
This is where I see the offset.
If I simply follow the RR route capturing only one GE image, with the track at center, then proceeding along the route to capture the next image, I do not have the problem.

I really didn't need to get in so close except when I wanted to detail the route's interlockings, etc. I have dealt with the offsets by estimating the position of the track, and this has worked out well enough.
The offset wasn't all that bad. It might have amounted to about 50m or so.

FW