WebOffice URL call interface

WebOffice 10.9 SP1 supports a set of actions and parameters in its URL call interface. The complete list of actions and parameters is provided in the file pub/url-parameters.info as well.

icon_comment

Parameters and values are in general case sensitive. Therefore please check the correct case of your HTTP query string parameters and values.

Values with certain characters like apostrophes, double apostrophes/quotes and various types of parentheses (round/square) are not used in the externalcall.jsp from CSS (Cross Site Scripting). The reason for this is that certain characters are no longer supported for security reasons, so that security gaps can be closed.

Affected special characters, which should be avoided for using in external-ID, are for example: <> ()

Note that whenever you want to pass floating point numbers (extents, x/y coordinates etc) in the call interface, then you need to use . (dot) as comma delimiter. WebOffice 10.9 SP1 parses floating point numbers in mathematical, locale independent way.

 

 

See below for a detailed description off supported actions and parameters.

Action/Parameter

Description

Basic information and project start

project

Specifies the ID of the project (Project ID) to be launched by WebOffice 10.9 SP1 client.

E.g. use

project=WebOffice_SampleProject

for starting the WebOffice 10.9 SP1 Sample Project configuration.

client_app_referer

When calling a project with this parameter, a new entry in the WebOffice 10.9 SP1 statistic file will be done. The value of the parameter will be written into the column APP_REFERER of the statistic file. With this parameter you can get an overview of how many calls to WebOffice from which applications are done.

Example https://<server>/<WebOffice_application>/externalcall.jsp?project=abc&client_app_referer=xyz

Calling this example will write the value xyz into the column APP_REFERER.

icon_comment

When calling a project with client_app_referer=..., also an entry in the column REQUEST will be done. There are two different possibilities:

When calling the project via synserver, PROJECT_START will be written into the column REQUEST.

When calling the project via externalcall.jsp, EXTERNAL_CALL will be written into the column REQUEST. Please consider, that the externalcall.jsp redirects to synserver, so that there will be two entries in the statistic file; one with EXTERNAL_CALL and one with PROJECT_START.

group_id

Holds the ID of the project group whose default project should be started. Project group ID have to be defined in application configuration.

language

Specifies the language to be used in the WebOffice 10.9 SP1 client.

If you e.g. want to start the WebOffice core client in German language then provide the setting language=de. Use language=en if you prefer English.

language=ar for Arabic.

language=bg for Bulgarian.

language=es for Spanish.

language=fa for Farsi.

language=fr for French.

language=hu for Hungarian.

language=it for Italian.

language=ro for Romanian.

language=ru for Russian.

language=sk for Slovak.

language=tr for Turkish.

client

Specifies the client to be used to start the WebOffice 10.9 SP1 application. If the parameter is not used the application will always start with WebOffice core client.

client=core starts with WebOffice core client

client=flex starts with WebOffice flex client

client=mobile starts with WebOffice mobile client

client=auto causes mobile devices to start with WebOffice mobile client, others with the standard desktop client (by default WebOffice core client).

icon_comment

The temporarily available client=coresyn parameter can be used to force against the former WebOffice core client configuration.

The client=auto parameter only works in combination with externalcall.jsp, but not with synserver.

icon_cross-reference

For detailed information how to change the standard desktop client, please see chapter Define the Standard Desktop Client.

skin

Skin to be used in the WebOffice flex client. Possible values are gray, green, brown or blue (that's the default-skin).

E.g. client=flex&skin=green

icon_comment

Parameter applies only to the WebOffice flex client.

icon_cross-reference

See chapter Skins for WebOffice flex for more details.

action

The parameter action=log is logging the client actions which can be displayed by the user using the CTRL+ALT+L shortcut.

icon_comment

Parameter applies only to the WebOffice flex client.

stateID

Loads the saved state specified by stated when launching the WebOffice 10.9 SP1 client. E.g. &stateID=<stateName>

icon_comment

The WebOffice 10.9 SP1 client generates e.g. a state when sending a placed symbol or markup to another user via E-Mail.

userprofile

Loads the specified user profile when launching WebOffice 10.9 SP1 client. userprofile is the name of a saved profile on the server.

startmode

icon_comment

Use externalcall.jsp instead of synserver for passing these parameters.

popup: The WebOffice 10.9 SP1 client starts in a new browser window without browser specific navigation buttons

popupfixed: Equal to startmode=popup, but the browser window is not resizable by the user

winwidth

winheight

The parameters winwidth and winheight specify the width and the height of the popped up browser window in pixels.

icon_comment

These parameters can only be used in combination with startmode=popup/popupfixed.

ribbon

Use this parameter if you want a specific tab to be opened directly in the WebOffice core client.

icon_comment

To use this parameter, an external id for ribbons have to be configured in Ribbons.

If, for example, the external identifier in the WebOffice author standalone Navigation then use: &Ribbon=navigation to have the corresponding tab open.

This configuration parameter is WebOffice core client specific.

maximizemap=true

With the parameter maximizemap=true the WebOffice core client will start with a maximized map, i.e. all ribbons and menus will be collapsed.

icon_comment

This parameter is WebOffice core client specific.

time_slider_profile_id

With the parameter time_slider_profile_id= one of the defined TimeSlider profiles can be preselect.

icon_comment

This parameter is WebOffice core client specific.

statusbar

If the parameter statusbar is passed with false, the WebOffice html client starts without showing the WebOffice statusbar.

icon_comment

This parameter is WebOffice html client specific.

toolbar

If the parameter toolbar is passed with false, the WebOffice html client starts without showing the WebOffice toolbar.

icon_comment

This parameter is WebOffice html client specific.

show_toc

If the parameter show_toc is passed with true, the WebOffice flex client starts with opened TOC.

icon_comment

This parameter is WebOffice flex client specific.

maponly

If the parameter maponly is passed with true, the WebOffice html client starts in a special GUI mode, where only the map is displayed.

icon_comment

This parameter is WebOffice html client specific.

ct

cd

display

These parameters will be used to display custom data from an external application in WebOffice 10.9 SP1 client and on the print output document. This attribute data can come from a third-party application and can be passed via URL call (http POST). Customtitle ct and customdata cd are used as a pair of values, it is possible to use several pairs. It is possible to pass multiple fact records to the URL Call Interface (ct<1>;cd<1> to ct<n>;cd<n>)

ct1=ID; cd1=123;

ct2=name; cd2=Miller;

ct3=city; cd3=Easton;

icon_comment

To use this function, at least one text field pair (ct1 and cd1) must be configured in the print template used. For more information, see the chapter Edit Print Templates.

 

For positioning the iFrame with the custom data in the WebOffice 10.9 SP1 client, use the parameter display:

topleft

topright

bottomleft

bottomright

floating

hidden

floating_minimized

 

icon_comment

In the WebOffice core client, the values topleft|topright|bottomleft|bottomright dock the iFrame in the left area.

The values floating|floating_minimized cause the iFrame to be placed over the map and can be moved.

The value hidden loads the iFrame into the hidden area.

 

The data will be displayed in the WebOffice 10.9 SP1 client in a table with two columns, the first column with customtitle ct and the second one with customdata cd. For values which are too long a line break will be made.

 

icon_comment

An automatic line break is only possible, if the given string allows a line break.

A linebreak in the custom data using \n will be interpreted accordingly in WebOffice 10.9 SP1 client.

 

Example:

https://gisserver/WebOffice/externalcall.jsp?project=WebOffice_SampleProject&ct1=currency&cd1=Schweizer Franken&ct2=GDP per capita&cd2=$ 68.433&ct3=inflation rate (2008)&cd3=0,7 Prozent&ct4=employee (2009)&cd4=ca. 4,53 Mio&display=topright

 

It is also possible to display the custom data on the WebOffice 10.9 SP1 print output document (like address, name of organization) if configured on the print template. See also chapter Custom data display on print template for more information.

Map view and position

view

Sets the initial Map view in the WebOffice 10.9 SP1 client.

icon_comment

The configuration of a map view contains a unique ID (External ID).

For example, if the ID in WebOffice author standalone is citymap, then use view=citymap

basemapview

Sets the initial Basemap view in the WebOffice 10.9 SP1 client.

icon_comment

The configuration of a base view contains a unique identifier (identifier for external call).

 

If e.g. the identifier is configured in the WebOffice author standalone to orthofoto, use: basemapview=orthofoto

geo_bookmark

Use this parameter if you want to display the map at a certain spatial extent.

icon_comment

To use this parameter at least one Geo bookmark has to be configured. (See chapter Geo Bookmark.)

 

If e.g. the identifier in WebOffice author standalone is configured to Vienna, use: geo_bookmark=Vienna

xmin

ymin

xmax

ymax

Use these 4 parameters for specifying the initial map extent

x

Use this parameter to define the center point (X coordinate) for the initialization.

y

Use this parameter to define the center point (Y coordinate) for the initialization.

lat

lon

Starts the application centered on the specified position (WGS84), which is defined by the parameters lat/lon (Decimal degree, separator = .). Works with any project lat/lon are projected from WGS84 into the project coordinate system.

scale

Use this parameter to define the initial scale.

icon_comment

This parameter can only be used in combination with the parameters x and y!

rotation

This parameter is used to make an external project call with map rotation. The value is given in degrees (e.g. &rotation=55)

icon_comment

For an external call this parameter is only considered if the function for map rotation in WebOffice author standalone has been configured and rotation is also allowed via a parameter (see Map Rotation).

width

Width (in pixels) of the map image

height

Height (in pixels) of the map image

dpi

Allows the creation of high quality map images for third applications. By default map images are rendered with a resolution of 96dpi. Increase the value to e.g. dpi=192 or dpi=288 for higher resolution.

icon_comment

If a map image with &dpi=288 is being requested, then the 288dpi image will nevertheless be displayed in 96 dpi. That is why the image size has to be increased as well. - If a map image with &dpi=288 is being requested, then the 288dpi image will nevertheless be displayed in 96 dpi.

exclude_north_and_scale=true

With the parameter exclude_north_and_scale=true only a map image will be displayed. North arrow, scale bar and copyright will be suppressed.

geo_tf

Defines a specific geographic transformation (EPSG code; e.g. geo_tf=1618: MGI to WGS84) to be used to transform geographic coordinates.

icon_comment

EPSG codes can be obtained from the Projection and Geotransformation Helper.

A geographic transformation with the command geo_tf only works for LAT&LON values. It is not possible to use a different transformation than already configured in the project.

coordmarker_lat_lon

Displays an image (by default pub\images\meet_x_20_20.png) to mark the spot which was defined by the specified coordinates (in LAT / LON). Separate the coordinates either with a space character or with %20.

icon_comment

The image can be changed by using the parameter coordmarker_id.

 

Example:

&coordmarker_lat_lon=47.069 15.435

&coordmarker_lat_lon=47.069%2015.435

coordmarker_x_y

Displays an image (by default pub\images\meet_x_20_20.png) to mark the spot which was defined by the specified coordinates (in X / Y). Separate the coordinates either with a space character or with %20.

icon_comment

This parameter can also contain several coordinate pairs separated by semicolons.

Only the first two axes are considered per coordinate pair, additional information such as z- or m-values are discarded.

The sequence X Y is expected for the specified coordinate pairs.

coordmarker_epsg

Optional parameter that must be specified in connection with the parameter coordmarker_x_y if the initial coordinate system (projection of the marker coordinates to be transferred) differs from the target coordinate system (projection of the main map service in the WebOffice 10.9 SP1 project). Otherwise the default value is always the coordinate system of the main map service.

coordmarker_geo_tf

Optional Parameter. Specifies a corresponding transformation code, if the markers should be passed in X/Y coordinates and the initial coordinate system (projection of the marker coordinates to be passed) differs from the target coordinate system (projection of the main map service in the WebOffice 10.9 SP1 project).

icon_comment

The transformation code passed in course of this parameter will not be considered, if a corresponding transformation code has already been configured in the WebOffice 10.9 SP1 project configuration.

The default transformation code proposed and used by ArcGIS will be used, if neither the WebOffice 10.9 SP1 project configuration nor the the appropriate URL contains a corresponding transformation code.

coordmarker_id

Enter the ID which is configured in WebOffice author standalone in Place Symbol as External Marker-ID. This image will be displayed on the spot that was defined in the parameter coordmarker_lat_lon.

marker

If marker=true the project starts with a marker at centerpoint when called in combination with x, y, scale or lat, lon, scale.

service_url

service_type

layer_visibility

Dynamically adds a map service at runtime (call shall be directed to externalcall.jsp, but from there may be redirected to synserver).

The parameter service_url specifies the URL of the map service to be included.

The parameter service_type specifies the type of service to be included (currently WMS for OGC WMS services or AGS for ArcGIS Server Internet Services)

The parameter layer_visibility (on|off) defines the state of layers of the added service; if not provided default = off)

geolocation

If the tool Geolocation is configured in the project, it can be opened via parameter geolocation=false to explicitly not use the geolocation tool.

External queries to WebOffice

query

 

To perform a search in WebOffice 10.9 SP1, this parameter can be passed.

WebOffice 10.9 SP1 then performs the search in the client and displays the results in the search result and on the map.

The parameter query identifies a predefined search (see chapter Query).

icon_comment

In order to use query, keyname and keyvalue parameters, an external layer ID and a search field are required.

 

Search with multiple search fields:
It is also possible to use multiple search fields. For example, if you enter address data with the attribute fields STREET NAME and HNR (=house number), then it is possible to search specifically for STREET NAME AND HOUSE NUMBER (for example, search for the address Down the Road, 1).
This is done by submitting a URL call such as:
https://gisserver/WebOffice/externalcall.jsp?project=WebOffice_SampleProject&client=core&query=address&keyname=STREETNAME&keyvalue=Down the road&query1=address&keyname1=HNR&keyvalue1=1

Using wildcards:
Using the * character it is possible to search for keyvalues with a wildcard. E.g. you can search for every customer starting with M by typing keyvalue=M*.

Multilayer-Search:
Multilayer searches can be performed by repeating the parameters query, keyname and keyvalue and appending a suffix.
You can use any suffix (numbers, letters, etc.) as long as it is associated with query, keyname and keyvalue.

 

icon_comment

Be aware that the WebOffice call using multilayer search is only available in the WebOffice core client because only there is an object browser available that can display multilayer results.

To trigger a multiple hierarchical search pleas see parameter processing.

 

Example:

https://gisserver/WebOffice/externalcall.jsp?project=name&query=queryid_layer1&keyname=field_layer1&keyvalue=value_layer1&query2=queryid_layer2&keyname2=field_layer2&keyvalue2=value_layer2

 

https://gisserver/WebOffice/externalcall.jsp?project=name&query_A=queryid_layer1&keyname_A=field_layer1&keyvalue_A=value_layer1&query_B=queryid_layer2&keyname_B=field_layer2&keyvalue_B=value_layer2

 

 

Geolocator service:
WebOffice 10.9 SP1 supports geolocator queries by using the parameters query and keyvalue. The parameter query contains the value that was assigned in the Geolocator query as External Layer-ID (see chapter Query), keyvalue contains the address for the Geolocator search.
 
Example:
https://gisserver/WebOffice/externalcall.jsp?project=name&query=geoloc&keyvalue=Herrengasse 1, 8010 Graz

keyname

 

Name of the search field

icon_comment

For keyname only use the technical field name but not the alias of the field.

keyvalue

Name of the search value

m_from

m_to

The parameters m_from and m_to are only used for route segment searches in combination with query, keyname and keyvalue. Additionally, it is also possible to define a multiquery on m_from and m_to in order to be able to select multiple sections.

icon_cross-reference

See chapter Layer queries for details.

 

Example:

https://gisserver/WebOffice/externalcall.jsp?project=SampleProject&query=road_routing&keyname=road_code&keyvalue=A23&m_from=13&m_to=18.5

separator

The parameter separator defines the separation between several search values (keyvalue).

icon_comment

The following separators can be used: @ ; - ! ~ / : =

By default, the *;* (semicolon) character is used as a separator.

selection_type

The parameter selection_type defines how the selection is executed:

new|add|subtract

icon_cross-reference

More details about the selection mode in the WebOffice core Client see chapter Select.

gui

The parameter gui defines the display of the result gui:

hideresult displays the attributive result table, but minimizes it to allow a larger map display;

maponly displays the WebOffice GUI in a mode with maximized map display; the attributive result table is minimized, the left and right areas are also minimized

icon_comment

The parameter maponly is only available in the WebOffice html client.

mode

The mode parameter defines the modes for external query calls.

Possible values are:

zoom_to
No attributive result display, features are displayed selected on the map, map zooms to the extent of the queried features

zoomto_minimized
Minimized attributive result display, features are displayed selected on the map, map zoom to the extent of the queried features

icon_comment

The parameter zoomto_minimized is only supported in the WebOffice mobile client.

zoom_only
No attributive result display, no selection of queried features on the map, map zooms to extent ob the queried features

result_only
Attributive result display only, no selection of queried features on the map, no map update

pan_only
No attributive result display, no selection of queried features on the map, map pans to center of the extent ob the queried features

locate_features
No attributive result display, no selection of queried features on the map, no map update but the position of each feature in the current map extent is displayed for a few seconds using images

clear_selected
Clears current selection, removes attributive result display, removes selection displayed on the map

processing

The parameter processing defines the processing of several queries, which are identified by keyname, keyvalue, ... the following parameters are specified:

combined (default value)
Multiple queries are merged into a minimum number of statements (implicit AND).

separated
A separate statement is created for each URL query (implicit OR). By specifying &processing=separated, multiple hierarchical searches can be triggered and displayed via the URL call interface.

 

Example:

https://gisserver/WebOffice/externalcall.jsp?

query1=searchlyr&keyname1=city&keyvalue1=Chicago&keyname1=zone&keyvalue1=890&query2=searchlyr&keyname2=city&keyvalue2=Dallas&keyname2=zone&keyvalue2=890;891&processing=separated

icon_comment

Values separated by ; are connected by OR.

 

The parameter &processing=separated means that query1 is executed before query2(internal): query1=searchlyr&keyname1=city&keyvalue1=Chicago&keyname1=zone&keyvalue1=890, then:

query2=searchlyr&keyname2=city&keyvalue2=Dallas&keyname2=zone&keyvalue2=890;891

The results will be connected by OR. All conditions with the same number (1,2) will (internal) be connected by AND.

query_preset

Specifies the default layer or query to be used.

icon_comment

Use the External call ID of the Query.

External filter definition to WebOffice

filter

 

 

Defines the external call ID of the layer

icon_comment

External filter calls are only enabled if a External filter is configured on the specified layer.

 

A combination of multilayer filters is allowed, following the same rules as multilayer queries.

icon_cross-reference

See multilayer queries for details and samples.

 

A combination of query and filter is allowed, following the same rules as multilayer queries.

Example:

https://gisserver/WebOffice/externalcall.jsp?query=queryid_layer1&keyname=field_layer1&keyvalue=value_layer1&filter2=queryid_layer2&keyname2=field_layer2&keyvalue2=value_layer2

keyname

Name of the search field (database field name, not the configured WebOffice alias)

keyvalue

Name of the search value

query_filtered

The parameter query_filtered offers the possibility to combine a query and a filter on a layer with the same parameters.

 

Sample long form:

https://gisserver/WebOffice/externalcall.jsp?query=queryid_layer1&keyname=field_layer1&keyvalue=value_layer1&filter2=queryid_layer1&keyname2=field_layer1&keyvalue2=value_layer1

 

Sample short form:

https://gisserver/WebOffice/externalcall.jsp?query_filtered=queryid_layer1&keyname=field_layer1&keyvalue=value_layer1

 

icon_comment

In case of using this parameter please also configure an External Filter and a Filtering search.

resetfilter

Defines the external ID for the layer (resets a set filter to the layers).

Starting WebOffice with a predefined active tool

tool

Use the tool parameter for setting a specific tool active.

icon_comment

To call a tool using the URL call interface, an external tool ID must be assigned to the corresponding tool in the project configuration.

It is not useful nor possible to activate all of tools using the URL call interface. WebOffice 10.9 SP1 supports certain tools for calling via the URL call interface.

Besides default tools, Custom tools can also be called directly at project start this way.

 

Below is a list of all tool identifiers that are supported:

EDIT
Opens the tool Editing

icon_comment

For more details regarding the parameter tool=edit see WebOffice URL Call Interface for Editing.

HELP
Opens the tool Help

IDENTIFY_LAYER
Opens the tool Identify

IDENTIFY_MAPTIP
Opens the tool Identify MapTip

LABEL
Opens the tool Label feature

MARKUP
Opens the tool Markup

MEASURE_ARCLENGTH
Opens the tool Measure Arc/Length

MEASURE_AREA
Opens the tool Measure Area

MEASURE_LINE
Opens the tool Measure Distance

MEASURE_PERPENDICULAR
Opens the tool Measure Perpendicular

MEASURE_POINT
Opens the tool Measure Point

PRINT
Opens the tool Print

RASTERINFO
Opens the tool Raster Info

UPLOAD_GEODATA
Opens the tool Add Data

Start WebOffice with predefined print tool

tool=print

Opens the tool Printing (Legacy) on project start up.

icon_comment

VertiGIS Printing is not supported in this case.

template_id

This parameter applies only to the Printing (Legacy) tool tool=print

The parameter template_id can be used to preselect a specific print template. The external template ID has to be used, which is configured directly at the respective print template in WebOffice author standalone.woas_print_Template_File_Name

 

Example:

https://gisserver/WebOffice/externalcall.jsp?project=WebOffice_SampleProject&client=core&tool=print&template_id=A3portrait&printfields=Referenznummer;Projektname;orgadr_value&printvalues=1234;Test-Projekt;Technologiestrasse 10

printfields

This parameter applies only to the printing (Legacy) tool tool=print and has to be used with the parameters template_id and printfvalues.

You can use the parameter printfields to pass the ID of field value/caption of printing fields and custom function fields (separated by semicolons if several values are used).

 

Example:

https://gisserver/WebOffice/externalcall.jsp?project=WebOffice_SampleProject&client=core&tool=print&template_id=A3portrait&printfields=Referenznummer;Projektname;orgadr_value&printvalues=1234;Test-Projekt;Technologiestrasse 10

printvalues

This parameter applies only to the printing (Legacy) tool tool=print and has to be used with the parameters template_id and printfields.

You can use the parameter printvalues to pass the values for Field value and Field caption of printing fields and custom function fields (separated by semicolons if several values are used)

 

Example:

https://gisserver/WebOffice/externalcall.jsp?project=WebOffice_SampleProject&client=core&tool=print&template_id=A3portrait&printfields=Referenznummer;Projektname;orgadr_value&printvalues=1234;Test-Projekt;Technologiestrasse 10

Start WebOffice with predefined layer activation

map_layers_visibility

This parameter is used to activate topics in the table of contents (TOC) via URL call interface.

Format: "<extcallid>:<ON|OFF>"

":ON" can be left out, i.e. "<extcallid>" is equivalent to "<extcallid>:ON"

Several configurations can be combined with ";"

 

The configured external identifier "extcallid" in "Search/query on layer (LAYERLIST)" -> "ArcGIS Layer (LAYER)" -> "Search/query (QUERY)" is used as extcallid. The layer that is defined as parent node "LAYER" is switched. Only searches are used for which the current user has permissions.

 

icon_comment

The ";" and ":" characters must be avoided in an extcallid if it is to be used for layer switching via the map_layers_visibility parameter.

 

This parameter is used both initially and for external calls to an existing session. Only the specified layers in the current TOC are switched. All other layers remain unchanged

 

If this URL parameter is used, the "<User defined>" entry is selected in the "Map View" dropdown. This also happens if a specific map view was also defined at the start of the project, as the switching of the theme tree differs from the original configuration of the map view.

 

Only individual themes can be activated, not theme groups or services. If the activated theme is in a group or service that is not set as visible, the theme is not displayed on the map view. This is consistent with the behavior when the corresponding box is activated by the end user with the mouse instead of via the URL parameter.

 

In order to be able to show nested layers via the URL parameter, it is recommended to use a map view in which all services and theme groups are already active.

 

Example:https://gisserver/WebOffice/externalcall.jsp?project=name&map_layers_visibility=emergency:OFF;poi:ON

Start WebOffice with predefined Concentric Circles

concentric_circle_radius

The radius must be specified in double values in meters (e.g. 2, 5, 10).

concentric_circle_rings

This parameter can be used to control the number of inner circles. This configuration is optional.

Only the following values are permitted: 1, 2, 3, 4, 5, 6, 8, 10, 15, 20

 

The default value is 3.

concentric_circle_label

This parameter controls whether the circles are to be labeled (true or false). The configuration is optional.

 

By default value true is defined here.

concentric_circle_crosshair

This parameter controls the crosshairs. Here you can choose between NONE, FOUR or EIGHT. The configuration is optional.

 

The default value is EIGHT.

concentric_circle_x_y

This parameter is optional. The position of the surrounding circle in X and Y coordinates can be determined here using double values.

 

By default, the center of the screen is used for positioning.

concentric_circle_epsg

This parameter is optional. This configuration can be used to define the EPSG code or a WKT (Well-Known-Text) to display the surrounding circle.

 

By default, the projection of the main map service is used here.

concentric_circle_geo_tf

This parameter is optional. This configuration can be used to define the EPSG code or a WKT (Well-Known-Text) to display the surrounding area.

 

No transformation is used here by default.

concentric_circle_id

This is also an optional configuration. The external call ID of a marking style can be specified here.

 

No predefined style is specified here by default.

 

 

icon_comment

Please note that in a WebOffice session the definition of several concentric circles can be defined via URL parameters with a parameter postfix 0...n.

 

Example:

concentric_circle_radius_1, concentric_circle_radius_two, concentric_circle_radius_station

WebOffice 10.9 SP1 URL call interface - actions and parameters

 

To get an impression of how to use the WebOffice URL Call interface and to have a test possibility for the calls, VertiGIS provides a test page for external calls (WebOffice - External call generator and test utility from file testextcall.htm) to view and test the functionality.

Call them with https://myserver.domain.com//testextcall.htm or in the WebOffice administration page (SynAdmin) in the area Application (Test page for external calls).

 

Test page for external calls

Test page for external calls