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:

City/ULB → Zone → Ward → Locality

In the above mentioned hierarchy, a city/ULB 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… .

Data Table

Data has to be collected for every boundary hierarchy level with a mapping between the boundary code and its parent boundary code. Following is the table which is to be used across all the hierarchy classifications:

*Mandatory columns

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

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.

• Boundary Name(English) : The name of the boundary that is being defined in English language.

• Boundary Name(Local Language) : The name of the boundary that is being defined in the local language of the state.

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

Steps to fill data

Following are the steps which should be used to fill the template:

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

• A parent child mapping code has to be created for every boundary level except for the top level.

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

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.

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.

• Every boundary level classification should have one template each.

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

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.

• Below is the attached sample data file for admin level hierarchy boundary data: