pgtopo_export(1)
β¨ pgtopo_export β¨
okay bestie, gather round, because this one is the PostGIS topology exporter and it is, lowkey, the moment. it's a page from the PostGIS manual, section 1 (that's the user commands girlies π
), and it does exactly one job and does it gorgeously.
π NAME π
pgtopo_export β postgis topology exporter πΊοΈβ¨
π¦ SYNTAX π¦
pgtopo_export [options] database topology
π DESCRIPTION π
so what does she do?? the pgtopo_export script connects to the database you name, then exports the data of the topology you name β plus its associated layers β out to a file with a custom format. that's it. that's the whole vibe. export and slay. π«Ά
πΈ USAGE πΈ
- <database> β the name of the database to connect to. literally just the db name, no notes.
- <topology> β the name of the topology to read data from. this is the one you're exporting.
β¨ OPTIONS β¨
the commandline options are, in order, no skipping:
-f<filename> β write the output to a particular filename instead of standard output. like, instead of dumping it at your terminal's feet, she writes it to a file. icon behavior. π--skip-layersβ do not export layers, just topology primitives. so if you only want the primitives and not the layers, this is your girl. π§-hβ display usage information. your little helper, always there for you. π
π₯ EXAMPLES π₯
an example session using the exporter to create an export file of a topology city_data from a database might look like this:
# pgtopo_export -f city_data.pgtopo_export my_db city_data
look at her go. -f says "put it in city_data.pgtopo_export", my_db is the database, city_data is the topology. flawless. no cap. β
π AUTHORS π
originally written by Sandro Santilli <strk@kbt.io>. we stan. π
π SEE ALSO π
pgtopo_import(1)β the other half of the duo, go say hi π¦- more information is available at http://postgis.net
real talk bestie: that's every option, every argument, every example and every link from the original β nothing dropped, nothing invented. periodt. π
and that's the whole page, bestie π this one's from the PostGIS manual, pgtopo_export(1) β go export something iconic. π¦β¨π
π¦ 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 bookworm: postgis 3.3.2+dfsg-1+b1 Β· 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