Support flatgeobuf in metadata explorer

[stefanocudini]

fix issues #2264

• adapt resource FlatGeobuf as Geonode datasets
• upgrade UploadPanel components for loading remote resource FlatGeobuf

flatgeobuf apply default geometryType for stiling

NOTE: this PR is in Draft because we waiting backend pass new attribute_set geometryType to apply correct Style.
Now the default style applied is for a GeometryCollection

A remote Flatgeobuf remote for testing:
https://flatgeobuf.org/test/data/countries.fgb

Open FlatGeobuf layer from Catalog:

fgb.catalog.mp4

Create new dataset use remote FlatGeobuf resource:

Peek.2026-02-18.16-28.mp4

[gemini-code-assist]

Summary of Changes

Hello @stefanocudini, I'm Gemini Code Assist¹! 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 significantly enhances the platform's capability to handle geospatial data by integrating FlatGeobuf as a supported remote dataset type. It streamlines the process of adding external FlatGeobuf resources by automatically identifying their type from URLs and ensures they are displayed with appropriate default styling. This expansion of supported formats broadens the range of data sources users can leverage within the system.

Highlights

• FlatGeobuf Support: Introduced support for FlatGeobuf (FGB) as a new remote resource type, allowing users to upload and manage FGB datasets within the platform.
• Dynamic Resource Type Detection: Implemented a new utility function to automatically detect the remote resource type (e.g., COG, FlatGeobuf) based on the file extension in the URL, improving the user experience during remote resource uploads.
• Default Styling for FlatGeobuf: Added logic to apply a default style to FlatGeobuf layers based on their detected geometry type, falling back to 'GeometryCollection' if not specified.
• Upload Panel Enhancements: Updated the UploadPanel components to include FlatGeobuf as a selectable remote type and made minor UI adjustments to the dropdowns for better presentation.

🧠 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.

Changelog

• geonode_mapstore_client/client/js/routes/UploadDataset.jsx
  • Added 'flatgeobuf' as a new option to the list of supported remote types in the UploadPanel.
• geonode_mapstore_client/client/js/utils/ResourceUtils.js
  • Imported createDefaultStyle from MapStore framework.
  • Extracted attribute_set from resource metadata to determine geometry type.
  • Implemented logic to configure FlatGeobuf layers, including setting a default style based on geometryType or 'GeometryCollection'.
• geonode_mapstore_client/client/js/utils/UploadUtils.js
  • Replaced isCOGFileUrl with a more generic remoteTypeByUrl function to detect resource types based on file extensions (e.g., .tif, .fgb).
  • Updated validateRemoteResourceUploads to utilize the new remoteTypeByUrl for automatic type assignment during validation.
• geonode_mapstore_client/client/js/utils/tests/UploadUtils-test.js
  • Replaced isCOGFileUrl test with remoteTypeByUrl tests.
  • Added new test cases for remoteTypeByUrl to verify correct detection of FlatGeobuf URLs.
  • Added a new test case for validateRemoteResourceUploads to confirm FlatGeobuf type assignment for .fgb and .flatgeobuf URLs.
• geonode_mapstore_client/client/themes/geonode/less/_upload.less
  • Adjusted the width of the .Select-control element from 85px to 116px.
  • Increased the font-size of .Select-menu-outer and .Select-value-label from 0.7rem to 0.8rem.
  • Modified the padding of .Select-value-label from 3px 7px to 3px 10px.
• geonode_mapstore_client/static/mapstore/configs/localConfig.json
  • Added 'flatgeobuf' to the list of supported remote resource types in the localConfig.json.

Activity

• No activity recorded yet.

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. ↩