1OSMIUM(1) OSMIUM(1)
2
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 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 –version
24 Show program version.
25
27 add-locations-to-ways
28 add node locations to ways in OSM file
29 apply-changes
31 apply OSM change file(s) to OSM data file
32 cat concatenate OSM files and convert to different formats
34 changeset-filter
36 filter changesets from OSM changeset files
37 check-refs
39 check referential integrity of OSM file
40 derive-changes
42 create OSM change file from two OSM files
43 diff display differences between OSM files
45 export export OSM data
47 extract
49 create geographical extracts from an OSM file
50 fileinfo
52 show information about an OSM file
53 getid get objects from OSM file by ID
55 getparents
57 get parents of objects from OSM file
58 help show help about commands
60 merge merge several OSM files into one
62 merge-changes
64 merge several OSM change files into one
65 renumber
67 renumber object IDs
68 show show OSM file
70 sort sort OSM files
72 tags-filter
74 filter OSM data based on tags
75 time-filter
77 filter OSM data by time from a history file
78
80 Most commands support the following options:
81 -h, –help
83 Show short usage information.
84 -v, –verbose
86 Set verbose mode. The program will output information about
87 what it is doing to STDERR.
88
90 Osmium commands try to do their work as memory efficient as possible.
91 But some osmium commands still need to load quite a bit of data into
92 main memory. In some cases this means that only smaller datasets can
93 be handled. Look into the man pages for the individual commands to
94 learn more about their memory use.
95 If you use the -v, –verbose option on most commands they will print out
97 their peak memory usage at the end. This is the actual amount of mem‐
98 ory used including the program code itself, any needed libraries and
99 the data. (Printing of memory usage is currently only available on
100 Linux systems.)
101 If an osmium command exits with an “Out of memory” error, try running
103 it with –verbose on smaller datasets to get an idea how much memory it
104 needs.
105 On Linux a program that uses a lot of memory can be killed by the ker‐
107 nel without the program being notified. If you see osmium dieing with‐
108 out any apparent reason, this might be the case. Search on the Inter‐
109 net for “OOM killer” to find out more about this.
110
112 · osmium-add-locations-to-ways(1), osmium-apply-changes(1),
113 osmium-cat(1), osmium-changeset-filter(1), osmium-check-refs(1),
114 osmium-derive-changes(1), osmium-diff(1), osmium-export(1),
115 osmium-extract(1), osmium-fileinfo(1), osmium-getid(1), osmium-get‐
116 parents(1), osmium-merge(1), osmium-merge-changes(1), osmium-renum‐
117 ber(1), osmium-show(1), osmium-sort(1), osmium-tags-filter(1),
118 osmium-time-filter(1), osmium-file-formats(5)
119 · Osmium website (https://osmcode.org/osmium-tool/)
121
123 Copyright (C) 2013-2018 Jochen Topf <jochen@topf.org>.
124 License GPLv3+: GNU GPL version 3 or later
126 <https://gnu.org/licenses/gpl.html>. This is free software: you are
127 free to change and redistribute it. There is NO WARRANTY, to the
128 extent permitted by law.
129
131 If you have any questions or want to report a bug, please go to
132 https://osmcode.org/contact.html
133
135 Jochen Topf <jochen@topf.org>.
136 1.10.0 OSMIUM(1)