I found this thread while searching about this same problem. I had some trouble the other day getting some geotiffs to import into their correct location, they were coming in way off, two states over at best. These were images that I’ve used before, but with a little trial and error I get them to import in the correct location, or so I thought.
We are currently digitizing a bunch of 24k geology quad maps. I have these maps as geotiffs on our server. I used mapiinsert to load one of the geotiffs and started digitizing. After I completed the digitizing I exported the areas to a shapefile on the server. I then opened Global Mapper and imported the same geotiff that I used in Civil3D and the shapefile that I created in Civil3D. I noticed that in Global Mapper my digitized lines were off from where they should be, but only in the top right corner, which makes me think scale issue. I get the same thing in ArcGIS. After some messing around I found that the digitized vectors never changed, it was Civil3D importing the geotiffs incorrectly when using mapiinsert. Then after reading this thread in the last post engrtech mentioned importing through raster design, so I tried that and it imports correctly.
I’m glad that I figured out how to fix the problem because of this thread (thanks engrtech) but I need to rant a little because this is so frustrating. I’ve had a team of three digitizing for a few weeks straight on files created with mapiinsert and now everything we’ve done is off slightly. But that’s nothing when I think that I’ve been using mapiinsert for years. How many years worth of work is slightly wrong now because of this? I feel like I need to let others know about this now. When mapiinsert imports hundreds of miles off that’s one thing, it’s easy to notice, but when it shifts roughly 15 feet over a mile it’s a lot harder to catch. Given the choices, is it not reasonable to assume the one with MAP in the command name would be the correct one to import a MAP with?
