Version: 2023.1.0
The problem is not with the images or GCP. I have processed data in a previous version, but in the new version I get this error. The error appears in the "Adjust Images" category.
The original issue has been resolved. The problem was a combination of the regional language pack Faroese (Denmark) and issues with importing metadata from the specific drone camera (DJI Mavic 3 Enterprise). When the Regional format in Windows was set to Denmark the camera values were not importing correctly.
Setting the regional language to English does not reproduce this issue.
When cameras do not have default camera values in the camera database Drone2Map will attempt to import the values from the image metadata. This is something that is not always accurate as different drone manufacturers can have slight formatting changes or even erroneous values. It is good to double check and make sure that the values appearing in the Edit Camera pane make sense. Importing from image metadata is a function that was added in the 2023.1 Drone2Map release and we are continuing to improve upon it.
After reviewing the dataset we found that the camera model was not supported by default within Drone2Map (Autel Evo II Pro version 2). Because of this the image metadata was used instead to attempt filling in the camera parameters. This resulted in no focal length being added and an erroneous value used for all coefficients.
Default values for this camera model have now been added to Drone2Map and will be present in the next patch. Additionally, a check has been added to make sure that dewarp values are valid.
The issue got resolved once i copied all the images to a local drive and not on a network remote drive. I was connected to my office via a VPN, spent hours trying different solutions... Once I copied the files to the local drive and disconnected the VPN, all worked out fine.
Has anyone found a clear source for this error? I had this error constantly in 2023.1, and now have 2024.1 and I'm still getting this same error regardless of the drone platform I'm using. CS's are correct, the "language" settings have done nothing, image metadata is correct, I've imported photos from both direct import images and import image folder. Images are stored locally. I get this error with Dji Ph4, Mavic3, Mavic3M, M200 with x4s. Esri support has emailed that "the bug will be fixed in new ArcGIS update, but with no clear answers as to what the problem is and their only feed back was to make sure images are sorted by file type and all in the same folder on the local harddrive. ....so 6 months of troubleshooting and I still don't have an answer.
Hi @EricElizondo ,
If you are open to sharing the data I can have a look and see if I can reproduce the problems you are seeing. Feel free to email me directly (mbarker@esri.com) and I can setup a data share.
Regards,
Mark
The Coordinate System my images are using is just WGS 1984 where as the Project Coordinate System is set to WGS 1984 UTM Zone 14N which is the zone the pics were taken. Not sure if the difference in the two is significant.
Sadly, that didn't change anything. Keeps coming up with that error. Ever since I updated to the latest version. Trying to render a tower with about 2100 images. Not sure if this is the best app to do it with but trying anyways.
Try to change the focal length to 0.55 mm and process everything again.
Hello, I'm also having the same error and using a Sony camera on a Skyfish drone. Attaching the camera parameters for info.
Hi @FrankiePettitGISP,We are still working on narrowing down the problem. So far I have been unable to reproduce the issue on my end, but the more information the better. If you can email me your system hardware information and let me know what other Esri software you have installed, if any. If you are also open to sharing out an example dataset I can get a shared folder going. What coordinate systems are you using for your project?Regards,Mark
I am getting the exact same issue with and without GCP. @MarkBarker1 did you find a solution?
Hi Peter,
Feel free to email me directly (mbarker@esri.com) and you can either share the data or I can setup a shared folder to do so.
Thank you,
Hi Mark
I am sure the data is within the coordinate system. I am willing to share data so the issue can be fixed. I can only attach 9 MB data, how should I share data?
Hi @PeterLarsen ,The error that you are seeing tends to happen when the dataset is not actually within the defined coordinate systems area. I was able to test the exact coordinate systems you used with our 3D sample data as it shares the same UTM zone. The dataset processed without errors on the transformation and output in the correct coordinate systems. If you are sure the data is within those coordinate systems, and you are consistently seeing this error, then are you willing to share out some of the data in question? If there is indeed a problem I would like to try to reproduce the issue so we can get a fix in. Thank you,Mark
Hi Pål
It could be related to the mosaic.
The processing fails after about 2 mins.
I made a new project
Hi Peter, never seen that before, but maybe the problem actually is related to the prior error "adding mosaic dataset failed" ? Did you reprocess in the existing project or did you create a new project?
pH
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
