Known issues

This section lists known limitations in ArcGIS Drone2Map. Software developers are working to fix these issues in future versions of the software.

  • Users that authenticate Drone2Map through an ArcGIS Enterprise portal account and try to upgrade will get an error. An ArcGIS Online account is required to download Drone2Map software updates.

    To upgrade Drone2Map, download the software from My Esri.

  • Projects sizes take up a large amount of storage or fail to complete.

    Many products in Drone2Map are currently produced in their natural formats which can be quite large, especially when processing 3D products. Ensure that none of the intermediate data options are checked on to be saved. Also make sure that you are saving enough additional space on your local storage for the intermediate data that is created and deleted during processing.

  • Drone2Map is not using 100% of my GPU when processing.

    The GPU is used at varying capacities for certain processing steps. It will never be continually used at 100% capacity as the software is more CPU bound. For more information on how hardware is utilized see: Hardware resources and performance

  • The generating dense point cloud step is delayed in showing progress percentage when running.

  • Processing DSM Mesh products can be resource intensive leading to slower output product generation.

  • Multispectral and thermal projects do not use dense matching. Any orthomosaics generated are not corrected to nadir.

  • Enabling a product in the project management pane does not add it to the map if Add to Map is checked.

  • If your source imagery contains a # in the header and the Use Image Orientations processing option is checked on then the image adjustment step will fail. Removal of the # character will allow for adjustment.

  • Offline basemaps are not available in 2.0 and later. It is recommended that you use Tile Package Kreator from Esri Labs to create offline basemaps for use in Drone2Map.

  • Images with low texture, such as agricultural land use, natural areas, and water, are not calibrated with default settings.

    Increasing the tie point options Initial Image Scale (for example, 1 or 1/2) or increasing the Matching Neighborhood setting will increase the number of calibrated images.

  • Calculating Volume displays an incorrect value for the Area property field in the Mensuration Results pane when the unit of measurement is changed.

  • If the Edit Camera pane is open prior to processing, it will not show the calibrated camera parameters after processing completes. The project needs to be reopened in order to see the calibrated camera parameters.
  • Projects that contain imagery from multiple drone flights captured at the same time may create flight lines incorrectly. Drone2Map uses the timestamp to generate the flight path for the project.
  • If any images in your flight contain metadata from another location far outside of the flight area, then the flight path may fail to create properly and processing could fail.