Latest Contributions by JohannesLindner

That's the plan, yes. ... View more

You're trying to use a list of layers as input, but the tool expects a layer.   So you will have to create your output fc and iterate through your SampleLines and append the result to the oputput fc. Or you can do it with an InsertCursor. And at that point, you can take the next logical step and skip the tools altogether and just use the geometry methods. input_point_fcs = ["TestPoints"] bearings = [0, 90, 180, 270, 45] distances = [50, 100, 150, 200] output_folder = "memory" output_name = "result" output_fc = arcpy.management.CreateFeatureclass(output_folder, output_name, "POINT") arcpy.management.AddField(output_fc, "Source", "TEXT") arcpy.management.AddField(output_fc, "Bearing", "DOUBLE") arcpy.management.AddField(output_fc, "Distance", "DOUBLE") with arcpy.da.InsertCursor(output_fc, ["SHAPE@", "Source", "Bearing", "Distance"]) as i_cursor: for point_fc in input_point_fcs: with arcpy.da.SearchCursor(point_fc, ["SHAPE@"]) as s_cursor: for point, in s_cursor: for bearing in bearings: for distance in distances: new_point = point.pointFromAngleAndDistance(bearing, distance) i_cursor.insertRow([new_point, point_fc, bearing, distance])     ... View more

Oof... Some incoherent points off the top of my head: The field calculator is clunky enough in its present state. We have questions here regarding syntax pretty often, especially for users not using the GUI, but calling the calculator in scripts (having to supply the expression as string). If you introduce regex into there, you will probably get a lot of questions about that. Regex is... let's say "not the most intuitive". I'm by no means a power user, but I have used it in some instances. I still don't have a clue what I'm doing. Every regex expression I've ever used was heavily inspired by online searches and long sessions on regex101. If I look at some of those expressions now, I only know what they're supposed to find because I documented it. I feel like the complicated syntax would stop many users cold in their tracks, leading to frustration and to them just using string.replace() anyway. Who's your audience here? I think most users who both know of regex and consider using it know enough about Python to either import re in the calculator or skip the calculator altogether and go straight for the UpdateCursor. On the other side, there's a big chance that users who are not as experienced in Python (or programming in general) have never even heard of regex. Swamping those users in regex syntax doesn't seem like a good idea to me.   So, personally, I think it would lead to much confusion for little benefit. Having said that, I don't know how QGIS does this. Maybe I'm making up problems and there are good ways of avoiding that confusion... ... View more

You can activate the time feature on layers. You seem to have done that (accidentally) for at least one of your layers.   To deactivate: Go into the layer properties, switch to the Time tab, switch the Layer Time property to "No time". Do this for each layer.     I'm not sure why you would see the time line on new and old projects. Do you use saved layer files in multiple projects? ... View more

Judging from the fields, you are writing this expression in the palm survey table. But it should be written for the palm layer. ... View more

Ah. As far as I know, there's no way to do that dynamically.   Only way I can think of is to have statically defined periods. So your users wouldn't be able to filter for "every point between these two arbitrary dates", only for "every point that falls into this predefined period". To do this, you can use this data expression:   // load your points var p = Portal("https://xxx/portal/") var id = "abc" var sublayer = 1 var date_field = "Zeitstempel" var layer = FeaturesetByPortalItem(p, id, sublayer, [date_field], true) // define the output var output_dict = { geometryType: "", fields: [ {name: "Period", type: "esriFieldTypeString"}, {name: "TotalArea", type: "esriFieldTypeDouble"}, ], features: [] } // define the periods as dictionary {period_name: [start, end]} // The Union() function below takes a lot of time, so don't use too many periods! var periods = { "2020": [Date(2020, 0, 1), Date(2020, 11, 31)], "2021": [Date(2021, 0, 1), Date(2021, 11, 31)], "2022": [Date(2022, 0, 1), Date(2022, 11, 31)], "2023": [Date(2023, 0, 1), Date(2023, 11, 31)], "2020 - Q1": [Date(2020, 0, 1), Date(2020, 2, 31)], "2020 - Q2": [Date(2020, 3, 1), Date(2020, 5, 30)], "2020 - Q3": [Date(2020, 6, 1), Date(2020, 8, 30)], "2020 - Q4": [Date(2020, 9, 1), Date(2020, 11, 31)], } // loop over the periods for(var p in periods) { // filter your points var start = periods[p][0] var end = periods[p][1] var sql = `${date_field} >= @start AND ${date_field} <= @end` var filtered_layer = Filter(layer, sql) // buffer each point var buffers = [] for(var f in filtered_layer) { Push(buffers, Buffer(f, 10, "meters")) } // union all buffers var unioned_buffers = Union(buffers) // write new feature var new_f = {attributes:{ Period: p, TotalArea: Area(unioned_buffers, "square-meters") }} Push(output_dict.features, new_f) } // return the featureset return Featureset(Text(output_dict))     Set the indicator's value to Sum of TotalArea. Instead of the date selector, use a category selector. Use your period names as categories.   As action, filter the indicator's Period field.     Now your users can filter by the periods you defined and get the unioned areas.     ... View more

Quick practical application of Dan's answer: land = "Land" #layer name or fc path # convert vertices to points land_points = arcpy.management.FeatureVerticesToPoints(land, "memory/land_points", "ALL") # create Thiessen polygons for the vertices # I'm assuming you can use planar calculations! If you need geodesic, use something else. thiessen = arcpy.analysis.CreateThiessenPolygons(land_points, "memory/thiessen", "ALL") # dissolve the Thiessen polygons -> centerlines between islands centerlines = arcpy.management.Dissolve(thiessen, "memory/centerlines", "ORIG_FID") # create buffers bufferlines = arcpy.analysis.Buffer(land, "memory/bufferlines", "3 miles") # intersect buffers and centerlines intersect = arcpy.analysis.Intersect([bufferlines, centerlines], "memory/intersect") # dissolve for ORIG_FID (Land_OID -> Vertices) and ORIG_FID_1 (Land_OID -> Buffer) baselines = arcpy.management.Dissolve(intersect, "memory/baselines", ["ORIG_FID", "ORIG_FID_1"]) # finally, delete every feature where the FIDs don't match with arcpy.da.UpdateCursor(baselines, ["OID@"], "ORIG_FID <> ORIG_FID_1") as cursor: for row in cursor: cursor.deleteRow()   Islands outlined in red, the resulting baselines in yellow:   ... View more

It can be done, but not in the advanced formatting. In there, you can only access the current datapoint, you can't load featuresets. Instead, you need to calculate the buffers in a data expression, use that expression as input for your indicator, and then filter the indicator's data source using user supplied values.   So, doing this step by step: Add an indicator   Create a new data expression for it // load your points var p = Portal("https://xxx/portal/") var id = "abc" var sublayer = 1 var date_field = "Zeitstempel" var layer = FeaturesetByPortalItem(p, id, sublayer, [date_field], true) // define the output var output_dict = { geometryType: "", fields: [ {name: "DateField", type: "esriFieldTypeDate"}, {name: "BufferArea", type: "esriFieldTypeDouble"} ], features: [] } // create the buffers for(var f in layer) { var new_f = {attributes: { DateField: Number(f[date_field]), BufferArea: Area(Buffer(f, 10, "meters"), "square-meters") }} Push(output_dict.features, new_f) } // return the featureset return Featureset(Text(output_dict))   Change the indicator's parameters: show the sum of the BufferArea field add some text Add a top or side bar   Add a date selector to the bar   Change these two parameters:   Add an action: Filter the indicator's date field   Now the user-selected date range filters the indicator's data source:     ... View more

An Arcade expression might not be the best way here.   Going from this:     Option 1: Definition query Go into the layer options, switch to the Definition Query tab.  Click on "New definition query" and use the UI to only select the features where the confirmation field ("TextField2" in my case) is not null. Alternatively, only select where the confirmation field is equal to "Yes". Apply.   This will hide all features with null values in the confirmation field, allowing you to use a simple symbology with unique values:   Option 2: Unique values with multiple fields In the symbology tab, select both the road type field and the confirmation field ("TextField1" and "TextField2" in my case):   Select each symbol where the confirmation field is null (Ctrl + left click to select multiple), remove those from the symbology:   Uncheck "Show all other values":   This will hide all features with null values in the confirmation field. BUT, while option 1 doesn't include those features in the layer, option 2 does, it only does not draw them. You can still see them in the attribute table, and they are still getting labeled:   Option 3: Arcade expression Sure, you can do this. Change to "Single Symbol", format the symbol. Allow symbol property connections and click on the button next to the color picker: Click on the expression button, copy/paste and edit the expression below, apply everything.     // hide unconfirmed features by giving them a fully transparent color if($feature.TextField2 != "Yes") { return "rgba(0, 0, 0, 0)" } // define a mapping of road type to color var mapping = { "Highway": "red", "Two-Lane-Road": "rgb(0, 255, 255)" } // return the color corresponding to the feature's road type return mapping[$feature.TextField]     As with option 2, this will include the unconfirmed features in the layer, but will not draw them:   ... View more