Latest Contributions by CodyBenkelman

There are no monthly limits.  As of today (Drone2Map version 2.0) the only licensing available is "named user" which must authenticate through ArcGIS Online or ArcGIS Portal, but there are no limits on # of projects or # of images.   At the 2.1 release we will add the "Single Use" license option which will not need to authenticate with a portal. Cody B ... View more

Based on what you’ve said, I’ll give abbreviated advice   At a high level, there are three primary options, described here only briefly.  It sounds like you’re in the first case, and for the benefit of other readers who may see this, I'll describe the two other options afterward:   Presuming a low number of photos and you do not need high accuracy, then use the Georeferencing tools.  Note this will not orthorectify the imagery (will not fit imagery to the terrain). Specifics: Georeference each image independently. Start with first order transformation to get started, but depending on your ability to find ad-hoc control points, use higher level transforms such as spline (a minimum of 10 tie points required to enable this transform). For reasonable accuracy you will want control points distributed around image and on terrain extremes. Use “Save” which will georeference using tie points in a small *.aux.xml file that can be edited (improved) later if necessary.  In this scenario recommend you do not use “Save As” which creates a new image file. Create a mosaic dataset to dynamically mosaic the images together.  (any image can be viewed, so pixels in overlap are not lost). Use Footprint feature class to clip the black collar (pixels not permanently removed, just hidden)   For highest accuracy, scalable to large blocks of film, users should apply photogrammetry via the Ortho Mapping capabilities (ArcGIS Pro Advanced license, Scanned Film workflow) Should have the camera report to define parameters such as focal length - this will most likely be available from USGS Earth Explorer Need to create* a table with approximate exterior orientation listing the (x,y,z) location and camera heading angles (kappa) for each image. This can be estimated if necessary.  May be created manually for small to medium size blocks of film. Need to provide a DEM – this can be exported from ArcGIS Online World Terrain image service, use an existing DEM, or generate a DEM from the imagery after block adjustment If you have limitations on inputs for #2 for Ortho Mapping (e.g. no exterior orientation table and/or not able to see fiducial marks on film) use the Drone workflow in Ortho Mapping to generate an approximate mosaic. For some use cases, this may produce adequate products. For users seeking the highest accuracy results, use results of this process as input to the Scanned Film workflow in Ortho Mapping   We’ll be publishing a deeper discussion on this on http://esriurl.com/ImageryWorkflows soon - I will plan to update this post when that is published.  Cody B ... View more

Jeff I think your new raster is probably fine but the map is applying an automatic histogram stretch.  (that's what Peter meant by "... the default renderer uses the stats to display the image. " If you go to the layer in the Table of Contents, right click, properties (like shown in your screenshot RasterSymbology2) and set Stretch to "none", it should look like the original.  If I'm correct and this fixes it, if you right click on the file in Catalog (not Table of Contents), go to Properties, and set Source Type to Processed this shouldn't reoccur each time you load it into the map. On a separate topic, I usually recommend against storing rasters inside geodatabases - is there a compelling reason you're doing that? Cody B ... View more