GNMMANAGE(1)

💖 NAME 💖

gnmmanage — okay so this is the girlypop who manages networks 🌸 and she's part of the GDAL family (that's the manual we're living in, section 1, bestie 🎀).

---

✨ SYNOPSIS ✨

Usage: gnmmanage [--help][--help-general][-q][-quiet][--long-usage]
                 [info]
                 [create [-f <format_name>] [-t_srs <srs_name>] [-dsco <NAME>=<VALUE>]... ]
                 [import <src_dataset_name>] [-l <layer_name>]
                 [connect <gfid_src> <gfid_tgt> <gfid_con> [-c <cost>] [-ic <inv_cost>] [-dir <dir>]]
                 [disconnect <gfid_src> <gfid_tgt> <gfid_con>]
                 [rule <rule_str>]
                 [autoconnect <tolerance>]
                 [delete]
                 [change [-bl <gfid>][-unbl <gfid>][-unblall]]
                 <gnm_name> [<layer> [<layer>]...]

ngl the synopsis ate 💅 one command, SO many little moves she can make.

---

🌈 DESCRIPTION 🌈

Not me about to explain that gnmmanage is the program that does various managing operations on geographical networks in GDAL 🦋. And it's not just create-and-delete basic behavior, okay — she also has capabilities of managing the network's features, topology and rules. It's giving project-manager-queen energy 👑.

Here's the whole menu, one by one, no skips:

• --help — Show this help message and exit. Short, sweet, iconic.
• --help-general — Gives a brief usage message for the generic GDAL commandline options and exit. The generic-girlie explainer 🫶.
• -info — Different information about network: system and class layers, network metadata, network spatial reference. Basically the vibe check on your whole network 💅.
• create — Create network. New network, new me ✨.
  • -f <format_name> — Output file format name.
  • -t_srs <srs_name> — Spatial reference input.
  • -dsco <NAME>=<VALUE> — Network creation option set as pair name=value.
• import <src_dataset_name> — Import layer with dataset name to copy.
  • -l <layer_name> — Layer name in dataset. If unset, 0 layer is copied.
• connect <gfid_src> <gfid_tgt> <gfid_con> — Make a topological connection, where the gfid_src and gfid_tgt are vertices and gfid_con is edge (gfid_con can be -1, so the system edge will be inserted). Fr fr, matchmaking but for topology 😭.

Manually assign the following values:

• -c <cost> — Cost / weight.
• -ic <invcost> — Inverse cost.
• -dir <dir> — Direction of the edge.

• disconnect <gfid_src> <gfid_tgt> <gfid_con> — Removes the connection from the graph. It's not you, it's the graph 💀.
• rule <rule_str> — Creates a rule in the network by the given rule_str string.
• autoconnect <tolerance> — Create topology automatically with the given double tolerance and layer names. In no layer name provided all layers of network will be used. She'll just do it herself, main character energy 🔥.
• delete — Delete network. Gone. Periodt.
• change — Change blocking state of network edges or vertices.
  • -bl <gfid> — Block feature before the main operation. Blocking features are saved in the special layer.
  • -unbl <gfid> — Unblock feature before the main operation.
  • -unblall — Unblock all blocked features before the main operation.
• <gnm_name> — The network to work with (path and name). This one's required, bestie.
• <layer> — The network layer name.

lowkey footnote: -q, -quiet and --long-usage show up in the synopsis above but the page doesn't spell out extra behavior for them, so I'm NOT gonna sit here and make stuff up 😌 no cap.

---

⭐ RETURN STATUS CODE ⭐

The program returns status code 0 in case of success, and non-zero in case of error — and listen, this part matters: non-blocking errors emitted as warnings are considered as a successful execution 🙈. So a lil warning doesn't ruin the whole slay.

---

🎀 AUTHOR 🎀

Mikhail Gusev <gusevmihs@gmail.com>, Dmitry Baryshnikov <polimax@mail.ru>

---

💜 COPYRIGHT 💜

1998-2026

---

And that's the whole page, bestie 🧚 — this was GNMMANAGE(1) from the GDAL manual, dated Aug 18, 2026. Obsessed with her, honestly 🍓💖.