[Feature]: Block diagram walls: a top band from a second polygon layer (soil over rock)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- data-visualization
Research direction
The proposal extends the walls key that the issue says already exists as walls.layer (#2173), so start by reading how that key is parsed and drawn; the payload does not name the files. The new walls.top option needs a band that follows each wall's ground line, takes its fill from the soils layer, and accepts a numeric thickness or a {"field": ...} lookup. Done means a block with both options renders the band, and the docs carry the 'not to scale' note. The design choices are still open, so confirm them with the maintainer first.
Written by the indexing model from the issue text.
Description
In teaching block diagrams, the walls show the soil as a band along the top of the cut and the rock below it. Today walls.layer takes one layer, so a block can show either the soils or the geology in its walls, not both.
Choices in this proposal
- New key:
"walls": {"layer": "geology", "top": {"layer": "soils", "thickness": 150}}.thicknessis in metres before exaggeration.- Instead of a number, it can be
{"field": "..."}, a numeric field of the soils layer.
- The band follows the ground line of each wall. Its colour is the soils layer's fill where it meets the side. Contacts between soil classes are short vertical lines across the band.
- The band is schematic and usually far thicker than the real soil. The docs say so, and suggest a figure note such as "soil thickness not to scale".
Builds on #2173 (walls.layer).
- 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
-
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
nautechsystems/nautilus_trader#5741 ·
Maintainers usually reply within 1 day
-
RunPlugin derives Hash over all fields while PartialEq compares only location and configurationOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
zellij-org/zellij#5969 ·
Maintainers usually reply within 1 day
-
eth_get_proof reports another account's fields for an absent accountPossibly taken @Indian-boult claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day