Latest Contributions by CodyBenkelman

Hi Joseph.  I'll ask our support team about what might cause this error but could you let us see an example of the imagery?  Specifically,  do you have ~70% overlap everywhere? is there tall vegetation and/or a lot of water in your imagery? thanks Cody B ... View more

Robert I can answer about Pix4D.  If you're already using Pix4D for processing drone imagery, most if not all of the resulting outputs are all compatible with the imagery capabilities of ArcGIS - that includes ArcGIS Pro, ArcGIS Online, and ArcGIS Earth.  (I'm assuming you're not using ArcGIS Enterprise or Image Server but the same is true).  I said "most" outputs because in some cases it will depend on the format  - e.g. if you want to use the point cloud, output a *.LAS file...   Note if you're not already using Pix4D, we have options for drone processing as well.  Drone2Map is generally equivalent to Pix4D for field/office use on a laptop, and Site Scan is our cloud-based (SaaS) offering.    These include direct connections for publishing results in ArcGIS Online. Cody B.  ... View more

Lance  Sorry I didn't respond soonr.  The single best resource for these questions about "What is recommended?" is our Imagery Workflows site at http://esriurl.com/ImageryWorkflows.  Specific sections I would recommend are the overview topic of Image Management starting at https://doc.arcgis.com/en/imagery/workflows/best-practices/what-are-best-practices.htm (continue with the rest of the section on Image Management) and a specific discussion of the multi-year case in  https://doc.arcgis.com/en/imagery/workflows/resources/managing-preprocessed-orthophotos.htm  Regarding that post that you found from 2016 - and I regret that I did not discuss this more deeply at that time.  My caution about the 'pitfalls' focuses on which raster type is used when adding a mosaic dataset (MD) as input to another mosaic dataset.   Briefly: I recommend *against* using the default "Raster Dataset" raster type which is recommended in the post you reference  Creating a mosaic dataset containing raster data from multiple dates  If you have 3 input MDs and use that raster type, your master MD will only have 3 records.  That may seem convenient and in some limited cases I'd say "Yes go ahead" but it can lead to performannce problems if you have 8 or 10 or more MDs and especially if you 'nest' them further in another layer of hierarchy because you've embedded database tables as single records inside other tables. What I *do* recommend in most cases is to use the Table raster type.  In my last statement, if you have 3 MDs with 100 records each as source data, your master MD will have all 300 records.  This avoids performance problems but it does (generally) require the additional step of defining one or more custom fields e.g. "Year" or "Date" as you note, and I also recommend adding a field (we typically call it "Dataset_ID") into each source MD so that the master MD will clearly show the source MD for each of the 300 records.  Hoping to avoid confusion, I should note that some of our documentation refers to the master MD as a "Derived" mosaic dataset - but this name is simply a convention, not a formally defined term. You also asked "How is there an advantage when you would need to filter the data to render each year individually?"  If you only have a small number of image collections (years or separate projects) this is not a major concern, but if you share each as a separate image service, those services will consume resources on the server even if nobody is using them.  If many collections are shared in a single image service, your use of server resources is more efficient (better performance).  The Landsat service is a good example - millions of individual records and it performs very well.   But yes, you do have to provide users with the ability to select images by date (or other attributes as necessary) - see the Time Selector tool in the Landsat Explorer app. Last, re: the Esri video in your 2nd reference, I do not agree that you need to create a new GDB for every MD.  I've never attempted nor felt a need for hundreds of MDs - and there probably is some reasonable limit - but multiple MDs in a single geodatabase should not be a problem. Cody B.   ... View more

Hi Eisele sorry for the delay in responding.  Your account administrator should have received an email explaining this - I believe it was in June. At the next release of Drone2Map (early November) we'll have two license levels, Standard and Advanced.  Current users were given early licenses to Drone2Map Advanced to support beta testing of the new version.  In the currently released version, there is only one license level for Drone2Map. Cody B.  ... View more