Geo | Fission

Fission

Product

▾

Setup

›

The Geo family contains 20 renderer-backed chart variants. Use this page as the entry point for choosing the right variant, then open the variant page for the screenshot, data shape, Rust API notes, and example code.

The chart family is still ordinary Fission UI. Each variant is constructed from typed Rust data, participates in layout and theme decisions, and can be driven by app state, reducers, resources, jobs, or services just like any other widget.

Variants

Chart	Data shape	Use when
Capacity regions map	Region values with visual scale.	Use it for capacity by geography.
Courier routes	Point-to-point route lines.	Use it for logistics routing.
Coverage score map	Coverage scores by region.	Use it for service coverage surfaces.
Data center links	Route-like links between points.	Use it for infrastructure network views.
Dispatch routes	Map regions plus route lines.	Use it when routes need region context.
Expansion plan map	Planning values by region.	Use it for geographic planning dashboards.
Flight density lines	Dense route lines between points.	Use it for movement patterns.
Incident routing lines	Routes representing response movement.	Use it for dispatch and response analytics.
Incident severity map	Severity values mapped to region color.	Use it for incident command views.
Market regions map	Named regions with values.	Use it for regional comparisons where shape matters.
Migration flow	Region map plus movement routes.	Use it for source-to-destination stories.
Network overlay	Region values with connection lines.	Use it for linked geographic systems.
Network traffic lines	Route lines with effect markers.	Use it for flow over a spatial surface.
Risk regions map	Region values mapped to color.	Use it to scan geographic risk.
Route overlay map	Map and line series together.	Use it when geography and movement are inseparable.
Sales route map	Sales territories with route overlays.	Use it for field team planning.
Sales territory map	Territory values over named regions.	Use it when territory is the mental model.
Service health map	Region health values.	Use it for operational geography.
Supply routes	Coordinate pairs representing routes.	Use it for route and movement diagrams.
Support demand map	Demand values over regions.	Use it to allocate support capacity geographically.

Choosing within this family

Start with the user's question, not the visual effect. Pick the simplest variant that makes the answer clear, add interaction only when it reduces work for the user, and keep animation purposeful enough that it explains a change rather than decorating the page.

Authoring from a Fission component

Use this reference page as the chart expression inside ordinary Fission component conversion. The chart is a Widget, so it can sit inside a Card, Grid, Scroll, responsive page section, or any other layout container.

use fission::prelude::*;
use fission::charts::{Axis, Chart, LineSeries};

pub struct GeoChart;

impl From<GeoChart> for Widget {
    fn from(_: GeoChart) -> Widget {
        Chart::new()
            .title("Geo")
            .x_axis(Axis::category(vec!["A", "B", "C"]))
            .y_axis(Axis::value())
            .series(vec![LineSeries::new("Series").data(vec![1.0, 2.0, 3.0]).into()])
            .into()
    }
}

Keep expensive data loading outside component conversion. A reducer, job, service, or server route should prepare the typed chart data, then the component should read that state and construct the chart deterministically.

Options, accessibility, and diagnostics

Area	What to decide	How to verify
Data shape	Keep source rows in typed Rust structs, then map them into the series type shown in the example.	Unit test the mapping separately from rendering.
Options	Choose axes, legends, labels, animation, and interaction based on the user's task.	Add a screenshot test when changing visual behavior.
Accessibility	Provide a clear title and adjacent summary text for important trends or outliers.	Inspect the generated semantics and make sure the chart is understandable without color alone.
Failure handling	Render an empty, loading, or error state before constructing the chart if data is unavailable.	Test empty data, partial data, and failed fetches.
Performance	Prefer summarized or windowed data for very large datasets; keep full raw history in the data layer.	Profile frame time and interaction latency with representative data volumes.

Variants

Choosing within this family

Authoring from a Fission component

Options, accessibility, and diagnostics

Fission

A cross-platform, GPU-accelerated user interface framework for Rust. MIT licensed.

Ready to use today. Widget APIs are expected to remain stable; some runtime and shell APIs may change before 1.0.0.

GitHub

Quickstart

Reference

Fission 0.7.0