Raster overviews in PostgreSQL/PostGIS databases are regular raster tables named o_…. If you have more than a few rasters in a database schema, the browser panel view is quite cluttered. As you rarely access the raster overviews directly as an user (I don’t know if there’s even a real use case for that), it would be nice to hide those from the browser panel.
Maybe the “hide path” feature could be extended to non-file datasources, including wildcards.
Even better would be to exclude any table listed in the view raster_overviews, so overviews are hidden even if they don’t use the standard name.
Feature description
Raster overviews in PostgreSQL/PostGIS databases are regular raster tables named
o_…
. If you have more than a few rasters in a database schema, the browser panel view is quite cluttered. As you rarely access the raster overviews directly as an user (I don’t know if there’s even a real use case for that), it would be nice to hide those from the browser panel.Maybe the “hide path” feature could be extended to non-file datasources, including wildcards. Even better would be to exclude any table listed in the view
raster_overviews
, so overviews are hidden even if they don’t use the standard name.Thanks for considering this idea!
Additional context
No response