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 14 Current »

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

Data Table

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

Procedure

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Mandatory

Description

1

Boundary Type 1

-

-

Yes

 The type of boundary the parent belongs to.

2

 Boundary Type 2

-

-

Yes

 The type of boundary the child belongs to.

3

 Sr. No

Alphanumeric

 64

Yes

 This to mentioned in an incremental order for every one new child level.

4

 Parent Level 

Alphanumeric

64 

Yes

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

5

 Parent Boundary Code

Alphanumeric

64 

Yes

 This is the code of the boundary for the Parent level.

6

 Child Level 

Alphanumeric

64 

Yes

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

7

Child Boundary Code

Alphanumeric

 64

Yes

 This is the code of the Parent level of boundary.

Steps to fill data

  1. Download the data template attached to this page.

  2. Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.

  3. In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.

  4. Firstly Identify all the child levels which have a relation with more than 2 parent boundary types and their hierarchy types as well.

  5. Fill up the boundary hierarchy (names/ codes) types in place of boundary type 1/2.

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

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

  8. Prepare a new table for every different parent child relation.

  9. Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.

Checklist

The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Sr. No.

Checklist Parameter

Example

1

Make sure that each and every point in this reference list has been taken care of.

Checklist

Entity Specific Checklist

This checklist covers the activities which are specific to the entity.

Sr. No.

Checklist Parameter

Example

1.

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.

-

2.

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

Data should exist in both the hierarchy types.

3.

Do not fill any relationship without a code.

No code(i.e parent as well as child) field can be left blank

Attachments

  1. Configurable Data Template - Cross Boundary Hierarchy Mapping.

2. Configurable Sample Data Template - Cross Hierarchy Mapping.

  • No labels