> This is a set of circumstances where the UX of the modern device is subtly far worse than the old pen and paper way, with some quite spectacular results. I u

> This is a set of circumstances where the UX of the modern device is subtly far worse than the old pen and paper way, with some quite spectacular results. I understand why, when helping a user navigate from one side of a dense city to the other, a mapping app might not draw in small alleyways that would make the big picture illegible. But why in the world are tiles/pixels on the map that, if zoomed in, contain navigation hazards, shown to contain no hazards?!? Take a look at this Google Maps view of the shoals in normal view, with pale blue everywhere: https://maps.app.goo.gl/2K27Bfp9C5YN7cDu7 https://maps.app.goo.gl/2K27Bfp9C5YN7cDu7 Maybe you see two tiny landmasses, maybe your screen doesn't show them. Zoom out far enough to 20 mile tiles and they go away completely. Zoom in close and see a tiny stripe of tan land. Then turn on satellite view...Does it match what you expect to see? If the map is already as dense as possible, it makes sense to simplify the least relevant details - it should be obvious that zooming in would be useful. But if it's almost featureless, there's no reason to simplify it to be completely feature-free, that implies there's nothing at any scale! > Ultimately the blame falls on the navigator and the skipper, but I can’t help but feel sorry for them. Certainly the proximate cause and liability for the grounded vessel fall on the navigator and skipper, it was in their hands and is their responsibility, but this is an easy and understandable mistake that will be made by someone else again if the root cause - bad UI on the chart plotter - is not also addressed.