Latest Contributions by AndrewQuee

I have to admit that I had second, third and even fourth thoughts about making suggestions to the legendary @DanPatterson but I thought "well, there might be just the tiniest chance they may not know one of those things (I'm still find ing new features in Pro all the time) and this content may help someone who doesn't know."  The phrase "teaching your grandmother how to suck eggs" comes to mind. 🙂 I agree the way the favourite tools work isn't great - you will get more and more tools on there until you end up with almost a copy of the toolboxes.  I'm not sure why Esri got rid of the ability to build your own custom toolboxes of standard tools, that was actually pretty neat.  Something something feature equivalency, Esri? 😛 As another option, you can create your own toolbars with groups of favourite tools, but this doesn't seem much better than saving them into the GP pane.  I also can't find a way of turning the groups on and off.  I guess you could have one tab per GP toolset but that would lead to tabspam and I don't think that's really what you're looking for. "You do not have permission to upload images" - really, Esri?  Uploaded as video instead. ... View more

In Desktop you have always been able to make your own toolboxes and customise them to suit your needs, so you might have one toolbox for spatial geoprocessing, another for statistical analysis, etc. https://desktop.arcgis.com/en/arcmap/latest/analyze/managing-tools-and-toolboxes/adding-tools.htm#GUID-CA99C4ED-DB43-4038-8C2E-2099F173F3F0 In Pro, although you can still make new toolboxes, it looks like Esri has deprecated that functionality and they now cannot contain copies of built-in tools, only ones you make yourself (unless you copied the python source and duped them).  The new system appears to be either favouriting a GP tool, or adding it to the analysis banner pane.  You can also add tools directly to the access bar, but none of these appear to be project-based so eventually you will end up with dozens of tools pinned, which may not be what you're looking for. There's a third option I've seen done quite a bit in Esri demos and I use myself: Search tools history or toolbox.  Just like Windows Start search, throw the first couple of letters in there, then pick the result you want which will be in the top few returned.  In practise I actually find this far faster than bobbling through toolbox names as it learns what I use most frequently. ... View more

I don't want to be negative but Esri has form with wiping out all community content/resources every few years, leading to massive frustration as years of work/solutions/highlighted problems are irrevocably lost and we have to start again fro scratch.  Also sometimes legacy resrouces need to be revisited.  I know of projects still using VB6/VBA under ArcGIS 9... I look forwards to being pleasantly surpised this time, but we shall see. ... View more

Yes, this is exactly what we are doing now in Desktop and Pro business systems.  We were hoping to return to somehting more COTS-like and reduce development overheads is all.  Thanks for the clarification. ... View more

The move to a flatter versioning system is welcome because it almost all cases we have no requirement to have versions on versions on a version.  There's change required to production data in multi-user editing, and that's it, so just the one child version per change (which only lasts as long as the edit lifetime) is all we need.  In fact unraveling accidental grandchild versions is the only thing we do with the current multiple layer versioning system. The move to a service-oriented system is also welcome and a great innovation, allowing much greater flexibility, scope and wealth of applications working with enterprise data across the internet, especially important while staff and clients can both be working from home during COVID-19. One thing that is a concern though is we currently allow users to create, edit, reconcile and post their versions to DEFAULT (we use customisations to prevent direct editing of DEFAULT) but this seems no longer possible unless we make them feature layer owners or portal administrators. We'd like to retain the efficiency of self-managed editing with a minimum administration overhead with protected DEFAULT version.  But it's inadvisable leave it unprotected or to make all users of the service Owners and unsafe to make them all Portal Adminstrators just to be able to reconcile and post to DEFAULT.  We'd also like to remain as close to COTS as possible to deliver development and support efficiencies. What would be ideal for our workflow is if in Enterprise permission can be given to allow classes of users the ability to create, reconcile and post their versions to a protected DEFAULT branch version, but not edit the default version directly. ... View more

Sorry let me try English again on my post (not allowed to edit)     " took many times longer in Pro than using Catalog" and "... would hate to doing this on dozens of objects in a Catalog pane on multiple enterprise geodatabases" Had a similar case yesterday.  Create new map, open catalog pane, connect database, select four FC.  Add to map.  Simple, yes? Nothing happened.  Wait.  Wait.  Wait.  [30 seconds later] Ok this is not happening, can you even add multiple items to a map at once?  Do it again.   Wait.  Wait. Wait.  Nothing happens.  Do it again. Give up and start adding them one at a time. All of a sudden multiple copies of the same FC erupt onto the map! [2 minutes later] Um.. okay? ... View more

I had an 'entertaining' example yesterday.  Exported some simple FC's into a network folder.  Two groups of three same-named FCs, each with maybe 10K features, nothing special.  Call them A, B, C and A, B, C.  Takes about 10 seconds in Desktop.   Okay rename the first three so avoid conflict on importing the second group:  A1, B1, C1.  Wait.  Wait.  Wait.  Nothing happens in catalog pane.  Press refresh.  Names finally change.  Why do I need to manually refresh an object list?  I haven't had to do that since the bad old days of Bashing console and FTP! Okay, bring in new group and rename also to show different origin, A2, B2, C2.  Refresh.  Check names have changed.  Wait a few seconds for hamsters to catch up.  Refresh to ensure names have changed. Copy all six into local FGDB on my computer.  The second group copy with the original names!  Go back to the source location.  Names are changed there, but not on destination.  FGDB has A1, B1, C1, A, B, C *flip mousepad and close Pro* This is a really really basic, simple operation done on my own computer, and took about many times longer in Pro than using Catalog simply because I couldn't trust the processing tools to be doing the right thing at the right time.  I would hate to doing this on dozens of objects in a Catalog pane on multiple enterprise. ... View more