Advanced parameter settings

When the application is deployed, a certain number of parameters are automatically created and saved in the database, in the gw_parameters table.

To consult the complete list of all the parameters available in the application, please refer to the Administration / Parameters / Advanced parameters.

Generating tiles

Mandatory settings

The following three parameter settings are required for the application to operate correctly:

  • geographics.server.gcisServer: local or url of a distant server, for example: http://my-pc:81/geoconcept-web/gc in the following format http/s://<SERVER/IP>:<PORT>/<APPLICATION>/gc
  • geographics.server.tileServer: /name_of_the_geoconcept_web_portal/maps,
  • geographics.server.mapServer: /name_of_the_geoconcept_web_portal/gcservlet.

Optional parameters

It is possible to edit the number of cores used by the tiling application by editing the “<GEOCONCEPT_WEB_HOME>”\gc\jee\gc\conf\service.xml file

The default value

executor/max-threads = auto

can be modified, for example, as below

executor/max-threads = 2

Activating WMS and WMTS

To authorise the distribution of layers in WMS or WMTS formats, you will need to activate the option. Two methods are possible:

  • Modify the following parameters:

    • services.wms.activate : the value must be set to true,
    • services.wmts.activate: the value must be set to true,
  • Or, activate the parameters via the services control panel. The latter is found under Administration then Tools ▸ Services.
[Note] Note

To consult WMS/WMTS, use the following URLs:

WMS GetCapabilities: http://<server>/geoconcept-web/wms?request=GetCapabilities

WMTS GetCapabilities: http://<server>/geoconcept-web/wmts/1.0.0/WmtsCapabilities.xml

Advanced geocoding

The administration module allows you to define some of the parameter settings for the Geoconcept Web geocoding module via the UGC component.

The parameters involved for the geocoding are as follows:

  • la datasource
  • le nombre de candidats max
  • la note minimale pour présenter un candidat
  • la distance de décalage orthogonale

These parameters are accessible in the global parameter geocoder in the Parameters menu in the Administration tab.

The datasource parameter must have as its assigned value the name of the geocoding referential stored in the “<DATA_HOME>”\data\maps folder.

All the parameters available in UGC are not listed in this administration interface. The file called service.xml serves to modify the parameters for UGC directly. This file is present in your UGC/conf installation directory.

The parameters that can be modified are listed in the section of the Universal Geocoder Server guide called “Fine tuning the datasource configuration”.

To use several referencials geocoding simultaneously consult the World geocoding section.

Advanced autocompletion

Parameters must also be set in the case where an autocomplete web service is used. There are two of these parameters:

  • geocoder.autocomplete.cacheSizeMB: this defines the size of the RAM disk space allocated to ongoing loading of reference files. The memory is therefore in constant use and not available for other applications. 
geocoder.autocomplete.cacheSizeMB=300
  • geocoder.autocomplete.datasource: this defines the directory in which the reference files are stored. Take care to only indicate the hierarchical tree below the autocomp folder. In our example, the value of the parameter is Auto_completion, for the “<DATA_HOME>”\data\maps\autocomp\ folder. 
geocoder.autocomplete.datasource=Auto_completion
[Tip] Tip

The cacheSizeMB parameter allocates a proportion of the RAM to the loading of reference files. The files will be loaded in increasing order (classification 1 first: address.1, then address.2, …). The files in classification 1 contain data that have been chosen as principal data items (Paris, Lyon, Marseille for example). The files are loaded as a function of the size allocated. For example, for the whole of France, loading all the reference files requires an allocation of more than 7 Gbytes of RAM.

To construct the autocompletion files, refer to the generation of autompletion files section.

Advanced route calculation

To use the Geoconcept Web SmartRouting component, you need to specify the name of the graph or network that will be used for route calculation via the SmartRouting component.

Other parameters can be assigned values to refine the utilisation of SmartRouting. Below is a list of modifiable parameters:

  • iti.graphname: mandatory. The network must be stored in “<DATA_HOME>”\data\maps directory,
  • iti.cost: optional: time or distance. This is the route calculation optimisation criterion,
  • iti.jndiName: mandatory. The value is, by default: java:comp/env/geoconcept/smartrouting/default,
  • iti.srsOut: optional. This will be the output coordinates system. The values are WGS 84, MAP (projection system for the map defined in the parameter geographics.map) or the EPSG code.
  • iti.graphSnapDistance: optional (in meters): snap-to-graph distance,
  • iti.graphSnapSpeedMPerS: optional (in meters per second): snap-to-graph speed
  • iti.referenceLevel: optional (integer between 1 and 5): restriction on utilisation of grades of roads,
  • iti.rejectFlags: optional (exclusions separated by commas): list of exclusions on types of routes (example: Toll,Bridge,Pedestrian).
  • iti.useMetaGraph: optional(true or false): utilisation of meta-graphs. The default value is set to false.
  • iti.speedProfile: optional. Speed profile

The graphname parameter must then be completed with the name of the graph to be exploited, with a name that does not have the .siti file extension:

It is also necessary to assign a route calculation method, selecting from the following options:

  • time or 0: the fastest route via the road network (graph),
  • distance or 1: the shortest route via the road network (graph),

To use several graphs simultaneously, consult the Road graphs section.

Adding new widgets

The development of new widgets so they can be integrated within the Composer of the Designer is described in the (cf. Kit de développement) section. The easy.widgets.path parameter (present by default, and its value can be modified) serves to specify the filepath towards the directory in which the new .jar file containing the new widgets will be placed.

Prev  Up  Next
  Home