We have a service with rapidly changing data. Some of our customers have Esri accounts and would like us to expose their data as Feature Services, which they will use in ArcGIS Pro.
Everything I've read about Feature Services suggests that they are published to ArcGIS Online or Server. But pushing updates to each customer's published instances upon every change, which would require storing access info such as credentials, is undesirable. Since a Feature Service is defined in section 9 of the GeoServices specification, and Koop outputs content according to the GeoServices spec, we assume using Koop is the most promising approach.
Our initial attempts have been met with mixed results. For example, we’ve found endpoints which render correctly in MapViewer, don’t render correctly in ArcGIS Pro. It's unclear whether this is because our Provider is not working correctly, Koop doesn't fully implement the spec, or perhaps ArcGIS Pro expects a Feature Service to be hosted in the ArcGIS ecosystem.
So, are our expectations realistic? Is it possible to expose a Feature Service with uncached, rapidly changing data, from a non-ArcGIS server (via Koop) and expect tools like ArcGIS Pro to consume them as if they were an ArcGIS hosted Feature Service? If there are gotchas, limitations or problems with our approach and assumptions that we can learn from others' experience, instead of through trial and error, it would be tremendously appreciated!
