import_and_export:importing_regions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
import_and_export:importing_regions [2021/08/11 15:15] Gary Willettsimport_and_export:importing_regions [2021/10/08 09:31] (current) Gary Willetts
Line 1: Line 1:
 {{indexmenu_n>93}} {{indexmenu_n>93}}
- +====== 17.10. Importing regions ======
-====== 16.10. Importing regions ======+
 Regions are geographic boundaries, currently used in mSupply to help in displaying data on maps. At the moment they are only used in certain customisations but more use of them will follow as development progresses.  Regions are geographic boundaries, currently used in mSupply to help in displaying data on maps. At the moment they are only used in certain customisations but more use of them will follow as development progresses. 
  
Line 36: Line 35:
   * if the row has an empty Geometry field, it will be imported with no geometry   * if the row has an empty Geometry field, it will be imported with no geometry
   * if the row has content in the Geometry field that does not match the geoJSON FeatureCollection schema it will be skipped   * if the row has content in the Geometry field that does not match the geoJSON FeatureCollection schema it will be skipped
-  * if the parent region does not exist the region will be imported with no parent+  * if the parent region does not exist or is empty the region will be imported with no parent
  
 When the import has finished you will be shown a message telling you how many assets were imported and how many rows of the spreadsheet were skipped. When the import has finished you will be shown a message telling you how many assets were imported and how many rows of the spreadsheet were skipped.
  • Last modified: 2021/08/11 15:15
  • by Gary Willetts