Latest Contributions by JohannesLindner

You could use the Calculate Field tool. Switch language to Arcade, use this expression (edit the 2nd line to load your line feature class) // load the line feature class var lines = FeaturesetByName($datastore, "LineFC") // create a buffer aroun d the current point var p_buffer = Buffer($feature, 10, "meters") // get all lines intersecting that buffer var i_lines = Intersects(p_buffer, lines) // check the count and return the correct result var c = Count(i_lines) return IIf(c > 0, "1", "NULL")   ... View more

@DavidNyenhuis1 , @Anonymous User Any news on this isssue?   I just answered another question about this and got curious. Here are some questions I found in a very cursory search where converting the Date() to Number() was the solution, I probably missed a few. Arcade script to split multi pick field values - Esri Community ArcGIS Dashboard Using Arcade to union two dataset... - Esri Community Solved: Help getting a data expression to work. - Esri Community Solved: Arcade Expression: No values returned by FeatureSe... - Esri Community Solved: Arcade dictionary to FeatureSet - Esri Community Solved: How to maintain date data in arcade expressions - Esri Community Arcade FeatureSets and Date Fields: What's Going O... - Esri Community Solved: esriFieldTypeDate in Data Expression in Dashboard ... - Esri Community Solved: Arcade Data Expressions with Date Column Not Worki... - Esri Community Solved: Date fields in data expressions for serial charts - Esri Community Solved: Feature not being created due to date field type - Esri Community Solved: Arcade Data Expression- Dictionary from multiple t... - Esri Community Solved: Pass values to new columns Arcade - Esri Community Solved: Re: Arcade - How to use a date field with a dictio... - Esri Community   There are probably many users who have the same problem but didn't ask a question (I know I was). They either got the solution from an already solved question (good: they got a solution, bad: they had this easily avoidable problem in the first place) or they couldn't solve this problem and moved on (obviously bad). ... View more

To get the average of a featureset column , we can use the Average() function.   Let's load some test data:     // create a test fs for a scoring survey. // 3 text fields with scores between 1 and 5 var survey_dict = { fields:[ {name: "Score1", type: "esriFieldTypeString"}, {name: "Score2", type: "esriFieldTypeString"}, {name: "Score3", type: "esriFieldTypeString"}, ], geometryType: "", features: [] } for(var i = 0; i < 200; i++) { var rating = {attributes: { Score1: Text(Round(4 * Random() + 1)), Score2: Text(Round(4 * Random() + 1)), Score3: Text(Round(4 * Random() + 1)), }} Push(survey_dict.features, rating) } var survey = Featureset(Text(survey_dict)) // return survey       Now, if we take the Average() of column Score1, we get this result:   This is obviously incorrect. It seems like the function doesn't convert to Number(), but instead somehow uses the bytes of the string values as number (or something else...). So we need to covert that column to a proper integer column first. I haven't found a way to do that inside the Average() function, so we should probably just convert the featureset before calling Average(): var score_fields = ["Score1", "Score2", "Score3"] // create an empty featureset dict var numeric_survey_dict = { fields: [], geometryType: "", features: [] } // add the score fields as integer fields for(var i in score_fields) { var field = {name: score_fields[i], type: "esriFieldTypeInteger"} Push(numeric_survey_dict.fields, field) } // go thorugh the original featureset and convert each value to Number() for(var f in survey) { var converted_f = Dictionary() for(var i in score_fields) { var field = score_fields[i] converted_f[field] = Number(f[field]) } Push(numeric_survey_dict.features, {attributes: converted_f}) } // convert the dictionary to a featureset var numeric_survey = Featureset(Text(numeric_survey_dict)) // get the Average() return Average(numeric_survey, "Score1")   ... View more

which means I have to go in and remove all the extraneous stuff . For that, I just use the block quotes... Personally, it doesn't bother me that much, because I often have to expand the toolbar anyway to get to the code button... ... View more

You're using an alias as join field ("Mapunit key"), that might be the problem. Try with the actual field name. If you can run it from the tool, then go to the geoprocessing history, right-click on the successfull tool run, send the code to the Python Window, and analyze the command. ... View more

You can't really undo it if it happened that long ago. You can only recreate the deleted features by copying from a backup of your feature class or from the original data.   If your feature class is versioned, you can add the archive to the map and get the historic features from there. If you made manual backups of your data, you could go back to a backup before the split and copy the missing features to your current feature class. If you're working on a network drive, you can talk to your IT department, they might be doing automatic backups. If none nof these apply, you're probably out of luck and have to redo your whole workflow for the deleted polygons. ... View more

This is a duplicate of this idea: Definition Query Icon in Table of Contents - Esri Community   It's currently closed, but there is a lot of discussion going on. Be sure to look through the dicussion to see an explanation of why this is currently not implemented.   In the meantime, there is a filter for the table of contents:     @KoryKramer  ... View more

Inside the category filter, don't use the "Features" option. You need the "Grouped Values" option and group by rent_amount, which should give you distinct values.   ... View more

1 Mb / 1000 rows / 1000 columns = 0.000001 Mb / Cell 0.000001 Mb = 1 Byte In 1 Byte (8 bit) of data you can store one of 256 (2^8) integer values (0 ... 255 or -128 ... 127).   Of course, that's the size for the pure raster cell values. In a "real" raster format (say ESRI's ASCII raster format), you would have separators between the values in one row (space), separators between the rows (linebreak), and header data (cell size, start coordinates), so the raster size would be somewhat above 1 Mb. ... View more

but I need to change the IsBusStop field based on whether or not "LOADING ZONE" is found in the description field.  Yes, but if the IsBusStop field can only have the values "Y" and "N", then you don't actually need to replace that value, you can just set it.   but I need to change the IsBusStop field based on whether or not "LOADING ZONE" is found in the description field.  That's because you use another expression. Try it with the expression that actually worked. ... View more

Phew, turns out to be more complicated than I expected. Or there is some simple solution I overlooked...   fc = "TestPoints" # get a near table with all pairs near_table = arcpy.analysis.GenerateNearTable("TestPoints", "TestPoints", r"memory/NearTable", closest="ALL") # extract the rank 1 pairs rank_1 = [row for row in arcpy.da.SearchCursor(near_table, ["IN_FID", "NEAR_FID"], "NEAR_RANK = 1") ] # save these connections for later feature_connections = list(rank_1) # find the clusters of those pairs clusters = [] while len(rank_1) > 0: cluster = set() # new empty cluster test_fids= set(rank_1[0]) # start with the first available fid pair while len(test_fids) > 0: cluster.update(test_fids) # add all test_fids to the cluster # find the next test_fids # all fid pairs where either fid is in the current_fids # and not already in the cluster next_fids = set() for r in rank_1: if r[0] in test_fids or r[1] in test_fids: next_fids.update(set(r)) test_fids = next_fids.difference(cluster) clusters.append(cluster) # remove all fid pairs of this cluster from the fid pair list rank_1 = [r for r in rank_1 if r[0] not in cluster and r[1] not in cluster ] print("Detected the following clusters:") print(clusters) # get the cluster connections cluster_connections = [] for cluster in clusters: start = set(cluster) not_stop = set(cluster) while True: # find nearest point in another cluster where = f"IN_FID IN {tuple(start)} AND NEAR_FID NOT IN {tuple(not_stop)}" sql = (None, "ORDER BY NEAR_DIST") with arcpy.da.SearchCursor(near_table, ["IN_FID", "NEAR_FID"], where, sql_clause=sql) as cursor: for connection in cursor: break # if the reverse connection already exists, get the second nearest # cluster, else you could get "super cluster" of clusters that are # each other's closest clusters rev_connection = tuple(reversed(connection)) if rev_connection in cluster_connections: other_cluster = [c for c in clusters if connection[1] in c][0] not_stop.update(other_cluster) # if the connection does not yet exist, we're done else: cluster_connections.append(connection) break print("Detected the following connections between clusters:") print(cluster_connections) # put all the connections together unique_feature_connections = [] for connection in feature_connections: if tuple(reversed(connection)) not in unique_feature_connections: unique_feature_connections.append(connection) connections = unique_feature_connections + cluster_connections print("\n\nDetected the following connections between the features:") print(connections)     Input (points, but it should work with any geometry type): Connections generated from a simple Generate Near Table: And the result of my script with connections between the clusters:   There are some cluster connections that aren't really necessary, for example between points 161/166, or 156/163. Sadly, you can't just connect to the closest cluster, because then you could get "super clusters" of clusters that are each other's closest clusters, for example the two clusters in the lower left. That's why I look for the second closest cluster if I detect a cluster connection multiple times. The "correct" way would be to check if the cluster is connected to the greater network of clusters and if so skip the detection of a new cluster connection, but I'm too lazy to figure out a proper solution for that...   ... View more

Related Idea trying to get this fixed: Arcade: Allow Date() values in date fields (esriFi... - Esri Community ... View more