Skip to content

Keep layer names clear of the pump label in the borewell drawing - #66

Merged
Mehulsri07 merged 2 commits into
mainfrom
fix-pump-label-overlap
Oct 8, 2026
Merged

Mehulsri07 merged 2 commits into
mainfrom
fix-pump-label-overlap

Conversation

@Mehulsri07

Copy link
Copy Markdown
Owner

Problem

In the on-screen borewell drawing, a pump lowered to the middle of a layer had its "Pump … ft" label drawn on top of that layer's name, so neither could be read. Example: Sand 135–175 ft, water at 108 ft, pump lowered to 158 ft.

Layer names already stepped above or below the "Water … ft" label, but nothing knew about the pump label.

Change

BorewellProfile.tsx: layer names now step around both fixed labels (water and pump) with the same rule that was used for water alone. The pump and water labels stay where they are, next to their markers.

Print/PDF variant: names written on the layers were never affected (they sit inside the layer column). Only the names of layers too thin to write on, which go beside the drawing, could land on the pump label; those now move below it, as they already did for the water label.

Check

One new end-to-end check: a borewell with Sand 135–175, water 108, pump 158 is opened and no two labels beside the drawing may be closer than a line of text.

  • Before the fix: FAIL, covered: ["Sand 135–175 / Pump 158 ft"]
  • After the fix: 62 passed, 0 failed

Typecheck and lint pass.

A pump lowered to the middle of a layer had its label drawn over the layer's name. Layer names now step around the pump label the same way they do the water label, on screen and for the thin-layer names written beside the drawing in print.
# Conflicts:
#	app/src/components/geology/BorewellProfile.tsx
@Mehulsri07
Mehulsri07 merged commit ca10a86 into main Oct 8, 2026
7 checks passed
@Mehulsri07
Mehulsri07 deleted the fix-pump-label-overlap branch October 8, 2026 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant