01-16-19, 07:00 AM
Hi
Can you describe the all details about the "Waypoint import improvements" made in the brand new LH3 sw release v3.8.97.
I suggest that you make a very detailed description how it works in the LH 3 handbook, especially the restrictions are undocumented in the LH manuals. I had to google quite a lot to find out that waypoint names can have maximum 16 characters, all waypoint names must be unique and that the comment field can have max 32 characters. These restriction are too restrictive. I understand that the available memory is an issue, but its better to have more quality information than 10´000 unique waypoints.
I have all my waypoints generated om my PC running OpenCPN. The text stored in the description field is not the same field used by LH3. I suggest that you make next version of LH3 more compatible with OpenCPN so the description field could be transferred between OpenCPN and LH3.
Best regards and Thanks
Stefan
Can you describe the all details about the "Waypoint import improvements" made in the brand new LH3 sw release v3.8.97.
I suggest that you make a very detailed description how it works in the LH 3 handbook, especially the restrictions are undocumented in the LH manuals. I had to google quite a lot to find out that waypoint names can have maximum 16 characters, all waypoint names must be unique and that the comment field can have max 32 characters. These restriction are too restrictive. I understand that the available memory is an issue, but its better to have more quality information than 10´000 unique waypoints.
I have all my waypoints generated om my PC running OpenCPN. The text stored in the description field is not the same field used by LH3. I suggest that you make next version of LH3 more compatible with OpenCPN so the description field could be transferred between OpenCPN and LH3.
Best regards and Thanks
Stefan