Esri ArcGIS Feature Service Writer Parameters
Authentication
Source Type ArcGIS Online (default) – The feature server is hosted on ArcGIS Online. Select the feature services through your ArcGIS Online account.
Web Connection
If the Authentication Type is Web Connection, specify the Web Connection to use.
Source TypeStandalone Server – The feature server URL will be specified directly.
Authentication Type
|
|
|---|
|
Web Connection (default) – Use a web connection to authenticate access. Several types of web services are supported:
|
|
None – Access the feature service anonymously. |
|
Kerberos – Also known as Integrated Windows Authentication (IWA). Authenticates as the current Windows user. This option is supported only on Windows systems connected to a domain. |
Source Type Enterprise – The feature server is hosted on an organization’s ArcGIS Enterprise instance. Feature services accessible through a user’s ArcGIS Enterprise account can be selected.
Site URL
The host URL of the ArcGIS Enterprise Installation. This is expected to include the web adaptor name. For example:
https://YOUR_HOST_NAME.com/portal
Authentication Type
|
|
|---|
|
Web Connection (default) – Use a web connection to authenticate access. Several types of web services are supported:
|
|
None – Access the feature service anonymously. |
|
Kerberos – Also known as Integrated Windows Authentication (IWA). Authenticates as the current Windows user. This option is supported only on Windows systems connected to a domain. |
Feature Service
URL
Specify the fully-qualified URL for the Feature Service to read. For example
https://services1.arcgis.com/organizationID/arcgis/rest/services/featureservicename/FeatureServer
Item Source
Determines whether the feature service to write to will be specified using a user folder or a group:
- User Content (default) – Select this option when selecting this feature service from a user folder.
- Group – Select this option when selecting a feature service from a Group.
Folder
Specifies the name of the folder in which the feature service is contained.
The default value of / (forward slash) represents the root user folder. Clicking the Browse button will display a list of a user’s folders.
Group
Specifies the ID of a group for an existing feature service. Clicking the Browse button will display a list of the groups a user belongs to, as well as all the groups in their organization.
Feature Service Handling
- Use Existing – This is the default value. The Selected Feature Service parameter can be used to specify the existing feature service.
- Create If Needed – If the specified Feature Service does not exist in the specified folder, the ArcGIS Feature Service Writer will create it. The Feature Service Name and If Feature Service Exists parameters can be used to specify the feature service. Refer to the Feature Service Creation sections for details regarding this procedure.
- Overwrite Existing – If the specified Feature Service exists, it will be overwritten. The Selected Feature Service parameter can be used to specify the existing feature service. If the feature service specified does not exist at runtime, this will create a feature service.
- When creating or overwriting a Feature Service, the feature operation of all the writer’s feature types should be set to Insert. Note that the Feature Type Handling option should not be set to Truncate Existing.
- If you wish to share a new Feature Service with a group, you can first create it in your own account and then share it to the group using the Esri ArcGIS Online Connector.
Feature Service
This parameter is used to specify a single feature service. Clicking the Browse button will display a list of all the feature services in the selected group or user folder. Once selected, the Feature Service Item ID will be appended to the name of the feature service.
Feature Service Name
Enter the name of a feature service. If the feature service does not exist in the user folder, it will be created.
An Item ID can optionally be appended to the feature service name.
Assuming the correct user folder is selected, these are all valid ways to specify an existing feature service with name My Feature Service and ID 567aba67c25cb60ee159d3fbe2b16eff:
- My Feature Service(567aba67c25cb60ee159d3fbe2b16eff)
- (567aba67c25cb60ee159d3fbe2b16eff)
- My Feature Service
- When creating a new Feature Service, provide only the name of the new Feature Service.
- If you manually enter an ID, you must enclose it within parentheses. Providing a Feature Service Item ID will override the destination specified by the User Folder or Group parameters. The provided ID must match a Feature Service item on ArcGIS Online; otherwise, the writer will fail when the translation is run.
If Feature Service Exists
This parameter controls behavior when the feature service specified with Feature Service Name exists.
- Use Existing – This is the default value. If the feature service exists, write to it without modifying the layer schema.
- Overwrite Existing – If the specified Feature Service exists, it will be overwritten.
Publishing
Specifies the target spatial reference of the published Feature Service.
The default value is WKID 102100. This value corresponds to the Web Mercator projection, which is the standard projection used to create XYZ tiled web maps. If not specified, the server default is used (which is typically also WKID 102100).
Advanced
Specifies the maximum number of features that may be present in a single write request to the server. This limit applies to Insert, Update, Delete, and truncation. The writer will issue a request to the server whenever a single feature type accumulates the number of output features specified by this parameter.
This parameter is useful for avoiding server timeouts or HTTP 500 responses that may result from long write operations.
Default: 1000
This parameter specifies whether Global IDs are to be used as the primary key for write operations, instead of Object IDs. This behavior may be necessary to use some ArcGIS features, such as Feature Service Sync.
When this parameter is set to Yes, it remains possible to insert features without a value for the Global ID attribute.
If this parameter is not provided, it defaults to No.
When Use Global IDs is set to Yes, this parameter determines the behavior during Insert/Upsert operations when a feature without a Global ID value is encountered.
- Yes – An error is raised if the feature does not have a Global ID. This is the default behavior for workspaces created before FME 2020.2.
- No – Auto-generated Global IDs are assigned to features without one.
Prior to FME 2022.0, web access through this format would automatically disable HTTPS Certificate verification when an SSL Error was received from the server. Now, this behavior must be explicitly enabled or disabled by this parameter.
The value of this parameter takes priority over the value of the Verify SSL Certificates parameter which might be defined by the Web Connection used with this format.
When Asynchronous Writes is set to Yes, the writer will send write requests without waiting for the status of the previous write request. For translations with many features, this can reduce the time that the workspace spends running. However, when in this mode, the status of write requests made will not be reported until all features have been written.
The value of this parameter is only used when writing to – not overwriting – an existing feature server. If the writer is creating a new feature service/overwriting an existing feature service, then this parameter will not be used.
- Yes – Perform writes in asynchronous mode. The feature service being written to must support asynchronous writes.
- No (default) – The status of each write request is reported before a new write request is filed.
When Asynchronous Writes is set to Yes, this option can be used to set whether the writer will poll for the status of each async write request after all features have been created.
- Yes (default) – The writer polls for statuses up to the timeout period defined. If a single write request failed, the translation will stop. Write requests which are still pending will not be treated as failures.
- No – The status of write requests is not reported. If write requests have failed, these will not be logged and the translation will proceed.
When Report Asynchronous Write Statuses is set to Yes, this parameter determines the maximum number of seconds the writer will poll for the status of write requests.
Default: 300