Skip to content

Conversation

@sijandh35
Copy link
Contributor

Fixes #13885

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

For all pull requests:

  • Confirm you have read the contribution guidelines
  • You have sent a Contribution Licence Agreement (CLA) as necessary (not required for small changes, e.g., fixing typos in the documentation)
  • Make sure the first PR targets the master branch, eventual backports will be managed later. This can be ignored if the PR is fixing an issue that only happens in a specific branch, but not in newer ones.

The following are required only for core and extension modules (they are welcomed, but not required, for contrib modules):

  • There is a ticket in https://github.com/GeoNode/geonode/issues describing the issue/improvement/feature (a notable exemption is, changes not visible to end-users)
  • The issue connected to the PR must have Labels and Milestone assigned
  • PR for bug fixes and small new features are presented as a single commit
  • PR title must be in the form "[Fixes #<issue_number>] Title of the PR"
  • New unit tests have been added covering the changes, unless there is an explanation on why the tests are not necessary/implemented

Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.

@sijandh35 sijandh35 self-assigned this Jan 16, 2026
@cla-bot cla-bot bot added the cla-signed CLA Bot: community license agreement signed label Jan 16, 2026
@sijandh35 sijandh35 requested a review from giohappy January 16, 2026 06:52
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @sijandh35, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces comprehensive support for Cloud Optimized GeoTIFF (COG) remote layers within GeoNode. It provides a dedicated handler that can validate COG URLs, extract essential geospatial metadata like CRS and bounding box using GDAL, and correctly register these remote resources. This enhancement significantly expands GeoNode's capabilities for handling and integrating external raster data sources efficiently.

Highlights

  • New COG Remote Layer Handler: A new handler, RemoteCOGResourceHandler, has been added to enable the import and management of Cloud Optimized GeoTIFF (COG) remote layers, extending GeoNode's data ingestion capabilities.
  • Robust URL Validation: The handler includes advanced URL validation for COG files, specifically checking for HTTP Range request support, which is crucial for efficient streaming and partial access of COG data.
  • GDAL-powered Metadata Extraction: It leverages GDAL's vsicurl functionality to directly extract essential geospatial metadata, such as Spatial Reference System (SRS/EPSG) and bounding box (BBox), from remote COG files without full download.
  • Support for Rotated Images: The implementation correctly calculates the bounding box for COG files that may contain rotation or skew, ensuring accurate spatial representation.
  • Comprehensive Testing and Integration: The new handler is fully integrated into the GeoNode resource handler settings and is accompanied by dedicated unit tests to ensure its reliability and correct functionality.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@sijandh35 sijandh35 marked this pull request as ready for review January 16, 2026 06:53
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces support for remote Cloud Optimized GeoTIFF (COG) layers by adding a new RemoteCOGResourceHandler. The implementation is well-structured, correctly validating remote COG files by checking for HTTP Range Request support and using GDAL's /vsicurl/ virtual filesystem to extract metadata. The handler also properly calculates the bounding box for rotated rasters. The changes are accompanied by a good set of unit tests. I have identified one critical issue in the new handler that could lead to an unhandled exception.

@codecov
Copy link

codecov bot commented Jan 16, 2026

Codecov Report

❌ Patch coverage is 83.75000% with 26 lines in your changes missing coverage. Please review.
✅ Project coverage is 74.22%. Comparing base (5ce993c) to head (58eb93f).
⚠️ Report is 50 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #13887      +/-   ##
==========================================
+ Coverage   74.07%   74.22%   +0.14%     
==========================================
  Files         932      946      +14     
  Lines       55720    56609     +889     
  Branches     7522     7669     +147     
==========================================
+ Hits        41277    42016     +739     
- Misses      12794    12901     +107     
- Partials     1649     1692      +43     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@sijandh35 sijandh35 marked this pull request as draft January 16, 2026 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed CLA Bot: community license agreement signed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support for Cloud Optimized GeoTIFF (COG) remote layers

2 participants