duncan_m
Member
So a couple of interesting points. On the whether they know it's a bug, I'd assume at least one person at Navionics has a sailing boat and uses their app so while the support team might not be regular sailors who use lots of tech, someone must be.
Though as I said I'm not sure this a 'global' issue...but I also cannot see how it couldn't be given there's no way to set an offset and indicate whether that is from the bottom of the keel or to the waterline.
Updated scenarios..
So there are a couple of possible scenarios from what's been suggested:
- Navionics ignore offset in the DPT sentence for the app and their sonar chart - This sounds like the most likely and I am yet to meet any boater who's interested in the transducer's depth rather than the waterline or keel/hull bottom;
-Navionics ignore offset in the DPT sentence only for the app but do feed the full data back - This seems unlikely and as mentioned many people offset to keel bottom or lower for safety rather than waterline or whatever their preference may be so sonar would be even more invalid;
- This is only an issue with my hardware set-up - I await someone to say otherwise but NM0183 sentences are pretty standard, would actually prefer if I was wrong;
Resolutions..
Either way there are a couple of fairly simple fixes available:
- Use the offset in the sentence and ask the user to indicate if this is bottom of keel or waterline in the app. This prompt could be preset with the current offset as most owners are probably have a vague recollection as to how they have their depth sounders set.
- Ask user to confirm if it's keel/other then prompt to update a value to get it to waterline for sonar chart;
- Alternatively if there's some sort of consistency issue around DPT sentences from different multiplexers/brands etc that Navionics are aware of, then ask the user to set the offset in the app one to what they want it to show in-app and one to the waterline;
For me as a sailor..
From a person goals perspective of accurate instruments any resolution is good.
For Navionics sonar charts
From a Navionics getting accurate sonar chart data perspective, both of the suggests above require some sort of 'trust' from the users to put in accurate values so that the output of the charts is accurate.
So for data normalisation you probably want an extra data point or two to work with. I'd go for boat make and model. Then if Navionics spot a Bravaria 37 with an offset that's outside of the normalised range for the above setting for that boat make/model then they could automatically discount it's data from sonar charts from a depth perspective.
I'm also assuming that they have some pretty decent bathymetry people at Navionics and that they can normalise the data in other ways but have no idea what happens behind the scenes. As Seven Spades has mentioned if the chart is just plain wrong too often then that's hard to argue.
...
Btw not sure if I'm going OTT with detail here but I genuinely think it's important to have good data when you're on a boat. If it's not accurate and you or one of the crew rely on it albeit accidentally if you know it's wrong then bad things can and do happen. For a new navionics user / sailor etc then they might think they're wrong....
Though as I said I'm not sure this a 'global' issue...but I also cannot see how it couldn't be given there's no way to set an offset and indicate whether that is from the bottom of the keel or to the waterline.
Updated scenarios..
So there are a couple of possible scenarios from what's been suggested:
- Navionics ignore offset in the DPT sentence for the app and their sonar chart - This sounds like the most likely and I am yet to meet any boater who's interested in the transducer's depth rather than the waterline or keel/hull bottom;
-Navionics ignore offset in the DPT sentence only for the app but do feed the full data back - This seems unlikely and as mentioned many people offset to keel bottom or lower for safety rather than waterline or whatever their preference may be so sonar would be even more invalid;
- This is only an issue with my hardware set-up - I await someone to say otherwise but NM0183 sentences are pretty standard, would actually prefer if I was wrong;
Resolutions..
Either way there are a couple of fairly simple fixes available:
- Use the offset in the sentence and ask the user to indicate if this is bottom of keel or waterline in the app. This prompt could be preset with the current offset as most owners are probably have a vague recollection as to how they have their depth sounders set.
- Ask user to confirm if it's keel/other then prompt to update a value to get it to waterline for sonar chart;
- Alternatively if there's some sort of consistency issue around DPT sentences from different multiplexers/brands etc that Navionics are aware of, then ask the user to set the offset in the app one to what they want it to show in-app and one to the waterline;
For me as a sailor..
From a person goals perspective of accurate instruments any resolution is good.
For Navionics sonar charts
From a Navionics getting accurate sonar chart data perspective, both of the suggests above require some sort of 'trust' from the users to put in accurate values so that the output of the charts is accurate.
So for data normalisation you probably want an extra data point or two to work with. I'd go for boat make and model. Then if Navionics spot a Bravaria 37 with an offset that's outside of the normalised range for the above setting for that boat make/model then they could automatically discount it's data from sonar charts from a depth perspective.
I'm also assuming that they have some pretty decent bathymetry people at Navionics and that they can normalise the data in other ways but have no idea what happens behind the scenes. As Seven Spades has mentioned if the chart is just plain wrong too often then that's hard to argue.
...
Btw not sure if I'm going OTT with detail here but I genuinely think it's important to have good data when you're on a boat. If it's not accurate and you or one of the crew rely on it albeit accidentally if you know it's wrong then bad things can and do happen. For a new navionics user / sailor etc then they might think they're wrong....