From 3dac3aa1a580f04376a1c16d2416f34351b14adb Mon Sep 17 00:00:00 2001 From: Nawa Date: Thu, 29 Nov 2012 23:54:29 +0100 Subject: Documentation: new corrections, mainly on the administration part --- docs/_build/html/import_export.html | 77 +++++++++++++++++++++---------------- 1 file changed, 43 insertions(+), 34 deletions(-) (limited to 'docs/_build/html/import_export.html') 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.

Importing

-

In Chimère the import mechanism is based on Import object. Theses objects +

In Chimère the import mechanism is based on Import object. 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.

+a same type of source is managed.

+
+

Note

+

The ability to do such updates depends on the existence of a unique id +for each object on your source.

+

To add an Import object you need to go to Chimere > Imports then Add.

After that you’ll have to select your source type and then the form depends on -the type of source.

+this source type.

Common fields

    @@ -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.
  • SRID: 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.
    • file. You’ll have to fill one of the two fields.
  • Filter: if you want to import only a specific Folder of your KML file put his name on this field.
    • -
  • Zipped file: if your source is a KMLZ file (a zipped KML) check this case.
    • +
  • Zipped file: if your source is a KMLZ file (a zipped KML), check this case.

Shapefile import

_images/chimere_admin_import_shapefile.png
    -
  • Web address/source file (mandatory): your KML could be distant or a local -file. You’ll have to fill one of the two fields.
    • -
  • Zipped file: only zipped shapefile are accepted this checkbox have to be +
  • Web address/source file (mandatory): your shapefile could be distant or a +local file. You’ll have to fill one of the two fields.
    • +
  • Zipped file: only zipped shapefiles are accepted so this checkbox has to be checked.
@@ -128,12 +132,17 @@ checked.

CSV import

-

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.

+

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.

+

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.

+
+

Warning

+

If you mean to update existing data by this import, do not modify the +geometry column.

+
_images/chimere_admin_import_CSV.png