The short trip out on the R/V Endeavor was a huge success. After leaving the dock and going to the VSAT internet connection I was able to quickly identify and squash a long-standing yet elusive bug in the ship-to-shore transfer code. I also discovered (and promptly squashed) quite a few minor bugs within OpenVDMv2, none of which had appeared in my development environment.
When I decided to leave NOAA’s Office of Ocean Exploration and Research it was in small part due to the excessive time spent at sea aboard the Okeanos Explorer. It’s been exactly 2 years since I left NOAA and I haven’t spent one night off-shore. Well that’s about to change. The reason: OpenVDMv2.
Quick update on some subtle improvements recently added to OpenVDMv2. As it turns out most research vessels do not have a gigabit internet connection. This makes leveraging cloud-based resources such as public map tile servers difficult. To meet this challenge OpenVDMv2 will begin deploying with a stand-alone map-tile proxy server.
Most days I feel pretty lucky. I live in a great part of the country and get to make a living doing what I love. Today I feel obnoxiously lucky. I’m bound for a beautiful place on other side of the planet, Maui, Hawaii! Oh yeah, it’s for work (mostly)!
Up until now almost all developments on the new user-interface and under-the-hood improvements with OpenVDMv2 have been centered around software and a web-interface installed shipboard. And while OpenVDMv2 provides mechanism for getting data off the vessel, not as much effort has been made to provide a slick portal for accessing that data on shore… until now.