Thank you for your suggestion. We have already planned to add different colours for different depth ranges. Regarding regional nautical charts, the data sources are different for each country, so we need to process and improve them one country at a time. Our system cannot see which country you are located in. If you are willing to tell us your country, we can give that area higher priority.

sir ASIA

Good day! Thank you for your suggestion and support. We have already released version 2.1.1 in the open testing track. This version includes the features you requested, such as depth colour changes for different depth ranges and AIS support. Please feel free to try it and let us know your feedback.

Greetings the depth bands colour is not very apparent, if may suggest, rainbow colours would be more apparent and informative (same as wind speed colours in weather apps) You can start with red for shallow areas up to 5 metres, progressing to orange,yellow, green, light green, light blue, darker blue...etc this would show at a glance the current depth and where you are heading without the need to read the depth measurement on the map (which is very hard to read specially on small screens) thank you for your patience Have a lovely day

Thank you for the suggestion. I have actually considered a similar approach before, and I agree that using different colours for different depth ranges would make the chart much easier to understand at a glance, especially on smaller screens. The main limitation is the amount of additional map data required. At the moment, most of the depth data is stored as lines and points. For example, a 5-metre contour is essentially stored as a series of coordinates forming a line, with the depth value attached to it. This is relatively efficient in terms of file size. However, to display coloured depth bands such as red for 0–5 m, orange for 5–10 m, yellow for 10–20 m, and so on, the map needs more than just contour lines. It needs to know the complete area between those lines so that the colour can be filled correctly. This means the line-based depth data has to be converted into many filled polygon areas. These polygons can contain a very large number of coordinate points, especially around complicated coastlines, islands, bays and irregular depth contours. Boundaries may also be repeated between neighbouring polygons, which increases the amount of data further. The original depth map file is currently around 500 MB. I previously tested adding a relatively low-precision coloured depth overlay, and even that increased the file size to around 800 MB. That is an increase of approximately 300 MB, or about 60%. Adding more detailed depth bands would increase the file size further. Since the app supports offline chart downloads, this would also increase download size, storage usage on the device, update time, and server bandwidth requirements. The colours themselves require almost no additional storage. The main problem is the large amount of polygon data required to define exactly where each colour should be displayed. For this reason, unfortunately this is not something I can implement at the moment, but thank you for the suggestion and for explaining the usability benefit so clearly.

Thank you for the clarification at the moment depth bands are shades of blues, and as you stated, they are not precise, only indicative of the general depth in the area since the colours themselves do not need additional data, perhaps changing the colour from blue spectrum to rainbow spectrum would be more visually indicative of the general depth in the area with the clearer information that the colours are general indicative not accurate demarcation and if possible make this an option in settings My objective is to make the app more useful and usable to the user, to attract as many users as possible In my case specifically I fish in the general area nearby and use general nowledge and experience, but I'm one of many with different needs Thanks again All the best

That makes much more sense now. Thank you for the clarification and suggestion. This change would require an update to the depth map data, so I’ll plan to work on it together with another ticket: “Add High-Resolution Bathymetry Data Sources by Region.” Thank you again for the helpful feedback.