Quote:
Originally Posted by Kurt
It would be great if we could start working towards best practices for the community!
Thanks!
-Kurt
|
I love AIS for it's usefulness helping me identify targets. But I don't want to use it for anything else because I can't trust anything that may be changed by the user. My idea of a best practice is that the AIS should be set up with static data per vessel, and then pretty much left alone. If someone really wants to know my draft they can call me on the VHF. If they really want to know the Pilot's name they can call me on the VHF. Personally I would choose to change dynamic data only when some regulator forces me to. I've got enough to keep me busy already than to have to go and change a field when the pilot comes aboard, and if I'm on a vessel that requires a pilot then the powers that be will know already. Understand that I'm speaking from the frame of reference of a tug boater, who inhabits the pilothouse alone most of the time. Deep draft types have the luxury of delegating this kind of stuff to someone else.
The MKD (Minimum Keyboard Display) is way too unfriendly for everyday use. Some fields can be altered via electronic charting systems such as the Transas Navi-Sailor.
I totally agree with the earlier post that emphasized not using AIS for collision avoidance, and when I teach students about AIS I try to pound that into their heads. But I constantly see people using AIS, especially when the radar is set to display AIS targets, for collision avoidance. It sends shivers down my spine.