Latest Contributions by JeffLiedtke

‎11-30-2016

Farouk, I just wanted to reach out with an update. The new Garmin VIRB Ultra camera records the proper metadata for use in the FMV Video Multiplexer tool. We are working directly with Garmin for an integrated solution that produces a CSV file that can be directly input into the multiplexer tool. This integrated solution should be available in early 2017. Regards, Jeff

‎11-30-2016

Please see the response in https://community.esri.com/thread/185638-working-in-fmv-no-datavideoanything-is-present-in-finalized-multiplexed-location I apologize if your question was somehow overlooked.

‎11-30-2016

Mark, I saw a post regarding time stamp conversion of your Contour data - but now I don't see it? I'm including my response below in case this helps. Regarding sending me your data - yes, I'd be happy to check it out. Please review the steps below first to make sure your time stamp data is properly converted for use in the multiplexer. Time Stamp conversion from human readable time to UNIX time. Use the converter at http://www.epochconverter.com/ to make sure your time is UNIX time in microseconds (16 digits) - you may have to add 3 zeros to their milliseconds value (13 digits). Convert the first time stamp and the last time stamp, then subtract the first timestamp from the last timestamp to get the total time range of your metadata. This should match the length of your video as a check. In Excel, divide the total time range (see above) by the number of metadata records to get the average increment change. Then in the second record in your metadata table, add this increment change to the first timestamp value to get the proper timestamp value for the 2nd record. Select the first 2 cells in the timestamp column (one containing the beginning UNIX timestamp and the 2 nd contains the incremental value added to the first value) and drag this formula all the way to your last record. All the timestamp records should be incremented properly. Create a new column in your spreadsheet, and copy all the timestamp values computed by the formula into this new column as a value. Then delete the timestamp computed by the formula column and retain the UNIX timestamp written as values column. Again – as a reminder - Excel insists on storing large numbers in scientific notation. When you save your updated csv file, make sure it is saved with the UNIX timestamp column [format cells] saved as a number with zero decimal places. Let me know how this works for you. Jeff

‎11-30-2016

Mark, When you save your CSV - presumably using MS Excel, please ensure that the format of your UNIX Time Stamp column is saved as a number with zero decimal places. Excel insists on representing this 16-digit number in scientific notation - you need to ensure it is a saved as a number. And the csv file needs to be closed before it can be used in the multiplexer tool. Jeff

‎11-15-2016

Hello Bledar Birbo, We continue to work with CompassDrone (Professional DJI Dealer) on an integrated solution for working with your DJI drone data in Esri FMV. We are making good progress with data from the Phantom 3 and Inspire 1 systems, and will then focus on the Phantom 4, Inspire 1 Pro, Mavic and Matrice systems next. The goal is to provide a solution that easily converts your metadata into a CSV file that is directly input into the FMV video multiplexer - along with your video data - for conversion into a single MISB-compliant video file for viewing and analysis in FMV. We expect to have a workable solution for the initial systems (P3 and Inspire1) in December. Thanks for your continued interest and patience. Jeff

‎11-11-2016

Steve, Thank you for your helpful post. Video data in .MOV format is not uncommon, and users need to know how to convert .MOV video files into a format supported by FMV. Just a little general background for our users: A codec is a compression standard that compresses raw video when encoding and decompresses the data upon playback. Examples of codecs are H.264, MPEG-2 and MPEG-4. A format is a file container that holds one or more codecs. Examples of container formats include .MOV, MP2 and MP4. Thus, .MOV is a container format, while H.264 is a codec. The recommendation to change the video file extension from .MOV to .H264 is generally true for new sensors since Apple adopted the H.264 codec for the .MOV file format. A simple solution that will work in many cases - users should try this first and see if the video works in FMV. However, older .MOV files or older sensors may utilize a codec different from H.264 and may not work in the FMV application. In the latter case, and as a general practice, we recommend that users explicitly convert their .MOV, etc. files into any of the 12 common file types supported by FMV. The supported file types include .ps, .ts, .mpg, .mpeg, .mp2, .mpg2, .mpeg2, .mp4, .mpg4, .mpeg4, .h264, .vob, or .m2ts. For best video quality-to-file size ratio, we suggest MP4 using the h264 codec. VLC is an excellent open source, free, multimedia player that converts between different formats (i.e., encapsulation) and codecs. Note: the VLC media player does not recognize MISB-compliant metadata, so if your video has MISB data encoded, it will be stripped away in the conversion process. I'm not aware of any sensors that produce MISB-compliant video data in .MOV format, but if in doubt, change the file extension first to see if this works. Jeff

‎11-09-2016

Jeff and Peter, Sorry you are having trouble. I went through the process outlined above just to double check and it worked fine for me. Did you enable ArcMap 10.4 with the proper authorization license file, and ArcMap 10.4 works OK? Jeff

‎11-08-2016

Jeff and Peter, Unfortunately, the FMV Add-in GP tools need to be uninstalled as part of uninstalling Desktop 10.2.2. I apologize for not being explicit about this. What you need to do is: 1) Uninstall 10.4 2) Reinstall 10.2.2 3) Uninstall the FMV 1.2.1 GP tools 4) Uninstall Desktop 10.2.2 5) Install Desktop 10.4 6) Install the FMV Add-In 1.3.1 7) Install the FMV Add-In 1.3.1 GP Tools I hope this does not pose too much of an inconvenience for you. Jeff

‎11-07-2016

Michal, I appreciate your follow up, especially since I had a misconception. I had the impression that the metadata was displayed on the video during playing only, and was not encoded in the video stream - which is not an unusual occurrence. However, it sounds like your metadata is indeed encoded in the video stream, and if this is true, the workflow you outline is correct. An added step is that you need to strip the metadata from your video before you can multiplex it into a MISB-compliant format the FMV Add-In can utilize. Let me summarize the workflow to be clear. 1) Start playing your video, then display the video metadata table that shows metadata values as the video plays. This sets up the environment. Stop playing the video. 2) In the metadata display window, select Record and navigate to an output directory and assign a name to the CSV metadata file to be created. 3) In the video player, go back to the very beginning of the video (00:00:00:00). Play the video which will also record the associated metadata at the same time and write the data to a metadata file on disk. 4) Strip the metadata from your video. Download and/or open VLC Media Player (free download). In VLC, main toolbar in the Media tab, choose Convert/Save. This opens a dialog; select your video on disk, then select Convert. This flips the dialog window to the Convert parameters, choose a video format and write to disk location. This process will export the video data to another disk file without metadata. 5) Review your metadata CSV file – open in MS Excel. You can either map your metadata field names using the Video_Multiplexer_MISB_Field_Mapping_Template.csv, or change the names of your metadata fields to be the MISB tag names. 6) The time stamp needs to be in UNIX time, use the converter at http://www.epochconverter.com/ to make sure your time is UNIX time in microseconds (16 digits). Convert the first time stamp and the last time stamp, then subtract the first timestamp from the last timestamp to get the total time range of your metadata. This should match the length of your video as a check. 7) In Excel, divide the total time range in (6) above by the number of metadata records to get the average increment change. Then in the second record in your metadata table, add this increment change to the first timestamp value to get the proper timestamp value for the 2nd record. Select the first 2 cells in the timestamp column (one containing the beginning UNIX timestamp and the 2 nd contains the incremental value added to the first value) and drag this formula all the way to your last record. All the timestamp records should be incremented properly. 😎 Create a new column in your spreadsheet, and copy all the timestamp values computed by the formula into this new column as a value. Then delete the timestamp computed by the formula column and retain the UNIX timestamp written as values column. 9) Excel insists on storing large numbers in scientific notation. When you save your updated csv file, make sure it is saved with the UNIX timestamp column [format cells] saved as a number with zero decimal places. 10) Use the FMV GP tool Video Multiplexer with the inputs being the new VLC video, the metadata csv file and the Video_Multiplexer_MISB_Field_Mapping_Template.csv. If you do not have video frame corner coordinates, nor the required sensor attitude info, you will only be able to display the ground track of the sensor on the map. If you have the sensor location and the center of the video frame on the ground (in map projected space), I can see how the video frame could be computed using the Field of View and trigonometry, but that requires the talents of someone well versed in coordinate mathematics and is beyond the scope of this workaround. All the Best! Jeff

‎11-03-2016

Michal, Thanks for the heads up regarding the 64-bit background processing issue with the FMV geoprocessing tools. This is a known issue but we don't have a solution for it yet. Regarding the necessary parameters to compute the 4 corners of the video frame - the sensor orientation parameters are needed to compute the transform between the video frame and the map display. It sounds like you have the sensor position displayed on the video, but this information would need to output to a csv file along with the time stamp to see the sensor position displayed on the map as a ground track. Additionally, the attitude parameters are also needed, including heading, pitch, roll, altitude and field of view. We don't have a work-around if these required parameters are not provided in a CSV. Regards, Jeff

‎11-02-2016

Peter and Jeff, The minimum version of ArcGIS that supports the video multiplexer is ArcMap 10.3 It is also supported on later versions of ArcMap 10.3.x, 10.4.x and 10.5 slated for mid-December 2016. If you update your ArcGIS before mid-December 2016, you will need to install the FMV Add-In 1.3.1. The new version of the FMV Add-In will be available late December, and will be FMV Add-In 1.3.2. Regards, Jeff

‎10-26-2016

Mark, Thanks for the helpful info and screenshots. You have access to the FMV geoprocessing toolbox and tools. What is missing is the FMV toolbar. The steps in the post above describe how to expose that toolbar. Perhaps the FMV Add-In is not installed? Go to the ArcMap main menu, select "Customize", then Add-In Manager. This opens the Add-In Manager dialog which should list the version of the FMV Add-In loaded on your machine. Also, what version of ArcMap are you running? Your screenshot of the FMV toolbar is an older one from several releases ago. The newer toolbar (as of 1.5 years ago, ArcMap 10.3) is one that looks like this (the search icon looks different). The version of the FMV Add-In needs to match the proper version of ArcMap. You can get the proper version of the FMV Add-In by browsing to the FMV Product page www.esri.com/FMV. Scroll to the bottom of the page for instructions on how to get the FMV Add-In for your version of ArcMap. It is free of charge if you are on maintenance. Otherwise there is a nominal fee of $19.99. Another good source for info if you need to install the FMV Add-In is the FMV User's Manual is: https://community.esri.com/docs/DOC-8607 Best, Jeff

‎10-25-2016

Hello Mark, Go to "Customize" on the main ArcMap menu and select "Toolbars" then scroll down and choose Full Motion Video. The toolbar will appear in ArcMap and you can then dock it as a toolbar group in ArcMap. Jeff

‎10-25-2016

Farouk, Do an internet search on inertial measurement unit - There are lots of options that are not expensive. That said, I am aware of the Garmin VIRB XE video camera that collects orientation information as it collects video data. I don't think it collects altitude. And remember that if the horizon in in the field of view you will not be able to project the footprint of the video frame on the ground at this time. We are working on a solution that handles this case. Jeff

‎10-24-2016

Michal, Presently, there is no FMV web capability, however FMV in a web environment is planned for late 2017. We expect to use JS API 4.x, but this may change as we get closer to implementation. Jeff

Online Status	Offline
Date Last Visited	‎08-09-2023 12:43 AM

My Ideas

Latest Contributions by JeffLiedtke

Re: Garmin Virb Elite

Re: Finalized Multiplexed video not present? FMV

Re: Working in FMV, no data/video/anything is present in finalized multiplexed location.

Re: Working in FMV, no data/video/anything is present in finalized multiplexed location.

Re: FMV 1.3.1 with DJI Phantom 4

Re: FMV 1.3.1 with DJI Phantom 4

Re: Full Motion Video Add-In: Video Multiplexer Access

Re: Full Motion Video Add-In: Video Multiplexer Access

Re: FMV GP tool error; FMV calculate corner coordinates

Re: FMV GP tool error; FMV calculate corner coordinates

Re: Full Motion Video Add-In: Video Multiplexer Access

Re: FMV Toolbar Missing (One of two)?

Re: FMV Toolbar Missing (One of two)?

Re: Collecting metadata for Full Motion Video without a drone

Re: ArcGIS Full Motion Video (FMV) 1.3 is released

Re: FMV Toolbar Missing (One of two)?

Re: FMV Sample Video

Re: ArcGIS Pro - Classification Wizard with DSM/DT...

Re: FMV GP tool error; FMV calculate corner coordi...

Re: Object Based (Oriented) Image Analysis

Imagery and Remote Sensing User Group