Can FMV use the position information (metadata) that the Garmin Virb Elite records?
any device that supports the formats listed here can be used according to the FAQ
Frequently Asked Questions about FMV
Thanks fro the information Dan
If you're going to ask advice here about metadata, please include information about (or a sample of) the metadata with your question. You'll get more answers if you do not require each of us to go do our own research to fill in the missing parts of your question.
A colleague of mine is familiar with the Virb Elite, and based on his experience and what I found here VIRB Elite Action Camera | Garmin I believe the answer is yes - you should have the required metadata, but some reformatting will be required for the multiplexer to work.
The FMV add-in needs GPS at a minimum (to know the location of the camera), and ideally three orientation angles written in compliance with the MISB specification (which you can find here http://www.gwg.nga.mil/misb/zip_pubs.html but this is probably more information than you need). I don't know for certain, but I think the Virb Elite does *not* write data in MISB format, but if you can get at all of the GPS and orientation metadata in ASCII text format, the FMV geoprocessing tools include a multiplexer which allows you to create MISB formatted metadata in the video stream. See this link for a tutorial: Tutorial for Full Motion Video 1.3.1 is availab... | GeoNet
The video file format (MP4) *is* compatible with FMV.
Thanks for the information. I did not include the file as it was fairly large. Just thought that some user may have used the Virb already. I know that that I can get the data from the unit in gpx format but the sensor orientation is not part of the export.
The Garmin VIRB XE includes both a GPS and orientation sensors. The GPS sensor supplies the camera position info while the orientation sensor supplies the heading, pitch, roll and yaw (also known as "crab") parameters. These, together with the sensor height info (provided by the altimeter) and time stamp are the minimum info needed by the FMV application to compute the video frame footprint on the map.
I took a look at the Garmin VIRB Elite manual and see that it includes the GPS info, but no reference to the orientation information. So it looks like this info is not available with the Elite. With just the GPS location info and the time stamp, you can display the sensor position on the map (but not the video frame footprint). And you will not be able to digitize features in the FMV video player and/or the map without those orientation parameters.
If you want to display the sensor ground track on the map, rename your gpx file extension to .xml. This can then be directly imported into Excel and saved out as a CSV file. The FMV User's Manual https://community.esri.com/docs/DOC-8607 details steps to ensure your metadata conforms to the MISB standard needed by the FMV application - see the Video Multiplexer section (page 39, through page 50).
Thanks very much Jeff
This clears things up. I assume that the multiplexer attaches the XYZ, sensor size and orientation (omega, phi, kappa) to each frame of the video thus allowing the reconstruction of the "footprint" on the ground
Thanks again FMV has now become a valuable application
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.
How's the integration solution for the Garmin VIRB Ultra camera going? We are looking the easiest off-the-shelf video camera to mount to a vehicle and use the resulting video within FMV.
You might consider MediaGeotagger from RedHenSystems.com... We have sorted out a number of "Clapboard" methods for geotagging video and imagery - works for really any camera and track logs you might have. To properly express the VIRB content, a transcoding process to MISB normal KLV form is required. This is also a process that requires a decision if the SPOI is the frame centroid or frame perimeter to establish how the ArcGIS FMV engine operates. If the camera orientation is noisy and/or mis-calibrated, aka uncertainty of the actual IMU, in our experience the frame centroid is a better off-set. Why?
BE-AWARE - azimuth is easily drawn-off an accurate magnetic north by adjacent vehicle iron and steel mass, including slightly magnetized helmet rivets, GPS antenna magnets, batteries, and others. The IMU is good at tilt (gravity does not vary greatly) and GPS is measured in RMS and CEP. Figure a worse-case 30 degree error for out-of-your-pocket handset and actioncam IMU orientation/calibration to magnetic North. This is a rule-of-thumb figure four percent error, eight percent full swing, or 30 degrees for handheld camera. For stabilized gimbals with 12 bit positioning on three or more axes, well figure once percent improvement for each additional $100k.
The record system that Garmin VIRBS provide are essentially a proprietary form of NMEA schema with some proprietary extensions for their related sports and training sensors. MediaGeotagger normalizes the VIRB trackings to NMEA standard which then operates as the geotagging side-car to drive the generation of the required SPOI values for insertion into the synchronized KLV transport stream. This step is a bit critical and magical. Given the tradition of SPOI is deeply related to the military concepts of cursor-on-target and that responsibility, we rely on ParGovernment's "GV Video Framework (Gv2F)" transcoder for the final transcoding to the FMV form. This is the same essential transcoder that is found in the Esri offering known as FMV. The Red Hen module XML2KLV is a special-case we have directly cooperated with Par Government through their Gv2F toolkit that offers an optimized C media framework for C++ and Java bindings.
Has anyone tried it with the Garmin VIRB 360?
Virb 360 has a proprietary metadata that requires normalization to the ArcGIS form of FMV. MediaGeotagger can conform the Garmin Metadata to provide XML structures - available at NGA GeoINT Apps Store. As a 360 image with equirectangular frame it will not conform to MISB SPOI. The Garmin is quite over priced as a spherical camera with quirky features in a two year old design that is out of alignment to easy use IOHO. The Theta and several other <$400 provide superior images and are "StreetView Ready".
FYIMidNight Mappera aka neil
Red Hen Systems StreetView Mobile - YouTube
Retrieving data ...