|
IDEA
|
For cases when ArcGIS Pro is thinking due to a slow process: If I click elsewhere in the application while it’s thinking, there will of course be a lag. But when it does finish thinking, it should honour that next position I clicked, not apply the click to the last thing that was selected, such as a selected layer in the table of contents. I believe other applications and operating systems behave in a more intuitive way: when lagging, the current mouse position is honoured. More information in this post — about layer properties changes being slow, and what happens when I click elsewhere: https://community.esri.com/t5/forums/postpage/board-id/arcgis-pro-ideas ArcGIS Pro 3.0.2
... View more
11-25-2022
06:00 AM
|
2
|
0
|
824
|
|
IDEA
|
In a layer's properties, when changing the layer's name/alias: When I hit OK to commit the name change, it takes two full seconds for ArcGIS Pro to think/commit the change. Two seconds might not seem like much, but for something as simple as a layer name change, I think it should happen sooner (immediately). Between the time when I hit OK and when it stops thinking, I've already started to do my next task, such as change the name of a different layer. But when I double click a different layer in the Table of Contents, it doesn't work as expected. Once it's done thinking, the application doesn't transfer focus to the next layer that I double clicked. Instead, the former layer's properties get opened, since that's technically the layer that is selected, which is confusing and frustrating. I think the situation would be improved if name changes happened faster. I also think double-clicking should apply to the thing/position I clicked, not the thing that is currently selected. I'm using ArcGIS Pro 3.0.2.
... View more
11-24-2022
11:53 PM
|
4
|
1
|
917
|
|
IDEA
|
If I understand correctly, there isn't a button in the Attribute Table in ArcGIS Pro for Selecting All Records. We can select all records by hitting the Switch Selection button, when no records are selected, which will select all records. But that's not very user-friendly; it took me a while to figure out how to do that. I think it would be better if there were a straightforward Select All Records button or menu option. Similar to what we have in ArcMap: https://desktop.arcgis.com/en/arcmap/latest/manage-data/tables/selecting-all-records-in-a-table.htm Thanks. ArcGIS Pro 3.0.2
... View more
11-24-2022
03:14 PM
|
9
|
3
|
7940
|
|
IDEA
|
When I open the Definition Query window, the comparison operator pick-list value gets truncated: I could click the pick-list or resize the window to see the full comparison operator name. But I think it would be better if it were displayed in full by default. Could the pick-list or window be widened by default to show the full comparison operator? Thanks. ArcGIS Pro 3.0.2
... View more
11-24-2022
08:10 AM
|
3
|
3
|
1629
|
|
IDEA
|
For non-GIS professionals, using ArcGIS Pro can be difficult. The two separate concepts of the layer legend/symbology vs. definition queries can be confusing. I think novices would find it easier if they could simply toggle attributes on/off directly in the legend in the table of contents. That would make basic data exploration easier for beginners. In this case, everything else was easy for the user, such as finding the data and adding it to the map. But doing basic filtering in ArcGIS Pro was cumbersome. They wanted to just check legend attributes on/off when exploring the data. But I don't think that's possible in ArcGIS Pro. Could Esri consider adding a checkbox functionality in the table of contents? Maybe the underlying mechanism would be: the toggled checkboxes would automatically generate a definition query behind the scenes. Related: Progressive Disclosure of Complexity (YouTube 22:57).
... View more
11-24-2022
07:35 AM
|
3
|
0
|
5687
|
|
POST
|
I used an ESRI competitor called GISCloud.com. It was surprisingly easy. Unlike AGOL, GISCloud supports WMS directly. Related: How to create a WMS Service to display a geo-reference image?
... View more
11-22-2022
01:48 PM
|
0
|
0
|
3545
|
|
POST
|
When idea A gets merged to idea B, does A’s kudos get automatically added to B?
... View more
11-21-2022
04:19 AM
|
0
|
1
|
1764
|
|
IDEA
|
For our notes, here's an example of your syntax working in SQL Server (the test has nothing to do with ArcGIS Pro): https://dbfiddle.uk/shBxoaUj
... View more
11-19-2022
05:12 PM
|
0
|
0
|
1000
|
|
IDEA
|
Related post: Definition Query SQL shouldn't autocomplete WHEN to WHENEVER
... View more
11-19-2022
05:04 PM
|
0
|
0
|
4520
|
|
IDEA
|
For what it's worth, your original syntax seems to work fine on Oracle tables in ArcGIS Pro, both on versioned and unversioned tables: FIELD1 = (case WHEN 1=1 THEN FIELD1 end) The brackets were just for legibility. They're not a subquery. It works without the brackets too: FIELD1 = case WHEN 1=1 THEN FIELD1 end Oracle 18c; 10.7.1 EGDB; ArcGIS Pro 2.6.8
... View more
11-19-2022
04:38 PM
|
0
|
0
|
4528
|
|
IDEA
|
In the Definition Query window in SQL mode: When typing the word “when “, it autocompletes to “WHENEVER”. I don't know what use case WHENEVER applies to, but 99.999% of the time we'd want WHEN, not WHENEVER. Example: I typed "field1 = case when ". Note the space at the end of "when ". It autocompleted "when " to "WHENEVER". That's not what I wanted. It changed valid SQL to invalid SQL. ArcGIS Pro 2.6.8. Related: Optionally disable SQL expression autocomplete
... View more
11-19-2022
04:30 PM
|
3
|
1
|
1207
|
|
POST
|
In the Definition Query window, is there a way to set the default mode to SQL? Instead of clicking the toggle every time I create a definition query? I'm using ArcGIS Pro 2.6.8
... View more
11-19-2022
04:24 PM
|
0
|
1
|
906
|
|
IDEA
|
I wonder if you could post a question on Stack Overflow or DBA Stack Exchange, with details like this: You are using software that has a limitation where using the CASE in the predicate directly in the WHERE clause expression doesn't work. So, is there a way to do what you want, using CASE in the predicate, but not directly in the WHERE clause? For example, could you wrap it in a subquery? A long shot: I wonder, is it actually a bug in ArcGIS Pro -- specifically a bug with how it handles definition queries on versioned data? Does it work on an unversioned table? I ask because I had a similar issue: Using Oracle SDE.ST_GEOMETRY functions in a defection query or attribute table doesn't work -- due to a bug with versioning in ArcGIS Pro. But if I wrap it in a subquery, then it works fine. Or if the data is unversioned, it works fine too. Use SDE.ST_GEOMETRY functions in Select by Attributes window Find multi-part features using SQL (ST_GEOMETRY) Esri Canada Case: 03080875 Bug Report: BUG-000150273 If you submit a case to support, and it turns out to be a bug, I suspect a bug would get fixed before an idea would get implemented,.
... View more
11-19-2022
04:02 PM
|
0
|
0
|
4544
|
|
IDEA
|
Interesting. I think I get it now. I hadn't seen CASE used that way before. I wonder why that doesn't currently work in ArcGIS Pro definition queries. If it's native SQL Server SQL, you'd think it would work. I don't see why ArcGIS Pro would treat it any differently than [WHERE] 1 = 1, or some other typical predicate.
... View more
11-19-2022
03:44 PM
|
0
|
0
|
4552
|
|
IDEA
|
I don't think I understand how you'd use that in a definition query. It doesn't have a predicate, does it? For example: WHERE A = B, or something like that. Would putting your logic into a subquery help? What database are you using? Doesn't the definition query use native SQL, meaning, it would support any SQL functionality that the database supports? I'd be interesting in knowing what the full use case is. Unrelated, but the notes in this idea might interest you: Training course on SQL in ArcGIS Pro
... View more
11-19-2022
03:11 PM
|
0
|
0
|
4562
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-20-2026 02:12 PM | |
| 1 | 03-19-2026 11:42 AM | |
| 1 | 06-03-2026 04:02 AM | |
| 1 | 03-18-2026 07:08 PM | |
| 2 | 3 weeks ago |