nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Verarbeitung mit 2.0 Fehlern

ElginMoore1

<\/HEAD>

Ungültiger Datei-Fehler bei der Verarbeitung ist der neueste Fehler....Ich habe 1.000 Acres mit 1.3x ohne Probleme verarbeitet. Jetzt, bei Verwendung von 2.x, schlägt die Verarbeitung manchmal ohne ersichtlichen Grund fehl. Ich habe; Blue Screen of Death, Verarbeitung stoppt einfach, Computer fährt herunter, "ungültige Datei", "Verarbeitung fehlgeschlagen" usw... Irgendwelche Ideen? <\/P>

Danke<\/P><\/BODY><\/HTML>

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

AnthonyMason

Jeremy,

Add them to the file before importing. For example, if importing a .csv file, add two columns to the end - one for horizontal accuracy and another for vertical accuracy. If you do not know the correct values, simply fill them in with .02 and you should get the same results you are seeing in Drone2Map 1.3.2.

Thanks

Tony

JeremyMurfitt

Tony

Thanks for the update. I don't have D2M open. Do I add accuracy columns in the GCP file or is this a setting I updat once the GCP's have been imported?

Thanks

Jeremy

AnthonyMason

Jeremy,

There is an issue in versions 2.0 and 2.0.1. If the horizontal and vertical accuracy are not specified when importing GCPs, the RMSE may be higher than expected.

A workaround for this in versions 2.0 and 2.0.1 is to make sure your GCPs include the horizontal and vertical accuracy values when importing. If the accuracy is unknown, set it to .02 for both horizontal and vertical accuracy in your GCP file before importing, as this is the default used in Drone2Map 1.3.2.

We have a fix for this coming soon in the 2.0.2 patch. Additionally in version 2.1 we will let you manually change the horizontal and vertical accuracy after importing control.

Thanks

Tony

JeremyMurfitt

I am based in the UK and have experienced processing errors with V2.0.1 when using GCP's. The final outputs have unusual GCP RMSE errors. I checked this by reprocessing projects previously done with 1.3 where I had RMSE errors of 10mm. When processed using 2.0.1 the errors are 250mm. To get back on track I have tried to reinstall 1.3 and that has really hit the buffers. Rolling back seems to be a technical challenge and this currently sits with ESRI UK Support.

RobCahalan

Deleting the DataInterop.dll file worked for me. Thanks!!

ConradStanley

We loaded up D2M 2.0.1 (the patched added) and cannot use GCPs anymore. I reverted to 131 and we are back in business

RobCahalan

Thanks for the info Anthony. I do have Data Interop installed for Pro. My IT manager is out but I will try your suggestions on Monday and reply with the results.

AnthonyMason

Great news Roger!

RogerDiercks1

Thanks for the advice, Tony. Pro is installed on the same machine as Drone2Map, but I don't have the Pro Data Interoperability extension installed. However, deleting DataInterop.dll as you suggested worked. Drone2Map is no longer crashing.

AnthonyMason

Would you guys happen to have ArcGIS Pro with the Data Interoperability extension installed on the same machine as Drone2Map? There is a known issue at Drone2Map 2.0 and 2.0.1 when running Drone2Map on the same machine with this extension.

If you do have this installed, I recommend uninstalling the Data Interoperability extension for ArcGIS Pro or remove the DataInterop.dll from \install location\Drone2Map\bin.

If you do not have ArcGIS Pro with the Data Interoperability extension installed on the same machine as Drone2Map, I would recommend opening a support ticket so we can help identify and resolve the issue.

Thanks

Tony Mason

RogerDiercks1

I can't add anything to this issue beyond that I'm seeing exactly the same behavior on hardware that is virtually identical to Rob's. Attempting to process a recent flight has resulted in 2.0.1 crashing every time. I really wish I had kept the Drone2Map 1.3.2 installer so I could roll back. It worked fine on the same computer.

RobCahalan

I have been having the same issues. I installed 2.0.1 yesterday and have tried running 2 2D Rapid processes and 1 2D full and have received the window to send in an error report all 3 times. As of now it appears that I cannot process any flights. I am running Windows 10, i7-6700 CPU processor, 16.0 GB of RAM...should be able to handle these projects.

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.