topic Re: Ortho Mapping - errors when creating workspace in ArcGIS Pro Questions

Ortho Mapping - errors when creating workspace

Anonymous User — Sat, 25 Mar 2017 04:52:13 GMT

Hi all.

Am having my first play with the 'Ortho Mapping' within ArcGIS Pro 1.4. I have some UAV photos captured using a Phantom 4.

I clicked new workspace, entered a name etc, then selected the folder where the photos were located. It successfully detected the geolocation data within the imagery and the spatial reference. I didn't change any parameters, just left everything as default, then I clicked next. It began to create the workspace and a log page appears.

However, here something goes wrong - it begins to spit out errors, looks like they are repeated once for each photo. I have pasted below the error messages. I'd be interested to know if anyone else has experienced this or knows what is happening here and how to fix whatever's going wrong.

Cheers,

-Paul

Queued...
Building image collection...
Start Time: Saturday, 25 March 2017 5:31:24 PM
2017-03-25T17:31:28.826: Loading raster datasets
2017-03-25T17:31:28.972: Completed crawling 573 data source items. Added 573 mosaic dataset items.
2017-03-25T17:31:28.978: Synchronizing crawled data source items
2017-03-25T17:31:29.021: Synchronizing items associated with raster type instance 'UAV/UAS' [ID: 1].
2017-03-25T17:31:29.043: Distributing mosaic dataset operation across 2 parallel instances on the specified host: [LAPTOP-8A254KAB].
2017-03-25T17:31:38.992: Error: 8004206c: Failures reported while processing specified command item. [1]
2017-03-25T17:31:39.002: Error: 80042019: Chained Error ID: 0X80042019
2017-03-25T17:31:39.010: Error: 80042019: Could not build mosaic dataset item. [ID: 1, URI: 'C:\Oskat\photos\DJI_0397.JPG']
2017-03-25T17:31:39.019: Error: 8004103f: Creation of frame camera model failed.
2017-03-25T17:31:39.039: Error: 8004206c: Failures reported while processing specified command item. [2]
2017-03-25T17:31:39.050: Error: 80042019: Chained Error ID: 0X80042019
2017-03-25T17:31:39.059: Error: 80042019: Could not build mosaic dataset item. [ID: 2, URI: 'C:\Oskat\photos\DJI_0398.JPG']
2017-03-25T17:31:39.067: Error: 8004103f: Creation of frame camera model failed.

etc, etc until the end:

2017-03-25T17:33:24.335: Error: 8004206c: Failures reported while processing specified command item. [200]
2017-03-25T17:33:24.345: Error: 80042019: Chained Error ID: 0X80042019
2017-03-25T17:33:24.357: Error: 80042019: Could not build mosaic dataset item. [ID: 200, URI: 'C:\Oskat\photos\DJI_0596.JPG']
2017-03-25T17:33:24.363: Error: 8004103f: Creation of frame camera model failed.
2017-03-25T17:33:24.558: Error: 8004205e: 573 mosaic dataset items could not be built.
2017-03-25T17:33:24.706: Removing invalid mosaic dataset items
2017-03-25T17:33:24.999: Removing unreferenced raster type and overview instances
2017-03-25T17:33:25.011: Removed 573 mosaic dataset items and 1 unreferenced raster type instances.
2017-03-25T17:33:25.270: Removing broken mosaic dataset items.
2017-03-25T17:33:25.499: Removed 0 mosaic dataset items and 0 unreferenced raster type instances.
2017-03-25T17:33:25.685: Completed synchronization: 573 items selected, 0 items synchronized.
ERROR 999999: Error executing function.
Failed to execute (AddRastersToMosaicDataset).
Failed at Saturday, 25 March 2017 5:33:30 PM (Elapsed Time: 2 minutes 5 seconds)

Re: Ortho Mapping - errors when creating workspace

DanPatterson_Retired — Sat, 25 Mar 2017 09:14:11 GMT

a threads dealing with workspace https://community.esri.com/message/664746-can-i-build-the-mosaic-for-a-ortho-mapping-workspace-manually

and one on camera frame model https://community.esri.com/message/665765-re-can-i-somehow-apply-yaw-pitch-and-roll-values-instead-of-omega-phi-and-kappa-when-i-create-a-new-ortho-mapping-workspace-drone-type-in-arcgis-pro-14?commentID=665765#comment-665765

Then there is whole litany of related topics in the help file that might suggest that a defaults install may not be appropriate

http://desktop.arcgis.com/en/arcmap/latest/manage-data/raster-and-images/ortho-mapping-overview.htm

Re: Ortho Mapping - errors when creating workspace

Anonymous User — Mon, 27 Mar 2017 19:41:14 GMT

Thanks Dan.

Seems like it's a more complex than I thought (i.e. not a straight forward process like drone2map).

I'll have to put it aside for another day to try and work through.

Cheers,

-Paul

Re: Ortho Mapping - errors when creating workspace

MingzhenChen — Wed, 12 Apr 2017 21:07:00 GMT

Might I have the Camera information (Maker and Model)?

Re: Ortho Mapping - errors when creating workspace

KevinCrichlow1 — Wed, 12 Apr 2017 22:42:11 GMT

I'm also having a problem building my ortho workspace. ArcGIS Pro is refusing to add my imagery to a mosaic dataset that is part of the process. I'm using Ultracam 20cm with EO & IO Parameters defined using a .csv.

Here is a screen shot of my error:

Re: Ortho Mapping - errors when creating workspace

Anonymous User — Wed, 12 Apr 2017 22:45:43 GMT

Hi Mingzhen

The images were taken using a DJI Phantom 4 Pro. This link should give you the details I think:

DJI Phantom 4 Pro – Specs, FAQ, Tutorials and Downloads

Here's a copy/paste of some of the info from that page, hope that's enough info??

Sensor	1’’ CMOS Effective pixels: 20M
Lens	FOV 84° 8.8 mm/24 mm (35 mm format equivalent) f/2.8 - f/11 auto focus at 1 m - ∞
ISO Range	Video: 100 - 3200 (Auto) 100 - 6400 (Manual) Photo: 100 - 3200 (Auto) 100- 12800 (Manual)
Mechanical Shutter Speed	8 - 1/2000 s
Electronic Shutter Speed	8 - 1/8000 s
Image Size	3:2 Aspect Ratio: 5472 × 3648 4:3 Aspect Ratio: 4864 × 3648 16:9 Aspect Ratio: 5472 × 3078

Re: Ortho Mapping - errors when creating workspace

MingzhenChen — Wed, 12 Apr 2017 23:37:26 GMT

Hi Paul,

Thank you so much.

Are the images oblique? Pro is unable to handle oblique images now.

Best regards,

Mingzhen

Re: Ortho Mapping - errors when creating workspace

Anonymous User — Wed, 12 Apr 2017 23:48:20 GMT

No they aren't. Although even if they were, how would that cause the intial workspace build to fail? I would have thought it would fail later on when it was trying to stitch them together?

Re: Ortho Mapping - errors when creating workspace

MingzhenChen — Wed, 12 Apr 2017 23:50:38 GMT

Hi Kevin,

It seems the Parameters didn’t be got correctly. Please double check the image location (GPS) and Camera parameters.

If possible, please share me some images and the .csv file.

Thanks,

Mingzhen

Re: Ortho Mapping - errors when creating workspace

MingzhenChen — Wed, 12 Apr 2017 23:56:02 GMT

Please double check the Camera Parameters. Make sure focal length, pixel size, columns and rows are correct.

Re: Ortho Mapping - errors when creating workspace

NaomiBegg2 — Wed, 28 Jun 2017 00:46:45 GMT

Hi Paul Haakma‌

Did you manage to find a solution?

I am trying to run some photographs taken using a DJI Phantom 4 Pro but I am receiving two errors for each photo

Error: 80042019: Could not build mosaic dataset item

Error: 8004103f: Creation of frame camera model failed

I can't see what specific settings require changing within the New Ortho Mapping Workspace as this is auto filled.

Re: Ortho Mapping - errors when creating workspace

Anonymous User — Wed, 28 Jun 2017 01:03:42 GMT

HI Naomi,

No I never did - to be honest I have never gone back and tried again (was only ever playing with it to see what it could do).

I had mentally parked it up as something to test again when Pro 2.0 comes out.

If you ever manage to get it going, please do post here.

Cheers,

-Paul

Re: Ortho Mapping - errors when creating workspace

NaomiBegg2 — Wed, 28 Jun 2017 04:56:03 GMT

Hi Paul

I've just downloaded Pro 2.0 and given it another run.

This still hasn't been successful but it has provided another line of error code which is helpful.

I now receive the following errors:

Error: 80042019: Could not build mosaic dataset item.

Error: 80004005: Creation of frame camera model failed.

Error: 80004005: The altitude is too low at -125.378768 meter.

I'm not sure if it is failing to convert the correct height as I definitely haven't flown the drone at -100m!

I thought at first that maybe 125m is the minimum height required, but this number slightly changes for each photo.

Re: Ortho Mapping - errors when creating workspace

NaomiBegg2 — Wed, 28 Jun 2017 05:07:09 GMT

I've just upgraded to Pro 2.0 and I am still getting error messages when I try to OrthoMap.

2.0 brings the addition of another error 80004005 which is telling me that the altitude is to low. However I don't understand how they get an altitude of -125m/-124m when the details on the pop-up clearly state that the altitude is 275.76.

Re: Ortho Mapping - errors when creating workspace

MingzhenChen — Fri, 30 Jun 2017 00:55:21 GMT

What is the elevation of working area? If the elevation is larger than GPS altitude (e.g. 275.76), it will cause the problem.

Re: Ortho Mapping - errors when creating workspace

NaomiBegg2 — Fri, 30 Jun 2017 03:23:53 GMT

Here are our contours for that area. Approximately 394m.

Re: Ortho Mapping - errors when creating workspace

MingzhenChen — Fri, 30 Jun 2017 14:18:47 GMT

It seems the GPS altitude (e.g. 275.76) is not the elevation. Please try using constant Elevation 0 as DEM.

Re: Ortho Mapping - errors when creating workspace

WilliamByrne1 — Wed, 15 Nov 2017 04:45:37 GMT

I have the same issue. I ran it with constant elevation of 0 and still no dice. Even if that was the case, flying at different elevations and flying oblique are essential to good 3D modeling.

Re: Ortho Mapping - errors when creating workspace

ToddUlery — Fri, 26 Oct 2018 22:07:28 GMT

This is a dated response, but did you ever get a resolution to the Altitude issue when making a workspace with Drone imagery? I have the same model and errors as you do.

Re: Ortho Mapping - errors when creating workspace

Carl_Flint — Tue, 08 Jan 2019 15:12:13 GMT

It appears that the software is misreading the exif metadata on the images themselves. I have a similar issue with Pro v2.2.4 and tested Desktop's method of creating a raster mosaic using the UAV/UAS parameter.

Below is a snip of the Camera Locations table created from the Pro Orthomapping tool. Currently the only way I have found to workaround is to set a static flight height for all images.

Below is a snip of the above highlighted records metadata in the image. Notice the Altitude value here is not negative.

There is some kind of issue with parsing the metadata and a simple fix would be to get the absolute value of the element.