There is a tool for creating aggregation layers in enterprise geodatabases called
Make Aggregation Query Layer (Data Management).
Could that functionality be expanded to file and mobile geodatabases too? Since both file geodatabases and mobile geodatabases support GROUP BY, JOIN, etc. See SQL for reporting and analysis on file geodatabases.
The obvious challenge is the fact that query layers are only supported for enterprise geodatabases, not file and mobile geodatabases:
And I’m aware that equivalent functionality can be achieved by writing SQL in database views in file and mobile geodatabases. However, writing full-blown SQL SELECT queries in database views has limitations:
- Writing complex SQL takes time, is not very user friendly, and is prone to error for non-experts. Not all ArcGIS pro users have advanced SQL skills.
- We don’t always want to make views in geodatabases.
- Map layers are useful for temporary or one-off cases where you don’t want to create an object in the database. Whereas views can add clutter to the db.
- It’s not possible to modify a file geodatabase view’s SQL definition once it’s created. The database view needs to be deleted and recreated in order to make a change, which is cumbersome.
Mobile geodatabase views can only be modified using an SQL client, not using ArcGIS Pro.- Whereas I would think an aggregation layer would be modifiable.
And using geoprocessing tools that output static copies of data is not desired in many cases. Dynamic queries are preferred and often necessary.
As @TanuHoque mentions in the article: Make Aggregation Query Layer - a new geoprocessing tool to compute and view dynamic summary statisti..., aggregation layers are quite useful. It would be great if we could use them for FGDBs and MGDBs too.
