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; } } }

Consistent extents notation in FC properties and GP tools

Bud

ArcGIS Pro 2.6.8:

In a feature class' properties, the extents textbox labels are full words: Top, Bottom, Left, Right.

But in geoprocessing tool parameters, the extents textboxes are denoted by arrows. And they are in a different order.

It would be easier to compare and copy/paste extents if they were displayed using the same notation and order. Could ArcGIS Pro be standardized so that the extents are displayed the same way in different parts of the application?

Finde mehr Beiträge mit dem Tag

Geoprocessing

Already Offered

Status: Already Offered

Kommentare

Bud

Also, in the feature class properties, the coordinates have commas. But the GP tool extents coordinates don't allow commas. It would help to be able to copy coordiates from the properties into a GP tool, without needing to manually remove the commas.

Could the commas (or no commas) be standardized?

Or, alternatively, automatically remove commas from number parameters in GP tools.

Bud

It looks like the extents parameters in GP tools were changed in more modern versions of Pro.

3.2:

However, they're still not consistent with the properties window. For example, the order of Top, Left, Right, and Bottom is different. So I think this idea still applies.

DrewFlater

Since this was labeled for Geoprocessing I'm marking this already offered as the Pro 3.2 extent control shows the order of the extent coordinates match what is used in Map Properties.

If you would like to recommend that feature class Properties be made consistent with the map extent and geoprocessing extent, please submit an Idea with the Geodatabase label.

You have also described that the geoprocessing extent and properties extent have different formatting with commas and other characters. For typical use of the geoprocessing extent, there isn't really a use case for manually copying and pasting of coordinates, as it has buttons to get the extent directly from the map, a layer, or geodataset. https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/basics/extent-control.htm

Unfortunately the Register with Geodatabase tool you pictured does not have an extent parameter, rather it is the type Envelope which doesn't support the same things as an extent. If you think it would be beneficial to have these easier ways of populating the extent for Register With Geodatabase, you could log another idea with the Geodatabase label to change the parameter type from Envelope to Extent.

Nehmen Sie an der Diskussion teil

Melden Sie sich an, um zu posten, Inhalte zu folgen und mehr. Neu hier? Kostenlos registrieren.