Latest Contributions by CodyBenkelman

‎03-31-2019

3 of 81 images calibrated means 78 images are not being used. Please check your image altitude (Z values) in a few of the images. I expect you likely have an error in the image heights - this is a common issue with some DJI drones. If the height above ground appears too high, the software does not have the correct overlap. Drone2Map has a function to adjust this Note for future flights I would recommend 70% overlap, not 55% Cody B

‎03-30-2019

Jason Can you tell us more about your project data? And/or, is it possible to send us a complete set of images? A few specific questions: 1) You've said "consistently get error" - How many different projects have you tried? e.g. "I've flown 10 drone projects, #1 works, the other 9 all fail" or do you have one project that you've tried and tried, changing configurations, and that one project always fails? 2) are you using ground control? 3) can you look at your one successful project, open the Processing Report, and let us know the "Camera Optimization" results? e.g. "XX% relative difference between initial and optimized internal camera parameters 4) is this a DJI drone? Some of the DJI drones report very poor values for flight altitude, and if you have that AND you don't have ground control, the software has to guess at the focal length and it can lead to some wildly erroneous values. (I'm not trying to blame DJI for the software errors, but just seeking to give you advice on how to move forward) Thx Cody

‎03-26-2019

Pål Drone2Map 2.0 (coming this summer) will have more datum support. Until then, you can simply use a constant elevation value, but this is only used for the initial estimation of scale/resolution. If you apply GCPs, they define the final height values for 3D products. Cody B

‎03-22-2019

Lan 1) First we need to figure out why step 1 did not work. 2) You'll want to run the multiplexer to calculate the XY coordinates of the frame corners. Did you deliberately choose to deselect that, or did you have problems and find it would not work unless you deselected that? You said "None of these tools work". You tried all 6 tools, and none of them worked? Extract video frames for Orthomosaic should export JPGs with EXIF metadata, but I have not tested it with the frame corners not calculated. (Logically the frame corners should not be required, but I would assume you DO want frame corners for the video to be useful). Am I correct that you did not shoot video at an oblique angle, but it was aimed at or near nadir? And did you also fly parallel overlapping flightlines? If my assumptions are not both true, then it is not likely that DroneDeploy will be able to process the single frames. Cody B

‎03-18-2019

Lan This is an example of what I was referring to, regarding inaccurate altitude values in DJI drones. It appears the altitude values in your metadata may be 80 m too high. Based on what you said here, I would EITHER: 1) use a calculation to subtract 80 meters from the Sensor True Altitude, then enter 545 m into the tool for "Average Elevation", or 2) leave the *.csv file as is, and enter 625 into the tool for "Average Elevation" The advantage of 1) is that your metadata.csv file would show the (approximately) correct altitudes - but if you're using MS Excel, be sure to remove the formulas after calculation and write numeric values (not formulas) in your metadata.csv file. Also be sure to CLOSE the file (not editing in MS Excel) before running the multiplexer. Cody

‎03-18-2019

Support for a DEM was implemented in the Pro version, but for the FMV 1.4 add-in to ArcMap, the multiplexer will process assuming flat terrain. I appears your metadata file reports height above sea level (orthometric height), so if 700 is correct for the flight altitude, enter the average elevation for the local terrain into the tool. If you would prefer to edit the metadata file such that it reports height above launch point, enter 0 for average elevation. Note that DJI drones often do not report accurate values for flying height, so you may need to adjust the metadata file to get the proper flight altitudes. ### UPDATE ADDED June 2022 ### We have published a tech article regarding how to apply corrections for height values in flight logs (most typically from DJI drones but applicable to any drone presuming you are able to extract the required metadata; Note this new article is ONLY about correcting height values, not about interpreting drone flight logs to FIND or FORMAT the metadata). See http://esriurl.com/CorrectDroneZ Cody B

‎03-12-2019

Upon review of the data, the MISB data stream had an erroneous value for height above ellipsoid, in the range of 10km. this must be corrected at the source.

‎03-11-2019

Tilmann We're always adding new camera definitions, but it's hard to cover everything in advance. If your GPS data is not recognized, note you can import GPS data in a CSV file and if your camera is not known, you can enter the minimal required metadata: Note the above should be true assuming you have an RGB camera. Hyperspectral cameras are not supported (and likely will never be) since they don't capture full frame images. As for multispectral cameras, if you're using one of the multi sensor cameras which don't have co-registered frames (Micasense RedEdge, Sequoia, Slant Range, Sentera, some of MapIR & TetraCam), those will be supported in a future version. Multispectral cameras made by modifying a single chip RGB Bayer-array sensor (MapIR Survey 3, AgroWing) should be able to process although you may have to manually re-sequence the spectral bands. If you use a multisensor camera with an internal beamsplitter (Fluxdata, and I believe some TetraCam models?), these should also process properly since the spectral bands are aligned. Note I'm going from memory on these different multispectral camera models, but one key issue is whether the spectral bands are aligned in the raw images. Another issue is the number of image files captured at a single exposure station. For any cameras that save multiple files per exposure, you'd need to process different spectral image collections separately (based on the current version of Ortho Maker - in the future, we may be able to add some features to handle these unusual configurations). Cody B.

‎02-15-2019

Do you have imagery from an aerial photography camera (whether a modern digital camera or scanned film) and the orientation data either by direct georeferencing or the results of aerial triangulation? If yes, you’ll want to work with a mosaic dataset, and load the imagery with the proper raster type. The mosaic dataset provides the foundation for many different use cases, including: On-the-fly orthorectification of images in a dynamic mosaic, for direct use in ArcGIS Pro or sharing through ArcGIS Image Server. Production of custom basemaps from source imagery. Managing and viewing aerial frame imagery in stereo. Accessing images in their Image Coordinate System (ICS). There are different raster types that support the photogrammetric model for frame imagery. If you have existing orientation data from ISAT or Match-AT, you can use the raster types with those names to directly load the data (see Help here). For a general frame camera, you’ll want to know how to use the Frame Camera raster type and we have recently updated some helpful resources: We’ve published a ‘best practices’ document at http://esriurl.com/FrameCameraBestPractices that provides a comprehensive overview of many different scenarios. We’ve also updated resources on the Imagery Workflows site to provide working examples you can follow. These resources start at this link http://esriurl.com/FrameCameraSample and will lead you to 2 different examples: First is the Manual workflow sample http://esriurl.com/FrameCameraManualSample if you’d like to see the “deep dive” details for how this raster type works. The second is the Automated sample script http://esriurl.com/FrameCameraAutomatedScript that provides support for ingestion of aerial triangulation project files from Bingo, Vexcel Ultramap, DVP PAR, Australis, and Sanborn. Further information: Note that if your imagery is oblique, the Frame Camera raster type supports multi-sensor oblique images. Refer to the http://esriurl.com/FrameCameraBestPractices for configuration advice. If you want to extract a digital terrain model (DTM) from the imagery, or improve the accuracy of the aerial triangulation, see the Ortho Mapping capabilities of ArcGIS Pro (advanced license). http://esriurl.com/OrthoMapping. If you are seeking additional detail on the photogrammetric model used within the Frame Camera raster type, see this supplemental document http://esriurl.com/FrameCameraDetailDoc

‎02-01-2019

April it appears you do not have your logging set to "debug" - we can't see anything useful in these log files but if you could enable debug mode and try again, let us know the results. If this continues, it's probably best for you to log a support incident at http://support.esri.com/ Cody B

‎02-01-2019

April As noted above, we had a known bug that could cause this, but we believed it had been fixed in 1.3.2. If you're getting tiles in the orthomosaic_tiles folder, this sounds like a different problem. How big is your project in terms of # of images? If it's more than ~1500-2000 photos, you may be having memory problems, so may need to split it into two subprojects - ensure some images overlap (~2 flightlines) and include ground control in the overlap region. Did the processing complete normally and declare "success"? If you have ArcGIS Pro (or ArcMap), you should be able to load the tiles into a mosaic dataset and review them - are there tiles missing? Best would be if you can send us the log file - Go to Processing Options/Resources and find the link to the log. Cody B

‎01-14-2019

Brandon I'm asking our support people for help on this. I don't understand why you're not seeing the "Data" option in the menu. What version of ArcMap do you have, and what License level? This help topic Exporting a raster in ArcMap—Help | ArcGIS Desktop says: In the ArcMap table of contents, right-click the raster dataset you want to export, click Data, then click Export Data. ...and I've tried it and it works with *.sid files. Do you have a *tif or another format file you could try, and let us know if the menu changes? The CopyRaster GP tool says it's available at all license levels, including Basic: Copy Raster—Data Management toolbox | ArcGIS Desktop at bottom says: Licensing information ArcGIS Desktop Basic: Yes ArcGIS Desktop Standard: Yes ArcGIS Desktop Advanced: Yes

‎01-14-2019

Brandon Help is here Using the Clip button on the Image Analysis window—Help | ArcGIS Desktop and I showed the UI's above for clipping. What happens when you try that? Error? Nothing? as for saving, Right click in table of contents (select the new layer after clip) to Export / Save As should also work to save a *.tif image copy of the *.sid image. Help is here Exporting a raster in ArcMap—Help | ArcGIS Desktop If these are not working, please log a support incident with Technical Support https://support.esri.com/en/contact-tech-support It looks like you have 1,000 polygons. Are you intending to clip out 1,000 separate tiny image in separate files? Or are you expecting to create one single image with 1,000 "islands" but remove all the pixels in between? Clipping from the Image Analysis Window (IAW) will do the latter; if you want the former, you'd have to use a GP tool or Python to select and clip one at a time, but I have a feeling there must be a better way to reach your end goal. If you put your *.sid file into a mosaic dataset and use your polygons to define the Footprint, then set mosaic dataset properties to "Clip to footprint? = Yes" you'll get 1,000 islands with no pixels in between. If your subsequent processes are in ArcMap this should work, but if you're trying to export to some other software, it won't understand the mosaic dataset. Can you let us know what you're seeking to accomplish? Cody

‎01-12-2019

Michael short answer, no. This was an error on my part - my apologies. I was thinking "wavelet compressed images" and mixed up *.ecw format and *.sid format. My comments were correct if we were discussing *.ecw, but NOT for *.sid. There is no restriction or problem with serving *.sid files, but *.ecw files cannot be shared through ArcGIS Image Server without an additional license from Hexagon. I'm going to edit and delete my erroneous comments from above, hoping to avoid confusing anyone. Cody B.

‎01-10-2019

Dan no, this is correct. We're only reading the *.sid file. If he clips and exports, he'll have to save the clipped raster as some other format. But (presuming one file) that's faster and easier than running CopyRaster for the entire file first, which I believe is what he ended up doing. Cody

Online Status	Offline
Date Last Visited	Wednesday

My Ideas

Latest Contributions by CodyBenkelman

Re: "Not Enough Tracks" error in Drone2Map

Re: Consistent processing failure immediately after substep Camera Calibration?

Re: Custom geoid in d2m?

Re: How do we process video from a DJI drone to bring it into FMV for ArcGIS?

Re: How do we process video from a DJI drone to bring it into FMV for ArcGIS?

Re: How do we process video from a DJI drone to bring it into FMV for ArcGIS?

Re: Question to Full Motion Video In ArcGIS Pro

Re: Orthomaker Metadata Detection From Imagery

Resources for access to frame camera imagery

Re: 'Create Orthomosaic' is checked in Processing Options, but none is actually created

Re: 'Create Orthomosaic' is checked in Processing Options, but none is actually created

Re: Can you clip a MrSID file in arcmap?

Re: Can you clip a MrSID file in arcmap?

Re: Can you clip a MrSID file in arcmap?

Re: Can you clip a MrSID file in arcmap?

Be one of the first to test and shape the future o...

Drone2Map v2026.1 has been released!

How to Migrate Oriented Imagery Catalogs to Orient...

New Release of ArcGIS Online - Are you looking for...

Oriented imagery classic will be retired soon!

Esri Forestry Group (EFG)

User Community for Geospatial Authorities (UCG)

UCG-WG2 Remote Sensing and GeoAI

Elevation Data

Drones, UAVs, UAS, and RPAs