pgtopo_import(1)
β¨ pgtopo_import β postgis topology importer β¨
okay bestie, welcome to pgtopo_import, part of the PostGIS crew π«Ά this is the little loader that takes your topology out of the group chat and puts it back into the database. let's get into it π
πΈ SYNTAX πΈ
pgtopo_import [options] topology
that's it, that's the whole vibe β¨
π DESCRIPTION π
so the pgtopo_import data loader reads an export file that was written by pgtopo_export π and then it spits out an SQL script that reconstructs the topology that's inside that file. literally that's its whole job. no cap. π
π USAGE π
the <topology> argument is the name you want to give to the re-created topology β and yes, it can be different from the name of the topology the export was originally made from. glow-up naming rights, you have them π
by default the SQL script gets written on standard output. so it just comes out, streamed, no extra files, very main character energy β¨
π OPTIONS π
these are the supported options π«Ά
note bestie:--skip-layersand--only-layersare mutually exclusive. pick one, not both, ok? π
--skip-layersβ do not include layers in the output SQL script. just the topology schema. layers? not invited to this party π--only-layersβ do not include the topology schema in the output SQL script. just the layers. schema? not invited to this party π¦-f<filename>β read the export file from the specified filename, rather than from standard input. so instead of piping it in, you point at it π-hβ display usage information. the little help me out moment, iconic πΈ
β EXAMPLES β
an example session using the loader to create an SQL file and uploading it might look like this:
# pgtopo_import city_data < city_data.pgtopo_export | psql newdb
look at that pipe. chef's kiss. pgtopo_import makes the SQL, psql eats it into newdb. ate. π₯
π AUTHORS π
originally written by Sandro Santilli <strk@kbt.io> π
π SEE ALSO π
more information is available at http://postgis.net π§
and that's the whole page, bestie!! this one came from the PostGIS source, and it's the pgtopo_import(1) page β go forth and reconstruct those topologies π
β¨π¦
π¦ where this page comes from
- alpine 3.24: postgis-doc 3.6.3-r0 Β· GPL-2.0-or-later
- arch rolling: postgis 3.6.4-1 Β· GPL-2.0-or-later
- centos-stream 10: postgis-client 3.5.3-4.el10 Β· GPL-2.0-or-later
- centos-stream 10: postgresql18-postgis-client 3.5.3-2.el10 Β· GPL-2.0-or-later
- centos-stream 9: postgis-client 3.6.1-1.module_el9+1300+1c4aa8df Β· GPL-2.0-or-later
- debian trixie: postgis 3.5.2+dfsg-1 Β· GPL-2.0-or-later
- fedora 43: postgis-client 3.6.0-1.fc43 Β· GPL-2.0-or-later
- fedora 43: postgis-client 3.6.4-5.fc43 Β· GPL-2.0-or-later
- fedora 43: postgresql16-postgis-client 3.6.4-5.fc43 Β· GPL-2.0-or-later
- fedora 43: postgresql17-postgis-client 3.6.4-5.fc43 Β· GPL-2.0-or-later
- fedora 44: postgis-client 3.6.2-1.fc44 Β· GPL-2.0-or-later
- fedora 44: postgis-client 3.6.4-5.fc44 Β· GPL-2.0-or-later
- fedora 44: postgresql16-postgis-client 3.6.2-1.fc44 Β· GPL-2.0-or-later
- fedora 44: postgresql16-postgis-client 3.6.4-5.fc44 Β· GPL-2.0-or-later
- fedora 44: postgresql17-postgis-client 3.6.2-1.fc44 Β· GPL-2.0-or-later
- fedora 44: postgresql17-postgis-client 3.6.4-5.fc44 Β· GPL-2.0-or-later
- nixos 26.05: postgis 3.6.4
- nixpkgs unstable: postgis 3.6.4
- ubuntu noble: postgis 3.4.2+dfsg-1ubuntu3 Β· GPL-2.0-or-later
- ubuntu questing: postgis 3.5.3+dfsg-2build1
- ubuntu resolute: postgis 3.6.2+dfsg-1 Β· GPL-2.0-or-later
- ubuntu stonking: postgis 3.6.4+dfsg-2 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms