Skip to content

Latest commit

 

History

History
69 lines (54 loc) · 3.92 KB

convert.asciidoc

File metadata and controls

69 lines (54 loc) · 3.92 KB
Raw

convert

Description

The convert command converts map data from one format to another. The process may be memory bound depending upon the input or output formats selected.

  • input(s) - Input(s); may be any supported input format (e.g. .osm file) or a directory if --recursive is specified.

  • output - Output; may be any supported output format (e.g. .osm file). If --separate-output is specified, this should be the format file extension (e.g. shp) or base URL of the output to be written and not a full URL (e.g. hootapidb://<user name>:<password>@<host name>:<port>/<database name>). or hootapidb://<user name>:<password>@<host name>:<port>/<database name>).

  • --recursive - Allows for processing the files contained in any directories specified in input(s) recursively. This parameter has no effect on the processing of non-directory inputs. This must be followed by either "" to denote no filtering or one or more wildcard name filters. e.g. ".osm;*.json" or "myFile". This parameter is not compatible with the OGR layer input syntax.

  • --separate-output - The default behavior when processing multiple inputs is to combine them into the same single output. With this parameter specified, each input is processed and written to a separate output with the format specified in output and the same file name as the input with the text "-converted" appended to it. This parameter cannot be used with OSM API database (osmapidb://) or OSM API (http://) inputs. This parameter is not compatible with the OGR layer input syntax.

  • --write-bounds - If the bounds configuration option is specified, optionally outputs a file containing the input bounds. The location of the file is controlled via the bounds.output.file configuration option.

  • --autoconfig-cache - If the convert operation is a streaming write, this option will automatically configure the element.cache.size.* settings by calculating the amount of free memory available multiplied by the threshold of 80% (by default) then divided by the calculated node/way/relation ratio and the actual memory size of the objects.

Usage

hoot convert (input) [input2...] (output) [--recursive "*"|"filter1;filter2..."] [--separate-output] [--write-bounds]

Translating Features

The configuration option, schema.translation.script, may be used to schema translate feature during the conversion process.

Conversion Operations

The convert.ops configuration option can be used to apply map operations to data during conversion. Information about the available conversion operations may be found with:

hoot info --operators

Filtering Features Geographically

If the configuration option, bounds, is set to a valid geographic bounds (see the configuration option documentation for formats), supporting readers will read data only from within the specified bounds. The bounds.* configuration options allow for further customization of the bounds requirement.

See Also