diff options
Diffstat (limited to 'docs/_build/html/import_export.html')
| -rw-r--r-- | docs/_build/html/import_export.html | 77 |
1 files changed, 43 insertions, 34 deletions
diff --git a/docs/_build/html/import_export.html b/docs/_build/html/import_export.html index acfb5eb..5a0dcd4 100644 --- a/docs/_build/html/import_export.html +++ b/docs/_build/html/import_export.html @@ -66,14 +66,18 @@ It has been updated for version 2.0.0.</p> <div class="section" id="importing"> <span id="id1"></span><h2>Importing<a class="headerlink" href="#importing" title="Permalink to this headline">¶</a></h2> -<p>In Chimère the import mechanism is based on <strong>Import object</strong>. Theses objects +<p>In Chimère the import mechanism is based on <strong>Import object</strong>. These objects are stored in database to keep trace of imports and to facilitate the re-importation from the same source. In fact if possible the update of data from -a same type of source is managed. The ability to do such updates depends on the -existence of a unique id for each object on your source.</p> +a same type of source is managed.</p> +<div class="admonition note"> +<p class="first admonition-title">Note</p> +<p class="last">The ability to do such updates depends on the existence of a unique id +for each object on your source.</p> +</div> <p>To add an <strong>Import object</strong> you need to go to <em>Chimere > Imports</em> then <strong>Add</strong>.</p> <p>After that you’ll have to select your source type and then the form depends on -the type of source.</p> +this source type.</p> <div class="section" id="common-fields"> <h3>Common fields<a class="headerlink" href="#common-fields" title="Permalink to this headline">¶</a></h3> <ul class="simple"> @@ -82,7 +86,7 @@ this is the name that will be used. If this field is empty the name of the associated category will be use.</li> <li><strong>SRID</strong>: Chimère will try to identify automatically the correct projection from the given source. But sometimes the information is not present or cannot -be guessed (for instance a Shapefile that uses non standard proj file). In +be guessed (for instance a shapefile that uses non standard proj file). In this case Chimère will use WGS84 by default (the classic latitude/longitude) but it is not always correct. If you experience problems with items localisation you should put here the SRID associated to the projection of @@ -105,16 +109,16 @@ associated to newly imported items.</li> file. You’ll have to fill one of the two fields.</li> <li><strong>Filter</strong>: if you want to import only a specific <em>Folder</em> of your KML file put his name on this field.</li> -<li><strong>Zipped file</strong>: if your source is a KMLZ file (a zipped KML) check this case.</li> +<li><strong>Zipped file</strong>: if your source is a KMLZ file (a zipped KML), check this case.</li> </ul> </div> <div class="section" id="shapefile-import"> <h3>Shapefile import<a class="headerlink" href="#shapefile-import" title="Permalink to this headline">¶</a></h3> <img alt="_images/chimere_admin_import_shapefile.png" src="_images/chimere_admin_import_shapefile.png" /> <ul class="simple"> -<li><strong>Web address/source file (mandatory)</strong>: your KML could be distant or a local -file. You’ll have to fill one of the two fields.</li> -<li><strong>Zipped file</strong>: only zipped shapefile are accepted this checkbox have to be +<li><strong>Web address/source file (mandatory)</strong>: your shapefile could be distant or a +local file. You’ll have to fill one of the two fields.</li> +<li><strong>Zipped file</strong>: only zipped shapefiles are accepted so this checkbox has to be checked.</li> </ul> </div> @@ -128,12 +132,17 @@ checked.</li> </div> <div class="section" id="csv-import"> <h3>CSV import<a class="headerlink" href="#csv-import" title="Permalink to this headline">¶</a></h3> -<p>As the format of the CSV file managed by Chimère could vary depending on the -property you have add on your Chimère instance we recommend you to first do -an export of some items in CSV with Chimère. The CSV format of the exported -file will meet Chimère requirements. By the way because of the geometry of -the item this format is not very convenient to add new content but could -be handy to update informations.</p> +<p>The format of the CSV file (number and order of columns) managed by Chimère +varies depending on the properties you have added on your Chimère instance. +So we recommend you to first do an export of some items in CSV with Chimère. +The CSV format of the exported file will meet Chimère requirements.</p> +<p>By the way because of the geometry of the item this format is not very +convenient to add new content but could be handy to update informations.</p> +<div class="admonition warning"> +<p class="first admonition-title">Warning</p> +<p class="last">If you mean to update existing data by this import, do <em>not</em> modify the +geometry column.</p> +</div> <img alt="_images/chimere_admin_import_CSV.png" src="_images/chimere_admin_import_CSV.png" /> <ul class="simple"> <li><strong>Web address/source file (mandatory)</strong>: your CSV file could be distant or a @@ -143,11 +152,11 @@ local file. You’ll have to fill one of the two fields.</li> <div class="section" id="openstreetmap-import"> <span id="osm-import"></span><h3>OpenStreetMap import<a class="headerlink" href="#openstreetmap-import" title="Permalink to this headline">¶</a></h3> <img alt="_images/chimere_admin_import_OSM.png" src="_images/chimere_admin_import_OSM.png" /> -<p>To import from OSM Chimère uses the XAPI API of OSM.</p> +<p>To import from OSM Chimère use the XAPI API of OSM.</p> <ul class="simple"> <li><strong>Web address (mandatory)</strong>: XAPI url used to import data. This field should be filled with a default address. By default the MapQuest server is used as it -seems to be the more robust. If you experience problems with OSM import check +seems to be the more robust. If you experience problems with OSM import, check the availability of the XAPI server used and eventually change it.</li> <li><strong>Filter area (mandatory)</strong>: draw the bounding box you want to use for your OSM import.</li> @@ -161,16 +170,16 @@ You have to hit this button before validating the form.</li> </div> <div class="section" id="id2"> <h3>Importing<a class="headerlink" href="#id2" title="Permalink to this headline">¶</a></h3> -<p>Once your new import item created. Select it in the import object list, select -the <strong>Import</strong> action and validated.</p> -<p>The import should be processing normally. If not an explicit error message -should be print in the state column of your import.</p> +<p>Once your new import item created, select it in the import object list, choose +the <strong>Import</strong> action and validate.</p> +<p>The import should be processing normally. If not, an explicit error message +should be printed in the state column of your import.</p> </div> <div class="section" id="managing-imported-data"> <h3>Managing imported data<a class="headerlink" href="#managing-imported-data" title="Permalink to this headline">¶</a></h3> <p>All new imported items have the state <strong>Imported</strong>. To make them available on -the map you’ll have to validate them. If you don’t want an item to be visible on -the map instead of delete them it is recommended to set them to the state +the map you’ll have to validate them. If you don’t want some items to be visible on +the map, instead of deleting them it is recommended to set them to the state <strong>Disabled</strong>.</p> <div class="admonition warning"> <p class="first admonition-title">Warning</p> @@ -183,8 +192,8 @@ is particularly important if you want to export your data to OSM.</p> <h2>Exporting<a class="headerlink" href="#exporting" title="Permalink to this headline">¶</a></h2> <div class="section" id="export-to-csv-kml-shapefile"> <h3>Export to CSV/KML/Shapefile<a class="headerlink" href="#export-to-csv-kml-shapefile" title="Permalink to this headline">¶</a></h3> -<p>Directly from the <a class="reference internal" href="administration.html#geographic-items-management"><em>geographic items list</em></a> you -can export to the choose format. All you have to do is to select the desired +<p>Directly from the <a class="reference internal" href="fr/administration.html#geographic-items-management"><em>geographic items list</em></a> you +can export to the chosen format. All you have to do is to select the desired items, choose the appropriate action in the action list and validate.</p> </div> <div class="section" id="export-to-osm"> @@ -192,41 +201,41 @@ items, choose the appropriate action in the action list and validate.</p> <div class="admonition warning"> <p class="first admonition-title">Warning</p> <p class="last">If you are not sure of what you are doing with OSM export: don’t do it! It is -really important to not mess with others data.</p> +really important to not mess with others’ data.</p> </div> <div class="admonition note"> <p class="first admonition-title">Note</p> <p class="last">Only export of OSM nodes are managed.</p> </div> <p>OSM export is not that easily managed. First (if not yet done) you’ll have to -define an import (<a class="reference internal" href="#osm-import"><em>see above</em></a> for details). This will permit +define an import (<a class="reference internal" href="#osm-import"><em>see above</em></a> for details). This will enable to determine:</p> <ul class="simple"> <li>the area concerned by your export.</li> <li>the key/value tag to append to your new/updated items.</li> <li>the subcategories concerned by your export. If you think that some items in -theses subcategories should not be in OSM database (because there are not +these subcategories should not be in OSM database (because there are not relevant or because of license issues) beforehand mark them as <strong>Not for OSM</strong> -in the <em>import fields</em> of the <a class="reference internal" href="administration.html#geographic-items-management"><em>geographic items forms</em></a>.</li> +in the <em>import fields</em> of the <a class="reference internal" href="fr/administration.html#geographic-items-management"><em>geographic items forms</em></a>.</li> </ul> <p>The OSM export in Chimère is designed to be the more preservative possible in regards to OSM database. That’s why before any export an import is done. If -the new import has updated data theses new data will overload data in your +the new import has updated data, these new data will overload data in your Chimère (if you don’t want that: don’t do export). All pending imported items should have been treated before doing an export.</p> <p>To launch an export select the appropriate Import object in the imports list. Then select the <strong>Export to OSM</strong> action and validate. Then you’ll be asked for your OSM username and password and the API you want to -use. If you use regularly Chimère to do export it is recommended to create an +use. If you regularly use Chimère to do export, it is recommended to create an OSM specific account for that. The test API is available to make export test. If you want to use the test API you’ll have to create a specific account on the test platform.</p> <div class="admonition warning"> <p class="first admonition-title">Warning</p> -<p class="last">The data on the test platform are not synced with the main platform you are -not going to have the same data that you got with XAPI.</p> +<p class="last">The data on the test platform are not synced with the main platform. You won’t +have the same data than the ones you got with XAPI.</p> </div> -<p>Once all this field filled you can (finally!) launch the export.</p> +<p>Once all this field filled, you can (finally!) launch the export.</p> <p>When exporting tags are automatically added/updated:</p> <ul class="simple"> <li><em>name</em>: get from the item name in Chimère.</li> |