Boundary Master

Introduction

The Boundary Master sheet defines the hierarchical administrative areas of a ULB using multiple boundary levels. Each boundary level follows the naming pattern:

<HIERARCHY_NAME>_<LEVEL_NAME>

Examples

• ADMIN123_STATE

• ADMIN123_CITY

Users only fill the hierarchy-level columns. The backend automatically generates metadata fields such as:

• CRS_BOUNDARY_CODE

This structure ensures accuracy, prevents duplication, and maintains a consistent administrative boundary tree.

Templates Provided:

• TEMPLATE – Auto-generated Boundary Master

• PREFILLED TEMPLATE – Prefilled Boundary Master Template

• Sample Generated Boundary Master: Boundary Master Auto Generate Sample Template

---

Data Table

S.No.	STATE	CITY	ZONE	LOCALITY	BLOCK	Boundary Code	LAT	LONG
1	Karnataka					(auto)	(optional)	(optional)
2	Karnataka	Bangalore				(auto)	(optional)	(optional)
3	Karnataka	Bangalore	Bangalore South			(auto)	(optional)	(optional)
4	Karnataka	Bangalore	Bangalore South	Koramangala		(auto)	(optional)	(optional)
5	Karnataka	Bangalore	Bangalore South	Koramangala	Block 1	(auto)	(optional)	(optional)

---

Procedure

Data Definition

Sr. No.	Column Name	Data Type	Data Size	Mandatory?	Purpose / Description	User Input?	Excel Validation
1	<HIERARCHY_NAME><LEVEL_NAME>	Text	256	Yes (as per hierarchy)	Boundary hierarchy: STATE → CITY → ZONE → LOCALITY → BLOCK	Yes	Alphabets & spaces only
2	CRS_BOUNDARY_CODE	Text	Auto	No	Unique boundary code generated by backend	No	Protected column (no input)
5	CRS_LAT	Decimal	Auto	No	The latitude of that Level	No	Decimal check (if filled)
6	CRS_LONG	Decimal	Auto	No	The Longitude of that level	No	Decimal check (if filled)

---

Steps to Fill Data

1. Download the Boundary Master template.

2. Review the hierarchy columns (STATE, CITY, ZONE, LOCALITY, BLOCK).

3. Enter values starting from the highest level:

   1. Fill STATE first.

   2. Fill CITY only if STATE is filled.

   3. Fill ZONE only if CITY is filled.

   4. Fill LOCALITY only if ZONE is filled.

   5. Fill BLOCK only if LOCALITY is filled.

4. Ensure all hierarchy names contain only:

   1. Alphabets

   2. Spaces No numbers or special characters.

5. Do not fill:

   1. Boundary Code - These are autogenerated by the backend.

6. After completing all rows, verify the sheet against validation rules.

7. Save and share for backend ingestion.

---

Excel Validation Framework

This sheet includes two major validation rules:

1. Alphabetic Text Validation (User Input Columns)

Applied to hierarchy columns (STATE, CITY, ZONE, LOCALITY, BLOCK).

Rules:

• Only alphabets (A–Z) allowed

• Spaces permitted

• No numbers or symbols

• No mixed alphanumeric entries

2. Mandatory Hierarchy Rule

Each deeper level must follow the correct hierarchy order.

Examples:

• CITY cannot be filled if STATE is empty

• ZONE cannot be filled if CITY is empty

• LOCALITY cannot be filled if ZONE is empty

• BLOCK cannot be filled if LOCALITY is empty

---

Backend-Generated Fields (Must Remain Empty)

The following fields must not be filled by users:

• CRS_BOUNDARY_CODE

Leaving these fields empty ensures correct backend processing and automatic generation.

---

Sample Rows (User-Filled Only)

STATE	CITY	ZONE	LOCALITY	BLOCK	Code	LAT	LONG
Karnataka					(filled by backend)	(optional)	(optional)
Karnataka	Bangalore				(filled by backend)	(optional)	(optional)
Karnataka	Bangalore	Bangalore South			(filled by backend)	(optional)	(optional)
Karnataka	Bangalore	Bangalore South	Koramangala		(filled by backend)	(optional)	(optional)
Karnataka	Bangalore	Bangalore South	Koramangala	Block 1	(filled by backend)	(optional)	(optional)

---

Backend Dynamic Generation Summary

The backend automatically generates the following:

Boundary Hierarchy Tree

Based on user-filled columns:

STATE → CITY → ZONE → LOCALITY → BLOCK

Boundary Code

Generated using:

• Hierarchy level

• Boundary name

• Backend rules