Changes between Version 206 and Version 207 of UserGuidelines/GIS/Data

Timestamp:

05/16/13 11:27:37 (12 years ago)

Author:

Fran Boon

Comment:

Update to current

UserGuidelines/GIS/Data

@@ -16 +16 @@
 The CSV needs to have specific columns:
  * WKT column if we have polygon info (or Lat and Lon for Points, if not)
- * For L1, we need these columns: Country, ADM1_NAME (& WKT)
- * For L2, we need these columns: ADM1_NAME, ADM2_NAME (& WKT) [Country can also be used to help separate duplicates]
- * For L3, we need these columns: ADM2_NAME, ADM3_NAME (& WKT) [ADM1_NAME and Country can also be used to help separate duplicates]
- * For L4, we need these columns: ADM3_NAME, ADM4_NAME (& WKT) [ADM2_NAME, ADM1_NAME and Country can also be used to help separate duplicates]
- * For specific lcoations, we need these columns: ADMx_NAME (for appropiate parent level of hierarchy) Name (& Lat/Lon) [ADM2_NAME, ADM1_NAME and Country can also be used to help separate duplicates]
- * Code columns are used, if-present
-  * ADM1_CODE, ADM1_CODE2, ADM2_CODE, ADM2_CODE2, ADM3_CODE, ADM3_CODE2, ADM4_CODE, ADM4_CODE2, Code, Code2
+ * For L1, we need these columns: Country, L1 (& WKT)
+ * For L2, we need these columns: L1, L2 (& WKT) [Country can also be used to help separate duplicates]
+ * For L3, we need these columns: L2, L3 (& WKT) [L1 and Country can also be used to help separate duplicates]
+ * For L4, we need these columns: L3, L4 (& WKT) [L2, L1 and Country can also be used to help separate duplicates]
+ * For specific locations, we need these columns: Lx_NAME (for appropriate parent level of hierarchy) Name (& Lat/Lon) [L2, L1 and Country can also be used to help separate duplicates]
+ * Key/Value columns are used, if-present
+  * e.g.: "L1 KV:GADM" adds a record in gis_location_tag for every L1 record with a key of "GADM" & a value of whatever is specified in the cell.
  * Population & Elevation columns are read, if-present
  * Ensure that names are consistent between Levels