...
This is the 3rd step that comes after the boundary data collection. Cross hierarchy mapping happen in case a child has a relationship with more than 2 parents. This double relationship between the child and parents could happen between different hierarchies as well.
For example : In Admin level boundary hierarchy a mohalla M1(child) could be a part of 2 Wards(parent) W1 and W2. In such a case a single Mohalla(child) has to be mapped to 2 Wards(parent).
...
Below is the data table for the Boundary:
Boundary Hierarchy Types | Boundary Type 1* | Boundary Type 2* | ||
Sr.No | Parent Level* | Parent Boundary Code* | Child Level* | Child Boundary Code* |
1 | Ward | W1 | Mohalla | M1 |
Ward | W2 | Mohalla | M1 | |
2 | Ward | W3 | Mohalla | M2 |
Ward | W4 | Mohalla | M2 | |
...
Below is the definition of columns present in the template:
Boundary Type 1: The type of boundary the parent belongs to.
Boundary Type 2: The type of boundary the child belongs to.
Sr. No: This to mentioned in an incremental order for every one new child level.
Parent Level : This is the Parent level of boundary classification in which the the Parent level is crossing.
Parent Boundary Code: This is the code of the boundary for the Parent level.
Child Level : This is the Parent level of boundary classification which is crossing in the Parent level.
Child Boundary Code : This is the code of the Parent level of boundary.
Steps to fill data
Firstly Identify all the Child child levels which are present in more than 2 Parent levelhave a relation with more than 2 parent boundary types and their hierarchy types as well.
Fill up the boundary hierarchy (names/ codes) types in place of boundary type 1/2.
Then along with the codes start filling in one by one with the proper mapping between every child and parent.
The Sr. No should be in an incremental order for every new child level.
Prepare a new table for every different parent child relation.
Validations
No child can be left without a parent.
All the fields with * sign in the data table are mandatory to be filled in. Without this information, the system configurations cannot be executed.
Parent child code which is being added here should have already been included in the boundary data which was the 2nd step in boundary data collection.
...