GPX and KML files can now be imported en masse. Drag and drop one or more files (or click on the input field to get a file open dialog).
You can either add them all to the existing Trip, or create a new trip.
Added Export of loaded trip to .gpx file (in Downloads directory). At present, route departure time and speed are not included. I’m trying to figure out which of the numerous competing .gpx extensions to support. If you have any requests or advice on this topic, please let me know.
This is mostly a fit and finish release. Lot’s of UI and perf improvements plus a new display of relative positions of earth, sun and moon. This animation, like everything else in DeepZoom is
linked to the timebase. The timebase is accessed by clicking on the time readout at the lower center of the screen.
Added “Find” to Trips page. This will show a list of all public trips within the current view. Filters are available for “power”, “sail”, “kayak”, and “swim” along with sorting by name, length, duration, and stars.
Added trip id to url so forward and back browser buttons work.
Fixed longstanding bug which could cause hangs, especially on Cordova demo trip.
Pilot Charts show probabilities of wind strength and direction for a particular location and time,
to help plan optimal sailing routes.
Historically, these charts were derived by manually collating the logs of thousands of vessels transiting the oceans over the last few hundred years.
Below is an excerpt from a traditional pilot chart for a portion of the southern Pacific ocean during the month of February.
Each windrose covers a 5°x5° area. The length of the barb indicates the percentage of time the wind blew from that direction,
and the barb style indicates the strength of the wind.
The Pilot Charts layer lets you plan a route based on historically measured wind speeds
and directions. This layer shows a probability windrose on a color coded background.
The background shows mean historical wind speed along with arrows showing mean wind
direction for each 14 day period.
Superimposed on this background is a windrose which shows the percentage of time the
wind is blowing from each of 16 cardinal/secondary/intercardinal directions. The length
of each bar shows the percentage of time the wind blows from that direction averaged
over a 14 day period. The length of the colored rectangles within each bar indicates the
percentage of time the wind blows with each velocity range.
Columbus trip 1
Here’s a trip showing how Columbus travelled to the Bahamas on his first voyage.
The bar from due east ending in the number “42”, indicates that the wind was blowing from that
cardinal direction 42% of the time. The wind was under 20 knots about 40% of the time, and there was
an easterly component virtually all the time.
Columbus was likely sailing straight down wind most of the westward voyage.
To create terrestrial routes, first define start, end, and waypoints as you normally would with
aquatic trips. Then on the routes page, change the mode of transit (driving, walking, biking),
and your route will be converted to the new mode.
If you need to change the route, the easiest way is just to convert back to the original “great circle” or
ship/plane navigation mode, add or change waypoints, and then convert back to driving, walking, or biking.
New Zealand is one of the few countries in the world which makes their nautical charts available for free.
Others include the USA, Brazil, and Argentina. Here’s a good listing of the worldwide nautical publishing agencies. And the USA is the only country which has placed in the public domain the tide and current
harmonics needed by DeepZoom to create animated current displays.
Instead, each country has a semi-functional website where you can license charts and download them in a bewildering array of formats.
Or you end up just paying your charting application to handle the licensing on your behalf.
Since this is a low budget operation, I can’t justify the rather exorbitant licensing cost for charts from each national government publishing entity.
If DeepZoom ever grows up to play in the big leagues, it will need to face this issue.
I started the original incarnation of DeepZoom sometime around 2008, mainly to learn web technologies and because I couldn’t find a good web visualization of tides and currents.
While sailing and kayaking in the Pacific Northwest and Alaska, I would sometimes find myself making little or no progress against a substantial tidal flow, so it’s been easy to become obsessed by the topic of tides and currents. Plus, I spent formative years of my youth with the wharf rats under the industrial docks in Everett, Washington, where tides were the main event.
The original version of DeepZoom was built with Silverlight, and then a version followed for Windows Phone. The Windows Phone version was actually kind of nice, responsive, and presenting a reasonably easy environment for me, the developer. But overall - What a fiasco!, having both technology platforms fail so spectacularly. Thanks, Microsoft!
Eventually I rebuilt everything using web technologies like Bootstrap and D3. It worked well enough and then I got distracted imaging neurons at the Allen Institute for Brain Science for a few years.
Being largely homebound for the duration of Covid-19 provided an opportunity to rework DeepZoom yet again, this time switching to Quasar/Vue as the primary client framework. And then came unbridled feature creep: trips, routes, markers, tracks, pilot charts, wikipedia, and the ability to share trip plans with others.
I’m much indebted to Morgan Conrad for help with wind data wrangling and Chris Mulverhill for Coast Pilot processing.
Where to next?
I’m often at a loss to figure out what features to prioritize next.
I’m just trying to include all of the tools I like to use when planning a voyage of a day, week, or months. If you have any suggestions,
I’d love to hear from you on the discussion forum.