nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Loading/Processing: Show actual progress with percentage and estimated time

s.schuette_ct

When running Geoprocessing tools, always show us the actual progress in percent and the estimated time, until the process will finish. (Will it be 2 minutes or 63 hours? Do some calibration in the backend to generate a baseline for the machine ArcGIS Pro is running on and use it to calculate the processing time)

What I do not want to see is a "progress" bar that just moves from left to right and starts again on the left

(provide us feedback on what is actually happening, like listing where the process is at or at which stage Analyze is.)

or just a spinning icon when rendering a map for example without any indication whatsoever when the process will be finished (2s? several minutes?)

(UI loading)

Why is this needed?
It would help to tell if I should leave ArcGIS Pro running over night or if it will finish before I want to shut down my computer. I also want to know if it is worth waiting or if I should do something else in between.

タグ付きの投稿をもっと見る

Geoprocessing

Status: 開く

SheriNorton

When using the Select By Attributes tool for large vector data sets, the "Selecting" status message is stuck at 4% until the selection processing is completed. I would be very helpful to the progress percentage value increase gradually as features are selected to indicate actual progress.

SheriNorton

Excellent question! I'd extend this further to display smooth continuous progress rather than jumping from say 10% to 40% after a long delay - so really show the minute progress instead of chunks. Not sure why geoprocessing behaves this way.

AlfredBaldenweck

To be fair to the tool writers, this is the sort of thing that is manually decided. You decide either 1) How much each step of your process is worth or 2) to count how many of the N records or tables you're working on. Some things might not make sense when you try to quantify them.

That's probably where the 10-->40% jump comes from; whoever was building it decided that Step 1 was about 10% of the process but step 20 was about 30% of the work.

会話に参加する

投稿、コンテンツのフォローなどにはサインインしてください。初めてですか？無料で登録しましょう。