selfserviceoperationgeocoding
This configuration is required when using the plugin Geocoder.
-
Documentation
-
YAML Format
-
XML Format
| Fill relevant inputs (blue boxes) and click the blue bars on the left to copy XML configuration snippets. |
Id of a geocodingService that will be used for geocoding address data. The geocodingService should be configured for the application and must support the structured or unstructured request type respectively.
Batch size for the geocoding, at most this many addresses will be sent to the geocoder at once for geocoding using this geocoder. Explicit batching for geocoding is disabled for non positive values. Note: This setting is not identical to the number of addresses that can be processed in a single geocoding operation (see element geocodingLimit).
Default: 100
Id of a geocodingService that will be used for geocoding address data. The geocodingService should be configured for the application and must support the structured or unstructured request type respectively.
Batch size for the geocoding, at most this many addresses will be sent to the geocoder at once for geocoding using this geocoder. Explicit batching for geocoding is disabled for non positive values. Note: This setting is not identical to the number of addresses that can be processed in a single geocoding operation (see element geocodingLimit).
Default: 100
Maximum number of addresses that can be processed in the same geocoding operation. If the source data contains more addresses, a corresponding message is displayed, and the user can cancel the operation if necessary. Note: This setting is not identical to the number of addresses sent to the geocoding service at the same time (see attribute 'batchSize' in structuredGeocodingServiceId or unstructuredGeocodingServiceId).
Default: 10000
Potential address columns of the data to be geocoded and their assignment to the input fields for the spatial reference in the geocoding dialog: Within predefined elements such as for the fields of the dialog, typical column names can be specified using elements. If these are present in the address data, they are automatically preset in the dialog.
| This is a generated sample file with fake data and all the possible options shown, refer to the Documentation tab for what combinations are valid and what is required or not. |
cadenzaconfig:
settings:
selfserviceoperationgeocoding:
geocodingServices:
structuredGeocodingService:
id: "text"
batchSize: 15
unstructuredGeocodingService:
id: "text"
batchSize: 15
geocodingLimit: 15
attributeMappings:
country:
- "text"
- "text"
federalState:
- "text"
- "text"
countrySecondarySubdivision:
- "text"
- "text"
zipCode:
- "text"
- "text"
city:
- "text"
- "text"
cityDistrict:
- "text"
- "text"
street:
- "text"
- "text"
streetNumber:
- "text"
- "text"
streetNumberSuffix:
- "text"
- "text"
freeFormAddress:
- "text"
- "text"
Filename: selfserviceoperationgeocoding-config.xml
| This is a generated sample file with fake data and all the possible options shown, refer to the Documentation tab for what combinations are valid and what is required or not. |
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<operationGeocoding>
<geocodingServices>
<structuredGeocodingService id="text" batchSize="15"/>
<unstructuredGeocodingService id="text" batchSize="15"/>
</geocodingServices>
<geocodingLimit>15</geocodingLimit>
<attributeMappings>
<country>
<attributeName>text</attributeName>
<attributeName>text</attributeName>
</country>
<federalState>
<attributeName>text</attributeName>
<attributeName>text</attributeName>
</federalState>
<countrySecondarySubdivision>
<attributeName>text</attributeName>
<attributeName>text</attributeName>
</countrySecondarySubdivision>
<zipCode>
<attributeName>text</attributeName>
<attributeName>text</attributeName>
</zipCode>
<city>
<attributeName>text</attributeName>
<attributeName>text</attributeName>
</city>
<cityDistrict>
<attributeName>text</attributeName>
<attributeName>text</attributeName>
</cityDistrict>
<street>
<attributeName>text</attributeName>
<attributeName>text</attributeName>
</street>
<streetNumber>
<attributeName>text</attributeName>
<attributeName>text</attributeName>
</streetNumber>
<streetNumberSuffix>
<attributeName>text</attributeName>
<attributeName>text</attributeName>
</streetNumberSuffix>
<freeFormAddress>
<attributeName>text</attributeName>
<attributeName>text</attributeName>
</freeFormAddress>
</attributeMappings>
</operationGeocoding>