Coordinate systems

The coordinate system section of the ServerConfiguration.xml supports for following coordinate systems:

• WGS 84
• WGS 84 Web Mercator Auxiliary Sphere—default setting for the system
• WGS 84 World Mercator
• Amersfoort / RD New

Here are other things to consider:

• The newly created .senc file will contain the set CoordinateSystem value in the name.
• To change projections you must modify the CoordinateSystem value, which is defaulted to 102100.
• S-57 datasets that fall outside the coordinate system boundary will not be generated and a warning message will be written to the log file.

DisplayParameters

These settings allow an administrator to optimize their display based on the S-57 datasets they are required to host. Normally these settings are not modified but allow for fine tuning.

<DisplayParameters>
<Chart minZoom=".05" maxZoom="1.2"/>
<Symbol scaleFactor="1.0" minZoom=".05" maxZoom="1.2"/>
<Line scaleFactor="1.0" minZoom=".05" maxZoom="1.2"/>
<Area scaleFactor="1.0" minZoom=".05" maxZoom="1.2"/>
<Text scaleFactor="1.0" minZoom=".05" maxZoom="1.2" removeDuplicateText="true" halo="on"/>
</DisplayParameters>

AutoCellUpdate

AutoCellUpdate allows you to automatically apply dataset changes without having to stop and restart the service. This feature will allow you to configure 24/7 support. By default, the Maritime Chart Service gets installed with this setting turned off. Before turning this setting on, you will need to understand how long it takes to copy a 5 MB file across your network and what your dataset update strategy is.

Once the AutoCellUpdate property is enabled by setting use="true", the Maritime Chart Service will detect if there are any changes to your datasets folder. Once a modification is detected, the same logic that is used when the service is started is run against the datasets folder. This will detect what dataset changes have occurred and update the service’s .senc and find.dat files, accordingly, while the service is still running. Users will only notice the change when the display is refreshed or search or identify is used on the dataset that is actively being processed.

The delaySeconds setting sets how long the Maritime Chart Service will wait before running its logic. For example, if set to 10 seconds, the Maritime Chart Service, once it detects a change to the datasets folder, will wait to run its logic for another 10 seconds. If another change is detected before it counts to 10, it will start counting over. Once it reaches the delaySeconds count value, it will process the changes. Each file that is copied to the datasets folder counts as a change. That means if you copy, for example, 10 files at once, each file as it is copied restarts the count.

If you do not set a large enough delaySeconds value and your dataset file takes longer than the setting to copy, Maritime Chart Service will not be able to process that dataset. This is no different than if you tried to manually start the map service before you finished copying data into the datasets folder. It is recommended that you set your delaySeconds value by at least a factor of 3 based on how long it takes to copy a single 5 MB .000 file into the datasets folder from your staging location.

Display parameters

There are various S-52 and server-based parameters that the client application can pass to the service, which allows the display to be modified independently by each client request. By default, when the service is started, the settings in S52DisplayProperties.xml will be used. The sample application will display those values to the user and provide additional values to be set that can also be found in the S52DisplayProperties.xml.

• Shallow Contour
• Safety Contour
• Deep Contour
• Color Scheme
• Depth Units
• Depth Shades
• Shallow Patterns
• Point Symbolization
• Area Symbolization
• Display Cell Extents: This setting is not currently part of the S52DisplayProperties.xml
• Honor SCAMIN
• Display National Object Names

Here is an example of what gets passed to the service by the client.

{"ECDISParameters":{"version":"1.0","StaticParameters":{"Parameter":[{"name":"AreaSymbolizationType","value":2},{"name":"PointSymbolizationType","value":2}]},"DynamicParameters":{"Parameter":[{"name":"ColorScheme","value":1},{"name":"DisplayDepthUnits","value":1},{"name":"TwoDepthShades","value":1},{"name":"DisplayNOBJNM","value":2},{"name":"HonorScamin","value":2},{"name":"ShallowDepthPattern","value":1},{"name":"ShallowContour","value":2},{"name":"SafetyContour","value":10},{"name":"DeepContour","value":30},{"name":"DisplayCategory","value":"1,2,4"}]}}}

Text groups

By default, all text groups associated with S-57 objects are turned on. These groups can be turned off by the administrator and cannot be overridden by the client.

View Over Groups

The S52DisplayProperties.xml comes with various samples of how to configure different feature layers within your service layer. By default, the ParameterGroup name ViewOverGroups will be used. You must make sure all other samples have a different name.

The concept of view over groups comes directly from S-52 and can be configured and extended just like S-52 can be configured and extended.

<ParameterGroup name="ViewOverGroups" deafultVisibility="false">
	<ViewoverGroupsDescription>This example includes all view groups into 8 feature layers</Description>
	<Parameter name="0" type="E" default="2" range="11000-11060,21010-21060,31000-31080">
		<Description>Information about the chart display</Description>
		<ExpectedInput code="1" value="False"/>
		<ExpectedInput code="2" value="True"/>
	<Parameter>

Viewing group descriptions (View Group)

According to S-52, S-57 Objects are grouped into View Groups. The View Group IDs are what your ViewOverGroups range values are set to. These View Group IDs are related to entries in your .dic files.

The .dic files, which are located with the rest of your control files, are part of the S-52 Standard and control how features are displayed. These view groups can be configured as much as necessary to create OverViewGroup feature layers for your service.

For example, the ViewGroup for beacon contains 5 individual S-57 Objects, but they are all controlled by one ViewGroup.

<ViewGroup id="17020" Description="beacon"/>
	<ViewGroupS57Objects Code="" Acronym="BCNCAR" Description="" Dictionary="psymrefs" Comments=""/>
	<ViewGroupS57Objects Code="" Acronym="BCNISD" Description="" Dictionary="psymrefs" Comments=""/>
	<ViewGroupS57Objects Code="" Acronym="BCNLAT" Description="" Dictionary="psymrefs" Comments=""/>
	<ViewGroupS57Objects Code="" Acronym="BCNSAW" Description="" Dictionary="psymrefs" Comments=""/>
	<ViewGroupS57Objects Code="" Acronym="BCNSSP" Description="" Dictionary="psymrefs" Comments=""/>

If you want to be able to turn on or off each beacon type individually, you would have to create new ViewGroups for each beacon type and modify your associated .dic files.