+46In the Esri ArcGIS Portal Feature Service I can reference a Feature Service in the parameters with the service name and an id
e.g.
But in the Esri ArcGIS Feature Service it’s not possible without a group? Is this correct?
Is there some secret syntax i’m missing?
+1Yep. In the new ArcGIS Feature Service reader, make sure to select the Item Source first - either Group or User Content.
Once you do that, FME will list all services available under that source.
+46That’s not the issue, i want to reference a featureservice without reference to a group, which was possible in the existing reader.
+64I think this is a missing feature nowadays. When your source is AGOL, you need to select a group. This used to work perfectly. When using different software than FME it still does works.
I also miss the option to use a token. I used to get data from other people’s mapservices by simply putting it in the FeatureService reader, combined with the temp token found in the developer window. This way I could easily download the data from a mapservice, even when there was no featureservice present. Now I need to keep an older version of FME to do this, or use Python.
+20
I also miss the option to use a token. I used to get data from other people’s mapservices by simply putting it in the FeatureService reader, combined with the temp token found in the developer window. This way I could easily download the data from a mapservice, even when there was no featureservice present. Now I need to keep an older version of FME to do this, or use Python.
@ebygomm, sorry for diverting your issue into a newer one. I’m quite familiar with
Her’s the configuration.
Here’s the end result
Having Add Web Connection is for convenience, but I’m too skeptical since the Add Web Connection in the Feature Service formats can be confusing than keeping it in the Web Connections under FME Options, specially for beginners. WHen there were three separate formats it was fine, but when they were combined into one format, all of a sudden the list of web connections got longer - showing both the legacy and the new web connections of all feature services, in addition to the option adding more with this Add Web Connection feature from the format dialog.
When you are migrating from the legacy feature service formats to the ESRI Feature Service format you can be overwhelmed if you manage numerous ArcGIS portals.
+46*When you are migrating from the legacy feature service formats to the ESRI Feature Service format you can be overwhelmed if you manage numerous ArcGIS portals.*
Sensible naming conventions are difficult when you need two different web connections to the same location across all environments whilst things are migrated.
