Depth Data for Nautical Charts

[quantenschaum]

Just for the record (resulting from #18092), I managed to create an OBF containing depth contours and spot soundings from data leeched from https://www.geoseaportal.de/mapapps/resources/apps/navigation (currently down 😞). The workflow is roughly like this:

• download data as GeoJSON
• import into QGIS
• filter the relevant rows
• add columns
  • depth=VALDCO
  • contour=depth
  • contourtype=[5m,10m,20m,50m,100m] with formula using depth%type==0
• export layer as geopackage only containing the 3 added columns
• import into JOSM via OpenData plugin
• save as OSM xml
• convert OSM to OBF using OsmAndMapCreator

Terrible, no command line tools, but it works.

OsmAnd does not display contours without a contourtype tag or values of contourtype<5m, so a 2m line will not show up on the map. I tweaked the nautical map style and the renderer settings for contour lines. Use these, and the map will look like this.

[miramikes]

Looks very good !

[quantenschaum]

Data Sources

IMHO the depth data supplied by OsmAnd is just a proof of concept showcase, they are very inaccurate and unreliable and not at all usable for actual navigation or trip planning.

Germany

The BSH provides access to nautical data in the GeoSeaPortal. There is no documentation, but simply by examining what the webviewer does reveals some WMS endpoints. Depth contours and areas can be found in

• https://www.geoseaportal.de/wss/service/NAUTHIS_Hydrography/guest
• https://www.geoseaportal.de/wss/service/NAUTHIS_SkinOfTheEarth/guest

What is particularly nice is, that the data can be downloaded as application/json;type=geojson, so we can pull vector data from this server! You can download the entire dataset in one go.

BTW: They also provide a tidal current atlas for free! In the webviewer you cannot select the time before/after HW, but if you use QGIS as WMS client, you can explore the datasets and switch between different times.

• https://www.geoseaportal.de/wss/service/Gezeitenstrom_Nordsee/guest
• https://www.geoseaportal.de/wss/service/Gezeitenstrom_Kueste/guest

Netherlands

RWS provides a full ENC with contours and spot soundings for free for some regions of NL like the Waddenzee and Zeeland.

• https://www.vaarweginformatie.nl/frp/main/#/page/infra_enc

Using GDAL the vector data can be extracted from the ENC.

[singlerider]

I wasn't able to find a route to actually download the OSMAnd Nautical Contours data directly from the source code files.

Is the data they supply available at a known route?

My intention is to parse and post-process it for a FOSS game project of mine, assuming the license allows for it. I've looked in other discussions, but this is the closest one I've found so far that may have people that have figured something like this out.

[singlerider]

Funnily, I found this in the LICENSES file right after asking:

https://www.gebco.net/data_and_products/gridded_bathymetry_data/

I can probably parse this for my purposes 👍

[quantenschaum]

depth Tag

Some objects like rocks or wrecks are tagged like depth=2.3. But this information is not displayed on the map, even though the data is compiled into the OBF as text already. It can be enabled by adding

    <case minzoom="10" tag="seamark:type" value="rock" textColor="$depthTextColor" textSize="14" textOrder="128" intersectionMargin="10" textDy="-12"/>
    <case minzoom="10" tag="seamark:type" value="wreck" textColor="$depthTextColor" textSize="14" textOrder="128" intersectionMargin="10" textDy="-10"/>

to the <text> section in the render.xml. The shield of the rock symbol (circle in background) clutters the map, it can be removed by setting shield="null".

The result looks like this, just using the OOTB OFBs provided by OsmAnd.

[quantenschaum]

Spot Soundings

are already supported by the nautical maps plugin. Just enable the "nautical depth" setting in the map config. Numbers will show up on the map for points tagged with

• point=depth
• depth=<value>

IMHO the font size is too small and should be increased/user configurable.

[quantenschaum]

Contour Lines

The contours currently implemented in OsmAnd seem to be a copy of the height contours with some small changes. But depth contours in nav charts are different.

• Navigators are interested in the shallow areas, <10m and need high resolution there. Contours in deep water are nice to have, but no necessary for safe navigation, they might be interesting for fisherman or divers, but high resolution is not required in these areas. Depth contours are like log-scale.
• There are negative depths for drying heights in tidal waters.
• Height and Depth have different reference datum. Depth usually refer to LAT in tidal waters and mean water level in non-tidal waters.
• Depending on the draft of your vessel, one particular depth contour is your "safety contour"

The INT1 section I contains explanations.

Different coloring schemes for the contours are used.

I would propose to only include integer depth levels (meters here, other units are a different thing) and tag the values (if available) <=5, 10, 20, 50, 100 with contourtype=<depth>m. This way you can

• hide/show lines at different zoom levels
• highlight an individual line

Other values may be in the dataset, but are tagged differently.

Currently OsmAnd does not show contours without contourytype tag and no lines <5m.

Tags for contourlines:

• contour=depth
• depth=<value>
• contourtype=<value>m or <interval>i (optional, needed because depth is consumed as text during OBF creation)

This requires not only changing the render.xml but the rendering_types.xml used in the OBF creation also needs to be changed.

[quantenschaum]

Putting it all together, it looks like this.

You want this, too? Have a look at https://github.com/quantenschaum/mapping/blob/master/DEPTH.md

[miramikes]

Excellent... thank you for your work !!!

[miramikes]

Hello,
As I understand the hard part for more depth files is to find a good data source.
Maybe I found some for Norway.
https://kartkatalog.geonorge.no/metadata/depth-curves/871960a1-0f01-4c47-8f79-5d338b65197e

There is a note ...
Use limitations: Not approved for navigation.

But maybe it's worth to try ...
According to this data might be even 5x5m ...
https://www.mareano.no/en/maps-and-data/marine-geospatial-data

Mira

[quantenschaum]

Nice, but it is very coarse. Most shallow contour is at 20m. But I found another dataset on this server, the depth data used in nautical charts.
https://kartkatalog.geonorge.no/metadata/sjoekart-dybdedata/2751aacf-5472-4850-a208-3532a51c529a

[quantenschaum]

I created an OBF for Agder, as proof of concept, and added it to the release. The dataset is quite big.

[miramikes]

Excelent... thank you 👍

[miramikes]

Your release of lightsectors V5 is amazing... the obf file is worldwide or only for some countries?

[miramikes]

Oh 😮 ... many thanks !!!

[andrejmat]

I upload depths data but nothing change, still are wrong in my country (Croatia), wrong by 20-50m on some places. How to solve this? Thanks

[quantenschaum]

I didn't supply any depth data for Croatia.

[andrejmat]

Oh, i read previus post that user "miramikes" ask about that region and i was thinking that is done also, sorry.
I have paper nautucal maps and totaly different depths but match with navionics, dont know from wich database are taken for OsmAnd, thanks for answer.

[quantenschaum]

There are depth data available in OsmAnd for download, but it is totally unclear where they come from and how old and accurate they are. I found them to be very inaccurate, too. They are effectively unusable.

[quantenschaum]

currently there files for download here http://waddenzee.duckdns.org/download/ updated regularly via cronjob

[quantenschaum]

I would like to propose here

1. update the depth data available (for germany I could provide up to date data)
2. change the tagging scheme of depth contours to include smaller values (<5m, these are the important ones)
3. add a tagging scheme for depth contour areas, have a look at http://waddenzee.duckdns.org/download/depth/
4. change the rendering of contours and areas

All of that is already implemented as part of the proposal #16894 (comment)

[josail]

@quantenschaum
I saw some detailed nautical map incl. bathemetry on the east coast of UK close to Hull in one of the online exchanges that I had. If I remember correctly, the information was that data originated from Emodnet. If I search the Emodnet map data viewer, I find that not the whole of UK, but the whole of North Sea including UK coast has "detailed bathemetry data" https://emodnet.ec.europa.eu/geoviewer/#! and can be displayed in the map viewer. So I think this was the source of information.

Emodnet is a European project and European Commission follows Open Accesss strategies and requirements for many of their projects. Thus, there should be a good chance to at least get this UK East coast and complete North Sea data. Find the Emodnet Map Viewer display as attached file.

[josail]

[josail]

See data product with green boundary. Does this lead to appropriate, open access usable data in Emodnet?

[josail]

maybe these links help opening this door?
https://ows.emodnet-bathymetry.eu/
https://emodnet.ec.europa.eu/en/emodnet-web-service-documentation
https://github.com/EMODnet

[quantenschaum]

Thanks. Didn't know that before. I will look into it.

[quantenschaum]

Some datasets are available from https://sextant.ifremer.fr/ like
https://sextant.ifremer.fr/record/SDN_CPRD_1850_UAEms_2015/
Pixel size = 0.00195313 Arc minute = 3.6m

[quantenschaum]

The entire dataset is here https://emodnet.ec.europa.eu/geonetwork/srv/eng/catalog.search#/metadata/ff3aff8a-cff1-44a3-a2c8-1910bf109f85
it can be downloaded from https://erddap.emodnet.eu/erddap/files/bathymetry_2022/ 136GB

Areas not covered by observations are completed by integrating GEBCO 2022 and IBCAO V4

So, it should be possible to extract contours and spot soundings from it.