Latest Contributions by BobSas

Yes, it is a deplorable business model, especially considering ESRI's market share and that it is a billion dollar corporation. There are numerous similar comments in this and other threads. ESRI's beta program will continue to drive us into the open-source beta community where we have more flexibility and where our time/skill investment is paid for by having free-of-cost software that is cutting-edge (even if buggy); it's ridiculous that there is not even a discount for ESRI beta testers. I am sure that many of us are in the consulting business and not in government agencies; we can simply educate our clients about QGIS and take paid software out of the contract and deliverable requirements if we so desire. We are also looking at more and more young GIS professionals that have the ability to code, which gives the industry even more flexibility... many consulting firms are moving away from software interfaces and towards code... so the UX in ArcPro will need to be so inviting that people who write code want to interact with software again... and people who don't write code won't give up on a buggy, slow and inconvenient software interface. I guarantee there are far more GIS users taking python courses than ESRI certification courses at this point.  ... View more

Sean, this captures things nicely. My concern is that ESRI has not defined what "Pro" means... currently it seems to mean that ArcGIS Pro is for "debugging Pro's" who are more adept in computer science than geographic information science.  ... View more

Specifically, as best I can detect, the slowness occurred because of an active layout consisting of a mapseries of 60 sheets with 3 dynamic maps and 15 fields of dynamic text per sheet. The issue was not actually because of undo edits in geoprocessing but in updating those edits into too many dynamic layout elements.  ... View more

Yes, the issue seems to occur with too many maps/layouts open in the same project.  ... View more

Calculate field > enable undo, resulted in an order-of-magnitude increase in processing time on the same file, with an almost identical operation.  "Enable undo" turned on took 24 minutes to run... and 32 seconds with "enable undo" turned off. What can be done so that "enable undo" becomes a usable option that isn't so expensive for efficiency? ... View more