|
IDEA
|
I marked this reviewed but it might be a duplicate of Add support for SQLite/SpatiaLite and PostGIS geodatabases As Tom pointed out, we're already using this with disconnected editing workflows.
... View more
06-02-2018
09:33 AM
|
0
|
0
|
1609
|
|
IDEA
|
Have you looked into An overview of attribute rules—Geodatabases | ArcGIS Desktop ?
... View more
06-02-2018
09:22 AM
|
0
|
0
|
1760
|
|
IDEA
|
It isn't in the right-click menu for a layer, but it is possible to add Build Definition Query to the Quick Access Toolbar (or to the ribbon). When I click this, it automatically opens the Definition Query dialog for the highlighted layer:
... View more
06-02-2018
08:03 AM
|
0
|
1
|
2805
|
|
POST
|
Tagging the Imagery and Remote Sensing GeoNet space
... View more
06-01-2018
11:07 AM
|
0
|
0
|
1898
|
|
IDEA
|
Thanks, Sean. For now, make sure you don't overlook that you can create your own tabs and groups within your custom tabs with tools and commands that move through a workflow. Customize the ribbon—ArcGIS Pro | ArcGIS Desktop
... View more
05-31-2018
12:19 PM
|
0
|
0
|
3174
|
|
IDEA
|
Reviewed... the Re-order part of this idea is In Product Plan since that is built into Pro 2.2 already. Yay! Adding groups to the Quick Access Toolbar is not. Maybe you just want to change the idea now to focus specifically on adding groups to the QAT?
... View more
05-31-2018
12:03 PM
|
0
|
1
|
3174
|
|
POST
|
Duncan, I apologize that we're still seeing this issue. Unfortunately, I can say that it will not be fixed in 2.2. I can't provide a release in which this will be fixed - the most optimistic would be 2.3 at this point...
... View more
05-31-2018
11:52 AM
|
1
|
1
|
2605
|
|
POST
|
Hi Jami. I'll speak for Alycia. Yes! Please send examples of what you'd like to see in Pro. Cheers, Kory Customer Advocacy Lead - Desktop
... View more
05-31-2018
11:13 AM
|
0
|
0
|
3652
|
|
IDEA
|
So the key workflow thing here is that you're saying your switching between the Map and the Layout. You're doing that because obviously you want to edit. After editing an element ((Feature class or shapefile or annotation) and double-clicking or pressing F2 to confirm an edit can the element then be "unselected" by default? Right Now, he default is the element remains selected. Inevitably I return to layout view and notice it's still selected, have to re-activate the map, and clear it and then return to the layout. (I know I'll eventually change my behavior....) If you want to be in the layout, but then edit something, instead of switching to the map, you just Activate the map from the layout. In the image above, I'm in a layout, right-click > Activate. Then I get all of my map controls just as if I were working in the map (at this point, I am working in the map). I can then select, edit, whatever, and the Clear button is active on the Quick Access Toolbar. I realize that you're still requesting that once an edit is completed you want it to automatically be deselected. That's fine and the idea still stands as reviewed. However, let's consider what that would look like for a lot of editing workflows. 1. I create a point and I want to work with its attributes in the Attribute Pane. I create the point and it remains selected by default so that I'm able to continue working with that feature's attributes. 2. If the default were that once a feature is created, the selection is automatically cleared, I have to finish the feature, nothing shows up in my Attribute Pane, and then I have to reselect the feature in order to be able to populate attributes.
... View more
05-31-2018
08:11 AM
|
1
|
1
|
2935
|
|
IDEA
|
Sean, what version of ArcMap are you using? Editing points, lines, polygons? The idea is fine, I'm just exploring the ArcMap equivalency aspect. I've tried with points and polygons. When I complete either, they remain selected in ArcMap 10.6. When I click Editor > Save Edits they remain selected. One thing you could do is add the Clear Selection button to your Quick Access Toolbar. Let me know about what I'm missing about your ArcMap clicks. Thanks
... View more
05-30-2018
12:33 PM
|
0
|
2
|
2935
|
|
POST
|
Right. So you're seeing what I see and this is the issue that we are aware of. Both of your layers have the same name. If the layers are named differently, this isn't an issue.
... View more
05-29-2018
08:56 PM
|
1
|
0
|
3841
|
|
POST
|
Dan, with both tables open side by side like you have them, make sure you have no selection in the table on the left. Select only one record in the table on the right. Open Calculate Field by right-clicking the test field from the table on the left (there is no selection on this table). With the Calculate Field tool open, NOW switch the input layer to the other table (table on the right where you have a selection). We think we should now be calculating only the selected record in the table on the right. Calculate. What happens?
... View more
05-29-2018
03:42 PM
|
1
|
5
|
3841
|
|
POST
|
I'm glad that you can't reproduce this. I don't think the version is important here. I could reproduce what I outlined above in 2.x (and probably in 1.x if we needed to prove it) because this is a known issue with layers in the Contents pane that have the same name. We would need a reproducible case of this happening with layers that are named differently in the Contents pane, because that is not something we're aware of and is not something that we've been able to reproduce. Please do follow up here if you can show us a way that that happens. Thank you!
... View more
05-29-2018
03:18 PM
|
0
|
8
|
9380
|
|
POST
|
This is a known issue when more than one layer has the same name in the Contents pane which is why the statement "aliases don't seem to matter" is critical. I cannot reproduce this when the layer names are different. Let me walk you through my testing: In the screenshot below, I want to calculate the subtype for record 3. I right-click the subtype field > Calculate Field Then for some reason I decide that I want to calculate record 1 to equal Medium (subtype 2) in my other table, for the other layer, so in the tool, I switch to points:2, and calculate to = 2. Nothing happens – well, nothing appears to happen but what actually happened was that record 3 in points:1 already equals 2 so it was calculated to the same value: This seems to be because the tool is still referencing the selection from the first layer on the left. Because even though I’m now referencing points:2 in the tool, and record 1 is selected, if I now set that to equal 1 (should change record 1 to Small in the right-hand attribute table) it calculates it for points:1 This is the scenario that we know about. I haven’t seen this happen when the layers are actually named differently. Please either provide a reproducible case with step-by-step instructions and screenshots like above where you have different layer names, or open a case with technical support to fully investigate and report the issue. Thank you!
... View more
05-29-2018
01:57 PM
|
1
|
10
|
9380
|
|
POST
|
Jill, we don't have any other reports of ECW failing after the 2.1.2 update. It would be best to open a case with technical support to investigate. Thank you.
... View more
05-29-2018
01:31 PM
|
0
|
0
|
1872
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 11-17-2017 07:44 AM | |
| 1 | 08-25-2023 08:42 AM | |
| 2 | 4 weeks ago | |
| 9 | 05-15-2026 03:23 PM | |
| 1 | 04-30-2026 03:55 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|