GNMMANAGE(1)

πŸ“¦
version 3.4.3 Β· 2 versions
, in epel 9

πŸ’… gnmmanage β€” it's giving network manager realness

okay so this is the gnmmanage page from GDAL, and honestly? she's a whole utility. bestie, if you've ever been like "how do I even touch a geographical network in GDAL" β€” this is your girl. let's get into it πŸ¦‹


✨ SYNOPSIS ✨

gnmmanage [--help][-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> ...]]

like, yes, that's a lot of brackets. breathe. it's giving choose-your-own-adventure and honestly that's the vibe πŸ’…


🌸 DESCRIPTION 🌸

the gnmmanage program can perform various managing operations on geographical networks in GDAL. no cap β€” she's the whole ops department. besides creating and deleting networks, this includes the ability to manage a network's features, its topology, and its rules. main character energy fr fr πŸ‘‘

πŸŽ€ the operations, one by one

  • -info β€” gives you different information about the network: system and class layers, network metadata, and the network spatial reference. it's the vibe check for your network, essentially ✨
  • create β€” create network. new network who dis.
    • -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. drop as many as you need, she slays.
  • import <src_dataset_name> β€” import layer with dataset name to copy.
    • -l layer_name β€” layer name in dataset. if unset, 0 layer is copied. (yes, the zeroth one. default behavior, iconic.)
  • 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). lowkey my favorite one because you get to pick the pieces apart πŸ’€

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. bye bestie 🫢
  • 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. if no layer name provided, all layers of network will be used. she does the work so you don't have to 🌈
  • delete β€” delete network. gone. reduced to atoms. πŸ™ˆ
  • 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. (special layer! she's got her own little room πŸŽ€)
    • -unbl <gfid> β€” unblock feature before the main operation.
    • -unblall β€” unblock all blocked features before the main operation. mass unblocking event, periodt.

🧚 the arguments

  • <gnm_name> β€” the network to work with (path and name).
  • <layer> β€” the network layer name.
heads up bestie πŸ’– β€” notice that <gnm_name> and the <layer> list come after whichever operation you picked in the synopsis. the operation is the main course, the names are the seasoning.

πŸ‘‘ AUTHOR

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


1998-2026


okay that's the whole page, you ate that πŸ“ this was GNMMANAGE(1) from the GDAL manual, dated Jan 08, 2026 β€” go forth and manage those networks, bestie, iykyk πŸ’œβœ¨

πŸ“¦ where this page comes from