Latest Contributions by JoshuaSharp-Heward

Hi Al, I'd definitely recommend keeping all of the data in the same table and having a drop down. Where are you aiming to display the data, in a web map in ArcGIS Online? You can set up filtering on a layer within web maps in AGOL, and ArcGIS Dashboards and Web Experience Builder/Web App Builder also have filter tools that would allow a user to query the data in a drop down box as they please. You may also just want to consider symbolising on the species field so you can easily see which species are where - Field Maps also now allows for the configuration of filtering by specific fields in a layer which would allow your data collectors to see the points for a specific species in the field too. Cheers, Josh ... View more

Have you confirmed that the intersect outputs what you want it to when you run it manually? I've updated the user above's code to store unique names for the input county/counties and print them at the end. aprx = arcpy.mp.ArcGISProject("CURRENT") m = aprx.listMaps("Map")[0] county = ["Dude County"] projectfilepath = "C:\\Users\\User\\Documents\\ArcGIS\\Projects\\ARCPY_test\\" datafilepath = "C:\\Users\\User\\Documents\\ArcGIS\Data\\" to_KMZs_filepath = "Circuits_KMZs\\" parcel = "Counties_(v17a)" gdb = datafilepath + to_KMZs_filepath counties = m.listLayers(parcel) import os fields = ["LABEL", "NAME_1"] names = {} for dirpath, dirnames, filenames in os.walk(rootdir): for file in filenames: if file.endswith("kmz"): try: arcpy.conversion.KMLToLayer( in_kml_file = m.addDataFromPath(os.path.join(gdb,file)), output_folder = projectfilepath, output_data = file + "_LAYER", include_groundoverlay="NO_GROUNDOVERLAY" ) line = m.listLayers(file + "\Polylines") tmp_int = arcpy.analysis.Intersect( in_features = [counties, line], out_feature_class = r"memory\temp_intersect", output_type = "POINT" ) with arcpy.da.SearchCursor(tmp_int, fields) as s_cursor: for label, name_1 in s_cursor: if label in county: # remove this conditional and adjust the indents below for it to include all counties in the intersect print(f"{name_1}") if label not in names: #if county not present as key in dictionary add it and add first name_1 value as a list names[label]= [name_1] print(f"Added {label} and {name_1} to names dictionary") else: if name_1 not in names[label]: #if county present as key and name_1 not in list of names, add it names[label].append(name_1) print(f"Adding {name_1} to {label} in dictionary") else: #if name already in list of names for county key in dict, don't add it print(f"Not adding {name_1} as already present in dictionary") except Exception: arcpy.AddMessage(os.path.join(rootdir, file)) # print the final message for k, v in totals.items(): print(f'County: {k} | names: {v}') The temp layers will always be overwritten with the above code because the output name is the same every time it's run, what we're doing here is extracting the information we want from the temporary layer, storing it to a dictionary outside of the for loop (so it's persisted) and then looping through the dictionary values at the end. ... View more

Hi, I think the structure of your data is fine as it gives you the granularity you would need to chain multiple selectors and filter down to the specific data you're interested in! Probably the best way to do this is to add multiple "Category" selectors (one for each variable) set to "Grouped" values and pointing to the respective fields you're wanting to filter by, so one Wind selector pointed at the "Wind" field etc.. With the grouped values this will a drop down where you can choose "True" or "False" and it will filter the rest of the data in your dashboard, once you've configured that in the "Actions" portion of the selector setup. ... View more

Adding to the above poster's comment, if you're doing this in a smart form/Field Maps, then you can just edit the final line to be this:   IIF($editcontext.editType == "INSERT", nearStation.station_name, destinationField)   With destinationField being the field you're writing the station name to. Which will mean that if a point is being added for the first time it will do the intersect and populate the field with the closest station, but if it's an update/edit then it just returns the current field value. ... View more

Hi, Do you just need to indent from the "fields" line down? With the search cursor outside of the for loop it'll keep overwriting the "memory\temp_intersect" output for each KML and then just run the search cursor over the final KML layer that is intersected. Although this would print out the values for each KML separately which it doesn't sound like you want the output to be. If you do want it all in one final search cursor, you could output each temp intersect layer with a different name (so it's not overwritten every time), then add a merge above the "fields" line to bring them all together, and use the merged layer as the input into your cursor? ... View more

No worries, glad I could help out mate! ... View more

My pleasure, glad that worked and that I could help out! I am also eagerly awaiting the day that attribute rules are supported, but glad this is an interim solution at least! ... View more

Weird, outputting the layer using feature class to feature class and storing it in the 'memory' workspace may be a decent option for temporary data, but if your process of outputting to a .lyrx is working then all good I guess! ... View more

Hi, If it's not automatically adding it you may be able to sandwich it within the following code to get it to add to the map - haven't tried it myself but it's the manual way of adding a layer to a map. myProject = arcpy.mp.ArcGISProject("CURRENT") #references current pro project myMap = myProject.activeMap #the rest of the code myMap.addLayer(outputLayer) ... View more

Hi, If you're running it from within Pro then MakeFeatureLayer should automatically add it to your active map. Although in testing this I've realised that MakeFeatureLayer doesn't honour the selection which is annoying. Does it have to be a temporary layer? If not then exporting to feature class should work https://pro.arcgis.com/en/pro-app/latest/tool-reference/conversion/feature-class-to-feature-class.htm If not you will need to take the selected features on the input and add their ObjectIDs to the where_clause in the MakeFeatureLayer function. This should work:   inputLayer = 'yourlayername' outputLayer = 'outputlayername' OIDS = arcpy.Describe(inputLayer).FIDSet #returns a string of all the OBJECTIDs sql = "OBJECTID IN ({})".format(OIDS.replace("; ", ",")) #formats the OBJECTiD string into the format of (1, 2, 3) required for SQL IN arcpy.management.MakeFeatureLayer(inputLayer, outputLayer, where_clause=sql)     ... View more

Do you want to do the selection in ArcPy as well or will you be selecting them using the regular tools in the GUI and then running some python to create the layer? This page https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/make-feature-layer.htm has the details of the make feature layer tool which is what you want, just click on "Python" in the Parameters section to see what the function is + what the inputs are. Pretty sure that by default if your input features into the tool have a selection on them that that will be honoured in any ArcPy tool. ... View more

Hi Aurelian, Unless I'm misunderstanding I think you might be over-complicating things. When adding the indicator widget you're able to add a filter (in this case FREQ_MAINTENANCE not equal 0) and choose the statistic as "SUM" on "Shape_Length". Cheers, Josh ... View more

Hi, I believe this support article shows an example of what you're trying to do: https://support.esri.com/en-us/knowledge-base/how-to-show-attachments-from-a-related-tablelayer-in-t-000027210 pulling the images from a related table onto the parent features popup. In this example it only returns the first image, but I think the code could be modified to return all images. ... View more