Repository navigation
feat(imagery): spectral profile: chart and compare a multiband raster's bands at points (#1622) - #1645
Conversation
…'s bands at points The Workflows pane's Spectral Analysis section becomes a spectral profile: pick a raster of two bands or more, turn on Pick Points and click. Each click adds a point until it is turned off. Up to six points are drawn as lines, each in the colour of a numbered marker on the map. The x axis is wavelength (nm) when the file gives one for every band, in wavelength order, and band number otherwise. Hovering shows a band's name, wavelength and each point's value; a point can be taken off; Clear and Export CSV... (desktop, a row a band, a column a point; names guarded against spreadsheet formulas). Identify's pop-up on a pixel of two bands or more gets a Spectral Profile button that adds that pixel and opens the section. After GeoLibre's spectral profile (opengeos/GeoLibre#1818). Bands gain `wavelength` (nm), read from GDAL's metadata tag and the .aux.xml sidecar: CENTRAL_WAVELENGTH_UM (GDAL's IMAGERY domain), or `wavelength` / `central_wavelength` in the unit `wavelength_units` gives (with none, a value under 100 is micrometres). Items that aren't a length are said; read ones are no longer counted as band items not read. The GeoTIFF writers write them back, and the commands that copy band names (georeference, mosaic, clip, pixel editor, project) copy them too. `raster.spectral` takes `points` ([[lon, lat], ...], up to 1000) for a profile each; a point off the raster keeps its place with null values and is said. Every answer carries `wavelengths` when the file gives any. A zone is read before points, and points before lon/lat: what isn't read is said. Closes opengeos#1622. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
Walkthrough
Merge Risk:
|
| Check name | Status | Explanation |
|---|---|---|
| Linked Issues check | Scope: #1622 is the only direct linked issue. It has no parent or contextual issue. Evidence is the whole-PR summary (merge base 02006f3 to head 7018460). The incremental changes since the previous r… |
|
| Out of Scope Changes check | Each changed area maps to #1622 or gives direct support to it:- crates/data/src/raster/mod.rs and pam.rs: wavelength field, parsing, GDAL metadata writing, and loss reporting. - crates/analysis/src/w… |
|
| Docstring Coverage | Docstring coverage is 83.72% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentati… | |
| Description check | The description is thorough and covers the template's required areas. The Summary explains the change and its motivation: a Workflows spectral profile replaces the JSON readout, with data, engine, and… |
Full details: Linked Issues check
-
Explanation
Scope:
#1622is the only direct linked issue. It has no parent or contextual issue. Evidence is the whole-PR summary (merge base 02006f3 to head 7018460). The incremental changes since the previous reviewed head (3b1779f) were not read as a separate diff. The summary covers the whole-PR state, so the verdict uses it.Requirements, grouped by objective:
(a) Wavelength data [
#1622]: Band gains wavelength: Option<f64> in nm (crates/data/src/raster/mod.rs). pam.rs reads CENTRAL_WAVELENGTH_UM (IMAGERY domain, micrometres), the per-band wavelength and central_wavelength items, and wavelength_units, from the GDAL metadata tag and the .aux.xml sidecar. Units fall back to micrometres below 100 and nanometres otherwise. Out-of-range or invalid values are reported and not counted as unread. Data-crate tests are listed.(b) Writing and preservation [
#1622]: gdal_metadata writes CENTRAL_WAVELENGTH_UM for the written bands. warp.rs Canvas::finish copies band wavelengths to output bands (project). imagery.rs preserves or derives wavelengths for rebuild (georeference), resample, mosaic, clip and pixel edit. Workspace mosaic keeps a wavelength only when all images agree. Mosaic reports wavelength mismatches. The GeoTIFF writers write only one band or RGB; the author discloses this limit. The issue does not require more.(c) raster.spectral [
#1622]: accepts points (up to 1000) and returns profiles with {lon, lat, pixel, values}. Off-raster points keep their place with pixel null and a notice. All-off-raster input is an error. Every answer carries wavelengths (nm, null per band without one) and wavelengthUnit. Zone, points and lon/lat precedence is reported. Test spectral_profiles_at_points_with_wavelengths is listed.(d) Spectral profile view [
#1622]: spectralui.rs implements the Workflows section. It offers rasters of two or more bands and Pick Points until turned off. It keeps up to six colour-keyed samples, removes the oldest with a notice, and draws numbered map markers. The axis is wavelength only when every band has one, and band number otherwise. Hover shows band and point values. Points can be removed, Clear empties the chart, and desktop CSV export guards formula-like text. egui_kittest tests are listed.(e) Identify [
#1622]: a Spectral Profile button appears in the Identify pop-up for rasters with two or more bands. It adds the pixel and opens the section.Excluded items in the issue (chart PNG export, polygon mean signatures in the chart, STAC eo:bands wavelengths) are not implemented, which matches the issue.
Disclosed limit: a raster that shares its name with an earlier layer cannot be charted. Identify reports this, and the section lists it as left out. The issue sets no requirement for same-name rasters.
No unmet coding requirement is found in the available evidence. Remaining uncertainty: the incremental changes since 3b1779f were not read separately.
Full details: Out of Scope Changes check
-
Explanation
Each changed area maps to
#1622or gives direct support to it:- crates/data/src/raster/mod.rs and pam.rs: wavelength field, parsing, GDAL metadata writing, and loss reporting.
- crates/analysis/src/warp.rs: copies band wavelengths in Canvas::finish. This supports the issue requirement that project keeps wavelengths.
- crates/engine/src/cmd/imagery.rs and tests.rs: points extension, wavelengths in answers, mosaic mismatch notice (extends the existing band-name notice to wavelengths), and round-trip and spectral tests.
- crates/ui-egui/src/spectralui.rs (new), analysispane.rs, lib.rs, panes.rs: the profile section, its wiring, project-reset cleanup, and pick cleanup when the Workflows pane is not selected.
- mapview.rs: map markers, the Identify button, and a comment change that clarifies raster pixel identity for the Identify hook.
- ribbon.rs: the Spectral Analysis tooltip text.
- docs/user-guide/analysis.md and data.md: documentation of the new behaviour, which the issue scope lists.
No change is found that is unrelated to
#1622. The check rests on the whole-PR summary, not on a full diff read. Incremental changes since 3b1779f were not read separately.
Full details: Docstring Coverage
-
Explanation
Docstring coverage is 83.72% which is sufficient. The required threshold is 80.00%. 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 43 functions across 10 files.
Full details: Description check
-
Explanation
The description is thorough and covers the template's required areas. The Summary explains the change and its motivation: a Workflows spectral profile replaces the JSON readout, with data, engine, and app parts, and it links issue
#1622. The Testing section lists new tests, the commands run, and the failing tests with their causes. The UI evidence section is filled in with before and after screenshots, which the template requires for visible UI changes. The Related issue section says 'Closes#1622'. The description is long and includes implementation detail, but every template section is present with real content.
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.
A rabbit plots a curve of green,
Then adds a point beside the scene.
Each band finds its wavelength place,
Six samples hop across the space.
A CSV follows, neat and bright,
The chart keeps every mark in sight.
Code reviewBugs
Security
Performance
Quality
AGENTS.md
Not raised. Earlier concerns: none (no prior review threads). Confidence. The bugs are from reading the diff against the surrounding code. I did not build or run the tests. Change sizeCompared: the whole PR against main (merge base 02006f3 to PR head 1520b88).
|
📖 Docs preview
GitHub Pages takes a minute or two to publish a new commit. |
…w round 1) - A wavelength whose nanometres overflow or round to zero isn't a length: the result is checked, not only the value read. - Another length for a band that has one is said and left out, in the metadata tag and the sidecar; the same length under two names is one wavelength. A sidecar band now takes its first item that is a length, as the tag does, instead of stopping at the first item there is. - raster.spectral says lon and lat left out when a zone is read too. Its points are read in their own function. - The notice for bands a raster doesn't have says "names or wavelengths"; the user guide says an export writes the wavelengths of the bands it writes, and a long line is wrapped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Review round 1 (9889e1b), the summary's other points:
🤖 Addressed by Claude Code |
Code reviewEarlier reviews: 3 threads already on this PR, all marked outdated. The code now addresses each one: the silent second wavelength (now noticed), the finite check on the result (now Bugs
Security
Performance
Quality
AGENTS.md
I did not compile or run the tests (no shell here). The findings come from reading the diff and the surrounding code. Change sizeCompared: the whole PR against main (merge base 02006f3 to PR head 9889e1b).
|
…eview round 2) - raster.mosaic says an input whose bands have other wavelengths than the first's, as it says other band or class names: "band names, classes or wavelengths other than west's, which the mosaic keeps". - A wavelength item of the dataset's own (no band) is for no band: it is counted in the wavelengths left out, in GDAL's metadata tag and in the .aux.xml sidecar, instead of passed over. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Code reviewI read the full diff, the prior review threads and the code they touch. I found two inline issues in the wavelength reader, plus some minor nits below. Nothing I found is a crash or a wasm break. I did not compile or run the tests here, since this environment has no build tools. Bugs
Security
Performance
Quality (per AGENTS.md these may wait for the release quality pass)
AGENTS.md
Confidence
Left alone (already raised in prior threads): sidecar overriding the embedded tag without a notice (answered by the author, left for a maintainer); the mosaic notice, the wavelength overflow and rounding checks, the zone Change sizeCompared with
Largest changes:
|
…lionth differ (review round 3) - A sidecar's empty wavelength item is counted as not a length, as the metadata tag's already was. - Two wavelengths for one band are the same only within a millionth of a nanometre (what micrometres are read to), not a millionth of their length: 665 and 665.0005 nm are two, and the second is said. - raster.spectral says what it left out only once the run has read what it does: a run that fails says only its error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Review round 3 (4b987ce), the summary's other points:
🤖 Addressed by Claude Code |
Code reviewI read the full diff, the eight earlier threads, and the code they point at. The PR is well covered by tests and most earlier concerns are fixed in Bugs
Security
Performance
Quality
AGENTS.md
Already raised (left alone)
Change sizeCompared: the whole PR against main (merge base 02006f3 to PR head 4b987ce).
|
- A wavelength_units item in GDAL's metadata tag for a band past the most a raster has is counted in the wavelength items left out, as a wavelength for no band already is. - raster.spectral reads its zone parameter once; a stale comment in the Identify pop-up is corrected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Review round 4 (0b8ba0f), the summary's other points:
🤖 Addressed by Claude Code |
Code reviewBugs
Security
Performance
Quality
AGENTS.md
Earlier concerns not repeated (already raised in prior threads): the cross-source sidecar-over-tag wavelength conflict (open, the author declined it), and the threads on the mosaic notice, the invalid Change sizeCompared: the whole PR against main (merge base 02006f3 to PR head 0b8ba0f).
|
… in Identify (review round 5) - A band's or the dataset's wavelength unit given again otherwise is said and left out (the first is read), in GDAL's metadata tag and in the .aux.xml sidecar; the same unit again is nothing. - Identify's Spectral Profile button on a raster another layer shares its name with (case aside) says so instead of charting the other one's pixels, since commands find a raster by its name. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Code reviewI read the full diff, the staged AGENTS.md and the 11 earlier threads, and checked the surrounding code: the map click intake, the Identify pop-up, Bugs
Security
Performance
Quality (grouped nits, not posted inline)
AGENTS.md
Earlier concerns
Change sizeCompared with
|
Code reviewI found no new bugs that the existing threads don't already cover. Most of the substantive concerns on this PR were raised earlier and answered or fixed, so I left those alone. I checked the new Bugs
Security
Performance
Quality (left for the release quality pass)
AGENTS.md
Prior concerns left alone: 22 threads on this PR were already raised, and I did not re-raise any of them. Many were resolved in code. The open ones were answered and left for a maintainer. Change sizeCompared: the whole PR against main (merge base 0fd8302 to PR head 9734f95).
|
The first paragraph of wavelength_nm's doc had stayed above the new Unit enum, where rustdoc gave it to Unit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
On the github-actions review's quality point: 🤖 Addressed by Claude Code |
Code reviewI read the full diff (about 2,100 lines) and all 60-plus prior review threads, then checked the claims that matter against the source. Most concerns already raised in earlier threads are left alone (about 40 of them). The one new finding is posted inline. Bugs
Security
Performance
Quality
Never silent (AGENTS.md)
AGENTS.md
Prior threadsAbout 40 earlier concerns were left alone because they were already raised and answered, or resolved. I posted nothing again. Change sizeCompared: the whole PR against main (merge base 0fd8302 to PR head 4e7a4da).
Largest changes:
|
The notices for a sidecar or metadata tag that can't be read (pam.rs, geotiff.rs, both COG readers' tests) named only band and class names, or statistics, no-data and band names; wavelengths come from the same metadata and go with them, so they are named too. A broken tag with a wavelength in it is tested. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Code reviewI read the full diff, the 44 earlier review threads, and the surrounding code for the changed paths. I found one new low-severity issue (posted inline) and a few notes. I did not re-raise the 8 open threads (sidecar-over-tag precedence, duplicate-map identity, export band loss, the two-clicks-per-frame case, the restart-notice overwrite), which the author answered or left for a maintainer. The other 36 are resolved. Bugs
I checked these and found no defect: the band wavelength readers in Security
Performance
Quality
AGENTS.md
Change sizeCompared with
|
from_identify opens the section only when it isn't shown: ui.pane.workflows ends any map pick, so running it with the section already open turned Pick Points off. Switching section still ends it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Code reviewI found nothing new worth raising at high or medium confidence. I read the full diff, the surrounding code (the GDAL tag and sidecar readers in Bugs: none found. I traced the wavelength range and overflow checks, the first-kept and same-length merge rules, unit spellings, every Security: none found. Performance: nothing significant. While the section is shown, each frame does Quality: nothing to act on now. AGENTS.md
Earlier concerns: 45 threads exist (8 open, 37 resolved). I did not repost any. The open ones I agree with as the author left them: sidecar precedence over the embedded tag, duplicated-map identity, the export notice for dropped bands, and the restart notice erased on the next click. Change sizeCompared: the whole PR against
|
|
Screenshots: the PR body now uses GitHub attachments ( 🤖 Addressed by Claude Code |
Keeps both sides in crates/engine/src/tests.rs: the spectral profile tests and main's reload streamed-geometry test. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Code reviewI read the full diff, the 45 prior review threads (19 outdated), and the surrounding source. The new code is careful about hostile input: no Bugs
Security
Performance
Quality
AGENTS.md
Earlier concerns left alone: 45 threads, of which 19 are marked outdated. Of the open or accepted ones, the sidecar-overrides-tag precedence, the GeoTIFF writer's band loss, and duplicate-map identity were answered and accepted by maintainers. Change sizeCompared with the base branch (merge base f62c795 to PR head 2fffea2). The stats are not truncated.
|
A raster whose pixels failed to load was left out of the section's list without a word, so a failed six-band scene read as "Add a raster of two or more bands first". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Code reviewI found no bugs, security issues, or performance problems in the changed lines. I read the whole diff, the 46 earlier review threads, and the code they point at, and checked the cross-crate callers. I could not compile or run the tests here (no shell in this session), so the checks below are by reading only. Bugs: none found. Security: none found. CSV cells are guarded against formula injection, and the new Performance: none worth raising. Quality:
AGENTS.md: I checked the never-crash, never-silent, background-work, wasm-gating, translation ( Checked and ruled out:
Earlier concerns left alone: 46 review threads are in Change sizeCompared with
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Code reviewBugs: No defects found in the changed lines. I traced the wavelength readers, Security: None found. The CSV export guards names against formula injection and writes only to a user-chosen path. Performance: Negligible. The popup and section paths do a few Quality: Nothing new beyond the earlier threads. Never silent / AGENTS.md (1 finding, outside the diff, confidence medium-high on the mechanism, low severity): Earlier concerns: I left 47 existing review threads alone. They were already raised, answered or resolved, and I did not see new evidence against any of the answers. Change sizeCompared: the whole PR against main (merge base f62c795 to PR head ea39667).
|
A cloud-optimised GeoTIFF drawn in place said only band and class names were left for a window; a header with only wavelengths, which this PR now reads, lost them without a word. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Re the review summary: fixed in 29677ce. The tile-layer notice in 🤖 Addressed by Claude Code |
Code reviewI found no new defects in the changed code, so there are no inline comments. I read the full diff, the 47 existing review threads, and the surrounding code for each changed path. I could not build or run the tests here, so compile, clippy and test results come from the CI run, not from this review. Bugs: none new.
Security: none. The new Performance: none worth raising. Each Pick Points click reads one point, and the 1000-point path is bounded and cheap per point. Quality (non-blocking, for the release quality pass): AGENTS.md:
Prior reviews: 47 threads, all resolved. I left all 47 alone and re-raised none. Several were settled by maintainer decision: sidecar precedence over the embedded tag, export notices for other writers, duplicated-map identity, and the empty-restart message. Change sizeCompared: the whole PR against main (merge base f62c795 to PR head 29677ce).
|
|
@coderabbitai approve |
giswqs
left a comment
There was a problem hiding this comment.
Thanks @elpidioassinaturas, this is a careful, well-tested piece of work and does what #1622 asked: wavelengths read from the GDAL tag and the sidecar (and written back), raster.spectral taking points, and the profile in the Workflows section with Identify's button.
Review notes:
- Read the full diff against AGENTS.md: no panics in non-test code, every left-out wavelength, unit or point is said with a count, the per-click read is one pixel so it stays on the UI thread, strings go through
tl!/i18n::fmt, and the wasm build passes. - Ran clippy (-D warnings) and the data, engine and ui-egui tests locally on the PR merged with main, all green, plus the spectral UI tests.
- Rendered it with
ui_shoton a 6-band scene with Sentinel-2 wavelengths (light and dark, in the comment above): markers, line colours and the wavelength axis line up, and the signatures look right. - Merged main into the branch (clean). Your three later commits (unread rasters counted, the tile-layer COG wavelength notice) look good.
- Resolved the open bot threads with maintainer replies: the sidecar-over-tag precedence follows GDAL, the once-per-frame click and section-change pick claims check out, Export Raster already says which bands it drops, and stable map ids are out of scope here.
Action performed
|


Summary
The Workflows pane's Spectral Analysis section, which showed
raster.spectral's answer as JSON, becomes a spectral profile, after GeoLibre's (opengeos/GeoLibre#1818,cog-spectral-profile.ts). It is in three parts, as proposed in #1622.Where it comes from. I read GeoLibre's TypeScript while writing this:
packages/plugins/src/plugins/cog-spectral-profile.ts, and for the chartapps/geolibre-desktop/src/lib/netcdf-band-axis.ts,netcdf-profile-series.tsandcomponents/panels/NetcdfProfileChart.tsx. I followed what they do: a clicked pixel's band values charted, against wavelength when the file gives one for every band and band number otherwise; wavelengths read from theGDAL_METADATAtag'swavelengthandcentral_wavelengthitems, a dataset-level item being for no band; and a CSV of the profiles. The Rust is written new, with no code copied: the values come from RustGIS's ownraster.spectral, the wavelengths go into its band metadata reader (pam.rs, sidecars too), and the chart is egui. GeoLibre is MIT (LICENSE, Copyright (c) 2026 Qiusheng Wu).Wavelengths on bands (data).
Bandgainswavelength: Option<f64>, in nanometres, read from the GeoTIFF's GDAL metadata tag (42112) and from the.aux.xmlsidecar:CENTRAL_WAVELENGTH_UM(IMAGERYdomain, micrometres);wavelengthandcentral_wavelengthitems, in the unit awavelength_unitsitem gives (the band's, else the dataset's).Items read are no longer counted in "band metadata item(s) not read"; an item that isn't a length from 1 nm to 1 m is said (
{n} wavelength(s) that aren't a length from 1 nm to 1 m in nanometres or micrometres, or for no band, left out), as is one for a band the raster doesn't have. A band takes the first item that is a length, in the order above, in the tag and the sidecar alike; another length for the same band is said and left out (1 other wavelength item(s) for a band that has one left out (the first is kept)), while the same length under two names is one wavelength. The GeoTIFF writers write the wavelengths of the bands they write back asCENTRAL_WAVELENGTH_UM, and the commands that copy band names copy them too: georeference (rebuild), mosaic, clip, resample, the pixel editor andraster.project(warp.rs); a mosaic says an input whose wavelengths differ from the first's, as it says other band or class names. Build Mosaic (imagery.mosaic, a workspace's) gives a band the images' wavelength when they all give the same one, and says how many bands they disagree on. A wavelength item of the dataset's own, for no band, is said and left out.raster.spectraltakes points (engine)."points": [[lon, lat], …], up to 1000, gives"profiles": [{lon, lat, pixel, values}, …], one per point. A point off the raster keeps its place with"pixel": nulland null values, and is said (scene: 1 of 3 points fall outside the raster: their values are null); when every point is off, it is an error. Every answer (one point, points, zone) now carries"wavelengths"(nm,nullfor a band without one) and"wavelengthUnit": "nm"when the file gives any. A zone is read before points and points beforelon/lat; what isn't read is said (scene: lon and lat left out: points are read,scene: points, lon and lat left out: the zone's mean is read). The old answers are unchanged otherwise.The profile (app), in
crates/ui-egui/src/spectralui.rs:analysis.md,data.md) say what it does.Choices and limits
raster.spectralextended, not a new command, so scripts, the MCP server and plugins get signatures from the one command that already read every band at a point.wavelength_units: a value under 100 is micrometres, anything else nanometres. Imaging sensors run from about 0.3 to 15 µm, so the two ranges don't meet. The docs say this.=,+,-,@), as the table export does.Up to 6 points are compared: the oldest one was taken off.). Another raster, the same one's bands changed, a raster of its name added again or on another map, or another project, starts the chart again. The command reads up to 1000.zone), and wavelengths for STAC cubes (eo:bands).spectralui.rswith its tests. It could be split into the data and engine part and the UI; it is one PR because the UI is what the wavelengths are for.Testing
New tests:
rustgis-data:reads_wavelengths_from_gdal_metadata(µm, nm,wavelength_unitsper band and per dataset, a value and a unit that aren't lengths, a band past the most a raster has),wavelengths_written_are_read_back,reads_wavelengths_from_a_sidecar.spectral_profiles_at_points_with_wavelengths: an RGB GeoTIFF with wavelengths written and read back throughlayer.addDataBytes; profiles, the off-raster notice, thelon/latleft out, wavelengths in every answer and none for a file without them, and seven malformedpoints.egui_kittest):the_spectral_profile_charts_points_picked(two points picked, the chart's lines, the CSV, taking one off, Clear),the_profile_keeps_six_points_and_says_what_it_leaves_out,identify_offers_the_profile_on_multiband_pixels.On
main0fd8302 (merged in), withRUSTGIS_LANGUAGE=enon Windows:cargo fmt --all --checkandcargo clippy --workspace --all-targets -- -D warningspass;rustgis-analysis443 passed,rustgis-data789 passed,rustgis-engine1,110 passed and 1 failed,rustgis-tilesCOG tests and the spectral UI tests pass.cargo check -p rustgis-web --target wasm32-unknown-unknowncan't run on this PC now (zstd-sysneedsclang, not installed), so the wasm build is left to CI. The last fullcargo test --workspace --no-fail-fast, onmain02006f3, gave 4,966 passed, 2 failed, 21 ignored. Both failures come from this PC's setup and touch nothing here:gdal_formats_open_when_gdal_is_installedneeds GDAL 3.8 for.geojsonl, and this PC's GDAL is 3.7.1.geolibre_tools_run_on_layers_and_add_their_outputsruns only where a GeoLibre runner is installed (it is skipped in CI), and this PC's runner refuses the.geojsoninput.UI evidence
A Sentinel-2 scene of the São Francisco valley (B02, B03, B04, B08, B11, B12) with the S2A central wavelengths in its
.aux.xml, taken withui_shot. Water, irrigated crops, Caatinga, bare soil and a solar farm compared.Before (
main): Spectral Analysis shows JSON, and the status bar says the wavelengths weren't read.After: the profile, the hover tooltip, and Identify's pop-up with its Spectral Profile button.
Related issue
Closes #1622.
🤖 Generated with Claude Code
Summary by CodeRabbit