Only the center of the image will appear close to the correct location assuming that the coordinate systems are set up properly. The error compounds radially from the center of the image. This simple conversion from the center-of-image to the upper left corner was programmed sloppily in Civil3D. Test it out on one of your American football fields and you'll see. Goal-to-goal equals 360 feet.
The displays are "rubber sheeted" in Google Earth according to your terrain options settings. The radial error is a pixel-to-ground innacuracy caused by sloppy programming on the Civil3D end. It is independent of the Google Earth terrain settings and still exists even when the terrain is de-activated. If you measure the distance in Google Earth it is correct. When you measure between the same points in Civil3D it is wrong. Fill your Google Earth screen with an east-west Football field with midfield at the center of the screen (artificial turf works the best). Perform the import into Civil3D. Measure known distances between the field markings in the imported Civil3D image and compare.
