Latest Contributions by RussellBrennan

Thanks for the examples, it might be worthwhile looking into taking the data offline in Pro to perform these types of analysis. With the data offline we can potentially query larger volumes of data faster for this type of analysis. You can then make edits to this data if needed and sync the changes back through the feature service.  Yes you should be able to run some subset of tools which will operate only on the default version using an SDE connection file, Append will work but I am not certain about others.  ... View more

Hi @Bud,  The easiest way to do it is to disable all editing on your layer. Be aware that if you are the owner of the layer  (or admin) you will always be able to edit. The view approach is helpful if you want to share an editable copy of the data with some folks and a read only version of the data with others or wanted to otherwise limit visibility of the original data in some way. If you just want a read only copy the best/easiest is simply to disable all editing. https://doc.arcgis.com/en/arcgis-online/manage-data/manage-editing-hfl.htm#ESRI_SECTION1_C30D73392D964D51A8B606128A8A6E8F ... View more

Hi @Bud,  In ArcGIS Pro a feature layer refers to any map layer representing feature data. The feature layer will have it's data source as things like geodatabases, shapefiles, feature services, etc. A feature layer's definition is the symbology, definition queries, visibility, along with it's data source.  In our portal environments (AGOL and Portal for ArcGIS) the term feature layer (sometimes 'web feature layer') was chosen to represent a similar concept on the web. It's a little bit bigger of an abstraction in what this means. I will do my best to clarify. A good start might be to read through this doc: https://doc.arcgis.com/en/arcgis-online/reference/feature-layers.htm Hopefully what I am about to say doesn't contradict that link 😀. There can be different data sources for feature layers such as feature collections, but typically feature layers have a data source which is a feature service. A feature service can have one or many (sub) layers and these flow through to the feature layer in the portal. When you add a feature layer to your map you will get all of the sublayers in that feature layer added and for convenience we will typically group that into a group layer. The sub layers can also be added individually, in which case they will not be grouped. When you add layers to Pro, the individual sub layers become 'Pro feature layers' (not an official term). These 'Pro feature layers' have the same behavior as any other feature layer, with the key difference being that thee data source for these layers is a feature service. From the Pro side of things I tend to think of 'web feature layer' = feature service = workspace these will be automatically grouped into group layers if you add them, while 'web feature layer sub layer' = feature service sub layer = feature class these will not get grouped into group layers. Hope this helps.  ... View more

Hi @Bud,  I don't think there is a 'best practice' per se. When you add the Feature Layer to the web map it will create a group layer if there is more than one sub layer. This can be useful if you have a lot of sub layers and you want to maintain organization but generally should not be functionally different from adding the sub layers. There may be some older clients that do not recognize group layers in which case but I think those are becoming less common. I will reply to your other thread about the terminology as well. Hope this helps.  ... View more