File: pgtopo_export.1

package info (click to toggle)
postgis 3.5.3%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 69,528 kB
  • sloc: ansic: 162,229; sql: 93,970; xml: 53,139; cpp: 12,646; perl: 5,658; sh: 5,369; makefile: 3,435; python: 1,205; yacc: 447; lex: 151; pascal: 58
file content (49 lines) | stat: -rw-r--r-- 1,119 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
.TH "pgtopo_export" "1" "" "" "PostGIS"
.SH "NAME"
.LP
pgtopo_export - postgis topology exporter

.SH "SYNTAX"
.LP
pgtopo_export [\fIoptions\fR] \fIdatabase\fR \fItopology\fR

.SH "DESCRIPTION"
.LP
The pgtopo_export script connects to the named database and exports
data of the named topology and associated layers to a file with a
custom format.

.SH "USAGE"
.LP
The <database> is the name of the database to connect to.

The <topology> is the name of the topology to read data from.

.SH "OPTIONS"
.LP
The commandline options are:
.TP
\fB\-f\fR <\fIfilename\fR>
Write the output to a particular filename instead of stadard output.
.TP
\fB\--skip-layers\fR
Do not export layers, just topology primitives.
\fB\-h\fR
Display usage information.

.SH "EXAMPLES"
.LP
An example session using the exporter to create an export file of a
topology "city_data" from a database might look like this:

# \fBpgtopo_export \-f city_data.pgtopo_export my_db city_data\fR

.SH "AUTHORS"
.LP
Originally written by Sandro Santilli <strk@kbt.io>.

.SH "SEE ALSO"
.LP
pgtopo_import(1)

More information is available at http://postgis.net