NAME¶

pyosmium-get-changes

SYNOPSIS¶

pyosmium-get-changes [options]

DESCRIPTION¶

Fetch diffs from an OSM planet server.

The starting point of the diff must be given either as a sequence ID or a date
or can be computed from an OSM file. If no output file is given, the program
will just print the initial sequence ID it would use (or save it in a file, if
requested) and exit. This can be used to bootstrap the update process.

The program tries to download until the latest change on the server is found
or the maximum requested diff size is reached. Note that diffs are kept in
memory during download.

On success, the program will print a single number to stdout, the sequence
number where to continue updates in the next run. This output can also be
written to (and later read from) a file.

*Note:* you may pipe the diff also to standard output using '-o -'. Then
the sequence number will not be printed. You must write it to a file in that
case.

Some OSM data sources require a cookie to be sent with the HTTP requests.
pyosmium-get-changes does not fetch the cookie from these services for you.
However, it can read cookies from a Netscape-style cookie jar file, send these
cookies to the server and will save received cookies to the jar file.

OPTIONS¶

-v

Increase verbosity (can be used multiple times)

-o OUTFILE, --outfile OUTFILE

Name of diff output file. If omitted, only the sequence ID will be printed where updates would start.

--format FORMAT

Format the data should be saved in.

--server SERVER_URL

Base URL of the replication server

--diff-type SERVER_DIFF_TYPE

File format used by the replication server (default: osc.gz)

--cookie COOKIE

Netscape-style cookie jar file to read cookies from and where received cookies will be written to.

-s OUTSIZE, --size OUTSIZE

Maximum data to load in MB (default: 100MB).

-I ID, --start-id ID

Sequence ID to start with

-D DATE, --start-date DATE

Date when to start updates

-O OSMFILE, --start-osm-data OSMFILE

start at the date of the newest OSM object in the file

-f SEQ_FILE, --sequence-file SEQ_FILE

Sequence file. If the file exists, then updates will start after the id given in the file. At the end of the process, the last sequence ID contained in the diff is written.

--ignore-osmosis-headers

When determining the start from an OSM file, ignore potential replication information in the header and search for the newest OSM object.

-d, --no-deduplicate

Do not deduplicate diffs.

--socket-timeout SOCKET_TIMEOUT

Set timeout for file downloads.

--version

show program's version number and exit

AUTHORS¶

pyosmium was written by Sarah Hoffmann <lonvia@denofr.de>.

DISTRIBUTION¶

The latest version of pyosmium may be downloaded from https://github.com/osmcode/pyosmium/