From 6b074e93ef8509450bbf159ff6913106fa86b096 Mon Sep 17 00:00:00 2001 From: Oliver Tonnhofer Date: Mon, 2 Sep 2013 10:29:20 +0200 Subject: [PATCH] wrap long command line examples --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ed9b07a..bfb7a2c 100644 --- a/README.md +++ b/README.md @@ -160,13 +160,15 @@ Usage For a simple import: - imposm3 import -connection postgis://user:password@host/database -mapping mapping.json -read /path/to/osm.pbf -write + imposm3 import -connection postgis://user:password@host/database \ + -mapping mapping.json -read /path/to/osm.pbf -write You need a JSON file with the target database mapping. See `example-mapping.json` to get an idea what is possible with the mapping. Imposm creates all new tables inside the `import` table schema. So you'll have `import.osm_roads` etc. You can change the tables to the `public` schema: - imposm3 import -connection postgis://user:passwd@host/database -mapping mapping.json -deployproduction + imposm3 import -connection postgis://user:passwd@host/database \ + -mapping mapping.json -deployproduction You can write some options into a JSON configuration file: