Error 999999 Failed to execute computecameramodel help please!

2671
7
Jump to solution
09-21-2018 06:47 AM
Labels (1)
On_BothSides
New Contributor

Hi Everyone, New user to Arcgis Pro and having inconsistent results trying to produce orthomosaics.

Error 999999 Computecameramodel

The error code is 999999 and the error message is failed to execute "ComputeCameraModel".

I tried working with a smaller sample of images. The camera used is the Mapir Survey 3N and I have populated the camera parameters with the correct Focal length, Pixel size and columns and rows.

Here is a copy of the logs.

Queued...
Running...
Building image collection...
Start Time: Friday 21 September 2018 14:24:19
2018-09-21T14:24:33.256: Loading raster datasets
2018-09-21T14:24:33.330: Completed crawling 23 data source items. Added 23 mosaic dataset items.
2018-09-21T14:24:33.335: Synchronizing crawled data source items
2018-09-21T14:24:33.371: Synchronizing items associated with raster type instance 'UAV/UAS' [ID: 1].
2018-09-21T14:24:34.288: Estimating raster statistics for mosaic dataset.
2018-09-21T14:24:34.960: Completed synchronization: 23 items selected, 23 items synchronized.
2018-09-21T14:24:35.692: Computing cell size levels
2018-09-21T14:24:35.694: Computing unique cell size values
2018-09-21T14:24:35.796: Computing maximum cell size values
2018-09-21T14:24:35.817: Computing minimum cell size values
2018-09-21T14:24:35.833: Updating visibility values of selected items
2018-09-21T14:24:35.880: Computing maximum cell size for mosaic dataset
2018-09-21T14:24:35.897: Completed computing cell size ranges.
2018-09-21T14:24:35.989: Completed building boundary.
Succeeded at Friday 21 September 2018 14:24:38 (Elapsed Time: 18.77 seconds)

--------------------------------------------------------------------------------------

Queued...
Running...
Computing Block Adjustment...
Start Time: Friday 21 September 2018 14:26:25
Computing initial tie points...
Analyzing initial tie point coverage...
1 2018_0917_044116_220
2 2018_0917_044119_222
3 2018_0917_044121_224
4 2018_0917_044124_226
5 2018_0917_044127_228
6 2018_0917_044129_230
7 2018_0917_044132_232
8 2018_0917_044134_234
9 2018_0917_044141_240
10 2018_0917_044144_242
11 2018_0917_044146_244
12 2018_0917_044149_246
13 2018_0917_044151_248
14 2018_0917_044154_250
15 2018_0917_044156_252
16 2018_0917_044449_394
17 2018_0917_044452_396
18 2018_0917_044454_398
19 2018_0917_044457_400
20 2018_0917_044459_402
21 2018_0917_044502_404
22 2018_0917_044504_406
23 2018_0917_044507_408
23 unsolvable images removed.
Estimating initial orientation...
ERROR 999999: Something unexpected caused the tool to fail. Please refer to the error help for potential solutions, or contact Esri Technical Support http://esriurl.com/support.
Failed to execute (ComputeCameraModel).
Failed at Friday 21 September 2018 14:27:56 (Elapsed Time: 1 minutes 31 seconds)

I've also attached a sample file.

Apologies if not posted in the correct place and Mods feel free to move if necessary. 

Any help is greatly appreciated!

0 Kudos
1 Solution

Accepted Solutions
CodyBenkelman
Esri Regular Contributor

Hi, I've had an engineer look at your notes, and I think the exposure is the problem.

Our camera database does not contain this camera, so it will not automatically recognize the MapIR, but it looks like you *do* have the workspace set up correctly.  Unfortunately, the image you sent is extremely dark - the brightest pixel in the image seems to be DN value of 13.  Are all of the images this dark?  Do you have another sample dataset with a more normal exposure?  

If the software can't find any tie points between images, it will remove them as "unsolvable".


Cody B

View solution in original post

0 Kudos
7 Replies
GuenterDoerffel
Esri Contributor

I am/we are happy to assist - but need more information. Best what you use as frame- and camera table, input data, ...

Guenter

0 Kudos
On_BothSides
New Contributor
Image Resolution12 MegaPixel (4,000 x 3,000 px), 8MP
Image FormatRAW+JPG, JPG (RAW is 12bit per channel, JPG is 8bit per channel)
Video Resolution2160p24, 1440p30, 1080p60, 720p60
Video FormatMP4 (H.264 Codec)
Lens Optics87° HFOV (19mm) f/2.8 Aperture, -1% Extreme Low Distortion (Non-Fisheye) Glass Lens
Ground Sample Distance (GSD)5.5 cm/px (2.17in/px) at 120 m (~400 ft) AGL
SensorSony Exmor R IMX117 12MP (Bayer RGB)
ChipsetNovatek NTK96663
GPS/GNSS (External)ublox UBX-G7020-KT
Capture SpeedRAW+JPG: 2.75 Seconds / Photo.  JPG: 1.5 Seconds / Photo
0 Kudos
On_BothSides
New Contributor
Sensor Width6.2496The sensor width of the camera (mm)
Sensor Height4.6872The sensor height of the camera (mm)
Focal Length8.25The focal length of the lens (mm)
Flight HeightFlight height AGL (m)
Flight Height393.701Flight height AGL (ft)
Image Width4032The image width (pixels)
Image Height3024The image height (pixels)
GSD (cm/px)4.050GSD = Ground Sampling Distance (cm/pixel)
GSD (in/px)1.594GSD = Ground Sampling Distance (in/pixel)
VelocityFlight Speed (m/s)
Velocity32.808Flight Speed (ft/s)
Velocity36.000Flight Speed (kmh)
Velocity22.369Flight Speed (mph)
Min Shutter S0.02025Seconds
Min Shutter S49.3831/X s
Front OverlapImage to Image Front Ovelap (%)
GSD Frame H139.968Meters
Min fps0.143Frames per Second Minimum
Photo Interval6.993Seconds Minimum Between Photos
Sensor Readout3.150Milliseconds
Displacement5.951Vertical Pixel Displacement
0 Kudos
On_BothSides
New Contributor

Thank you Guenter! I have posted all the info I could find on the camera and regarding the input data do you need the whole image set? I uploaded one image with my original post so let me know. I really appreciate you taking the time to help!

0 Kudos
CodyBenkelman
Esri Regular Contributor

Hi, I've had an engineer look at your notes, and I think the exposure is the problem.

Our camera database does not contain this camera, so it will not automatically recognize the MapIR, but it looks like you *do* have the workspace set up correctly.  Unfortunately, the image you sent is extremely dark - the brightest pixel in the image seems to be DN value of 13.  Are all of the images this dark?  Do you have another sample dataset with a more normal exposure?  

If the software can't find any tie points between images, it will remove them as "unsolvable".


Cody B

0 Kudos
On_BothSides
New Contributor

Thank you Cody! I will look at the exposure settings. Mapir state not to adjust the default exposure settings on the camera. I'll test and let you know.

0 Kudos
On_BothSides
New Contributor

Solved! Thank you everyone. Its was the exposure settings as you stated. They were set too low by default on the Mapir camera and as you mentioned this stopped the software from finding tie points between the images. Much appreciated.

0 Kudos