Video best practices
Hivemapper supports video from practically any camera and automatically generates 3D maps. Hivemapper will search an entire video and find all suitable frames for mapping so even video not intended for mapping can produce stunning maps. If you are collecting video for the purposes of mapping here are some things to consider to make the most out of your collection time:
Hivemapper currently works best with airborne video with plans to support ground collection soon. Here are some guides Hivemapper has created for common collection methods.
- Collect video with commercial drones
- Collect video autonomously using commercial drones
- Collect video from an airplane (coming soon)
Supported video specs
Hivemapper accepts a wide range of video specifications for building maps:
|Type||Some of the supported video formats that will work with Hivemapper:|
|Frame-rate||Any frame-rate is acceptable.|
|Max length||30 minutes|
Learn more about supported cameras and lenses
Many video cameras produce metadata containing information about their location and camera settings. This metadata is helpful for building accurate maps. Hivemapper automatically extracts metadata from a wide variety of cameras. Video cameras produce this metadata in different formats:
Traces.CSV is a simple video metadata format defined by Hivemapper. If Hivemapper does not support a specific metadata format you can translate the unsupported format into the Traces.CSV format and then upload the file alongside the original video file.
Key Required Description Units Example Value sensorLatitude Required Sensor Latitude. Based on WGS84 ellipsoid. Degrees 60.17682266 sensorLongitude Required Sensor Longitude. Based on WGS84 ellipsoid. Degrees 128.4267578 timestamp Required Represented in the number of microseconds elapsed since midnight (00:00:00), January 1, 1970 not including leap seconds. Microseconds 1442942949817896 sensorTrueAltitude At least one altitude field is required Altitude of sensor as measured from Mean Sea Level (MSL) Meters 14190.71973 sensorGroundAltitude Altitude of sensor as measured from the ground Meters 14190.71973 sensorWGS84Altitude Altitude of sensor as measured from the WGS84 ellipsoid Meters 14190.71973 sensorLaunchAltitude Alttiude of sensor ans measured from the launch point Meters 14190.71973 sensorHorizontalFov Optional Horizontal field of view of selected imaging sensor. Degrees 144.5713043 sensorVerticalFov Optional Vertical field of view of selected imaging sensor. Degrees 152.643631 timeframeBegin Optional Timeframe that data maps to in video, relative to beginning of video. For example, if the data stream starts 1 second into the video feed and the first entry is 2 seconds long, then timeframeBegin=1 timeframeEnd=3 Seconds 1.12 timeframeEnd Optional Seconds 2.25
Video cameras often produce metadata in the form of an SRT file. The metadata in the SRT file describes the location, camera attributes, and timestamp
Below is a snippet from an SRT file produced by the camera on a DJI Phantom 4. As you can see it’s generating metadata every second:
00:00:01,000 --> 00:00:02,000
HOME(-122.2090,37.4178) 2016.10.09 15:55:40
ISO:100 Shutter:400 EV: 0 Fnum:F2.8
00:00:02,000 --> 00:00:03,000
HOME(-122.2090,37.4178) 2016.10.09 15:55:41
ISO:100 Shutter:400 EV: 0 Fnum:F2.8
Video Camera Produces SRT metadata Hivemapper Automatically Extracts DJI Phantom 3 ✓ (as file) ✓ DJI Phantom 4 ✓ (as file) ✓ DJI Mavic Pro ✓ (as file) ✓ DJI Phantom 4 Pro ✓ (embedded) ✓ DJI Mavic Pro 2 ✓ (embedded) ✓ Inspire 2 ✓ (embedded) ✓
Embedded metadata means the video will not produce a separate file; rather the metadata sits inside of the video stream and Hivemapper will automatically extract it once you upload the vide
If you are aware of other video cameras that produce SRT metadata that you want to use with Hivemapper, please contact us.
Many video cameras embed metadata in the video they produce in the form of MISB. More specifically, the KLV format is defined by MISB standards.
Below is a snippet of MISB generated metadata produced by the FLIR StarSafire 380HDc that Hivemapper will automatically extract and convert to JSON:
"checksum" : 25668,
"frameCenterElevation" : 43.150989532470703,
"frameCenterLatitude" : 37.9351806640625,
"frameCenterLongitude" : -122.40153503417969,
"imageSourceSensor" : "FLIR SS380-HD HDEO",
"platformHeadingAngle" : 59.019454956054688,
"platformPitchAngleShort" : 4.197998046875,
"platformRollAngleShort" : -4.6966552734375,
"sensorHorizontalFov" : 8.5200271606445312,
"sensorLatitude" : 37.928791046142578,
"sensorLongitude" : -122.40070343017578,
"sensorRelativeAzimuthAngle" : 287.7613525390625,
"sensorRelativeElevationAngle" : -35.492134094238281,
"sensorRelativeRollAngle" : 0,
"sensorTrueAltitude" : 754.3099365234375,
"sensorVerticalFov" : 4.7928586006164551,
"slantRange" : 1007.9564819335938,
"targetWidth" : 151.06431579589844,
"timestamp" : 1519414443032479,
"uasLocalSetVersion" : 4
Hivemapper automatically extracts MISB metadata from some video cameras:
Video Camera Produces MISB metadata Hivemapper Automatically Extracts FLIR StarSafire 380HDC ✓ ✓ Video Sensor for Shadow 200 RQ-7B ✓ ✓ Raytheon MTS-B ✓ ✓ Wescam MX-15 ✓ ✓
While the MISB standard sets the format for the KLV metadata some video manufacturers modify this format. Hivemapper works with certain video camera manufacturers like FLIR to support the modified version
- No Video Metadata available
If your video does not include any metadata you will be asked to provide a Location Estimate in order for your map to be georegistered. Learn more about adding a Location Estimate Here.
Enable metadata on DJI products
Some camera products capable of recording detailed metadata do not record this information by default. To enable SRT’s on DJI products:
- Open the DJI Go app.
- Open the camera settings menu.
- Switch to the third sub menu (this will be a gear or wrench icon.
- Enable Video Captions.
It is recommended you do a test and verify a corresponding .SRT files is being produced for each clip. Be sure to include both these files when uploading to Hivemapper.com. Enabling video in DJI go will carry over to 3rd party controller apps such as Litchi.