gol copy 2.2

Copies tiles between Libraries and Bundles.

Usage:

gol copy <source> <target> [<options>]

<source> and <target> must be of the same type (GOLs or GOBs).

• To copy tiles from a GOB into a GOL, use gol load.

• To store tiles from a GOL as a GOB, use gol save

If an area is specified (using --bbox or --area, only the tiles touching that area are copied.

If the source and target GOL contain different versions, the target’s version is set to the newer version, and all tiles from the older GOL are marked as stale.

Options

-a, --area <COORDS> | <FILE>

Defines the (multi)polygon area to which the command should be applied. The following coordinate formats are supported:

• GeoJSON

• WKT

• Raw coordinates in the form lon_0, lat_0, ... , lon_n, lat_n. To specify multiple polygons, or a polygon with one or more “holes,” place each ring in parentheses. Rings do not need to be closed.

You can specify coordinate values directly, or via a file.

-b, --bbox <W>,<S>,<E>,<N>

Defines the rectangular area (bounding box) to which the command should be applied. Coordinates are specified in WGS-84 (degrees longitude and latitude) and take the form <west>,<south>,<east>,<north>. Coordinates must not be separated by spaces (otherwise, they would be interpreted as separate arguments).

As an alternative, this option accepts a tile descriptor in the form z/x/y.

-q, --quiet

Displays only minimal output. Apart from error messages, only minimal progress updates are written to stderr.

-s, --silent

No output at all is written to stderr, not even error messages. (Whether a command succeeded or failed can only be ascertained via the status code returned by the process).

-v, --verbose

Writes extra information to stderr.