1OSMIUM(1) OSMIUM(1)
2
3
4
6 osmium - multipurpose tool for working with OpenStreetMap data
7
9 osmium COMMAND [ARG...]
10 osmium --version
11
13 Multipurpose tool for working with OpenStreetMap data.
14
15 Run osmium help COMMAND to get more information about a command. This
16 will only work on Linux and OS/X systems and only if the man command is
17 available and working correctly.
18
20 -h, --help
21 Show usage and list of commands.
22
23 --version
24 Show program version.
25
27 add-locations-to-ways
28 add node locations to ways in OSM file
29
30 apply-changes
31 apply OSM change file(s) to OSM data file
32
33 cat concatenate OSM files and convert to different formats
34
35 changeset-filter
36 filter changesets from OSM changeset files
37
38 check-refs
39 check referential integrity of OSM file
40
41 derive-changes
42 create OSM change file from two OSM files
43
44 diff display differences between OSM files
45
46 export export OSM data
47
48 extract
49 create geographical extracts from an OSM file
50
51 fileinfo
52 show information about an OSM file
53
54 getid get objects from OSM file by ID
55
56 getparents
57 get parents of objects from OSM file
58
59 help show help about commands
60
61 merge merge several OSM files into one
62
63 merge-changes
64 merge several OSM change files into one
65
66 removeid
67 remove OSM objects with specified IDs
68
69 renumber
70 renumber object IDs
71
72 show show OSM file
73
74 sort sort OSM files
75
76 tags-filter
77 filter OSM data based on tags
78
79 time-filter
80 filter OSM data by time from a history file
81
83 Most commands support the following options:
84
85 -h, --help
86 Show short usage information.
87
88 -v, --verbose
89 Set verbose mode. The program will output information about
90 what it is doing to STDERR.
91
93 Osmium commands try to do their work as memory efficient as possible.
94 But some osmium commands still need to load quite a bit of data into
95 main memory. In some cases this means that only smaller datasets can
96 be handled. Look into the man pages for the individual commands to
97 learn more about their memory use.
98
99 On most commands, if you use the --verbose/-v option, osmium will print
100 out the peak memory usage at the end. This is the actual amount of
101 memory used including the program code itself, any needed libraries,
102 and the data. (Printing of memory usage is currently only available on
103 Linux systems.)
104
105 If an osmium command exits with an “Out of memory” error, try running
106 it with --verbose/-v on smaller datasets to get an idea how much memory
107 it needs.
108
109 On Linux a program that uses a lot of memory can be killed by the ker‐
110 nel without the program being notified. If you see osmium dieing with‐
111 out any apparent reason, this might be the case. Search on the Inter‐
112 net for “OOM killer” to find out more about this.
113
115 • osmium-add-locations-to-ways(1), osmium-apply-changes(1), osmium-
116 cat(1), osmium-changeset-filter(1), osmium-check-refs(1), osmium-de‐
117 rive-changes(1), osmium-diff(1), osmium-export(1), osmium-extract(1),
118 osmium-fileinfo(1), osmium-getid(1), osmium-getparents(1), osmium-
119 merge(1), osmium-merge-changes(1), osmium-renumber(1), osmium-
120 show(1), osmium-sort(1), osmium-tags-filter(1), osmium-time-fil‐
121 ter(1), osmium-file-formats(5), osmium-index-types(5), osmium-output-
122 headers(5)
123
124 • Osmium website (https://osmcode.org/osmium-tool/)
125
127 Copyright (C) 2013-2022 Jochen Topf <jochen@topf.org>.
128
129 License GPLv3+: GNU GPL version 3 or later <https://gnu.org/li‐
130 censes/gpl.html>. This is free software: you are free to change and
131 redistribute it. There is NO WARRANTY, to the extent permitted by law.
132
134 If you have any questions or want to report a bug, please go to
135 https://osmcode.org/contact.html
136
138 Jochen Topf <jochen@topf.org>.
139
140
141
142 1.14.0 OSMIUM(1)