v.net.bridge(1grass)

💖 v.net.bridge 💖

okay so bestie, this is the v.net.bridge page from the GRASS User's Manual, and it's literally the tool that finds bridges and articulation points in your network. iconic behavior fr fr.

✨ KEYWORDS ✨

vector, network, articulation points 🦋

---

🌸 SYNOPSIS 🌸

v.net.bridge
v.net.bridge --help
v.net.bridge input=name output=name  [arc_layer=string]
[node_layer=string]   [arc_column=name]   [arc_backward_column=name]
[node_column=string]  method=string  [--overwrite]  [--help]
[--verbose]  [--quiet]  [--ui]

🎀 Flags

• --overwrite — lets your output files just bulldoze over existing files, no questions asked 💅
• --help — prints the usage summary so you're not out here confused
• --verbose — verbose module output, aka it tells you everything going on 🗣️
• --quiet — quiet module output, aka it says nothing, shhh 🤫
• --ui — forces the GUI dialog to launch, main character energy ✨

🌈 Parameters

• input=name [required] — Name of input vector map. Or, plot twist, a data source for direct OGR access 👑
• output=name [required] — Name for output vector map 💖
• arc_layer=string — Arc layer. okay so vector features can have category values in different layers, and this number determines which layer to use. When you're using it with direct OGR access, this is the layer name instead. Default: 1
• node_layer=string — Node layer. same deal: features can have category values in different layers, this number picks which one. With direct OGR access, it's the layer name. Default: 2
• arc_column=name — Arc forward/both direction(s) cost column (number)
• arc_backward_column=name — Arc backward direction cost column (number)
• node_column=string — Node cost column (number)
• method=string [required] — Feature type. Options: bridge, articulation
  • bridge: Finds bridges
  • articulation: Finds articulation points

---

💜 DESCRIPTION 💜

v.net.bridge finds bridges and articulation points in a network. that's it, that's the job, and it eats every time 🍓

---

🦋 NOTES 🦋

okay so a bridge in a network is an edge/line whose removal would disconnect the (sub-)network. meanwhile a node is an articulation point if its removal would disconnect the (sub-)network. if you want the more formal definitions and the full lore, go check the wikipedia entries: bridge and articulation point. iykyk 📚

The output of the module contains the selected features. For method=bridge, lines corresponding to bridges are copied from the input map to the output map. On the other hand, for method=articulation, points are created on the positions of articulation points. two very different vibes, same module 💅

GRASS lore drop incoming: in GRASS, a line is not always a single line segment. It might be — and honestly often is — a sequence of line segments between two intersections. Also, "articulation point" is standard graph theoretic terminology which is slightly misleading in GRASS. An articulation point in graph theory is an articulation node in GRASS terminology. not me getting tripped up by naming conventions 😭

---

🌟 SEE ALSO 🌟

• v.net
• v.category

---

🫶 AUTHORS 🫶

• Daniel Bundala, Google Summer of Code 2009, Student
• Wolf Bergenheim, Mentor

---

⭐ SOURCE CODE ⭐

Available at: v.net.bridge source code (history)

Latest change: Friday Aug 08 09:39:19 2025 in commit: ed72c71d8580e872cd6fd345c84a15c324764465

Main index | Vector index | Topics index | Keywords index | Graphical index | Full index

---

and that's a wrap bestie 🎀 this was v.net.bridge from the GRASS 8.5.0 Reference Manual, © 2003-2026 GRASS Development Team — slay, stay curious, and may your networks never disconnect 💖✨🌈