Skip to content

brasildata 0.1.29: INPE fire risk layer - #61

Merged
giswqs merged 1 commit into
opengeos:mainfrom
elpidioassinaturas:brasildata-0.1.29
Nov 11, 2026
Merged

giswqs merged 1 commit into
opengeos:mainfrom
elpidioassinaturas:brasildata-0.1.29

Conversation

@elpidioassinaturas

@elpidioassinaturas elpidioassinaturas commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Plugin: BrasilData (brasildata), elpidioassinaturas/BrasilData

What it does: this updates registry/brasildata.json from 0.1.28 to 0.1.29. Nothing else changes.

Unchanged: the permissions (edit, files, network), the minimum RustGIS (0.5.0) and the categories.

0.1.29: INPE fire risk

  • Fire risk (Meio físico › Queimadas): the monthly climatology of INPE's Fire Risk model (Programa Queimadas, model RF version 11, 2001 to 2025, 0.01°), from INPE's open data server.
    • It reads only the area's window of the month's GeoTIFF, as the GMIA layer does, so it needs a RustGIS that reads a remote window (rustgis-cli 0.6.0; the desktop from the release with feat(plugins): a plugin command's layer.addUrl with "bbox" goes to the app (#1330, part 2) RustGIS#1581). On an older RustGIS the command says so.
    • The window is put on the project grid (bilinear onto a finer grid, average onto a coarser one) and clipped by the area.
    • The colours are the method's five classes (minimum, low, medium, high, critical), as a stepped ramp.
    • The month comes from the command's dialog, a panel slider, or a script ("mes": 1 to 12); September by default.
    • The layout recipe adds a subtitle, a colour bar from 0 to 1 and a note with the classes.
    • When INPE's server does not answer, the message says so and asks to try again later.

Tested:

  • In rustgis-cli 0.6.0: the whole of Bahia in September and March, with a layout exported for each.
  • In a desktop build of RustGIS main with #1581 and #1723: the dialog, the month changed to August, and the layer on a 30 m project grid.
  • The unit tests pass, the smoke test passes in rustgis-cli 0.5.0 and 0.6.0, and the release asset's SHA-256 matches the entry.

Not tested in the web app: the fire-risk layer.

  • The entry's source.url is a release asset of the plugin's repository, and sha256 is that file's.
  • The plugin asks only for the permissions it uses.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated the listed BrasilData release from v0.1.28 to v0.1.29. The registry now reflects the newer release, so its displayed version is current. No other user-facing changes are included in this update.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The BrasilData registry entry now points to release v0.1.29 and uses the release’s updated SHA-256 digest.

Changes: BrasilData Registry Release

Layer / File(s) Summary
Update registry release reference
registry/brasildata.json
The download URL now uses release v0.1.29. The entry also uses its updated SHA-256 digest.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Feature

Possibly related PRs

Merge Risk: Minimal · up to 841a0

This updates the BrasilData registry entry to v0.1.29 with a digest that matched the published asset in an earlier check. No actionable merge-blocking risk was found.

Pre-merge checks: Passed 5

Check name Status Explanation
Title check Passed The title clearly identifies the BrasilData version update and its main feature, the INPE fire risk layer.
Description check Passed The description includes the plugin, purpose, testing details, release asset verification, and permissions checklist. It provides the information required by the template.
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Finishing Touches

Generate unit tests (beta)

  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

A rabbit checks the registry line,
A newer release looks just fine.
The digest matches, neat and clear,
v0.1.29 is listed here.
One quick hop, and updates are done!

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: b5c29104-9595-4f36-ad14-9a043349a8f0
Commits

Reviewing files that changed from the base of the PR and between 3afee2d and 841a073.

Files selected for processing: 1

  • registry/brasildata.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

@github-actions

github-actions Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

🧩 Plugin preview

Removed: the pull request is closed.

@giswqs
giswqs merged commit a31b156 into opengeos:main Nov 11, 2026
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants