Latest Contributions by JohnFannon

The Experience Builder Query Widget currently allows for specifying a spatial filter using "Selected features from Data Source", which then requires pre-defined layers to be selected for the filter. This has to be done for each query configured and can be very painful where there are multiple layers in the map. An obvious solution to this would be to have an "All layers in map" option (preferably default), which would allow all layers from the specified map to be used in the spatial filter, rather than specifying the specific layers to use (see images). This would be very similar to how the Web App Builder Query Widget works, which does not require the specific layers to be selected for use in the spatial filter and therefore allows all suitable layers in the map to be used. ... View more

We have developed arcpy scripts to automate layer publishing that follow the examples at: https://pro.arcgis.com/en/pro-app/latest/arcpy/sharing/mapimagesharingdraft-class.htm We have a requirement for the correct copyright/attribution/credits to be populated on both the resulting feature service and feature layer within the feature service, so that these are displayed correctly in the OOB attribution on maps and apps. The documentation states: However, when we publish layers using arcpy, the credits/copyright is not populated on the resulting feature service or feature layer (within the service): If we override the credits after generating the sddraft (using sddraft.credits = "Some text"), the copyright is populated at the feature service level, but not at the feature layer level. For the credits to appear correctly in map viewer and apps, they need to be populated at the feature layer level. Note that it works when manually publishing from ArcGIS Pro, but we need to publish in an automated way as part of a CI/CD pipeline, so this is not an option. We have raised with Esri support and they have created an enhancement request, but has anyone else found a work around for this issue? Is there a way to update the copyright on the feature layer after the service has been published (e.g. with the rest api). We are using ArcGIS Enterprise 10.9 (Server & Portal) and not ArcGIS Online and these are standard feature layers and not hosted feature layers. Any thoughts much appreciated. Sample python code for generating an SD file below (which can then be published in server manager). John import arcpy import os import sys import xml.dom.minidom as DOM #params if len(sys.argv) != 8: print("Incorrect arguments. Usage: creditstest.py <portal url> <server url> <portal user> <portal password> <pro project path> <out directory path> <override credits (Y/N)>") sys.exit(1) portalUrl = sys.argv[1] serverUrl = sys.argv[2] portalUser = sys.argv[3] portalPassword = sys.argv[4] arcgisProProjectPath = sys.argv[5] outDirPath = sys.argv[6] overrideCredits = sys.argv[7] # layer from project print("Opening Pro project...") proj = arcpy.mp.ArcGISProject(arcgisProProjectPath) map = proj.listMaps('Map')[0] layer = map.listLayers()[0] # Set output file paths print("Building output file paths...") sddraftFilename = "{0}.sddraft".format(layer.name) sddraftPath = os.path.join(outDirPath, sddraftFilename) sdPath = sddraftPath.replace(".sddraft",".sd") #If any old service definitions exist, remove them for filePath in [sddraftPath,sdPath]: if os.path.exists(filePath): os.remove(filePath) # Sign in to portal print("Signing in to Portal...") arcpy.SignInToPortal(portalUrl, portalUser, portalPassword) #Create map image sharing draft print("Generating SD draft...") sddraft = map.getWebLayerSharingDraft("FEDERATED_SERVER", "MAP_IMAGE", layer.name, [layer]) #Set draft properties sddraft.federatedServerUrl= serverUrl sddraft.copyDataToServer = False #sddraft.overwriteExistingService = True #sddraft.description = "" #sddraft.summary = "" # Set the credits/attribution/copyright based on the credits in the layer metadata # Note this ONLY sets the credits at the service level and NOT at the layer level # (which is required for copyright to display in map viewer for feature layers) if overrideCredits.upper() == "Y": print("Overriding credits with layer credits...") layerCredits = layer.metadata.credits if layerCredits != None and len(layerCredits.strip()) > 0: sddraft.credits = layerCredits #Export service definition draft print("Exporting SD draft...") sddraft.exportToSDDraft(sddraftPath) # Modify sddraft to enable feature access # Read the file print("Add feature server to SD draft...") doc = DOM.parse(sddraftPath) # Find all elements named TypeName # This is where the addition layers and capabilities are defined typeNames = doc.getElementsByTagName('TypeName') for typeName in typeNames: # Get the TypeName to enable if typeName.firstChild.data == "FeatureServer": extension = typeName.parentNode for extElement in extension.childNodes: # Enable feature access if extElement.tagName == 'Enabled': extElement.firstChild.data = 'true' # Write to a new .sddraft file sddraftMod = layer.name + '_mod_xml' + '.sddraft' sddraftModPath = os.path.join(outDirPath, sddraftMod) with open(sddraftModPath, 'w') as f: doc.writexml(f) # Stage service print("Generating SD file...") arcpy.StageService_server(sddraftModPath, sdPath) print("Successfully generated SD file.")   ... View more

I have a requirement to process some features from a feature layer in ArcGIS Online to merge them together based on unique combinations of attributes and write the output to another feature layer. We want to do this in a scheduled notebook, but have been having some issues with the union operation when it comes to creating multi-part polygons. When I union two polygons that are disjoint (not intersecting) I expect the union operation to create a single multi-part polygon, as it does in desktop and arcpy. However, when we do this in a standard ArcGIS Online notebook, the result is not a multi-part polygon, but just the first of the two polygons used as input. The below is a test using an ArcGIS Online notebook. When the input polygons are intersecting, the union works as expected. However, when they are disjoint, it doesn't work as expected: I have tested the exact same notebook code within ArcGIS Pro and get a multi-part feature when the input polygons are disjoint (non intersecting), which is expected: I have attached the test python code. I know there are some differences in the way the API works in ArcGIS Online vs ArcGIS Pro, as arcpy is not used in the standard Online notebooks. However, the documentation for the API seems to suggest union is supported and will use the shapely library when arcpy isn't available. It seems like a fairly basic thing to want to do, so does anyone know how to get this union working, so that unioning two disjoint polygons results in a multipart polygon, in an ArcGIS Online notebook without arcpy? Is there something specific I need to do to use shapely? ... View more

When creating a hosted feature layer view from a hosted feature layer, various metadata from the parent layer item is not copied to the view layer item, meaning having to manually copy information between the two. It would be great if, by default or as an option, when creating a hosted feature layer view, all the metadata from the parent hosted feature layer item was copied to the view layer item, including: tags summary description credits terms of use categories The user would still have the capability to ammend these once the view item is created. ... View more

Currently when creating a hosted feature layer view, it is not possible to exclude fields from the view that are set as non-nullable. It should be possible to exclude these fields from views. The reason given in the documentation for not allowing non-nullable fields to be disabled is that these may be needed for editing. However, this is only true if the view is intended to be used for editing. For example, we have a layer with some fields that we absolutely want to be populated when editing, so we set these fields to be non-nullable. These fields may contain sensitive/personal information and for GDPR purposes, we do not want all viewers of this data to see or have access to the contents of these fields. We should be able to create a hosted feature layer view that is not editable and that excludes these fields. ... View more