Skip to main content
Solved

Possible unnecessary required parameter for new Esri ArcGIS Feature Service [Writer] / Esri ArcGIS Online Connector package

  • November 5, 2025
  • 1 reply
  • 49 views
sammy
Supporter
Forum|alt.badge.img+23

Hello,

I am testing out the Esri ArcGIS Feature Service writer that is in the Esri ArcGIS Online Connector package (Esri ArcGIS Connector v3.13.2). I’m using Form 2024.2.2.0 (20250114 - Build 24820 - WIN64). Screenshots are edited to remove confidential information.

 

I have noticed that the “Target WKID” cannot be left blank even if you have selected “Feature Service Handling: Use Existing”

 

If I am understanding the documentation correctly, this parameter is only needed if the writer is creating a Feature Service. However, as the default is set to WKID 102100, if you don’t change this to the correct WKID, it will write the data out to the wrong location. I initially made this mistake before I realized I had to input my data’s WKID.

 

For the old Esri ArcGIS Portal Feature Service Writer, you were able to leave this parameter blank:

 

I think this parameter being a required parameter is unnecessary when Feature Service Handling is set to “Use Existing” and I like the way it was in the older writer. But I am wondering if I am overlooking some reason for it being required now?

Best answer by crystalwang

Hi ​@sammy,

Thanks for sharing your observations about the Target WKID parameter in the new ArcGIS Feature Service Writer.

We currently have an internal issue filed that describes similar behavior, where the Target WKID must be manually set to match the spatial reference of the target feature service (tracked as FMEENGINE-88607). Otherwise, features will be written to incorrect locations. The proposed improvement in that report is for FME to automatically detect and apply the feature service’s WKID when using an existing feature service, rather than requiring users to verify and set it manually.

I’ve added your feedback to the internal report to provide the development team with additional context on how the current behavior affects users. The issue is still awaiting review, but once it has been addressed, we’ll notify you.

In the meantime, the best approach, as you’ve already identified, is to explicitly set the Target WKID to match the spatial reference of your feature service to ensure data is written in the correct location.

Thank you again for taking the time to document your findings. We apologize for any inconvenience this causes. We appreciate your input, as it helps us continue to improve how the writer handles spatial references.

 

UPDATE:

Our development team has confirmed that the Target WKID parameter being required when Feature Service Handling is set to “Use Existing” is not intentional. For future versions of the new Feature Service Writer, the field will still be mandatory, but we’ll ignore it in in non-overwrite/create cases and use the existing spatial reference. Thank you for your patience while we work to address this issue.

The map is not the territory.
salvaleonrp
tnarladni

1 reply

crystalwang
Safer
Forum|alt.badge.img+15
  • crystalwangSafer
  • Safer
  • Best Answer
  • November 11, 2025

Hi ​@sammy,

Thanks for sharing your observations about the Target WKID parameter in the new ArcGIS Feature Service Writer.

We currently have an internal issue filed that describes similar behavior, where the Target WKID must be manually set to match the spatial reference of the target feature service (tracked as FMEENGINE-88607). Otherwise, features will be written to incorrect locations. The proposed improvement in that report is for FME to automatically detect and apply the feature service’s WKID when using an existing feature service, rather than requiring users to verify and set it manually.

I’ve added your feedback to the internal report to provide the development team with additional context on how the current behavior affects users. The issue is still awaiting review, but once it has been addressed, we’ll notify you.

In the meantime, the best approach, as you’ve already identified, is to explicitly set the Target WKID to match the spatial reference of your feature service to ensure data is written in the correct location.

Thank you again for taking the time to document your findings. We apologize for any inconvenience this causes. We appreciate your input, as it helps us continue to improve how the writer handles spatial references.

 

UPDATE:

Our development team has confirmed that the Target WKID parameter being required when Feature Service Handling is set to “Use Existing” is not intentional. For future versions of the new Feature Service Writer, the field will still be mandatory, but we’ll ignore it in in non-overwrite/create cases and use the existing spatial reference. Thank you for your patience while we work to address this issue.

sammy

Community Stats

32,154
Posts
122,043
Replies
39,812
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.