|
IDEA
|
Agree - both or either idea would be handy. Lots of groups and maps that appear in multiple groups can be frustrating to navigate. Likewise, the full list of maps can be a lot to scroll through as well. Being able to filter by other types of categories would be useful.
... View more
09-17-2025
04:56 PM
|
0
|
0
|
418
|
|
IDEA
|
We have scenarios where a webmap is configured with a particular basemap for efficiency, but some users would prefer a different basemap for offline use. Currently the only way of keeping everyone happy is to provide 2 copies of the webmap with different offline basemap settings. Allowing the user to change to a different basemap from the basemap gallery at the time of download would be a handy function.
... View more
09-17-2025
04:44 PM
|
0
|
0
|
165
|
|
POST
|
In Model Builder, I want to clear custom Workspace variables in the Environment settings. To be clear, I want a model to run using whatever the default database/workspace of a given user is. The below screenshot shows a brand new model with a simple string variable in it) where I have Saved it without having touched the Environments. I then opened it and confirmed the pathways were pointing to my default gdb (as shown in the tool tip for Scratch Workspace). I then got a colleague to open the model and the Environments, and both pathways had changed to show her default geodatabase. I got her to manually enter a different pathway for the Current Workspace (%userprofile%\scratch.gdb) and save the model. I then reopened it and can see the updated Current Workspace pathway, but the Scratch one (left unchanged by my colleague) still reverted to my default gdb. How do I get the pathway that has been customised to go back to defaulting to the default gdb of any given user? Simply selecting the pathway and deleting it doesn't work - this just results in the current default in my project being put there and remaining hardwired for other users.
... View more
09-17-2025
12:12 AM
|
0
|
3
|
290
|
|
POST
|
Hi All. Has anyone else noticed that after upgrading to 3.5 (could be 3.4, but we skipped that version), that the Auto Layout function produces a less well displayed result? You can see in my screenshot below an existing model that was created with a previous version. If I open in 3.5 and click Auto Layout, it condenses all the groups, resulting in overlapping boxes which are harder to discern. And it's not just the grouping boxes that overlap, but they in turn also impinge on tools, resulting in no white-space around them (top row of tools for example). I can't figure out how to change this if it's a settings thing. But even if I can, it's still kind of annoying that it's happened.
... View more
09-16-2025
11:46 PM
|
2
|
11
|
991
|
|
IDEA
|
Good idea. This isn't a solution, but something that may help make life easier in the meantime. You can set bookmarks in the webmap which can be accessed by field staff when they are creating offline areas in the field. If you have lots of features in a feature service, you could try automating the bookmark creation. I generated the below script with Copilot, but it is UNTESTED. You could implement in a Notebook and schedule regular updates (it should overwrite all existing bookmarks each time it is run). from arcgis.gis import GIS
from arcgis.mapping import WebMap
from arcgis.features import FeatureLayer
from arcgis.geometry import Geometry, union
# --- CONFIGURATION ---
feature_service_url = "https://services.arcgis.com/your-org-id/arcgis/rest/services/your-layer/FeatureServer/0"
webmap_id = "your_webmap_item_id"
bookmark_name_field = "Name" # Field used to group and name bookmarks
point_buffer = 500 # Buffer distance in meters for point features
# --- CONNECT TO GIS ---
gis = GIS("home") # Assumes you're logged in via Notebook or ArcGIS Pro
# --- LOAD WEB MAP ---
webmap_item = gis.content.get(webmap_id)
webmap = WebMap(webmap_item)
# --- LOAD FEATURE LAYER ---
layer = FeatureLayer(feature_service_url)
features = layer.query(where="1=1", out_fields="*", return_geometry=True).features
# --- GROUP FEATURES BY NAME ---
grouped_features = {}
for feature in features:
name = feature.attributes.get(bookmark_name_field, "Bookmark")
grouped_features.setdefault(name, []).append(feature)
# --- CREATE BOOKMARKS ---
bookmarks = []
for name, group in grouped_features.items():
geometries = [Geometry(f.geometry) for f in group]
# Union geometries
dissolved_geom = union(geometries)
# Determine extent
if dissolved_geom.type == "point":
x, y = dissolved_geom['x'], dissolved_geom['y']
extent = {
"xmin": x - point_buffer,
"ymin": y - point_buffer,
"xmax": x + point_buffer,
"ymax": y + point_buffer,
"spatialReference": {"wkid": 102100}
}
else:
extent = dissolved_geom.extent
bookmarks.append({
"name": name,
"extent": extent
})
# --- UPDATE WEB MAP ---
webmap.definition["bookmarks"] = bookmarks
webmap.update()
print(f"✅ Added {len(bookmarks)} bookmarks to the web map.")
... View more
09-14-2025
04:59 PM
|
0
|
0
|
592
|
|
POST
|
Thanks for sharing! Certainly sounds like your passion for GIS has not waned but grown over time!
... View more
09-03-2025
08:54 PM
|
1
|
0
|
1107
|
|
IDEA
|
I'm actually having trouble understanding the request and how it relates to the replied roadmap item. The roadmap item itself is clear enough, but it's not what I think of when reading the OP's idea. To me it sounds more like you want to lock layers so that they can't be inadvertently changed to suit one Map Frame, which then impacts another existing Map Frame/Layout that uses the same source map? It should remain consistent across all layouts. Is that right?
... View more
09-02-2025
06:17 PM
|
0
|
0
|
673
|
|
POST
|
Ahhh - I see what you were trying to achieve. Not quite what I'm looking for. That Filter list you have created is static. It will only change if you open the Model Properties > parameters and update the list manually. I want the list to be generated dynamically depending on the values from a specified field in a feature class or table. For example, my feature class has a list of plantations. I want to be able to process data on one plantation selected from the list. Over time, more plantations are added to the feature class, but the list won't update to reflect that unless I do so manually. Not ideal when I'm building models for lots of different business units and the data changes regularly. Side note - that video you linked to is a great video though. I hadn't seen it before so will try watch it through to see what else I might be able to learn.
... View more
08-25-2025
06:01 PM
|
0
|
1
|
205
|
|
IDEA
|
In Model Builder, one of the core fundamentals is input parameters - being able to select a feature class, field, value, etc etc to feed into your model and do things. But one limiting factor seems to be that for Field and Value type parameters, you need to pre-author the value list (drop-down list) that can be selected from in the model parameters. There is no way (that I have been able to find out as documented here) to have these lists generate dynamically based on a predetermined or input feature class/table. IDEA: Add out-of-the-box functionality to Model Builder to generate dynamic value lists in Model Parameters based on a previously input dataset. The dataset may or may not also be a configurable input parameter. Use Case: When create a model where the input feature class changes, the list of fields and/or values may also then change, meaning you can't pre-create value lists in the Model Parameters. Even where an input feature class doesn't change and is no a parameter, the values in a feature class may change over time, meaning the Filter Value Lists are no longer representative of the dataset being filtered.
... View more
08-24-2025
06:11 PM
|
1
|
0
|
373
|
|
POST
|
Unfortunately no! I just retried some of the linked content and still nothing worked. I gave up in the end. Have checked and couldn't find an idea that reflected this need so have created one. Dynamic parameter Filter/Value lists in Model Buil... - Esri Community
... View more
08-24-2025
05:32 PM
|
0
|
4
|
1205
|
|
POST
|
Support ticket submitted to add support to the listed Bug and Enhancement requests above! UPDATE: Response from Esri Support (Australia) below. The slower performance observed in the Edit widget was attributed to querying all layers within the associated Web Map. This issue aligns with a previously identified defect (ENH-000175894), which was addressed in the ArcGIS Online June update. However, similar behaviour has been reported again in this case and a few others. As a result, a new defect has been logged to formally recognise this recurring issue with the Edit widget in Experience Builder. ENH-000178405 - Allow the Edit widget of ArcGIS Experience Builder application to load faster.
... View more
08-20-2025
05:14 PM
|
0
|
0
|
290
|
|
POST
|
Good work figuring it out. Sometimes, it's all down to how you phrase a question! Especially with so many similar terms in use across so many platforms and language groups.
... View more
08-17-2025
05:20 PM
|
1
|
0
|
493
|
|
POST
|
Have you tried Searching in the Attribute Table? Open the attribute table > click on the field you want to search > Ctrl + F > enter search term > Enter. Can then select all matching features returned if desired. Also, I assume you are currently using the Locate function like this? From what I can see, there is no way of changing this to the default setting unfortunately.
... View more
08-12-2025
12:30 AM
|
0
|
0
|
183
|
|
BLOG
|
@AlfredBaldenweck Yes! You're right! It could be made even simpler and more versatile. I'll update the original post to reflect this. This is in fact what I had hoped to achieve in the first instance. Thanks for the prod.
... View more
08-11-2025
07:24 PM
|
0
|
0
|
340
|
|
BLOG
|
I've been working on a problem lately, and discovered that there was no out-of-the-box way to achieve this. In short, I have 2 feature classes going into a Spatial Join, but the fields in those feature classes could change each time the model is run. The issue here is that the Field Map in the Spatial Join tool is static, and can only be updated by editing the model, running up to the Spatial Join, opening the Spatial Join parameters and resetting the Field Map to include additional fields, or remove those no longer present in the input datasets. This is obviously not ideal - Model Builder should be able to deal with this. Enter python script tools! With a bit of help from a certain AI that everyone seems to know of, I quickly had a python script that when loaded into a python script tool, would take the Target feature class and Join feature class (or as many input datasets as required), iterates through the fields in each and adds them to a Field Mappings object. This Field Mappings object is then passed as an output of the script tool and as an input Field Mappings parameter to the Spatial Join. This then dynamically updates the Field Map of the Spatial Join every time the model is run. Configuring the parameters of the python script to accept the multiple input datasets and output Field Mappings object, this tool was ready to be added to my model. In short, I now have a reusable tool that when added to any model, will generate a new Field Map for any GP tool that requires it (e.g. Export Features) import arcpy
# Get semicolon-delimited input feature layers
input_features = arcpy.GetParameterAsText(0)
# Split into a list of layers
layers = input_features.split(";")
# Create FieldMappings object
field_mappings = arcpy.FieldMappings()
# Add fields from all input layers
for layer in layers:
fields = arcpy.ListFields(layer)
for field in fields:
if field.type not in ['Geometry', 'OID']: # Skip geometry and object ID fields
field_map = arcpy.FieldMap()
field_map.addInputField(layer, field.name)
field_mappings.addFieldMap(field_map)
# Set output parameter (derived)
arcpy.SetParameter(1, field_mappings) This approach could be used to work with any tool that requires a Field Map (e.g. Export Features). Next time you have a problem with tools in Model Builder not quite doing what you need, fire up ChatGPT, Copilot or another AI helper and ask it how to make your process happen. Check the code it provides thoroughly because they do make mistakes, but it's a great way to get into the coding space when you just don't quite know where to start. ***Update*** - since originally posting this, I have simplified it as I had made things more complex that necessary. Also another risk with the AI helpers. They don't always point out that there may be easier ways of achieving a problem as they tend to focus on the problem through the narrow lens of the prompts you entered. Always ask if a solution can be streamlined or done with fewer steps.
... View more
08-11-2025
12:40 AM
|
3
|
2
|
775
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Thursday | |
| 1 | 08-24-2025 06:11 PM | |
| 1 | 3 weeks ago | |
| 1 | 10-08-2024 09:01 PM | |
| 1 | 06-05-2025 12:17 AM |
| Online Status |
Offline
|
| Date Last Visited |
Thursday
|