Description
Features to KML converts an array of Esri FeatureSets into a KML format. This activity supports point, polyline, and polygon geometry types.
Offline Support
Supported. Please contact us directly to license for offline support and installation instructions.
Example Workflow and Output Files
-
- In Workflow Designer, click File in the sidebar
- Click Open by URL and paste in the following url:
https://www.arcgis.com/home/item.html?id=fecd04e1d02e4a7fa291f98563159abb - To Save, click File in the Workflow Designer sidebar, and click Save.
Inputs
Feature Collection Name
Required
Type: String
The name for the feature collection.
Array of FeatureSets
Required
Type: Object[]
Object Type: esri.FeatureSet
An array of Esri FeatureSets to convert to a KML. The FeatureSets must be in either Web Mercator or WGS84.
Array of FeatureSet Names
Optional
Type: String[]
Array of strings to provide sheet names for the array of Esri FeatureSets input. The order of the string array should match the Esri FeatureSet array.
Outputs
Result
Type: Object
Properties:
Blob: Type: BLOB
Response: Type: Object
A response object containing the file BLOB and a response Object.
Properties
ID
Optional
The activity’s ID, which is used in other activities to access the activity’s output. The ID must be unique across the entire workflow and it’s subworkflows – two activities cannot have the same ID.
You might want to change the ID to shorten it. Shorter IDs make expressions more compact.
Display Name
Optional
The activity’s name in Workflow Designer. The display name appears at the top of the activity on the design surface. The default display name for this activity is Feature to Spreadsheet.
You might want to change the display name to a name that describes what the activity does in the context of your workflow. Description names make workflows easier to understand and maintain.
Description
Optional
A description of what the activity does. The description appears below the activity’s display name.
Use the description to record what the activity does in the context of the workflow. Descriptions make workflows easier to understand and maintain.
