Latest Contributions by Geographic_Mythos

Presently, when you fire up the Enterprise Patch Updater for Server or Portal, there are limited settings available. You can choose a Proxy, or some basic installation directory locations. Due to numerous security reasons we have internally, we would like to limit where the Patch Updater is allowed to get these updates from. Without going into specifics, we have a need to be able to limit the countries of origin where these edge caches are being looked at to pull from. My option at the moment is to manually review the updates and grab the appropriate ones that I need (as this is still unblocked). Is there a way we can introduce some method to limit where the Enterprise Patch Updater gets its patches pulled from? ... View more

We've been expanding our Parcel Types recently to include several layers for Administrative Boundaries now that we are working with 10.9/2.8. In total, we are adding an additional 18 types to our Fabric to support both Jurisdiction Boundaries, as well as their Annexations. Adding a Parcel Type works as you would anticipate. Input a Fabric, name a Feature, check the Admin Boundaries box, and you get two feature classes and their respective relates and Topology. What is not working for me, and perhaps for all of you as well, is if you are going to then prime and load your existing data into this newly created set of features. Since none of your existing fields in your data are going to be present when you first create these new features, you have to step out of the Add Parcel Type, and then go into Design and add those fields. If you were only adding one feature class, this would likely not be a big deal. If you are adding more than a couple, doing this process repeatedly adds a considerable amount of time to creating the Parcel Types you need. I have two suggestions/enhancements to this process. Allow the ability to select a Feature Template from an existing Feature Class, or allow the ability to add fields before Add Parcel Type executes. ... View more

In ArcMap, the Traverse grid allowed certain curve parameters before keying in the data. I'd like an option to use the "Classic" interface of the Traverse Tool for ease of working with curve data, instead of typing in various "shortcut" abbreviations while entering curve data. I've added the ArcMap Traverse window with one of the curve options for reference as an attachment. ... View more

在ArcMap,遍历网格和包裹织物grids did not auto-commit data every time I entered a new row in the Traverse. I would like the option to pause the auto-commit while entering the Traverse so that I could enter all the information before it draws. There are several members of my team who are rather proficient in entering Metes-and-Bounds, and this longer pause during the auto-commit is adding significant time to their keying of those descriptions. Imagine writing a COGO distance, then waiting 5-10 seconds for the line to make the loop back and forth from the database/feature service. Then do this again for dozens of lines. If you were to type too quickly, you end up creating mistakes that you then have to go back and edit, again, and still wait for the commit. Barring that, have the Traverse draw data locally instead of sending the information back to the feature service, the same way that the Links and Anchors do during an Alignment so that the grid works faster. ... View more

Larger edits in Branch Versioning workflows. These seem unavoidable when working with larger amounts of Land Records data. Think about what goes into making a subdivision for a moment. Create Subdivision lines. Build a Subdivision polygon from those lines. Points get created from these first two. Create Lot Lines. Build Lots. Points get created here as well. Duplicate Lots to Parcels (assuming they are the same of course.) This creates more lines, and points. A record is being generated if you are working within one in a Parcel Fabric. Don't forget about all those attributes you need to update! Now imagine you did this for 100 lots or more in this subdivision, and that you are not the only person working on similar projects within your Enterprise. When you have larger transactions like this one occur, things tend to get locked up when you send off for Reconcile/Post. If you have 5-10 people do this, the fact that they happen in a synchronous fashion, timeouts against the service start to occur, even if you have them set out as far as 600 seconds (10 minutes). No one likes to lose hours of work! If the reconcile/post became asynchronous, the risk of losing work could be greatly diminished. Barring that, is there any way that the Reconcile/Post can be done faster than it is currently? Please make the Reconcile/Post Process faster or asynchronous! ... View more

As I am sure many of you doing edit workflows in Pro are aware by this time, you get a status window when you Reconcile back. For whatever reason, there is no window for this when you Post. Leaving you with only three ways I know of something is still happening in the system. Look for the spinning wheel. If you look down at the bottom right of the screen for pausing or refreshing the map, you can see that the wheel is turning during longer Post-backs. Once a Post-back has gone through, the Map will flicker. Be an admin in your respective RDBMS environments, and look for long running transactions. This works for me just watching for Active Expensive Queries in SSMS, but there are likely similar methods for Oracle and PostGRES that I do not know. Please show a status Pop-up like you do for Reconcile. ... View more