>When Python is installed by uv, it will not be available globally (i.e. via the python command). Support for this feature is in preview. See Installing Python executables for details.
>You can still use uv run or create and activate a virtual environment to use python directly.
>Thirdly, even if I would touch type, my job needs me to take my eyes of the "IDE screen" occasionally to look at other things like datasheets, PCBs, notes, etc.
What if I told you that touch typing means you could do that while you are typing.
Depends on the ship as well, not all ships change their draught ("depth") that much according to what they carry, but ships like bulk carriers and oil carriers certainly do. They report it via AIS data as well, but as its manually input it is often unreliable. An other idea that has been utilized is to look at the vake patterns (wave patterns) to estimate the speed of the ship.
This is really interesting. I have worked a lot with AIS data (messaging system that relays information such as the position of a ship), but the AIS data can some time lack information (and sometimes can be spoofed). However I have never got around working with imagery data. This seems like a great starting point for that :)
This was a really nice post, using imagery to confirm the positions of ships is really useful when the normally used data source, AIS data, has lacking data or may be spoofed. I have mostly worked with AIS data, but might incorporate these data as well to see what can be found.