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 2 Next »

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

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

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

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

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

Steps to fill data

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

  2. Then along with the codes fill in the template accordingly.

Validations

  1. No child can be left without a parent.

Do’s and Don'ts

  1. 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:

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

  • No labels