|
IDEA
|
To KNTR - this does not answer your request (Randall already explained) but I wanted you to know the Experience Builder widget is now available. New Experience Builder (ExB) widget for Oriented Imagery is available!
... View more
03-02-2025
08:37 AM
|
0
|
0
|
1641
|
|
BLOG
|
For those of you who've been using (or wanting to use) oriented imagery in the web, and you'd been waiting for the ability to configure a web app for your organization, the new Oriented Imagery Viewer widget for Experience Builder is here! (Released today, Feb 26, 2025) With this widget, organizations can now build flexible web apps to maximize the value of their oriented images. The Experience Builder apps can load and choose from multiple oriented image layers and/or display two or more separate oriented image windows. If you need to make measurements, horizontal distances and areas on the ground are enabled via this widget, as well as vertical height measurements. Accuracy estimates are automatically included (based on metadata). And working with GIS features is now enhanced: feature data can be displayed in the viewer, and new features can be digitized directly within the oriented images. Build your apps, and let us see what you've accomplished!
... View more
02-26-2025
02:22 PM
|
7
|
7
|
3293
|
|
POST
|
Morgan - thanks, knowing those were completely different dates does make the color correction more challenging. Can you clarify terminology and workflow? You said "mosaic dataset" and I just want to clarify how you're using them. https://pro.arcgis.com/en/pro-app/latest/help/data/imagery/mosaic-datasets.htm Are you processing date 1 in Drone2Map, then a separate project for date 2 (etc.), creating multiple true orthos for different sections of campus, then managing those orthos using a mosaic dataset? Presumably intending to create a raster tile cache (basemap) out of the mosaic dataset when campus is complete? If correct, this is a perfectly valid workflow for the geometry of the pixels, but unfortunately color correction will be much more difficult because each true ortho is adjusted for color, but the edges will be impossible to match. I'd suggest one of three alternatives to improve the tonal mismatch between orthos: 1) fastest/easiest is to apply blending across the seamlines between the true orthos, and you should be able to apply a wide blend distance (? 10 meters?) if you have adequate overlap. (And for future flights, ensure a lot of overlap between the output orthos, e.g. 2 full flightlines if possible). This should look relatively good at large scale (zoomed way in) but when you zoom out, you'll still see tonal differences between the flights. 2) another option is to process all drone images in a single Drone2Map project - this should automatically compensate for the tonal differences but depending on total number of images the project may be too large. (Do you have access to the ArcGIS Reality Extension for Pro? That should allow you to scale to a larger single project) 3) I was going to describe a third option but I'm pretty sure this will not yield acceptable results. You could use Drone2Map flight-by-flight to run photogrammetric processing but not create true orthos, then apply the exterior orientation (xyz, omega phi kappa) for all of the individual frames using a mosaic dataset to rectify the images on-the-fly; but this won't give you a true ortho, and with a 200' flight over campus buildings the horizontal layover will be unacceptable. (if you ever had to do a large project over natural terrain, this approach might be perfectly acceptable) Cody
... View more
02-26-2025
07:00 AM
|
0
|
1
|
2725
|
|
POST
|
That "Road" result does not look normal - you should not see sharp edges from different images. Can you confirm which version of Drone2Map you're using, and the settings you applied?
... View more
02-23-2025
05:46 PM
|
0
|
1
|
2740
|
|
POST
|
Tim Sorry this hasn't been answered yet. You should be able to process the original RJPG files without conversion, although you're correct that we have not implemented any corrections for ambient conditions or distance to sensor. I'd be curious to discuss your requirements. (I sent you a direct message) One detail to note, for DJI thermal sensors only, is software from DJI is required to perform the conversion from raw digital numbers (proportional to energy) to temperature units. We don't install that software by default due to the security limitations I assume you've heard about. This doesn't impact geometric processing, so it's not required to run a project, but you won't get temperature units - I think that may be what you indicated above. If you don't have the DJI download, check your MyEsri portal - let us know if you can't find it. Also note you can choose Celsius or Fahrenheit but you have to make that choice before processing. Cody B.
... View more
02-10-2025
02:57 PM
|
0
|
1
|
1231
|
|
BLOG
|
Introduction The use of thermal infrared (TIR) imagery sensors has seen dramatic growth in the last few decades, addressing many applications for users of mapping and GIS. The purpose of this blog is to introduce some of the many use cases, and to provide recommendations for ArcGIS users to take advantage of these sensors. The examples included here will focus on imagery captured from an aerial drone followed by photogrammetric processing to generate a True Ortho composite image, but use of a drone and post-flight processing are not always required - some very powerful applications may also be addressed with single images or video (airborne or ground-based), and for large area studies, satellite sensors may be most appropriate. Note that we’re using the acronym “TIR” here to refer to the thermal infrared region of the electromagnetic spectrum. This blog does not address properties of near infrared (“NIR”) or shortwave infrared (“SWIR”) energy or sensors. Use Cases Some of the many applications for TIR imagery within ArcGIS include: 1. Monitoring energy loss from buildings This application is growing rapidly since it provides a low-cost analytical method for a facility to reduce operational costs as well as environmental impact. Thermal infrared imagery is typically captured by a drone to view the rooftops of buildings under study, and areas that are losing energy can be easily observed as warmer or cooler than their surroundings. That is, if the outdoor weather is warm and the building has air conditioning, energy leaks will appear as cool regions. If the building is losing interior heat during wintertime, relative warm areas may be visible. Areas of the building that are noticeably cooler or warmer than their surroundings help building managers prioritize improvements to ventilation systems as well as locate and repair areas of insufficient building insulation. Examples can be found in this publication from ACCESSiFLY. An example image (showing false colors applied to the single band TIR image) is shown here, highlighting warm regions around roof vents. 2. Detecting potential maintenance problems in electrical/mechanical equipment Another application where TIR imagery can provide value is by identifying equipment that appears to be overheating, indicating possible physical wear or failing electronics. This is applicable for a variety of types of equipment, including but not limited to photovoltaic solar arrays, electrical transformers, industrial motors, and more. An example image is shown below, provided courtesy of Rocky Mountain Unmanned Systems. In this image, one section of the photovoltaic (PV) array is noticeably brighter (warmer) than the neighboring panels in the installation, indicating a possible defect in either the array or its control electronics. With prompt maintenance, the operator can reduce lost productivity and possibly avoid a more serious failure in the future. 3. Detecting leaks in pipelines Thermal Infrared imagery is also applied to monitoring pressurized pipelines to detect leaks. A leak can sometimes be observed as an area on or near the pipeline with a temperature anomaly – warmer or cooler than the surrounding region. If a liquid such as water is leaking, it can cool the local vegetation/soil relative to ambient background temperature. In the case of other pipelines, such as natural gas, a leak can result in a loss of pressure, and evidence of emerging gas can sometimes be observed as a cold plume (although there are other sensors that are better suited for detecting flammable gas). In the example images below (provided courtesy of EagleHawk) we can clearly see the route of an underground steam pipe (1 in the first image, TIR), with evidence of a condensate leak (2) entering a storm drain. In top center (3) we can see the warm water condensate running into a nearby ravine. The second image provides a natural color view of the same site. Based on this imagery, the leak was promptly located and corrected. 4. Other Use Cases The use cases listed above are just a sample of the much broader array of applications for thermal infrared imagery. There are many more – for example: TIR sensors are used on drones as well as crewed aircraft to search for lost hikers or conduct wildlife surveys. In law enforcement, residual heat can be detected and applied as forensic evidence showing where a vehicle had been parked but then departed the scene prior to image capture – either where heat from an operating vehicle had warmed the pavement, or alternatively where the shadow of a parked vehicle had left evidence as a cooler region, having reduced solar heating of the surface. Environmental studies focusing on aquatic habitats where narrow temperature ranges are required for successful fish spawning can cover relatively large areas with thermal infrared imagery to supplement in situ temperature sampling. Interpretation / Analysis For most of the above examples, users can detect thermal anomalies through simple visual assessments of the area of interest to identify regions that appear warmer (or colder) than everything nearby. As a result, the user can extract useful information with relative (qualitative) observations, but without performing absolute (quantitative) measurements of exact temperatures. The exception to this in the above examples is an application such as monitoring water temperatures in fish spawning beds, where spawning success may depend on water temperatures within a relatively narrow temperature range. In use cases that require absolute and accurate temperature measurements, users will need to consider radiometric calibration of their sensor system, and properties of the materials being observed, especially metal surfaces which often show reflections of TIR energy coming from another source – e.g. the sky (which will typically appear very cold) or the sun. Surface Properties and Emissivity Making accurate remote temperature measurements of an object is challenging. Images captured by thermal infrared sensors are proportional to the energy received, and those energy measurements are then used to determine the apparent temperature of the surfaces in view. Some sensor manufacturers provide information to enable conversion of TIR images into energy units, then from energy to surface temperature. An important consideration is the surface property referred to as Emissivity (represented by ε). Different surface materials emit thermal energy at different rates. The difference in emitted energy for two surfaces at the same temperature is characterized by their emissivity, ranging from 0.0 to 1.0. The apparent temperature of a surface is typically lower than the actual temperature, presuming the surface emissivity is less than 1.0. Remote temperature measurements can be misleading for low ε surfaces such as most metals, since they emit very little energy and they can also reflect TIR energy coming from another source (e.g. the sky, which will appear to be very cold, or a separate heat source). A more detailed discussion of this topic is beyond the scope of this blog post, but it is important to understand that calculation of the most accurate temperature of any surface – concrete, water, grass, metal, etc. – would require knowledge of the emissivity of that surface as well as the possibility of observing reflected heat sources. A table of emissivity values can be found HERE. Note that, since most natural surfaces have an emissivity value of 0.9 or greater, in most applications described above, correction for emissivity may not be necessary. Practical Application In practice, the user should consider whether absolute temperature measurements are required for their use case. Since many applications do not require absolute temperatures, it is reasonable to visually identify thermal anomalies, and thus derive significant value from TIR imagery without needing to calibrate to temperature units. For TIR sensors carried on a drone, users wishing to generate a True Ortho data product must capture multiple frames (with recommended overlap of 90% due to the low image resolution) and then run photogrammetric processing to create an orthomosaic for visual interpretation. For satellite sensors, a single image will often cover the full site of interest. If absolute temperature measurements are required, support in Esri software will depend on the sensor. Additional software from the sensor manufacturer may be required to perform the conversion. Refer to the ArcGIS Help documentation for your software and sensor. The sensor manufacturer may also have separate tools to apply for temperature calibration. For satellite sensors, the proper Raster Type must be defined, then processing templates can be applied to the TIR bands to convert pixel values into degrees Celsius or Fahrenheit
... View more
02-07-2025
06:14 AM
|
1
|
0
|
3542
|
|
BLOG
|
Oriented Imagery Classic — the add-in, community-supported solution for managing and visualizing street-level images, 360 images, full-resolution drone images, video, mobile phone images, and more — is being deprecated. We are integrating the Oriented Imagery capability directly into the ArcGIS system. An introduction is available here. The integrated version is replacing Oriented Imagery Classic. Oriented Imagery Classic will be maintained until the integrated capability within ArcGIS has reached equivalency. This deprecation notice is offered to ensure users have sufficient time to migrate their data and workflows to the new data model and tools, at which point Oriented Imagery Classic will be retired. Please visit the deprecation and retirement notice on the Esri Support Site for more information.
... View more
01-22-2025
02:15 PM
|
3
|
0
|
651
|
|
BLOG
|
Attention all users! A new version of ArcGIS Drone2Map is now available in MyEsri, and we encourage everyone to upgrade.
We’ve made improvements and additions in many areas of the software, focusing as always on improved quality in your output data products, and more robust review of your data & metadata to help avoid any issues with processing your drone imagery.
Since many Drone2Map users are in the Construction or Utilities industry, an important improvement is for better detail of thin structures in the 3D mesh. An example is shown below.
We’ve kept this post very brief, but you can see more detail in the What’s New blog at https://esriurl.com/D2M20242whatsNewBlog
You can find a complete listing of new features in Help documentation at https://esriurl.com/D2MwhatsNewHelp and this list of specific issues which have been addressed https://links.esri.com/arcgis-drone2map-issues-addressed-2024-2.
... View more
11-14-2024
04:26 PM
|
4
|
6
|
1805
|
|
POST
|
hi Anthony
We've done some internal testing but can't reproduce this, and we've never seen or heard of this from other users. Have you seen this with other datasets?
Can you send us your DSM and DTM? Either that and/or send us some of your source images? I'll send you a direct message so you have my email.
If the files are too large, we could do some testing with subsets (clipped area of interest) from the DSM and DTM. If the data is proprietary, we'll keep it confidential within Esri. But if it's highly sensitive and you can't share it, we'll have to pursue other methods to find the problem.
Thanks Cody B
... View more
10-09-2024
01:06 PM
|
0
|
0
|
1874
|
|
POST
|
Jon
It sounds like you have your Source and Derived configured the way I would recommend - my only thought re: wrong source OVR image coming to foreground is that it might depend on exactly where your map is centered at the problematic zoom level.
Have you built footprints for the OVRs? That might be a bit tricky - in the Source MDs I think it will skip those where Category is not Primary, but once you ingest into Derived it may be slow to build footprints. (I can't honestly recall if the BuildFootprints tool can skip all with existing footprints, therefore building ONLY for the Source OVRs now tagged as Primary.).
The assignment of Category depends on context and desired behavior, but in this scenario I would leave them as automatically configured e.g. what were Source OVRs are now considered Primary in the Derived. I don't believe you should have to edit any fields of the Attribute table in the Derived. I would have thought that what you did should work properly so I'm not clear why it is not... If I can think of other settings to change I'll respond again.
Cody
... View more
10-05-2024
01:13 PM
|
0
|
2
|
3590
|
|
POST
|
Hi JM32
How are your overviews configured? In this scenario we'd recommend you build overviews on the Source mosaics, and you'll have to ensure to copy appropriate fields to the overviews in the attribute table before ingesting them into the Derived mosaic. Then do not build overviews on your Derived mosaic, and this should behave as expected.
Note this assumes you don't have a large number of Source MDs. If you do, then you may have performance problems rendering multiple Source OVRs when zoomed out. If that's the case, then you'd change what I said above, and DO create OVRs on the Derived at an appropriate scale where your users can understand "if you zoom out to here, you'll just see the standard view of the project area, NOT the most recent imagery (at very low resolution) in every sub-area". At some reasonable zoom scale, the difference between image dates is presumably (?) not relevant. Note for the "standard view of the project area" you could choose to use a Landsat or Sentinel-2 scene etc. - swap out a good synoptic view for OVRs composed from your individual datasets
If that doesn't make sense let us know.
Cody B
... View more
10-04-2024
07:09 AM
|
1
|
1
|
3612
|
|
POST
|
Can you tell us what Cool Hydrants and Cool Centers are?
... View more
10-03-2024
11:35 AM
|
0
|
1
|
863
|
|
POST
|
Anthony
Sorry nobody has replied. I don't fully understand this - Is this a Drone2Map question? D2M does not provide the ability to represent DSMs/DTMs as slope. Are your screenshots generated in ArcGIS Pro or some other software? Or did you create a slope function template in Pro and import it into Drone2Map?
If you can send your original DSM, DTM, and slope version of one or both it might help - but let us know how they were created.
Cody B.
... View more
10-02-2024
01:07 PM
|
0
|
3
|
1942
|
|
POST
|
Jonathan
no, Drone2Map only processes single frame images. What would you hope the software would do with 360 images?
Cody
... View more
09-23-2024
07:05 AM
|
0
|
0
|
630
|
|
POST
|
Tara Fundamentally, the image matching performed by Drone2Map requires the ability to see features on the ground that are not moving - so unless the water is extremely calm and you can see the lake bottom clearly in each image (with no sky reflections or wavecrests) the block adjustment will fail since it is looking for fixed features. Your best approach may be to use the Image Collection directly, without block adjustment. Contact me via email (see private message) Cody B.
... View more
09-13-2024
06:54 AM
|
0
|
0
|
1420
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | 03-02-2026 03:35 PM | |
| 1 | 03-02-2026 11:46 AM | |
| 2 | 02-05-2026 05:21 PM | |
| 2 | 11-20-2025 03:34 PM | |
| 1 | 02-07-2025 06:14 AM |
| Online Status |
Offline
|
| Date Last Visited |
3 weeks ago
|