# M3E RTK not compatable with Mapper? **URL:** \ **Category:** PIX4Dmapper\ **Created:** [April 5, 2023, 2:25pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012 "2023-04-05T14:25:17Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![Fletch](https://avatars.discourse-cdn.com/v4/letter/f/919ad9/32.png) [@Fletch](https://community.pix4d.com/u/Fletch)\ **Post date:** [April 5, 2023, 2:25pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/1 "2023-04-05T14:25:17Z")
I am unable to process images from a M3E RTK. after Step 1 it creates a big mess ![2023-04-05 15_23_42-Carolina Scan PC - TeamViewer](https://global.discourse-cdn.com/pix4d/original/2X/4/4951e98d416a9d6b7665a828633ea3179ece3bd9.png) According to other users I have asked Pix4D cannot use the M3E RTK properly and I should get other software. ---
**Author:** ![Fletch](https://avatars.discourse-cdn.com/v4/letter/f/919ad9/32.png) [@Fletch](https://community.pix4d.com/u/Fletch)\ **Post date:** [April 5, 2023, 2:25pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/2 "2023-04-05T14:25:48Z")
![2023-04-05 15_22_44-Carolina Scan PC - TeamViewer](https://global.discourse-cdn.com/pix4d/original/2X/b/bb9072ad549963b8cea8638659e33ee0e8ad33d0.png) ---
**Author:** ![Mike\_K](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/mike_k/32/4697_2.png) [@Mike\_K](https://community.pix4d.com/u/Mike_K)\ **Post date:** [April 5, 2023, 5:38pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/3 "2023-04-05T17:38:16Z")
Hi mnfletcher, Full support for the Mavic 3 Enterprise came in version 4.8.3. I highly suggest installing this version for the best results with this drone. ---
**Author:** ![Fletch](https://avatars.discourse-cdn.com/v4/letter/f/919ad9/32.png) [@Fletch](https://community.pix4d.com/u/Fletch)\ **Post date:** [April 5, 2023, 5:54pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/4 "2023-04-05T17:54:02Z")
im running 4.8.3 ---
**Author:** ![Yoko\_Rader](https://avatars.discourse-cdn.com/v4/letter/y/51bf81/32.png) [@Yoko\_Rader](https://community.pix4d.com/u/Yoko_Rader)\ **Post date:** [April 5, 2023, 7:04pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/5 "2023-04-05T19:04:18Z")
Could you attach your quality report and we can take a look at it. ---
**Author:** ![Fletch](https://avatars.discourse-cdn.com/v4/letter/f/919ad9/32.png) [@Fletch](https://community.pix4d.com/u/Fletch)\ **Post date:** [April 6, 2023, 8:38am UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/6 "2023-04-06T08:38:32Z")
[Area A pt2\_report.pdf](https://community.pix4d.com/uploads/short-url/4xK83KGjdCMZFU6mSGcLuChzfOd.pdf) (1.2 MB) ---
**Author:** ![Jaakko\_Laihola](https://avatars.discourse-cdn.com/v4/letter/j/f6c823/32.png) [@Jaakko\_Laihola](https://community.pix4d.com/u/Jaakko_Laihola)\ **Post date:** [April 6, 2023, 4:07pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/7 "2023-04-06T16:07:25Z")
Change the image cooridinate system to wgs84 and you should be fine. BTW Mavic 3e with RTK is working perfectly on 4.7.5 (except geoid support) ---
**Author:** ![Mike\_K](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/mike_k/32/4697_2.png) [@Mike\_K](https://community.pix4d.com/u/Mike_K)\ **Post date:** [April 6, 2023, 5:40pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/8 "2023-04-06T17:40:49Z")
Yes, I agree. You need to change your image coordinate system to wgs84. You might also want to use the Accurate Geolocation and Orientation calibration method as well. ---
**Author:** ![Fletch](https://avatars.discourse-cdn.com/v4/letter/f/919ad9/32.png) [@Fletch](https://community.pix4d.com/u/Fletch)\ **Post date:** [April 7, 2023, 11:24am UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/9 "2023-04-07T11:24:52Z")
I dont want to be in WGS84. Are you suggesting I shouldnt produce output in another coord system? ---
**Author:** ![Mike\_K](https://sea2.discourse-cdn.com/pix4d/user_avatar/community.pix4d.com/mike_k/32/4697_2.png) [@Mike\_K](https://community.pix4d.com/u/Mike_K)\ **Post date:** [April 7, 2023, 2:24pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/10 "2023-04-07T14:24:41Z")
Hi Fletch, The image coordinate system is different than your output coordinate system. Your drone should be tagging the images in WGS84. However, you should then select your desired output coordinate system in PIX4Dmapper. This will give you a better result. ---
**Author:** ![Fletch](https://avatars.discourse-cdn.com/v4/letter/f/919ad9/32.png) [@Fletch](https://community.pix4d.com/u/Fletch)\ **Post date:** [April 7, 2023, 3:20pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/11 "2023-04-07T15:20:47Z")
The drone is acquiring images in WGS84. Then we transform to our coord system. the image coord system is thus correct and is the same as the output system. Pix4D does not do a good enough transformation between WGS84 and our country system. Also the time taken to do step 1 is ridiculous. The report I attached was half the project. The full project with about 4800 images took nearly 5 hours for step 1 on 1/4. I used geometric matching and that took over 6hrs. Crazy. Needless to say I have processed it successfully with no fuss using another vendor and the time it took for the initial step was **significantly** less. Our Pix4D licenses are up for renewal in a few months and I dont think we will be doing that especially if we cant understand what is happening here. Now I’m perfectly willing to accept there might be a setting I need to use or something like that but even just processing WGS84 to WGS84 with no attempt at a transformation results in the same mess. ---
**Author:** ![Jaakko\_Laihola](https://avatars.discourse-cdn.com/v4/letter/j/f6c823/32.png) [@Jaakko\_Laihola](https://community.pix4d.com/u/Jaakko_Laihola)\ **Post date:** [April 7, 2023, 3:59pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/12 "2023-04-07T15:59:35Z")
If you have to use your local coordinate system in the pictures you will need to update the exif data in the pictures to correspond that coordinate system. Otherwise it will mess up the first step. I Would use wgs84 as the image coordinate system and choose the output as desired (IRENET95 / Irish Transverse Mercator in your case). And if you did the flight with RTK remember to change the calibration method to ‘Accurate Geolocation and Orientation’. Lastly if you need to use orthometric heights change the ‘height above ellipsoid’ offset according to your local offset since the Pid4mapper doesn’t have proper geoid support. ---
**Author:** ![Fletch](https://avatars.discourse-cdn.com/v4/letter/f/919ad9/32.png) [@Fletch](https://community.pix4d.com/u/Fletch)\ **Post date:** [April 7, 2023, 4:37pm UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/13 "2023-04-07T16:37:29Z")
I did update the exif data thats why the image and output coord systems are the same. We do accurate transformations and then update the images and change input coord system. I will consider your comments regarding the calibration methods as these are the kinds of settings I suspect are the issue. Thank you. ---
**Author:** ![wail](https://avatars.discourse-cdn.com/v4/letter/w/97f17d/32.png) [@wail](https://community.pix4d.com/u/wail)\ **Post date:** [April 29, 2023, 4:28am UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/14 "2023-04-29T04:28:23Z")
Lastly if you need to use orthometric heights change the ‘height above ellipsoid’ offset according to your local offset since the Pid4mapper doesn’t have proper geoid support. How is this done?? ---
**Author:** ![Jaakko\_Laihola](https://avatars.discourse-cdn.com/v4/letter/j/f6c823/32.png) [@Jaakko\_Laihola](https://community.pix4d.com/u/Jaakko_Laihola)\ **Post date:** [April 29, 2023, 5:14am UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/15 "2023-04-29T05:14:55Z")
In the ‘Select Output Coordinate System’ windows tick the Advanced Coordinate Options box and type your local offset to Geoid Height Above… box ![image](https://global.discourse-cdn.com/pix4d/original/2X/e/e25f42b99eeefaa4cfbed7eaa2ad5d995aa5fdca.png) ---
**Author:** ![wail](https://avatars.discourse-cdn.com/v4/letter/w/97f17d/32.png) [@wail](https://community.pix4d.com/u/wail)\ **Post date:** [April 29, 2023, 6:56am UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/16 "2023-04-29T06:56:57Z")
Thanks Jaakko, is that a standard difference calculation …17.701? I should convert all my heights by 17.701? Thanks ---
**Author:** ![Jaakko\_Laihola](https://avatars.discourse-cdn.com/v4/letter/j/f6c823/32.png) [@Jaakko\_Laihola](https://community.pix4d.com/u/Jaakko_Laihola)\ **Post date:** [April 29, 2023, 7:17am UTC](https://community.pix4d.com/t/m3e-rtk-not-compatable-with-mapper/26012/17 "2023-04-29T07:17:06Z")
Hi there That was just a screenshot from my latest project, so do not use that as an offset in your projects. You need to always use the local offset. Local offset can be measured by GNNS receiver or you can check if you National land survey can provide you with that information. And remember that if you are mapping large areas or roads for an example the offset can be different in different parts of you project. I would recommend that you use few GCP’s in you projects so you can verify the data. There’s a few processing softwares that support geoids natively (Pix4Dmatic, Metashape, DJI Terra to name a few) if you want to make your life a little bit easier.