Boundary import
Load official NPC geography before field deployment.
Import official State, LGA, Ward, settlement/locality and EA boundaries. Run a dry-run first to catch missing parent codes or invalid geometry before changing the database.
1. Choose level2. Paste data3. Dry-run validation4. Import official records
States
-
0 with boundaries
LGAs
-
0 with boundaries
Wards
-
0 with boundaries
Localities
-
0 with boundaries
EAs
-
0 with polygons
Import setup
Use stable official codes. Child records must reference the parent code already in the database.
CSV uploadUpload reads the file into Boundary data, switches format to CSV with WKT, and maps common header names automatically.
Arrange CSV for Wards
Required columns: code, name, lgaCode, wkt. Each ward row must include lgaCode matching an existing LGA code.
Geometry must be WKT in longitude latitude order, EPSG:4326. Because WKT contains commas, wrap the whole WKT cell in double quotes.
Show sample CSV
code,name,lgaCode,wkt NG-LA-IKJ-GRA,Ikeja GRA,NG-LA-IKJ,"MULTIPOLYGON(((3.33 6.58,3.35 6.58,3.35 6.60,3.33 6.60,3.33 6.58)))"