I am developing a base plan from RTK survey shots as I have done many times in Map 2006. After I've connected the points and drawn my physical features, I insert the underlying TIFs from our statewide orthophoto set as a check. These are tifs along with .trf, .aux, .rrd, *.tif.xml files. This latest drawing was created in Map 2006 with no problems inserting the tifs. In 2007, using the same method, they insert in the wrong place and 12 times larger. I brought the drawing back into 2006 and it still inserts in the wrong place. Only if I start a new blank drawing in '06 will they insert in the correct spot. I CAN bring them into the correct spot using Display Manger, but the resolution is degraded. (They are .25m resolution tifs) Any thoughts?
In the Map Image Correlation Box on the Source Tab, are the Units for Insertion Point and Density set to the units the image is in (eg. most of my images are in inches per pixel, so it should be set to Inches)?
This is usually the source of a similar error I receive from time to time.
I have just loaded ACADMAP2007, after tearing my hair out over this image insertion problem I found your reply - very useul - it worked with my images.
One thing of note is that on the second tab - I cannot for the life of me get this to be anything other than inches even though the INSUNITS is set to 6 (metres). The weird thing is that after inserting an image the INSUNITS is set to 0 ???
Also we have one copy Raster Design 2007 (compared to lots of MAP) - in this when you insert images you CAN change the insertion units to metres (to match the image) and eveything works fine.
I am finding that the INSUNITS is getting reset. My drawing unit is originally set to feet. Then I go to Map... Image... Insert... and select the tif which has a tfw file with it. I modify the correlation and change the source units to Meters since the tif is based on meters. But the Insertion tab now has the AutoCAD Units now set to Inches instead of Feet.
Then I quit out and check the Drawing Units and it has been reset to Unitless. So far I haven't figured out why it is doing that.