Introduction
This is the 3 step that comes after the boundary data collection. Cross hierarchy mapping is done in order to get the data for boundaries which where a cross mapping is happening.
For example : a Parent level of boundary is could be a part of 2 Parent level hierarchies.
In Admin level boundary hierarchy a mohalla M1 could be a part of 2 Wards W1 and W2.
Data Table
Parent Level* | Boundary Code* | Parent Level* | Boundary Code* |
Ward | W1 | Mohalla | M1 |
Ward | W2 | Mohalla | M1 |
*Madatory Columns
Procedure
Data Definition
Parent Level : This is the Parent level of boundary classification in which the the Parent level is crossing.
Boundary Code: This is the code of the boundary for the Parent level.
Parent Level : This is the Parent level of boundary classification which is crossing in the Parent level.
Boundary Code : This is the code of the Parent level of boundary.
Steps to fill data
Firstly Identify all the Parent levels which are present in more than 2 Parent level.
Then along with the codes fill in the template accordingly.
Validations
No child can be left without a parent.
Do’s and Don'ts
Do not fill the boundary data for the hierarchy which is not present in more than 2 levels.
Attachments
Below is the attached template for cross boundary hierarchy:
| View file | ||
|---|---|---|
|
Below is the sample data for cross boundary hierarchy which can be used a reference:
| View file | ||
|---|---|---|
|