Latest Contributions by Bud

@SteveLynch Yes, good point. If I understand correctly, Find Identical and Delete Identical don't let me prioritize rows using rank fields. ... View more

Related: An idea that's similar, but it's for spatial joins, not tabular joins: Spatial Join — "One-to-one (ranked by field)" join operation Idea: Consistent one-to-one/one-to-first wording in GP tools ... View more

A ROW_NUM pseudo column would also help with Join — Control what related record gets used. In a FGDB database view: ORDER BY on the grouping ID/common ID field, then on the field that we want to prioritize for the one-to-first join, so that the desired row is at the top of each grouping. Reason: one-to-first joins use the related record that has the smallest object ID. Replace the real OBJECTID field with a fake/new OBJECTID using ROW_NUM. ... View more

Possible workarounds: Since one-to-first joins use the related record that has the lowest OBJECTID, we could consider sorting the rows for each grouping/common ID, along with generating a new OBJECTID on the sorted data, using techniques like: Query layer (enterprise geodatabases only) (untested) select cast(rownum as int) as objectid, --Fake OBJECTID. Uses sorted subquery. a1, b1 from (select a1, b1 from table_1 order by a1, b1 desc) Database view (mobile or enterprise geodatabase; file geodatabase SQL is likely too limited) (untested) Sort geoprocessing tool (static output) Other? Python?   ROW_NUMBER function in FGDB SQL https://community.esri.com/t5/arcgis-pro-ideas/row-number-function-in-fgdb-sql/idc-p/1526715/highlight/true#M31739  ... View more

If not, you could submit an idea and link to it here. And link to this question in the idea. ... View more

Have you tried using geoprocessing tools for this? Something like the following (untested): Export your hosted points layer to a geodatabase feature class. Create new fields: POINT_X and POINT_Y. Populate using Calculate Geometry. Create more new fields: NORTH_X and NORTH_Y EAST_X and EAST_Y SOUTH_X and SOUTH_Y WEST_X and WEST_Y Populate the new fields with mappable coordinates using Calculate Field. The math is up to you. Using a database view (or any other method, such as manually loading data into a newtable), unpivot the data so that you have a row for each cardinal direction vertex, producing a sort of vertical table. Fields: POINT_ID, X, Y. Use the XY Event Layer tool to generate a spatial point layer of the X and Y vertices. Buffer the points. Dissolve using the POINT_ID field. Use the Minimum Bounding Geometry tool to create convex hull polygons from your buffered multi-part/dissolved point polygons. There are likely some details I've overlooked. But maybe the general idea is useful. Edit: Why do you want convex hulls? Why not a minimum bounding circle? A minimum bounding circle might eliminate the need for the buffered points step. https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/minimum-bounding-geometry.htm Or, better still, could you generate a circle using the longest cardinal direction measurement, using the point geometry as the middle of the circle? (Maybe using a simple technique like the Buffer tool.) If not, can you show us a screenshot of your data, demonstrating why the technique you described is better? (buffering the cardinal directions points and then doing a convex hull to make a polygon from them) ... View more

@JustinH, I wonder if you could adapt @jcarlson's Arcade field calculator answer to suit your needs: Field Calculation Between Related Tables - ArcGIS Pro It shouldn't be too hard. In Arcade, you can access related tables with the function FeatureSetByRelationshipName, and the result of that function is already filtered to the related records. You'd need some way to filter the result to a single feature. Here's me just grabbing the first record in a related table. var can2 = FeatureSetByRelationshipName($feature, 'Relate1', ['the_field_you_want'], false) // get the first feature var can2_feat = First(can2) // return value return can2_feat['the_field_you_want'] Just be sure you get the relationship name right in that first line, and ask for whatever fields you need to do your work. Assuming it's just pulling a single value, though, it's a pretty straightforward operation. Maybe instead of getting the First() related value, you could get the max() related value. Just a blind guess. ... View more

What kind of geodatabase? For example, Oracle 18c 10.7.1 enterprise geodatabase. What version of ArcGIS Pro? Related: 1:M Join to Pull feature with Specific Attribute information Can you confirm that a relate is indeed needed due to the underlying data structure being one-to-many? Or is the data structure one-to-one? Have you ruled out using a one-to-many join? What does the data look like? ... View more

Are you looking for a dynamic, ad-hoc querying mechanism? Meaning, you don't want to create multiple, messy static output FCs using assorted geoprocessing tools? And attribute rules, database views, and query layers don't apply because the data is in AGOL? (and those mechanisms would require extensive custom code anyway, which you stated in your related question that you want to avoid; and database views in file geodatabases aren't suitable due to limited SQL support) ... View more

Related: Generate geometry from expression ... View more

Related: Generate geometry from expression ... View more