Esri ArcGIS Feature Service Writer Parameters

Web Connection

If the Authentication Type is Web Connection, specify the Web Connection to use.

Authentication Type

Web Connection (default) – Use a web connection to authenticate access. Several types of web services are supported: Select Esri ArcGIS Generate Token Web Service and login credentials to generate a token Select Esri ArcGIS Provide Token Web Service and provide your own token. Select Esri ArcGIS Login Web Service to authenticate via NTLM, HTTP Basic, or HTTP Digest.

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.

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: Select the Esri ArcGIS Enterprise OAuth Web Service if your organization uses SAML (Security Assertion Markup Language) or federated login. To configure an OAuth Web Service for use with an ArcGIS Enterprise instance, refer to the instructions in the Esri ArcGIS Enterprise OAuth Web Service template included with FME. The Enterprise Site URL parameter value in the FME reader/writer parameter should match the value entered for the Enterprise Site URL parameter in the web service template. Select the Esri ArcGIS Generate Token Web Service and login credentials to generate a token. Select the Esri ArcGIS Provide Token Web Service to provide your own token. Select the Esri ArcGIS Login Web Service to authenticate via NTLM, HTTP Basic, or HTTP Digest. Most Enterprise sites do not accept HTTP Basic or HTTP Digest as valid authentication methods.

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.

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.
Note  Selecting the Use Existing option disables Publishing parameters.
• 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.

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

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.

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.

Specifies whether layers and tables should be created with attachment support. You can use the ArcGISAttachmentConnector transformer to manage attachments (for example, download/upload).

• Yes (default) – All layers and tables in the created feature services will allow attachments.
• No

Check this option to work with the Version Management Server.

Version Name

The name of the Branch Version to write against. If the version does not exist, it will be created. Clicking the Browse button will display a list of branch versions.

Reconcile

Indicates whether to reconcile the Branch Version against the DEFAULT version at the end of the translation.

• Yes – Reconcile the Branch Version when the write completes.
• No – Do not reconcile.

Post

Indicates whether the Branch Version changes should be merged (posted) to the DEFAULT version at the end of the translation.

• Yes – Post the Branch Version.
• No – Do not post.

If Conflicts Detected

Indicates whether to complete the reconcile and/or post if conflicts were detected.

• Yes – Post the Branch Version.
• No – Do not post.

Access Permission for New Versions

Indicates the permission level to use when creating new branches.

• Private (default) – Only the administrator of the feature service can read or edit data in the created version.
• Protected – All users may read data from the created version, but only the feature service administrator can edit data in the created version.
• Public – All users may read or edit data in the created version.

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.
• No – Auto-generated Global IDs are assigned to features without one.

Specifies whether the writer should verify HTTPS Certificates:

• Yes – Ensures that a URL's digital certificate is valid (signed by a trusted certificate authority), trusted, and belongs to the domain to which you are connecting.
• No – Verification will not be performed (that is, there is no verification that the URL’s certificate is valid or trusted).
• Use Web Connection Value – The parameter uses the Verify SSL Certificate parameter defined in the web connection.

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

When performing UPSERT feature operations or when creating or overwriting feature services, the writer will try to use the Append operation to upload data to a feature service. This parameter controls the data format used for Append operations.

• Feature Collection (default) – Write data is uploaded as a Feature Collection.
• GeoJSON – Write data is uploaded as a GeoJSON file.

This setting enables the creation of layers without data features.

• No (default) – Layers are only created when receiving data features.
• Yes– Layers are created without data features if possible.

Coordinate systems may be extracted from input feature data sources, may come predefined with FME, or may be user-defined. FME allows different output and input coordinate systems, and performs the required coordinate conversions when necessary. To perform this reprojection, FME uses the CS-MAP reprojection engine, which includes definitions for thousands of coordinate systems, with a large variety of projections, datums, ellipsoids, and units.

For systems that know their coordinate system, this field will display Read from Source and FME will read the coordinate system from the source dataset. For most other input sources, the field will display Unknown (which simply means that FME will use default values). In most cases, the default value is all you'll need to perform the translation.

You can always choose to override the defaults and choose a new coordinate system. Select More Coordinate Systems from the drop-down menu to open the Coordinate System Gallery.