|
POST
|
Going just off your description: select all stormwater inlets that intersect the SinkDA polygons, then select all SinkPoly polygons that intersect the previous selection. Only the inlets that hit a SinkDA will be selected first, so any SinkPoly selected next must be one that shares an inlet with a SinkDA.
... View more
02-10-2025
11:34 AM
|
1
|
1
|
921
|
|
IDEA
|
This would be a fantastic addition, our team occasionally has projects where many line features run tightly parallel and it can be tough to keep each feature's popup title distinct, especially when it's impossible to test the final output without saving the map, refreshing Field Maps etc. etc.. Adding a word wrap option in the designer would be fantastic; letting tablet users resize the feature selection pane would also be nice. As a workaround, updating the symbology so that more info is captured in the polygons themselves might help here. Just eyeballing the example above, the plant species could be used as the fill color or perhaps a point fill symbol per species. That would leave plenty of room for the polygon tag.
... View more
02-06-2025
11:22 AM
|
0
|
0
|
2215
|
|
POST
|
If the subsequent questions are identical then a select_one communities with a matching choice list is all you need. Each survey feature will have that community logged so you can aggregate and pivot easily. If there's differences in the questions based on the community, then things get tricky. If it's the same field set but different choices/constraints/etc. then you can use tools like cascading selects or conditional statements in constraints (e.g. . < if(${community} = 'San Francisco', 80, 40)). If the fields change between communities this will make the analysis more difficult as each community has to be treated differently but this is easy to do in the survey form, just use a condition in the relevant column to only show the correct fields for each community.
... View more
02-06-2025
11:06 AM
|
1
|
0
|
673
|
|
POST
|
The official docs for ImportToolbox should cover that.
... View more
02-06-2025
09:21 AM
|
0
|
1
|
1407
|
|
POST
|
What Profile are you running this Arcade code in? If this was for a map popup, you'd be better off using FeatureSetByName with the $map global to reference the other layers. For anything more complex, the Playground is the only way I know to test your expressions. Unfortunately the Playground can only access public data, so you'll either have to hunt down a set of public data that's close enough to your data, or create test data from scratch using the FeatureSet function. For what it's worth, I get the same "Verify test data" error in the playground so there might be a chance everything's working except accessing the data from AGOL, replacing that with test feature sets will help you isolate that issue.
... View more
02-06-2025
09:17 AM
|
1
|
1
|
1573
|
|
POST
|
To call the function "pdf" in the file "ExportPDF.py" in the folder "//spatialfiles2.bcgov/work/FOR/RNI/DPG/!Tenures/Templates/ExhibitA.Pro/Python" the technique is: import sys
sys.path.append(r"\\spatialfiles2.bcgov\work\FOR\RNI\DPG\!Tenures\Templates\ExhibitA.Pro\Python")
from ExportPDF import pdf
... View more
02-05-2025
04:44 PM
|
1
|
3
|
1461
|
|
POST
|
You can run Excel to Table to an intermediate table, then tweak the schema as needed, then copy that to the final location
... View more
02-05-2025
03:15 PM
|
1
|
1
|
1068
|
|
POST
|
Getting data from another layer or table like that isn't allowed in label expressions to avoid performance issues. If you have access to Attribute Rules you can calculate a color every time the call sign changes and store it in a field, or even calculate the entire label ahead of time. If not, you can write a lookup table into the label expression and update it by hand as new data comes in. Something like: var color = "red='128' green='128' blue='128'";
var color_red = "red='255' green='0' blue='0'";
var color_white = "red='255' green='255' blue='255'";
var lookup = {
"A1": color_red,
"A2": color_red,
"B1": color_white,
"B2": color_red
};
var cs = $feature.call_sign;
if (HasKey(lookup, cs)) {
color = lookup[cs];
}
return `<CLR ${color}>${cs}</CLR>`
... View more
02-04-2025
11:01 AM
|
0
|
0
|
744
|
|
POST
|
I'll admit I didn't test this thoroughly but everything seemed to work in the ArcGIS Online map viewer. Field Maps has its own rendering engine so you'll have to do your own testing in there. Unless I've missed something, there's no way to configure this without Pro so you'll have to avoid symbology edits outside of there, so make sure everyone's happy with the rest of the symbols before you hit production. Good luck!
... View more
02-04-2025
09:18 AM
|
1
|
0
|
4906
|
|
POST
|
What version of Pro are you using? Manually created relationships that use GUID types used to be flaky but I'm on Pro 3.1 and I've created dozens of them with zero issues. Simply ensure the origin/parent item has GlobalIDs enabled and the destination/child item has a GUID type field. Then create the relationship class and pick the appropriate fields. Note that GlobalID to GlobalID won't work as the relationship can't override any existing values here.
... View more
02-03-2025
01:36 PM
|
1
|
0
|
2243
|
|
POST
|
If you have access to Pro you can try attribute driven symbology, I detail the basics in this thread.
... View more
02-03-2025
12:46 PM
|
1
|
3
|
4943
|
|
POST
|
I'm on the same version of Chrome and I can't get the AGOL Map Viewer to trigger that error. More concerningly, the bug referenced in that message has been fixed a decade ago. Try some other maps (even if it's jsut a basemap) and try using other computers, I have a feeling your old Quadro is bugging out a bit.
... View more
01-30-2025
01:12 PM
|
0
|
0
|
13922
|
|
IDEA
|
If you're already querying every web map in your org, why not build a comprehensive table? from arcgis.gis import GIS, Item
def build_layer_lookup(portal: GIS, query: str = "*") -> dict[Item, list[tuple[str | None, str | None]]]:
retval = {}
for web_map in portal.content.search(query, item_type="Web Map", max_items=10000):
retval[web_map] = []
data = web_map.get_data()
for layer in data.get("operationalLayers", []) + data.get("tables", []):
retval[web_map].append((layer.get("itemId", None), layer.get("url", None)))
return retval
portal = GIS("Pro")
lookup = build_layer_lookup(portal)
table = []
for web_map, layers in lookup.items():
for layer_id, layer_url in layers:
table.append((layer_id, layer_url, web_map.id))
... View more
01-30-2025
11:07 AM
|
0
|
0
|
1474
|
|
POST
|
That function returns a FeatureSet object which the popup appears to have trouble with. There's probably a way to turn that into popup friendly data, but chances are you just want one address's data or an aggregate of address data based on the feature selected. Try something like this: var addresses = FeatureSetByName($map,"Civic Addresses",['full_address'], false);
var filter_value = $feature.my_field;
var address = First(Filter(addresses, "full_address = @filter_value")); // Replace with a proper SQL statement
return address.full_address
... View more
01-29-2025
04:59 PM
|
0
|
0
|
732
|
|
POST
|
Does the tool work better if you add that feature class to a map as a layer, then use the layer specifically? I've found using Select By Attribute/Location on feature class paths is flaky.
... View more
01-29-2025
04:49 PM
|
1
|
0
|
1252
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Thursday | |
| 2 | Thursday | |
| 1 | Thursday | |
| 2 | a week ago | |
| 1 | 2 weeks ago |
| Online Status |
Offline
|
| Date Last Visited |
Friday
|