In an SQL Expression or a database view on a file geodatabase:
If I understand correctly, we can't access the XY coordinates of a point feature using SQL.
For example, something like this:
x_coord(shape) --would resolve to 665,478.140 meters
Could that functionality be added as a function in the FGDB engine/SQL syntax?
I'm aware that a workaround would be to store the X and Y coordinates in static fields in the FC via a calculation attribute rule. But it would be a lot of work to implement that for all FCs in all FGDBs. Doing it in SQL would be better.