Configuring traffic transfer service provider

SuperMap iServer supports the following types of traffic transfer service providers:

• • Configuring local traffic transfer service provider
  • Configuring REST traffic transfer service provider

Configuring local traffic transfer service provider

Configure a UGC traffic transfer service provider as illustrated below:

<provider name="trafficTransferAnalystProvider-Changchun" class="com.supermap.services.providers.UGCTrafficTransferAnalystProvider"> 
  <config class="com.supermap.services.providers.TrafficTransferAnalystSetting"> 
        <name>Traffic-Changchun</name>  
        <workspaceConnectString>../../samples/data/NetworkAnalyst/Changchun.sxwu</workspaceConnectString>
        <transferLineSetting>
                <datasourceName>Changchun</datasourceName>
                <datasetName>BusLine</datasetName>
                <lineIDField>LineID</lineIDField>
                <nameField>Name</nameField>
                <lineTypeField>LineType</lineTypeField>
        </transferLineSetting>
        <transferStopSetting>
                <datasourceName>Changchun</datasourceName>
                <datasetName>BusPoint</datasetName>
                <stopIDField>StopID</stopIDField>
                <nameField>Name</nameField>
        </transferStopSetting>  
        <transferRelationSetting>
                <datasourceName>Changchun</datasourceName>
                <datasetName>LineStopRelation</datasetName>
                <lineIDField>LineID</lineIDField>
                <stopIDField>StopID</stopIDField>
                                <datasetNetworkName>RoadNet</datasetNetworkName>
                                <edgeIDField>SmEdgeID</edgeIDField>
                                <nodeIDField>SmNodeID</nodeIDField>
                                <fNodeIDField>SmFNode</fNodeIDField>
                                <tNodeIDField>SmTNode</tNodeIDField>
        </transferRelationSetting>
        <mergeTolerance>100.0</mergeTolerance>
        <snapTolerance>50.0</snapTolerance>
        <walkingTolerance>1000.0</walkingTolerance>
        <unit>METER</unit>
  </config> 
</provider>

Where <transferLineSetting/> and <transferStopSetting/> correspond to the transfer line and transfer stop settings respectively. <transferRelationSetting/> specifies the relation between the transfer lines and transfer stops.

• <transferLineSetting/>: Parameters include <datasourceName>, <datasetName>, <lineIDField>, <nameField> etc.

• <transferStopSetting/>: Parameters include <datasourceName>, <datasetName>, <stopIDField>, <nameField>, etc.

• <transferRelationSetting/>: Parameters include <datasourceName>, <datasetName>, <stopIDField>, <lineIDField>, etc.

• <workspaceConnectString>: The path of the workspace used by the service provider. In addition, the workspace path supports reading from environment variables and system configuration files. It can be written as:

• <workspaceConnectString>${datapath1}/World.sxwu</workspaceConnectString> 
  

  For details, see: Presetting local workspace path

For parameter types, please refer to TrafficTransferAnalystSetting. For parameter introduction, please refer to Configuring Traffic Transfer Service Provider.

Configuring REST traffic transfer service provider

Configure a REST traffic transfer service provider as illustrated below:

<!--  REST traffic transfer service provider-->
<provider class="com.supermap.services.providers.RestTrafficTransferAnalystProvider" name="restSpatialProvider"> 
        <config class="com.supermap.services.providers.RestTrafficTransferAnalystProviderSetting">
                <restServiceRootURL>http://localhost:8090/iserver/services/traffictransferanalyst-sample/rest</restServiceRootURL>
                <restProviderCacheConfig>
                        <maxElementsInMemory>1</maxElementsInMemory>
                        <maxSizeOnDisk>2048</maxSizeOnDisk>
                        <timeToLiveSeconds>0</timeToLiveSeconds>
                        <timeToIdleSeconds>0</timeToIdleSeconds>
                </restProviderCacheConfig>
                <useCache>true</useCache>
        </config>
</provider> 

Where the class of <provider> identifies the implementation class of the REST traffic transfer service provider, the class of <config> identifies the RestTrafficTransferAnalystProviderSetting, and the content of <config> is its corresponding configuring items:

• <restServiceRootURL>: REST traffic transfer service address, pointing at the root resource path, such as http://localhost:8090/iserver/services/traffictransferanalyst-sample/rest.
• <useCache>: Whether to use caches. Default is true. After opening the REST cache, the REST request to the resource will be cached locally. For the later same requests will be read directly in the cache.
• <restProviderCacheConfig>: The storage settings about the historical request cache of the provider in the memory, including
• <maxElementsInMemory>: The maximum of records in the memory. 0 denotes unlimited; 1 denotes not to use the cache of the memory. Default is 1. If not 1, then the request will be stored in the memory in precedence.
• <maxSizeOnDisk>: The maximum capacity of the disk. Unit is MB, and default is 2048MB.
• <timeToLiveSeconds>:Sets the upper limit for the survival of the cache, beginning at the creation of the record. The cache is automatically removed after the limit. Unit is second. Default is 0, denoting permanent survival.
• <timeToIdleSeconds>:Sets the upper limit for the idle time of the cache, beginning at the last visit. The cache is automatically removed after the limit. Unit is second. Default is 0, denoting permanent survival.
• <token>: When enabling the security mechanism, visiting the protected REST resource needs to provide Token .