|
POST
|
Cara you said that the output raster is identical to dem1 and doesn't include values or counts for dem2 and dem3. Do you mean the pixels and extents of dem2 and dem3 were simply ignored and not properly added into the output raster? If that's the case, it sounds like a bug. What version you're using? If you're on an old version, this may be a bug that was fixed long ago. Are you using ArcGIS Pro? ArcMap? You should work with Support on this. If I misunderstood and the pixels are all there but simply the attribute table has not been updated, have you run "Build Raster Attribute Table" on the new raster after combining the three source rasters? Last, (re: Dan's last comment), don't confuse a Mosaic Dataset (a database structure unique to ArcGIS for accessing and mosaicking separate rasters on-the-fly) with a mosaic. This is the first mention of a Mosaic Dataset (which I might recommend if you're not using the resulting file outside ArcGIS, and you have some experience with it) but I assume you have a reason for wanting to create a new file with all three original datasets combined into one. Cody
... View more
10-09-2018
01:42 PM
|
0
|
0
|
6063
|
|
POST
|
Hi, I've had an engineer look at your notes, and I think the exposure is the problem. Our camera database does not contain this camera, so it will not automatically recognize the MapIR, but it looks like you *do* have the workspace set up correctly. Unfortunately, the image you sent is extremely dark - the brightest pixel in the image seems to be DN value of 13. Are all of the images this dark? Do you have another sample dataset with a more normal exposure? If the software can't find any tie points between images, it will remove them as "unsolvable". Cody B
... View more
09-25-2018
09:26 AM
|
0
|
2
|
5785
|
|
POST
|
If you define your polygon and then Run the “clip” tool, be sure to turn on checkbox to clip to geometry, and define a NoData value for pixels outside the polygon, you'll clip out a new image containing pixels only within the polygon: If you do not wish to save your clipped file to disk, you can also use the CLIP raster function to create a temporary layer. Then run "Band Collection Statistics" to calculate mean, standard deviation, more: (note this requires the Spatial Analyst extension) Your statistics should not be counting the NoData pixels - verify that in your statistics table. If you have a multiband file, you'll get statistics for each band Cody B.
... View more
09-24-2018
06:54 PM
|
0
|
1
|
1364
|
|
BLOG
|
Ed - sorry my blog wasn't more complete (I try not to make them too long!) but the above discussion is my best understanding of ANY metadata file written by the DJI drones - I don't know what is different about the *.dat vs. *.srt files. (I've updated the text above) If time permits, I'm hoping to have an engineer at Esri focus some time on understanding and reading these files, but my understanding is that they may not include complete records without temporal gaps. If you have a readable (ASCII) version of the *.srt file, we'd be happy to take a look at it. It would need to be reformatted for compatibility with our "multiplexer" GP tool (see doc at http://esriurl.com/FMVmanual).
... View more
09-19-2018
11:42 AM
|
1
|
0
|
14128
|
|
POST
|
Thanks to Guenter for the prompt reply, and accurate advice. I want to add that we have more resources re: the mosaic dataset and automation using MDCS at this link ArcGIS Imagery Workflows | ArcGIS. On this landing page, if you will follow the link to our ArcGIS Online Group, you will find a sample dataset for the Frame Camera raster type (here), and we will be posting a sample script based on MDCS very soon - I will update this post with a link when the script is available. Thanks Cody B.
... View more
09-13-2018
08:57 AM
|
1
|
5
|
2909
|
|
BLOG
|
For FMV in ArcGIS (ArcGIS Pro 2.2 or later with Image Analyst Extension, or ArcMap 10.x with the FMV add-in) to display videos and link the footprint into the proper location on the map, the video must include georeferencing metadata multiplexed into the video stream. The metadata must be in MISB (motion industry standards board) format. Information is here http://esriurl.com/misb, but drone users do not need to study this specification. For non-MISB datasets, Esri has created a geoprocessing tool called the Video Multiplexer that will process a video file with a separate metadata text file to create a MISB-compatible video. This is described more completely (e.g. format for the metadata about camera location, orientation, field of view, etc.) in the FMV Manual at http://esriurl.com/FMVmanual.
Running the Video Multiplexer is straightforward if you have the required metadata in the proper format, so that is the key challenge. Esri has an app available at http://esriurl.com/SSEE that can be used to plan and control drone flights. This app for iPad is free for users with an ArcGIS Online or Enterprise account, and it will automatically record the metadata required for the Video Multiplexer on any video flight (manual or autonomous). Drones supported by this app are listed at https://esriurl.com/SiteScanSupportedDrones.
For users that require Android, Esri business partner CompassDrone has built an application called CIRRUAS that will capture video metadata required for FMV support. CIRRUAS is available at https://compassdrone.com/cirruas/. Note that the required metadata must be captured at the time of the drone flight. If you have videos that were previously captured without using this app, it may be possible to extract the required metadata, but there are limitations and our experience has shown that it is challenging. Further discussion is included below.
DJI drones write a binary formatted metadata file with extension *.dat or *.srt (depending on drone and firmware) for every flight. There is a free utility called “DatCon” at this link https://datfile.net/DatCon/downloads.html which will reportedly convert the DJI files to ASCII format. That ASCII file could then be manually edited for compatibility with ArcGIS Pro as described below. If you decide to pursue this editing and reformatting, please see this blog for additional advice: http://esriurl.com/MultiplexerTipsTricks.
Key points:
Esri has not tested and cannot endorse the free DatCon utility. If you choose to use it, as with any download from the internet, you should check it for viruses etc.
DJI has changed the format of the metadata in this file on multiple occasions, so depending on your drone and date of its firmware, you will find differences in the metadata content. Esri does not have a specification for the DJI metadata at any version, so cannot advise you what to expect to be included in (or missing from) this file.
Another key point is that the DJI *.dat and *.srt files were created for the purpose of troubleshooting; they were NOT designed with the intent of supporting geospatial professionals seeking a complete metadata record for the drone, gimbal, and camera. As a result, users will typically find temporal gaps in the metadata. As a result, processing this metadata through the FMV Multiplexer will likely generate incomplete and/or inaccurate results, unless you apply manual effort to identify the temporal gaps and fill in your own estimated or interpolated values for the missing times and missing fields.
This blog was first written in September 2018, and it is very possible that DJI will make firmware changes in the future to change the readability and completeness of their metadata.
NEW UPDATE September 2022: if any portion of your video aims above the horizon, the features of FMV may not be suitable for your needs. See resources in post below from 09-20-2022.
Check back in this blog for updates as more capabilities are developed.
... View more
09-09-2018
07:27 PM
|
6
|
25
|
23988
|
|
POST
|
Bob sorry for the late reply - I just found this thread. DId you resolve this? What I believe will work is 1) build footprints so the image borders are clipped off when zoomed into (nearly) full resolution, then 2) rebuild all overviews (the reduced resolution views) What you're seeing when you zoom out are overviews based on the current view when they're built. But one note - you said you built footprints with minimum value of 75 - this should normally be 0, or near zero if you have imagery using lossy compression (JPG, JP2, MrSID etc.). If you use 75, I'd expect a lot of darker pixels (values below 75) around the edge of the images would get clipped out by the footprint, contrary to your intent... Let us know if this is still an issue Cody B
... View more
08-27-2018
07:48 AM
|
0
|
1
|
1193
|
|
POST
|
Load the service into the map Go to table of contents, right click --> properties --> processing templates --> none select layer in table of contents, go to Image Service Layer on toolbar and select Symbology ... and you can assign any band to the R and G and B displays Note the Processing Templates provide faster access to the most common band combinations and indices (see 2nd screenshot above)
... View more
08-01-2018
09:29 AM
|
0
|
0
|
6385
|
|
POST
|
Dan "Oriented" imagery is a new capability for ArcGIS, enabling management and exploitation of imagery with part or all of the image viewing above the horizon (although the schema also supports low oblique imagery and Image Services). Support is provided in ArcGIS Pro as well as the web. It is available under Esri's Early Adopter program at http://esriurl.com/OrientedImageryDownload Brady I will forward this to our engineers Cody B.
... View more
07-31-2018
04:02 PM
|
0
|
1
|
3651
|
|
POST
|
Jennifer Please accept our apologies. The installation file for the Oriented Imagery tools was supposed to have doc included, but it was left out. We're correcting that in the download but you can get the doc directly from here: https://go.esri.com/OrientedImageryDoc Cody B
... View more
07-25-2018
01:34 PM
|
0
|
1
|
1569
|
|
POST
|
Alex Stop the service, edit the MD to add the new field, then restart the service. My guess is this is all working, but you also need to edit the Service Properties --> catalog --> allowed fields to enable access to the new field. By default it will be off.
... View more
06-04-2018
01:49 PM
|
0
|
5
|
3284
|
|
POST
|
Przemek I have spoken to our Technical Support staff, and this sounds like an installation problem. Can you please log a tech support incident with them, and they can do a screenshare meeting to determine what is wrong. https://support.esri.com/en/contact-tech-support Thanks Cody B
... View more
06-01-2018
10:08 AM
|
1
|
1
|
2630
|
|
POST
|
Przemek I ran this tutorial data and it worked fine. Just to clarify, you are trying to multiplex the tutorial data (01425001.csv and 01425001.mpeg) and your output file is zero size? Do the tutorial videos play properly in FMV? Have you tried any of the other geoprocessing tools? I am wondering if your installation of the add-in was completely successful. Cody
... View more
06-01-2018
08:54 AM
|
0
|
3
|
2630
|
|
POST
|
This is typically a problem with the UnixTimeStamp data. Since you said the same happened with the tutorial data, it is possible you did this: 1) open metadata csv file in MS Excel 2) save file 3) try multiplexer If you do the above without adding step 1.a.) BE SURE TO SET THE TIMESTAMP FIELD FORMAT FORMAT TO "NUMBER" then MS Excel converts the data to scientific notation and effectively corrupts your UnixTimeStamp. another possibility is if your UnixTimeStamp records are milliseconds vs. microseconds. It needs to be a 16 digit number (but this should not have been a problem with the tutorial data). If that does not work please upload your metadata file. (I don't need the video) Cody
... View more
05-31-2018
04:10 PM
|
0
|
5
|
2630
|
|
POST
|
This could be your answer. The PNG format tiles are not compressed. We recommend using "mixed JPGPNG" format, which uses JPG for all tiles *except* those that have pixels labeled as transparent. Using any compression method (JPG, ECW, MrSID, others), if a pixel is 0, the compression may change that to a 1 or a 2 (still very dark black). If 0 is supposed to be treated as transparent, the compressed nonzero values will no longer treated as NoData in ArcGIS (a.k.a. transparent). For those (typically few) tiles with NoData values, they'll be written as PNG, but the majority will be JPG. Try reprocessing a SUBSET (not the entire dataset!) and use format = JPGPNG. If you have a lot of NoData pixels within the interior of your dataset, this may require further discussion.
... View more
05-31-2018
11:16 AM
|
1
|
0
|
4343
|
| 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 |
Tuesday
|