Introduction

This is the next step after collating all the boundary hierarchies which are being used in the state.

In a hierarchy there are certain levels of boundary classification and in all the levels there will be a mapping which we could define as a parent child mapping in order to link certain levels of the classification.

For example a hierarchy could be:

State → City → Zone → Ward → Locality

In the above mentioned hierarchy, a state is being divided into different cities then a city into zones followed by zones into wards and at the end wards into locality. Every subdivision must be having some code for example C1, Z1, W1, L1… .

The sub classified entities must be having a mapping between the each other in order to correlate between each other. For example:

There is a state S divided into cities/ULB’s with the city codes as C1, C2, C3,… . And a city is divided into Zones with zone code as Z1, Z2, Z3, the following could be a mapping between these 2 entities:

Further the zones are subdivided into Wards with the ward codes as W1, W2, W3, the following could be a mapping between the wards and zones:

And further the classification could be drilled down to Localities/Mohalla’s etc depending upon the state’s/clients requirement.

Data Table

The following is the data table:

*Mandatory columns

A similar table has to be constructed for all the sub classifications in all the hierarchies.

Procedure

Data Definition

Following is the definition of the data columns which are being used in the

• Boundary Code : This is a code for the sub classification for a particular boundary.

• Parent Boundary Code : This is the mapping code which identifies a parent boundary of a certain boundary code.

Steps to fill data

• After Identifying all the boundary hierarchy, get the sub classification of all the hierarchies.

• Figure out the codes for all the sub classification for a particular city/ULB.

• Start filling the template from the top of the hierarchy in a drill down approach.

• Every Boundary Code should have a mapping with the parent boundary.

• Follow the steps till you reach the last sub classification.

Validations

• All the boundary codes have to be alphanumeric i.e start with the first letter of the sub classification and rest could be followed by numbers.

• There could be infinity hierarchies, but every hierarchy must have a proper sub classification in a similar fashion.

Do’s and Don'ts

• Do not leave any hierarchy.

• Do not leave any boundary code without a parent boundary code.

Attachments

Following is the attached template for the collection of boundary data. The state is free to increase/decrease the boundary sub classification levels according to there requirements.