I haven't tested this hypothesis yet, but would it help if the image were projected as Lat.-Long. before exporting as a geotiff?
GeoTIFF can handle all sorts of different coordinate systems. It doesn't have to be in lat/lon. Respectfully, you're not taking the right approach if you want help. The most likely problem is some error in workflow, although it might be something else. To find a possible error, anybody who wants to "look over your shoulder" needs details on what you're doing. Jumping around considering various hypotheses without describing the basics doesn't help. There are three very important reasons to describe the basic, necessary info in complete detail: First, the process of simply stating everything that's going on in detail very often reveals an error in workflow, something overlooked, something that's been assumed to be a particular way when it isn't, etc. Second, you can't narrow possible issues down without knowing what's going on. Third, on rare occasions bugs do pop up, but those get exponentially harder to find if the basic info isn't there. So start by saying what version/build of 9 you're using, how the image was created, exactly where it is supposed to be, and how it was exported. Verify there's nothing wrong with basic coordinate system management by doing things like displaying it in a map with "known good" layers like Bing streets or Google satellite, exporting it from 9 and then re-importing it into 9 and verifying it does come back in where it is supposed to be. Once you have all that verified, if the issue is importing it into 8, say exactly how you're doing that, what version/build of 8 you're using, whether the various other files like .tifw and .prj files are in the folder from which you import, etc. With all the details in hand, odds are great the forum can help out, and if not, those details will be essential for tech support to look into the matter to help you out, or if a new bug is in play to find and fix that bug rapidly.
|