wxGUI: Implement structural group folders for Data Catalog elements - #2
Closed
saket0187 wants to merge 7 commits into
Closed
wxGUI: Implement structural group folders for Data Catalog elements#2saket0187 wants to merge 7 commits into
saket0187 wants to merge 7 commits into
Conversation
github-actions
Bot
added
libraries
module
GUI
raster
temporal
CMake
docs
translation
Python
markdown
tests
labels
- Added _popupMenuMultipleStds for multiple temporal dataset selections - Added 'Register maps' and 'Unregister maps' STDS options - Added 'Duplicate dataset', 'Rename dataset', and 'Delete dataset' options - Added 'Merge datasets' option for multiple STDS selections - Optimized t.connect background checks to prevent unnecessary scanning across all mapsets
…oss-mapset support - Add active mapset locks for --ui dialogs (Create STDS/Register/Unregister) - Enable cross-mapset execution for native background tasks (Rename/Delete) - Implement safe JSON parsing for g.mapsets search path check for Merge STDS option
- Removed options: Removed the 'Duplicate dataset' option and removed the standalone 'Display map(s)' method. - Updated map ID structuring: Upgraded t.*.list queries to fetch id,name natively and store the map_id. This ensures that maps registered in an STDS from other mapsets maintain their correct paths for basic functions. - Expanded STDS context menu: Added 'Plot timeline' (g.gui.timeline) and 'Modify metadata' (t.support) to the primary Space Time Dataset context menu. - Standardized map actions: Added a 'Copy name' option to STDS maps and fixed edge cases for 'Display layer' and 'Show metadata' by utilizing the new map_id fallback and safely creating cross-mapset environments. - Created a dedicated context menu (_popupMenuStdsMap) specifically for maps inside an STDS. This prevents users from accidentally triggering standard spatial tools (g.rename / g.remove) that desync the temporal SQLite database. - Added temporary UI icons: Replaced duplicate mapset placeholders with temporary STRDS, STVDS, and STR3DS icons in the Data Catalog treeview.
saket0187
force-pushed
the
datacatalog-group-mockup
branch
from
July 10, 2026 11:29
b0e24e6 to
09f8b8d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces hierarchical grouping for map layers within the DataCatalogTree. Maps are now logically organized into specific folders (Raster maps, 3D raster maps, Vector maps, and Spatio-temporal datasets) rather than sitting directly underneath the Mapset node.
For the UI visuals, I am currently using a clock icon for the "Spatio-temporal datasets" folder, and our temporarily created icons for the individual STDS items inside it.
Here is a demo video of the new structure:
Screen.Recording.2026-07-10.at.4.27.55.PM.mov
For comparison, if we use the standard default icons for the STDS items under that folder, it looks like this: