Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Introduction

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.

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).

Data Table

Below is the data table for the Boundary:

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

*Mandatory Columns

Please note: The data mentioned in the table is a sample boundary data.

Procedure

Data Definition

Below is the definition of columns present in the template:

  1. Sr. No: This to mentioned in an incremental order for every one new child level.

  2. Parent Level : This is the Parent level of boundary classification in which the the Parent level is crossing.

  3. Parent Boundary Code: This is the code of the boundary for the Parent level.

  4. Child Level : This is the Parent level of boundary classification which is crossing in the Parent level.

  5. Child Boundary Code : This is the code of the Parent level of boundary.

Steps to fill data

  1. Firstly Identify all the Child levels which are present in more than 2 Parent level.

  2. Then along with the codes start filling in one by one with the proper mapping between every child and parent.

  3. The Sr. No should be in an incremental order for every new child level.

Validations

  1. No child can be left without a parent.

  2. All the fields with * sign in the data table are mandatory to be filled in. Without this information, the system configurations cannot be executed.

  3. 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.

Do’s and Don'ts

  1. Do not fill the boundary data for the hierarchy which is not present in more than 2 levels.

  2. Do not fill any relationship without a code.

Attachments

  1. Below is the attached template for cross boundary hierarchy:

2. Below is the sample data for cross boundary hierarchy which can be used a reference:

  • No labels