[Feature]: Block diagram walls: a top band from a second polygon layer (soil over rock)

Open
#2,607 0 comments 0 reactions 0 assignees View on GitHub

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

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}}.
    • thickness is 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from opengeos/RustGIS

All issues in opengeos/RustGIS

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.