This project allows you to convert nautical dataset and display it with Mapserver. It include all utilities to convert data from S57 to a shapefiles and to create mapfiles for a Mapserver WMS service. This package uses the a python script and bash scripts to build a complete mapfiles from a set of templates and styling information to enable display of nautical data in the format S57.
The package enables mapserver to display nautical charts in different color modes and with alternative color tables. Currently only simplified S52 symbology is carried out. But future plans are to include paper chart symbology as a separate style. The package also contains tools to create AML mapfiles for Mapserver.
The data handling is carried out with the OGR package. For performance reasons all S57 data is converted into shape format and every object type is split into separate files. Separate files are also created for point, line and polygon features
Furhter on a tool is provided to process tiff files and create mapfiles automaticly.
- Your own S-57 dataset source files
- XMLStarlet (to create color tables)
- ImageMagic (to create symbolset files)
- GDAL/OGR (to convert S-57 source dataset)
- Running Linux OS (Ubuntu 16.04 / Debian 8 tested)
- Up to date GDAL/OGR S-57 metadata
GDAL/OGR used OpenCPN configuration file to read and extract data from S-57 dataset. If you don't have up to date metadata file on your system, you will be unable to read all the data available in S-57 dataset. You have to make sure to update those files on your system to make run properly data converter script. In S-57 OGR driver documentation said: The S-57 reader depends on having two supporting files, s57objectclasses.csv, and s57attributes.csv available at runtime in order to translate features in an object class specific manner. These should be in the directory pointed to by the environment variable S57_CSV, or in the current working directory
For your setup and future usage, be sure to find GDAL/OGR S-57 configuration file, and update them like this:
$ ogrinfo --version
GDAL 2.2.2, released ...
$ find / -name s57objectclasses_iw.csv
/usr/share/gdal/2.2/s57objectclasses_iw.csv
$ wget https://raw.githubusercontent.com/OpenCPN/OpenCPN/master/data/s57data/s57objectclasses.csv
$ wget https://raw.githubusercontent.com/OpenCPN/OpenCPN/master/data/s57data/s57attributes.csv
$ cp s57objectclasses.csv /usr/share/gdal/2.2/s57objectclasses_iw.csv
$ cp s57attributes.csv /usr/share/gdal/2.2/
You can test your setup by using ogrinfo and other ogr2ogr tools with S57 profile like this:
ogrinfo --config S57_PROFILE iw -ro CA479099.000 | grep "SLOTOP"
Or add extra OGR environment variable on your system
export S57_PROFILE
To process sound depth points properly and other Multipoint dataset, you have to set OGR environment variable on your system
export OGR_S57_OPTIONS=SPLIT_MULTIPOINT=ON,ADD_SOUNDG_DEPTH=ON
There's two way to convert data in project. The first one convert all the requierded data for the basic map and the second one is needed when you want create a map service based on OpenCPN lookup table.
Create a folder that contains all your S-57 files and run the conversion script by specifying input S-57 dataset files and output shapefiles
cd chart-installation/data_files_conversion
python ./S57_to_Shape.py [ENC_ROOT] [output_path]
This script will build all data needed for enhance nautical charts map service based on OpenCPN configuration file and support light sectors layers. This script will create shapefiles based on data configuration from OpenCPN project (s57objectclasses.csv and s57attributes.csv). The script will create shapefile for S-57 object ONLY if data is found in your source files.
cd chart-installation/data_files_conversion/shp_s57data
bash generateShapefiles.sh [ENC_ROOT] [output_path]
This project will automatically create lights sector shapefiles based on LIGHTS dataset create by enhance data process.
In case you need to update Lights sector or change the default radius, you can simply run this script:
cd chart-installation/data_files_conversion/shp_s57data
python generate_light_sector.py [input_lights_shp_path] [radius]
# NOTE 1: input shapefile must be named as *_LIGHTS_*.shp
# NOTE 2: if radius = valmnr keyword, distance will be take from data
Working with enhanced data allows to create mapfiles from the chartsymbols.xml file. This file contains all the specification of all symbols of the IENC symbology and is provided by OpenCPN. The file provided by OpenCPN does contains a few errors or limitation that are not currently handled.
- Only point layers are created from the chartsymbols.xml file. Line and polygon layers are still generated from template mapfile.
- The layer order is only managed at type levels. Points are on top, followed by lines and then polygons. The layers of each types are added to the map in pseudo random order.
- The data files contain a MinScale / MaxScale information and this is not directly used. We currently separate in only 6 levels:
- 2000000
- 600000
- 150000
- 50000
- 25000
- Symbology is created from SY, TE and TX instruction. Basic CS(LIGHTSxx) support have been added, but is not complete. Other CS code are not supported yet.
- Symbols in MapServer are anchored to the map in the center vs in the top-left corner for OpenCPN. This brings a disparity in the symbol placement when they are stacked together.
- Current implementation stack levels as you zoom in so you get level 1 features and labels in level 2 maps.
- Symbology can be created from vector and bitmaps. We are only supporting bitmap symbology.
- TOWERSxx symbols are present twice in the chartsymbols.xml. We only use the second one.
- SOUNDG labels are set with FORCE TRUE. This make to many appear in the map at small scale.
- Some text layers (SBDARE) contain numeric values that must be transformed to string.
- Some layers are exported as LINE instead of POLYGON
- Some layers defined in the chartsymbols.xml are pointing to non-existing data columns:
- BCNSPP layer (lookup #1781) uses BOYSHP == 1 Expression, but this field is not present. We replaced it by BCNDHP == 1.
- BCNSPP layer (lookup #1784) uses CATLAM == 1 Expression, but this field is not present. We replaced it by CATSPM == 1.
- RADSTA layer (lookup #1222, #2340) uses COMCHA field for label, but this field is not present. We replaced it by OBJNAM.
- RDOSTA layer (lookup #2350) uses DGPS field for label, but this field is not present. We replaced it by OBJNAM.
- TOPMAR layer uses OBJNAM field for label, but this field is not present
- SOUNDG layer is in display-cat Other, it has been transfered to Standard
To create symbolset used by generated mapfile, we used source files download from s57data directory of OpenCPN Repository.
Need to download latest version of source files. Up to datThose files
cd chart-installation/generate_map_files/scripts/
python ./generate_symbolset.py update
Create symbolset mapfile and generate all png image symbols.
python ./generate_symbolset.py [day|dusk|dark] [output_path]
Display all available options with help switch
python ./generate_map_config.py -h --- shows all options
Specify rules directory and shapefiles source directory. The mapfiles are placed in /data/Chart_dir along with the converted data.
python ./generate_map_config.py -rules ../resources/layer_rules/rules/ -basechartdata /data/Chart_dir
To build mapfiles for enhanced nautical chart map services based on OpenCPN lookup table, we have to specify the chartsymbols file, the enhance shapefiles path, the graphics style(tablename: Paper|Simplify) and choose the display category (dedault is Displaybase,Standard, All display category is still not supported). This script will create mapfile based on data found into enhancedchartdata. If you update your enhance data repository you should run again this script to update your map service.
python ./generate_map_config.py -rule-default-color IHO --chartsymbols ./chartsymbols_S57.xml -enhancedchartdata ./shp_s57data/shp --tablename Paper --displaycategory Standard --rule-set-path ../resources/layer_rules/rules/
NOTE 1: The output mapfile directory will be saved in map folder under shapefiles directory. In this example, mapfiles will be saved in ./shp_s57data/map
NOTE 2: Please used chartsymbols_S57.xml file locates in the scripts directory. This file has been modified to fix some issues found in original OpenCPN chartsymbols file.
Then You should be able to test the configuration in the built in open layers viewer with:
NOTE: You should adjust to EPSG:3857 and a suitable BBOX for your data.
IENC (S-57) data is compiled for a variety of navigational purposes. This project is built to mainely support all of them. First version will support the first 6 navigation purpose. At the end, all of thos levels will be converte to mapfiles.
- 1 - Overview - For route planning and oceanic crossing.
- 2 - General - For navigating oceans, approaching coasts and route planning.
- 3 - Coastal - For navigating along the coastline, either inshore or offshore.
- 4 - Approach - Navigating the approaches to ports or mayor channels or through intricate or congested waters.
- 5 - Harbour - Navigating within ports, harbours, bays, rivers and canals, for anchorages.
- 6 - Berthing - Detailed data to aid berthing.
The following directory structure is mandatory. On each volume within an exchange set there must be a root directory called ENC_ROOT. Data is publish throught .000 source file and data update are store into .001, .002 and so on. OGR2OGR software is able to read all this data.
NL600021.000
NL600021.001
NL600021.002
A valid data set file must be uniquely identified world wide by its name. The data set files are named according to the specifications given below:
CCPRRRRR.EEE
| | | |
| | | |------------ EEE = update number
| | |
| | |----------------- RRRRR = waterway code and waterway distance (kilometre) or
| | identification of the equivalent paper chart number
| |
| |------------------- P = navigational purpose
|
|--------------------- CC = producer code