Analyze Geocode Input

geocodeServiceURL

(Required)

The REST URL of the geocode service that you want to geocode your addresses and places against. The URL must end in geocodeServer . This can be a utility service or a locator that is anonymously accessible. The geocode service must be configured to allow batch geocoding. For more information, see Configure the portal to geocode addresses.

inputTable

(Optional)

Syntax: The input table specification must include the following:

• A URL to an input table
• A service token to access the table

Note that if the table is a hosted table on the same portal, serviceToken is not required.

Example

1
inputTable={"url":"<table url>","serviceToken":"<token>"}

inputFileItem

(Optional)

Syntax: The input file should be a portal item. Input the itemid of the item in the portal. The format of the item in the portal can be in one of the following formats:

• Comma-separated values file (.csv )
• Microsoft Excel worksheets (.xls and .xlsx files)

Example

1
inputFileItem={"itemid":"<itemid of file>"}

columnNames

(Optional)

Instead of providing inputTable or inputFileItem , you can provide columnNames . columnNames is required if there is no header row in the inputTable or inputFileItem . columnNames should be separated by commas.

Example

1
columnNames=address,city,state,zip

inputFileParameters

(Optional)

Enter a JSON that contains information about how to parse the file. If you are using inputTable instead of inputFileItem as input, you can leave this parameter blank. You can leave any of the values in the JSON blank ("") if they do not apply to the file.

Values can be the following:

• fileType —Enter CSV or XLS for the file format of inputFileItem .
• headerRowExists —Enter true if your file has a header row, false if it does not.
• columnDelimiter —Enter SPACE , TAB , COMMA , PIPE , or SEMICOLON .
• textQualifier —Enter either SINGLE_QUOTE or DOUBLE_QUOTE .

Example

1
inputFileParameters={"fileType":"xlsx","headerRowExists":"true","columnDelimiter":"","textQualifier":""}

locale

(Optional)

Enter the two-letter en or four-letter ar-il specific locale if geocodeInput is in a language other than English. For more information about localization and specific language codes, see localization

context

(Optional)

The Context parameter contains the following additional settings that affect task operation:

• Extent (extent)—A bounding box that defines the analysis area. Only input features that intersect the bounding box will be analyzed.
• Output spatial reference (outSR)—The output features will be projected into the output spatial reference.

Syntax:

1
2
3
4
{
  "extent" : {extent},
  "outSR" : {spatial reference}
}

geocodeParameters

geocodeParameters is a JSON that contains information about the file, field info, and a suggested field mapping.

Example

1
{"url": "https://<analysis url>/AnalyzeGeocodeInput/jobs/<jobId>/results/geocodeParameters"}

The result contains the geocodeParameters JSON, which is the first input into the BatchGeocode tool.

1
2
3
4
5
6
7
8
9
10
11
12
13
{
  "paramName": "geocodeParameters",
  "dataType": "GPString",
  "value": {
    "field_info": "[('ObjectID', 'TEXT', 255), ('Address', 'TEXT', 255)]",
    "column_names": "",
    "file_type": "xlsx",
    "column_delimiter": "",
    "text_qualifier": "",
    "field_mapping": "[['ObjectID', 'OBJECTID'], ['Address', 'Address']]",
    "header_row_exists": true
  }
}