[Feature]: A line stroke coloured along the line (start colour to end colour)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- data-visualization
Research direction
Start by locating layer.lineStrokes, layer.symbolBy, and the Strokes section of the pane in the RustGIS codebase; the issue does not name specific files or tests. Read how line stroke colors and legend symbols are currently produced. Done means strokes can interpolate two colors by distance from first to last vertex, expressions can supply per-origin colors, and the legend shows the same fade.
Written by the indexing model from the issue text.
Description
What's missing
A stroke has one colour (layer.lineStrokes, layer.symbolBy). A flow line can't fade from its origin's colour to its destination's, which is how a reader tells the direction without arrowheads. QGIS has this as the interpolated line and the gradient in its line symbols.
Proposal
A stroke property "gradient": {"from": "#RRGGBBAA", "to": "#RRGGBBAA"} in layer.lineStrokes, and in the Strokes section of the pane:
- the colour changes along the line's length, from its first vertex to its last;
fromandtocan also come from an expression (layer.symbolBy), for one colour per origin;- the legend shows the stroke as a short line with the same fade.
Choices in this proposal
- By distance along the line, not by vertex: it doesn't change with how densely a line is drawn.
- Two colours, no ramp of stops: it covers flow direction; a ramp of stops can come later if asked for.
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 268
- Avg merge
- 11h 1m
- Merged PRs (30d)
- 942
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opengeos/RustGIS
-
[Bug]: layer.move to the place a layer already has fails and stops a script; with several layers it leaves an empty undo stepPossibly taken @jgregoriorincon claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opengeos/RustGIS#2621 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
opengeos/RustGIS#1446 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
All issues in opengeos/RustGIS
Similar issues
-
文件夹重大BUG:不支持重命名Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
postgresql-rules / queue-rules: implicit KEY SHARE before a parent key update, and job self-overlapOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jonathanong/no-mistakes#3879 ·
Maintainers usually reply within 1 day
-
area:index v0.35.0
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pbakaus/impeccable#1653 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
nautechsystems/nautilus_trader#5741 ·
Maintainers usually reply within 1 day