Copy To Data Store takes an input layer and copies it to a data store. Data is copied to ArcGIS Data Store and is stored in your relational or spatiotemporal data store.
For example, you could copy features that are stored in a big data file share to a relational data store and specify that only features within the current map extent be copied. This would create a hosted feature service with only those features that were within the specified map extent.
The layer or table that will be copied.
Syntax: As described in detail in the Feature input topic, this parameter can be one of the following:
REST web example:
REST scripting example:
The task will create a feature service of the results. You define the name of the service.
REST web example: myOutput
REST scripting example: "outputName" : "myOutput"
Context contains additional settings that affect task execution. For this task, there are four settings:
The response format. The default response format is html.
Values: html | json
When you submit a request, the service assigns a unique job ID for the transaction.
"jobId": "<unique job identifier>",
"jobStatus": "<job status>"
After the initial request is submitted, you can use jobId to periodically check the status of the job and messages as described in Checking job status. Once the job has successfully completed, use the jobId to retrieve the results. To track the status, you can make a request of the following form:
When the status of the job request is esriJobSucceeded, you can access the results of the analysis by making a request of the following form:
http://<analysis url>/CopyToDataStore/jobs/<jobId>/results/output?token=<your token>&f=json
The output parameter will contain the copied features.
The result has properties for parameter name, data type, and value. The contents of value depend on the outputName parameter provided in the initial request. The value contains the URL of the feature service layer.
See Feature output for more information about how the result layer is accessed.