|
POST
|
Thanks to Mark for posting the workflow. If you're interested, we've published a blog discussing the different ways of compiling images into the orthoimage outputs - True orthos, the traditional orthomosaic, and also the dynamic mosaic (a.k.a. image collection). See https://esriurl.com/3orthoTypesArcGIS
... View more
05-16-2023
08:44 AM
|
1
|
2
|
3176
|
|
POST
|
Haris7 ArcGIS Pro with Advanced license has ortho mapping https://pro.arcgis.com/en/pro-app/latest/help/data/imagery/ortho-mapping-in-arcgis-pro.htm. This is in the same section as the help Dan pointed you to, but the ortho mapping workflow (using the ribbon wizard) is very simple. I don't actually know if your Student license enables this - try going to the imagery tab and on far left hit "create workspace"... Cody B.
... View more
04-14-2023
06:44 AM
|
0
|
0
|
1102
|
|
POST
|
David Sorry that nobody has replied - do you still need help with this? I'm not familiar with the sara repository - it's possible that the format of the images has been changed in some way. Have you tried with files directly from https://sentinel.esa.int/web/sentinel/missions/sentinel-2? Perhaps easier, have you looked at our image service at https://sentinel2explorer.esri.com/? It gives you direct access to current imagery in a dynamic image service Cody B.
... View more
04-06-2023
09:10 AM
|
0
|
1
|
3210
|
|
POST
|
Phil there is not enough information in your post to allow us to answer. The raster you show clearly has multiple values in the pixels - do you mean you've remapped the pixel values to 1? Then can you explain what you're doing with the raster? If your study area is your raster, nothing outside that raster should be contributed to a model or analysis - if that's not currently true, what is currently happening outside the raster extent? Cody B
... View more
03-21-2023
04:19 PM
|
1
|
1
|
1307
|
|
POST
|
Janniewu The points in your 4th screenshot are NOT in the wrong location. The basemap that you show in the screenshot is a 'traditional' orthophoto, with accurate locations for anything on the ground, but that tall building is clearly leaning away from you. The top of the building IS located where the blue photo points are shown. It's very important to understand this, both for your processing and also if you are using this basemap image to do your flight planning! If you're flying a drone near a tall building and you do not plan for the proper XYZ position of your target, you may crash your drone. (this is assuming your drone is flying on its own, using GPS. I'm guessing you flew manually in this case?) This blog may be helpful for you to understand what you are seeing in the orthophoto https://esriurl.com/3orthoTypesArcGIS although it does not discuss 3D drone flight planning. Note if you have a DJI drone and an iPad, you can use a free app from Esri to plan and control your flights https://esriurl.com/ssle NOW - this does not answer your question about why the processing failed. The project did not complete setup, so the processing could not continue. I can see that the Z values are incorrect. This is a very common problem for drones, and the Z value you show of 33 meters must refer to height above sea level (not 33 meters above ground). At your location, the ground ~31 meters above sea level, so this is telling Drone2Map that your drone was 2 meters above ground! (see my screenshot from https://esriurl.com/map4groundelevation ) Please review this help document https://doc.arcgis.com/en/drone2map/latest/help/flight-data-geolocation.htm and look for Adjust image altitudes Cody B.
... View more
02-09-2023
02:32 PM
|
0
|
0
|
3477
|
|
POST
|
George There are a lot of questions and assumptions in your post, so this will be more than a "one answer and done" response. for a very general response, please review ArcGIS Pro Help system, and also note that the Imagery Workflows documentation site has advice on best practices (expanding on the core help topics). You'll find resources there to provide a good background for questions such as this. specific to your question, I'd advise you classify ground first, then buildings, then vegetation but there are many footnotes. if your data already has ground points classified, you should consider carefully before altering those class codes (depending on the source). If you feel the current Ground class is significantly in error, then yes you can "reclassify everything to unassigned and then just go one classification type tool at a time" You ask "is the Classify Ground tool better than or different from how Ground is created when calculating statistics?" but the latter does not perform classification - it's simply summarizing existing classifications for your question re: vegetation density, one method (perhaps not the only way to do it) would be to generate rasters for POINT density and also PULSE density, then use the latter to normalize the former. (Where you have extra points in the overlap, the PULSE density will quantify the extra sampling). See discussion of those two QC rasters here (from the workflows site) regarding building footprints, that is not a separate classification code in the lidar - you'd use the building classified points to generate polygons. See this blog. I'll forward your questions to some of my colleagues and they may have further advice for you. Cody B.
... View more
01-17-2023
03:03 PM
|
1
|
0
|
2817
|
|
POST
|
I've confirmed this will be enabled in the next release, planned for the end of January 2023
... View more
11-29-2022
09:54 AM
|
1
|
2
|
1087
|
|
POST
|
Allix Can you tell us which version of Drone2Map you're using? Is it 2022.1, and a Standard or Advanced license? I expect the problem may be regarding overlap. Two things you can check: 1) many drones report incorrect Z values - can you verify you have accurate values for each image (orthmetric height, above sea level - not height above ground, or ellipsoidal height). This blog http://esriurl.com/correctDroneZ was written for the case of capturing video, but there are useful resources if you need to calculate a correction for your height values. (e.g. "Use this ArcGIS Online map to find elevation values for the terrain of the project site") 2) ignoring the GPS metadata, if you visually evaluate a few image pairs (along and between flightlines), did you successfully capture ~70% overlap or more? (#1 is intended to tell us if the metadata might be *indicating* the images have insufficient overlap. #2 will tell us if your images *actually* have insufficient overlap) If you could let us review a block of images we could advise further - e.g. minimum of 3 flightlines, 5 images per line... Thanks Cody B.
... View more
10-13-2022
12:00 PM
|
0
|
1
|
999
|
|
BLOG
|
### ADDING ANOTHER UPDATE September 20, 2022 ### On the general subject of "Using video in ArcGIS" many of you may be interested to learn about Oriented Imagery. This is a capability designed specifically for images and video that cannot be mapped onto the ground - e.g. if any portion of your video aims above the horizon, some of the features of FMV in ArcGIS aren't applicable (e.g. "zoom to extent of video footprint" will zoom out to 1:1 million scale because the footprint extends to the horizon). If you are capturing video with a drone, dashcam, etc. aimed toward the horizon (even if there's a building in the view and you can't see the horizon) Oriented Imagery may provide a better solution for working with your video in ArcGIS. A good starting point is this resource https://doc.arcgis.com/en/imagery/workflows/resources/managing-and-visualizing-oriented-imagery.htm and note it points to other documentation (See Imagery Workflows resources) including public sample web apps (including some video datasets) at https://esriurl.com/OIgallery IMPORTANT SUMMARY: Oriented Imagery supports video aimed partially or completely above the horizon, but all of the discussion in this blog above regarding the format and completeness of suitable metadata (XYZ location, heading, and field of view of the sensor) is still applicable. Oriented Imagery does not provide a solution for missing or improperly formatted metadata. Cody B.
... View more
09-20-2022
08:10 AM
|
0
|
0
|
7880
|
|
POST
|
Chuck I'd have esimilar comments and questions re: my response to Jessica above. Cody B
... View more
09-17-2022
03:47 PM
|
0
|
0
|
1568
|
|
POST
|
Jessica - sorry for the delay - I did not see your message. Have you gottn this resolved already? It appears you have the Standard license, is that correct? We sometimes see minor misalignments but typically not as much as you show in this screenshot. Can you confirm you had ~70% overlap or more, both along and between flightlines? I you have less overlap, you may find these sorts of difficulties. Did you us "None" for the orthorectification setting? If your project has significant terrain changes, you may want to use the "Sparse point cloud" instead of "None". If you still need help, please contact Tech Support. Cody B
... View more
09-17-2022
03:44 PM
|
0
|
0
|
1568
|
|
POST
|
Bill I apologize for the long delay - I missed your message. (Note I posted this an hour ago, then edited - so if you saw my original post, please review again) These are known limitations in the multispectral processing workflows - we hope to be able to address this in the version 2023.1 release (Q1 next year). If you have access to version 2.3.3, you should be able to proceed with the GCPs, but the water mask was not available in that version. Cody B.
... View more
09-08-2022
09:05 AM
|
0
|
0
|
740
|
|
POST
|
Kevin - this is an age-old debate. Many people refer to DEMs as "2.5 D" since they're clearly more than 2D, and yes, useful for some 3D analysis such as line of sight/viewshed. The fundamental reason we don't consider them fully 3D is that you can't represent any overhanging features (e.g. look under tree canopy to see the tree trunk). In the case of a building with overhanging eaves, the DSM shows the building as having the full XY extent of the roof footprint, whereas the foundation of the building is smaller - and in most applications seeking the building footprint, they want the foundation, not the roof extents. But for some specific applications, you're correct that the DEMs can be considered and used as 3D datasets. Personally I think it's an advantage to call these "2D" for users of Drone2Map Standard - the Standard license does not include full 3D functionality but it IS able to create the DEMs (DSM and DTM) - so it's a benefit to these users who may want to calculate volumes of stockpiles or excavations - but the terminology is certainly open to ongoing debate. Cody B
... View more
09-08-2022
09:02 AM
|
0
|
0
|
557
|
|
POST
|
Dilshan Once again sorry for the long delay - not sure if you still need this - we wrote up a procedure for correcting altitude values here https://www.esriurl.com/CorrectDroneZ It discusses sampling the ground elevation from the Esri ArcGIS Online world terrain service, but you could also use your own DEM - it doesn't matter what projection the DEM is in - but a high accuracy DEM is not required. You're correcting for the drone's reported altitude above sea level or above the ellipsoid - localized changes in the DEM are not reflected in the drone altitude. However, after running the multiplexer, if you want to show your FMV-compatible video on top of a custom DEM, you can do that by adding the DEM into ArcGIS Pro as an Elevation Source Layer
... View more
08-10-2022
10:25 AM
|
0
|
0
|
3621
|
|
POST
|
Patrick Creating single file OBJs is on the roadmap. I'll confirm with the engineers regarding FBX Cody B.
... View more
08-03-2022
08:09 AM
|
0
|
3
|
1117
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 11-20-2025 03:34 PM | |
| 1 | 02-07-2025 06:14 AM | |
| 2 | 05-16-2025 09:20 AM | |
| 1 | 05-16-2025 08:41 AM | |
| 7 | 02-26-2025 02:22 PM |
| Online Status |
Offline
|
| Date Last Visited |
12 hours ago
|