Latest Contributions by Bud

ArcGIS Pro 3.4.2 When editing a cell value in the attribute table, it would be great if there were a picklist in the attribute table that would insert common symbols into the cell text. For example, the degrees symbol. I'm aware that there are Windows keyboard shortcuts for symbols: Type the Degree Symbol like a GIS Pro. I think it would be more reasonable to get users to click a button compared to memorizing numeric keyboard shortcuts. ... View more

ArcGIS Pro 3.4.2 I have a layer in the Contents pane (List By Drawing Order tab) that is not selectable in the List By Selection tab. I want to easily make the layer selectable, while preserving other selectable layers, by right-clicking the Contents List By Drawing Order tab layer and choosing a new "Make Layer Selectable" option from the Selection context-menu section. I'm aware that if the layer is highlighted(has focus) in the Contents List By Drawing Order tab, then it will be automatically highlighted(has focus) in the List By Selection tab. That's useful, but I would rather make the layer selectable using the idea I described. I think that would be most intuitive for non-experts.     ... View more

ArcGIS Pro 3.3.5; Oracle 19c 11.3 EGDB; standalone tables: One-to-first joins are supposed to use the related record that has the smallest OBJECTID. Add Join The Join Operation parameter has three states to adjust the cardinality. The default is no value and will allow the data source to attempt a one-to-many join. The Join one to many option will work only on specific data sources that have an Object ID field. The Join one to first option will use the first match in the table, which may result in different outputs if the Object ID field is changed or the workspace the table is copied to changes. One-to-first joins are not case sensitive; one-to-many joins are case sensitive. If the joined table does have an Object ID, the first match will be the record with the lowest Object ID. In ArcGIS Pro 3.3.5, that seems to apply to file geodatabases, but not to Oracle enterprise geodatabases. Pro seems to be grabbing a different related record; it isn’t grabbing the lowest OBJECTID. My I.T. department is currently in the process of upgrading us from Pro 2.9.5 to 3.3.5 (10.7.1 EGDB to 11.3 EGDB). Are there any patch levels of 3.3.x that don't have this issue? Maybe we could pivot to a different patch level of 3.3.x. I ask because we were really looking forward to using the new one-to-first join functionality as a way of working around some of the issues we have in Pro that are related to one-to-many joins. It would be disheartening if we couldn't use one-to-first joins, since EGDB tabular analysis is a huge part of our business. ... View more

ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 EGDB and ArcGIS Pro 3.3.5; Oracle 19c 11.3 EGDB If I create a new FC via the Feature Class Wizard, then the new FC's alias is prefixed with the owner/schema/user name. Result: ENGINEERING.ROADS. That works as expected. However, if I copy a file geodatabase FC via Catalog and paste it into the enterprise geodatabase, the new FC's alias isn't prefixed with the owner/schema/user name. Result: ROADS. That isn't expected. As a result, ROADS is displayed as the item name in the Contents pane when the item is added to the map. I'm wondering if it would be more intuitive/consistent if Pro automatically put the prefix into the alias in the second scenario, just like the first scenario. ... View more

ArcGIS Pro 3.3.5; Oracle 19c 11.3 EGDB: In the attribute table, using a standalone table, it takes two clicks to navigate to the last row. Click "Move to End". All rows are loaded, but the attribute table does not move. Click "Move to End" again. This time, the attribute table scrolls down to the last row. ArcGIS Pro 2.9.5 doesn't behave this way. But I vaguely remember support saying somewhere that it's working as designed with two clicks in 3.x, so I'm submitting this as an idea.   ... View more

ArcGIS Pro 3.3.5; Oracle 19c 11.3 EGDB In the attribute table, I've used Select By Attributes to select some features in a line feature class. I click "Show Selected Records Only", then scroll right to view some fields that are further to the right. I want to continue viewing those fields on the right-hand side of the table. But instead of just viewing the selected records, I want to view all records again, so I click "Show All Records". The attribute table pauses for a second, then automatically scrolls to the left-hand side of the table. That's annoying/unexpected. Could that behavior be changed so that the horizontal scroll position persists after hitting "Show All Records"? For what it's worth, a workaround is to click a cell in the attribute table before clicking "Show All Records". It won't automatically scroll left in that case. ... View more

My I.T. department is upgrading us from ArcGIS Pro 2.9.5 to 3.3.5 (Oracle 18c 10.7.1 EGDB to Oracle 19c 11.3 EGDB). Users like me primarily use Pro for: Tabular data analysis in attribute table, joins, query layers Oracle EGDB feature editing and standalone table editing Schema/table design changes Linear referencing (no Roads & Highways) Simple spatial analysis like Select By Location Map exploration and producing PDF maps — lots of layers Are there any high-priority issues or gotchas that we should look out for? For example, in Pro 2.6.8, there was an issue where saving edits actually discarded the edits. And in Pro 2.9.12, linear referencing layers were profoundly slow; too slow too use. What about Pro 3.3.5? ... View more

ArcGIS Pro 3.3.5; File Geodatabase I have a roads FC and an events standalone table. The relationship of the underlying data is one-to-many (no relationship class). One road to many events via a common ROAD_ID field. I want to make a one-to-first join from roads to events. But I only want to join to events where the EVENT_STATUS='ACTIVE'. Creating an EVENT_STATUS='ACTIVE' definition query on events wouldn't be suitable because once the join is created, the filter will be applied by Pro after the one-to-first join is performed, not before. I need the filter to be applied before the join is performed, so that only ACTIVE events are joined. I don't want to make a copy of the filtered data; that's messy and causes confusion. And I don't want to use Make Query Table to pre-filter the data; the resulting filter isn't visible anywhere in Pro, so it isn't modifiable and confuses users (also, joining to query tables is slow). I would prefer not to create a database view each time I do tabular analysis like this in Pro; that would be cumbersome. I want to be able to edit the roads features/fields in the attribute table, as well as see fields from the events table, so a join is the only suitable option. It would help to have a more intuitive way to filter the related table prior to joining for ad-hoc, dynamic analysis.   ... View more

ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 EGDB (will be upgraded to Pro 3.3.5; Oracle 19c 11.3 EGDB soon) Background: I have inherited an unregistered database view (non-spatial). The view has some joins. select --cast(rownum as number(38,0)) as rownum_, cast(rownum as int) as rownum_, sn.rdsec, sn.ownership, sn.name, sn.from_, sn.to_, sn.boundary_rd, sn.boundary_juris, sn.sort, sn.surf_mater, sn.surf_width, sn.shold_type, sn.shold_width, sn.row_, sn.desrow, sn.platw, sn.environ, sn.fenviron, sn.tcyear1, sn.tcaadt, sn.aspd, sn.replac_surf_width, sn.class_op_grouped, sn.recon_activity, sde.st_length(sn.shape) as road_length, rs.length_assumed_only, sde.st_length(sn.shape) - rs.length_assumed_only as length_vs_assumed, sn.numb_lanes, sn.lane_km, sn.strad_wavg, sn.surface_condition_wavg, sn.surf_year, sn.base_year, sn.gran_year, sn.surf_age, sn.base_age, sn.gran_age, sn.det_model_constr_type, sn.next_forecast_activity, sn.next_forecast_activity_descr, sn.next_forecat_year, sn.last_forecast_activity, sn.last_forecast_activity_descr, sn.last_forecat_year, arw.replacement_cost from infrastr.strln_svw sn left join infrastr.ar_road_vw arw on sn.rdsec = arw.inventory_asset_id left join infrastr.am_excluded_roads_sd er on sn.rdsec = er.rdsec left join ( select rdsec, sum(evt_to - evt_from) as length_assumed_only from infrastr.road_assm_status where assm_status = 'A' group by rdsec ) rs on sn.rdsec = rs.rdsec where er.rdsec is null and (sn.aspd <> 'UNIMPROVED' or sn.aspd is null) and rs.length_assumed_only is not null   Regarding casting ROWNUM as an integer: cast(rownum as int) as rownum_, ArcGIS Pro is treating the ROWNUM_ column as a double: So ROWNUM_ can't be used as the unique ID when dragging the view from Contents to the map:   However, if I were to cast ROWNUM as a  number(38,0), then ArcGIS Pro would treat it as a long integer, which is good: cast(rownum as number(38,0))   Question: Why does Pro treat  cast(rownum as int)  as a double?     ... View more