Runtime Local Server: Input Feature Set is shown as GPString not as Feature Set?

[Jan-Tschada]

We started using the Runtime Local Server 100.9 for a kind of Proof of Concept for our GEOINT platform v-next. The GEOINT officer use case describes a workflow where a GEOINT analyst is creating a Geoprocessing package using ArcGIS Pro Intelligence (based on ArcGIS Pro 2.6.3) and delivers this Geoprocessing package to all the clients having a ArcGIS Runtime 100.9 based app and the local server deployed. The GEOINT officer is doing his INTEL work to gain some insights from various offline geospatial analysis and is creating a detailed INTEL report.

In the past we used ArcMap 10.6 for creating the Geoprocessing packages and used Feature_Set input params as input. Starting with ArcGIS Pro Intelligence the input params are always shown as GPString. I have attached a simple .gpkx file. Maybe we need to adjust some style definition or configuration for making it work.

Thanks in advance.

[Jan-Tschada]

Anyone seen this behaviour before or can reproduce this?

[Jan-Tschada]

We could not reproduce this in ArcMap 10.8.1. Is ArcGIS Pro creating incompatible Geoprocessing Packages? Any help would be appropriated.

[Jan-Tschada]

@LucasDanzinger would you be so kind and take a look at this behaviour.

Thanks in advance.

[Jan-Tschada]

Did anybody used a ArcGIS Pro based Geoprocessing Packages with Features as Input Parameter with the Runtime Local Server 100.9? We are still waiting for any feedback related to this issue... meanwhile the support is trying to find any documentation about "Best Practices for creating Geoprocessing Packages with ArcGIS Pro".

[MichaelBranscomb]

Hi,

Can you share more details about your exact workflow to create the packages, specifically how you're exposing the features as inputs? A sample gpkx would be ideal.

If you're not able to go into that level of detail and/or share examples here feel free to email me at mbranscomb@esri.com.

Thanks

Mike  

[Jan-Tschada]

Hi Michael,

the "buffer.gpkx" sample is attached to the initial post. We stripped it down to a simple buffer model using features as input and output. We can use all of our GPKX packages in any ArcGIS Pro environment and publish it into any of our ArcGIS Enterprise environments. The input "features" parameter is correctly offered as a "GPFeatureRecordSetLayer".

Meanwhile we had to create the following support case Geoprocessing packages created in ArcGIS Pro do not offer Feature Set as input parameter by using Ar...  for this blocker.