I work on systems for Fire and EMS including 911 and Dispatch. The only function I need use in services is to project incoming long lat values to the projection that the client uses for their maps.
We would like to move some of our enterprise application work off of the thick client and into services for geometry manipulation and processing. We also would have a use-case for handling geometry operations for incoming flat files that we import from third parties for import into our clients.
Loading features from service tables would also be helpful for inspecting and validating data in some of our automated services as well. Geocoding is also another instance we would like to leverage.
We also have document generation services that currently export maps via REST export requests we could expand a bit on the functionality in there if we could load feature attributes and shape data.
There would also be a use-case for serialization to some of our internal auditing apps when we hit edge cases during data imports and some of the year-to-year rollover processes we use.
We are facing a lot of integration issues when using the default author & publish approach with GP Tools and cascading web services (NTLM authentication with SSO using custom GP Services). All our use cases are connecting to custom data stores using web services with authentication/authorization and execute predefined geospatial workflows like buffering, spatial join, spatial aggregation and so on running in ArcGIS Enterprise.
We are not able to reuse/delegate the authentication from our GP Service to the custom data store REST/GraphQL/gRPC endpoint. Right now, we have to use predefined "technical users", "system accounts" for accessing theses datastores. If we could use a geospatial engine running in our own web services, we would be able to directly authenticate against the custom datastore endpoint and do the geospatial processing without authenticating against and transferring the data back and forth to ArcGIS Enterprise using the Geometry Services.
The only functionality I need is converting lat/long to projected points or projected points to lat/long. As it turns out, one of my co-workers showed me an open source project that can do that; so I don't really need runtime for that any more.
@PhilipMeeks_CS we would prefer to stay with ArcGIS Runtime. We want to reuse our existing core libraries for mobile, desktop and web service development. Also, some of our system integrators ran into a bunch of serious licensing issues when combining various Open Source libraries in the past.
@Jan-Tschada We are still considering how to deliver a Runtime product for use in a service as it is a very popular request. Most of those requests center on workflows to support feature serialization, editing, and use of geometry engine operations. This request appears to include authentication and use of tasks (eg geoprocessing task) to access ArcGIS service endpoints. Sounds reasonable. It may take some time, but we'll start moving on this in 2022 to assess technical and business viability.
%20Office%20skaliert.png "Jan-Tschada"){kind=avatar}
