# Contours and Imagery Not Lining Up

**URL:** <https://community.pix4d.com/t/contours-and-imagery-not-lining-up/6713>\
**Category:** PIX4Dmapper Questions/Troubleshooting\
**Created:** [June 18, 2018, 10:35pm UTC](https://community.pix4d.com/t/contours-and-imagery-not-lining-up/6713 "2018-06-18T22:35:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Henry\_Melgar](https://avatars.discourse-cdn.com/v4/letter/h/df788c/32.png) [@Henry\_Melgar](https://community.pix4d.com/u/Henry_Melgar)\
**Post date:** [June 18, 2018, 10:35pm UTC](https://community.pix4d.com/t/contours-and-imagery-not-lining-up/6713/1 "2018-06-18T22:35:06Z")

</div>

When I create contours in Pix4D I am creating them as 1-foot contours both DSM and DTM and export in a .dxf format.&nbsp; I bring the contours into Microstation V8.&nbsp; I then bring in the orthomosaic created from the same Pix4D project.&nbsp; However, each time I do, Microstation shows the contours offset from the imagery.&nbsp; This is not the case if I bring the same data into GIS (they line up perfect).&nbsp; I also tried bringing the data into Global Mapper and the data was offset even worse.&nbsp; Global Mapper also indicated that the contour data had no projection assigned to it.&nbsp; However, the imagery does have a projection.&nbsp; I’m thinking that each software is trying to reproject the contour data into whatever coordinate system is set by the ortho but not doing a very good job of it. Any thoughts?

---

<div class="post-metadata">

**Author:** ![Antigoni\_Makri](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/antigoni_makri/32/187_2.png) [@Antigoni\_Makri](https://community.pix4d.com/u/Antigoni_Makri)\
**Post date:** [June 22, 2018, 9:30am UTC](https://community.pix4d.com/t/contours-and-imagery-not-lining-up/6713/2 "2018-06-22T09:30:39Z")

</div>

Hello Henry,

The contour lines that are generated by Pix4D are georeferenced and they refer to the selected output coordinate system, the same as the rest of the Pix4D outputs.&nbsp;  
What kind of offset do you observe? Is it horizontal, vertical or in both directions?

Are you using the .dxf&nbsp;file for the&nbsp;Microstation V8 and the GIS software? Or are you maybe using the shapefile for GIS?  
Could you please post here the quality report of the project and share with us the contour lines and the DSM/DTM files?

Regards,

---

<div class="post-metadata">

**Author:** ![ajohnson](https://avatars.discourse-cdn.com/v4/letter/a/57b2e6/32.png) [@ajohnson](https://community.pix4d.com/u/ajohnson)\
**Post date:** [October 11, 2021, 9:21pm UTC](https://community.pix4d.com/t/contours-and-imagery-not-lining-up/6713/3 "2021-10-11T21:21:36Z")

</div>

I am actually having this same issue. When importing the orthomosaic into Civil3D it comes in properly located just as every other file produced from Pix4D. However, when I try importing the ortho and the dsm.tif file into an ArcGIS map, they come into the incorrect area horizontally. The contours for the dsm/dtm (shape file), come in the appropriate location. I have noticed that after importing the files there is an associated file in the file directory that is a .ovr file type.

Any guidance would be very much appreciated as I can’t really find anything online about this.

Thanks,  
AJ Johnson

---

<div class="post-metadata">

**Author:** ![Holden\_Greene](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/holden_greene/32/425_2.png) [@Holden\_Greene](https://community.pix4d.com/u/Holden_Greene)\
**Post date:** [October 25, 2021, 5:17pm UTC](https://community.pix4d.com/t/contours-and-imagery-not-lining-up/6713/4 "2021-10-25T17:17:35Z")

</div>

HI AJ. This sounds like a coordinate system issue. Can you double-check what the data is referenced to and ensure that you have the correct settings in ArcGIS?

---

<div class="post-metadata">

**Author:** ![ajohnson](https://avatars.discourse-cdn.com/v4/letter/a/57b2e6/32.png) [@ajohnson](https://community.pix4d.com/u/ajohnson)\
**Post date:** [October 25, 2021, 5:58pm UTC](https://community.pix4d.com/t/contours-and-imagery-not-lining-up/6713/5 "2021-10-25T17:58:56Z")

</div>

> [@Holden\_Greene](#):
>
> is sounds like a coordinate system issue. Can you double-check what the data is referenced to and ensure that you have the correct settings in ArcGIS?

Hey Holden (and everyone else for that matter),

I did have everything correct in ArcMap. The issue came from the Pix4D exported file. Though it was projected in the proper coordinate system, the spelling/abbreviations were slightly different than what ArcMap recognized. I decided to use the project tool on the raster image, selected what should have been the same coordinate system, and just like that, it moved into the correct location.

For additional context, the Coordinate system I am using as recognized by ArcMap is _NAD\_1983\_(2011)\_IaRCS\_zone\_5_ while the exported information from PiX4D is _NAD\_1983\_2011\_IaRCS\_zone\_5_. Just missing the parenthesis seems to have caused the issue.

Hope this helps someone out there.  
Thanks,  
AJ Johnson

---

<div class="post-metadata">

**Author:** ![Holden\_Greene](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/holden_greene/32/425_2.png) [@Holden\_Greene](https://community.pix4d.com/u/Holden_Greene)\
**Post date:** [October 25, 2021, 8:52pm UTC](https://community.pix4d.com/t/contours-and-imagery-not-lining-up/6713/6 "2021-10-25T20:52:34Z")

</div>

Thanks for sharing. Yeah, that can happen. That’s why I recommend working with EPSG numbers or PRJ files in PIX4Dmapper to avoid these super subtle differences. Good on you for catching that. Thanks for letting us all know.
