# DVL - Georeferencing video or exporting a timelog of lat long
**URL:** https://discuss.bluerobotics.com/t/dvl-georeferencing-video-or-exporting-a-timelog-of-lat-long/15014
**Category:** Third Party Products
**Tags:** dvl
**Created:** [September 6, 2023, 12:24pm UTC](https://discuss.bluerobotics.com/t/dvl-georeferencing-video-or-exporting-a-timelog-of-lat-long/15014 "2023-09-06T12:24:26Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@GavXYZ](https://discuss.bluerobotics.com/u/GavXYZ)
#### Post date: [September 6, 2023, 12:24pm UTC](https://discuss.bluerobotics.com/t/dvl-georeferencing-video-or-exporting-a-timelog-of-lat-long/15014/1 "2023-09-06T12:24:26Z")
We’ve successfully integrated the Waterlinked DVL with our BlueROV2 (w/ pixhawk & Pi).
The BlueRobotics documentation is very good for this.
However, it’s not clear to me how we can either log the latitude and longitude of the ROV with time or include the lat long in the telemetry.
I have no problem setting the initial position/co-ordinate and we can see the ROV on the map within QGroundControl which would lead us to believe that there is co-ordinate information hiding in there somewhere.
Is anyone able to offer some guidance?
---
### Author:  [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)
#### Post date: [September 6, 2023, 8:53pm UTC](https://discuss.bluerobotics.com/t/dvl-georeferencing-video-or-exporting-a-timelog-of-lat-long/15014/2 "2023-09-06T20:53:55Z")
Hi @GavXYZ,
I believe I responded to this when you asked a few weeks ago in a different post:
> [@Waterlinked GPS Data log](https://discuss.bluerobotics.com/t/waterlinked-gps-data-log/14777/8):
>
> The vehicle has internal DataFlash `.bin` log files, and QGroundControl also logs the MAVLink messages it receives during operation in `.log` telemetry logs, which can both be parsed using [Log Viewer](https://ardupilot.org/dev/docs/common-uavlogviewer.html) or programs like Pymavlink’s [`mavlogdump.py`](https://www.ardusub.com/reference/data-logging.html#mavlogdumppy).
>
> If you’re using `.bin` logs the [`VIS*`](https://docs.bluerobotics.com/ardusub-zola/software/autopilot/ArduSub-4.1/developers/log-messages/#viso) messages give you the information ArduSub is receiving from the DVL extension, and the [`POS`](https://docs.bluerobotics.com/ardusub-zola/software/autopilot/ArduSub-4.1/developers/log-messages/#pos) messages log the vehicle’s position estimate from ArduSub’s sensor fusion (its EKF). In `.log` files you can look at the [`GLOBAL_POSITION_INT`](https://mavlink.io/en/messages/common.html#GLOBAL_POSITION_INT) message data, and possibly also any `VISION_*` messages that get passed along.
Feel free to follow up if you have additional questions 🙂
---
### Author:  [@GavXYZ](https://discuss.bluerobotics.com/u/GavXYZ)
#### Post date: [September 7, 2023, 9:16am UTC](https://discuss.bluerobotics.com/t/dvl-georeferencing-video-or-exporting-a-timelog-of-lat-long/15014/3 "2023-09-07T09:16:14Z")
Eliot, my mistake. I remembered posting this but couldn’t find it. I see now that I originally commented on a similar thread. Hopefully the new keywords in this threads title 'georeferencing/DVL/lat/long will lead others to your answer.