File: pgtopo_import.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 (59 lines) | stat: -rw-r--r-- 1,375 bytes parent folder | download | duplicates (4)
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
50
51
52
53
54
55
56
57
58
59
.TH "pgtopo_import" "1" "" "" "PostGIS"
.SH "NAME"
.LP
pgtopo_import - postgis topology importer

.SH "SYNTAX"
.LP
pgtopo_import [\fIoptions\fR] \fItopology\fR

.SH "DESCRIPTION"
.LP
The pgtopo_import data loader reads an export file written
by pgtopo_export and outputs an SQL script reconstructing
the topology therein contained.

.SH "USAGE"
.LP
The <topology> is the name to give to the re-created topology, which
can be different from the name of the topology the export was made
from.

By default the SQL script is written on standard output.

.SH "OPTIONS"
.LP
These are the supported options

(Note that \--skip-layers and \--only-layers are mutually exclusive.)
.TP
\fB\--skip-layers\fR
Do not include layers in the output SQL script. Just the topology
schema.
.TP
\fB\--only-layers\fR
Do not include the topology schema in the output SQL script. Just the
layers.
.TP
\fB\-f\fR <\fIfilename\fR>
Read the export file from the specified filename, rather than from
standard input.
\fB\-h\fR
Display usage information.

.SH "EXAMPLES"
.LP
An example session using the loader to create an SQL file and uploading it
might look like this:

# \fBpgtopo_import city_data < city_data.pgtopo_export | psql newdb\fR

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

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

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