Core development focused heavily on streamlining navigation and administrative workflows, marked by a major shift to a view-first architecture in the Explorer tool and direct database-driven theme customization features on the Landing Page.

The engineering team strengthened cross-stack system integration through automated role synchronization with Apache Superset and expanded the platform's utility belt with a new lightweight HTTP server.

GC Landing Page​

• Theme settings: Added a dedicated theme customization screen that allows setting the platform logo URL and login page background URL directly into the database via a new GC settings table on every VM[cite: 1, 2, 3]. This eliminates the previous barrier of accessing CapRover environmental variables and supports instantaneous auto-saving alongside a live visual preview.

• Roles / User management: Introduced the ability to completely remove a user from the platform to satisfy partner requests, expanding on the older approve/disapprove mechanics[cite: 1, 2, 3]. Additionally, refactored role permissions descriptions to utilize clear, non-developer terminology instead of technical routing jargon.

• Dark mode: Officially rolled out native dark mode support across the landing page UI.

GC Explorer​

• View-first architecture: Refactored the underlying database model and front-end interface to adopt a view-first workflow rather than a dataset-first layout[cite: 1, 3]. Users now define the visual layout type (e.g., map, gallery) prior to attaching specific datasets.
• Consolidated pages: Deprecated the standalone /config and /datasets application routes in favor of a centralized front-page dashboard[cite: 1, 2, 3]. Automated toast notifications and redirects guide users away from legacy URLs, saving administrative clicks.
• Gallery UI improvements: Upgraded the gallery view to an image-first/media-first format featuring an interactive carousel view for multi-media observations (e.g., CoMapeo datasets)[cite: 1, 2, 3]. Integrated explicit file download buttons to assist non-technical users who are unfamiliar with right-click browser downloads.

• Bugfixes / small improvements:
  • Prepopulated map configuration initializations with a default base map style (Satellite Streets).
  • Added formal parsing support for GeoJSON coordinates that explicitly contain elevation parameters ([lon, lat, elevation]).
  • Programmed the UI to automatically hide the base map selector component if only one style option is available.
  • Improved multi-column selection layouts within active data filters.
  • Added dynamic external Google Maps redirection links for logged alerts.

GC Scripts Hub​

• Dataset Uploader: Added an interactive dropdown selection utility to find existing datasets while typing. Background validation continues to handle collision logic by alerting users that new entries will append directly to existing datasets.

• Conditional inputs: Dynamically hide CSV-specific geographic coordinate mapping elements when uploading native spatial files.
• New formats: Introduced built-in support for the latest CoMapeo export configuration. Patched interpretation bugs concerning GPX XML document parsing.
• New Connectors: Deployed an official data connector script for EpiCollect5 to handle tracking requirements in Tanzania.

Superset​

• Role Synchronization: Permission mapping between Guardian Connector credentials and Apache Superset (e.g., Admin maps to Admin, Member maps to Alpha, Guest maps to Gamma).

GC HTTP Server​

• Static content delivery: Deployed a highly optimized, lightweight on-demand HTTP server to host custom static HTML and JavaScript single-page applications. The system allows partners to isolate legacy data views behind basic username and password restrictions.

GC Docs​

• New reference pages: Created new technical documentation covering landing page personalization, an expanded Superset cookbook with advanced SQL queries (e.g., converting text strings to timestamp fields), Mapbox style customization procedures, and supplemental tool profiles for the new HTTP Server and Wildlife Viewer.

GC Deploy​

• Terminal GUI: Introduced a modular terminal-based graphical user interface to simplify stack installations for system administrators and enable granular per-service log parsing.
• Uptime Health Check: Formulated a convenient gc-healthcheck Python automation script within the GCForge repository to instantly ping platform endpoints and detect silent service failures[cite: 1, 2, 3].

1. User Experience & Interface​

Landing Page Redesign and Usability​

The first page that you see in GC has received a complete overhaul to improve navigation and accessibility:

• The login page has been redesigned with a new layout, updated logos, and improved language picker functionality.
• Improved User Guidance: The landing page now provides clearer information on how to integrate data, including examples of compatible apps like CoMapeo and KoboToolbox, to assist new users.
• Accessibility: Swahili and Thai language support have been added to the platform.

Explorer Interface and Consistency​

The following updates were made to the GC Explorer tool:

• Visual Standardization: The platform's visual identity is now more consistent, with and uniform color usage and icon styling.
• Enhanced Feedback: Empty state screens for various views, such as the Gallery view, have been introduced to provide better feedback when no data is available, replacing previous blank screens.
• Alerts and Statistics: The Alerts Dashboard now allows users to download statistics that are filtered by the currently selected date range.

2. Data Handling and Connectors​

Data Performance Improvements​

• Data Loading Limit: To prevent performance issues when visualizing large datasets, a hardcoded limit of 10,000 records has been implemented for data visualization in GC Explorer. A toast notification now alerts users when this limit is triggered.

New External Connectors​

• Cyber Tracker Connector: Support for Cyber Tracker has been added to the GC Scripts Hub.
• GeoPackage Uploads: Support for GeoPackage file uploads has been added to accommodate workflows from QGIS and QField.

3. Engineering​

• Deployment Fixes: Deployment documentation has been improved to address common issues encountered during the installation process.

4. Documentation​

• A new guide for Local Contexts has been added to the documentation, providing instructions on project setup, label curation, and resource configuration within the Windmill tool.

What are Incidents?​

In the Alerts Dashboard, an incident is a new way to group related information together. Often, an event on the ground isn't just a single data point; it's a combination of different alerts and field observations that sometimes span over a long period of time.

This new feature allows you to bundle these disparate pieces of information into one cohesive package. Importantly, creating an incident is completely non-destructive —it does not change or alter your original source data. You can think of it like creating a music playlist or a digital photo album: you are simply curating existing items into a specific, named group while the originals remain perfectly intact.

Seamless Grouping and Selection​

We have designed the incident creation process integrated directly into your existing map view.

• You can group data entries together by selecting features directly on the map using tools like a bounding box, lasso, or by using shift-click to select multiple items.
• You can mix and match different types of data into a single group. For example, a single incident could be made up of one gold mining point and four monitoring corroboration points.
• Easy navigation: All your incidents are saved safely within the system. You can easily explore a list of everything you've created, click to activate one, or even copy a direct link to share a specific incident with your team.

Built-in Annotation and Detailing​

Once you have grouped your map items, we've made it simple to add crucial context.

• Standardized sidebar form: A clean, standardized form will appear directly in your sidebar, keeping your entire workflow contained within GC Explorer without needing external tools.
• Comprehensive details: You can customize your incident by adding specific information, such as the incident name, the type of activity occurring, the responsible party, and a description of the impact.

We believe this new Incidents workflow will significantly enhance how you organize, analyze, and report on the vital data you collect.

Introducing the New Guardian Connector Landing Page​

This page is your new central hub—your go-to destination for all things Guardian Connector. Accessible from your main Guardian Connector URL, this page provides direct access to all the services and applications you utilize within the Guardian Connector ecosystem.

Enhanced Permissions Administration​

We understand the need for self-sufficiency and immediate control over your team's access. Self-Service Management: Previously, creating new users and adjusting permissions required direct coordination with our team. We're excited to announce that you are now empowered to manage these aspects yourself. Direct Access: You can now access and manage your Guardian Connector users and permissions directly from your new Guardian Connector Landing Page, giving you immediate control over your team's access levels and data security.

New Features within GC Explorer​

The GC Explorer remains the core environment for your data analysis, and we've added powerful features to enhance its utility: Dataset Visibility Control: Within GC Explorer, you now have the ability to explicitly set your Dataset Visibility. This feature allows you to control which users or groups can see and interact with specific datasets, ensuring sensitive or proprietary information is appropriately protected while promoting collaboration where needed.

Enhanced Dataset Identification: To make navigating your growing data library easier, you can now enrich your datasets with essential identifying information. Within GC Explorer, you can add basic dataset information so you can spot them easily, including:

• A Descriptive Name: Replace generic titles with clear, recognizable names.
• A Detailed Description: Provide context and vital metadata about the dataset's contents and origin.
• An Identifying Image: Upload a representative thumbnail or image to quickly distinguish between different data sources at a glance.

We are really excited about these improvements and hope they will enhance your productivity and control within the Guardian Connector platform.

We look forward to a vibrant and productive new year, and one that finds us working closely together!