...

In a hierarchy there are certain levels types 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.

...

*Mandatory columns

Please note: The data mentioned here is just for reference and not an actual data.

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

...

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

• 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 boundary code of the parent which identifies a parent boundary of a certain boundary codeto which parent the child belongs.

Steps to fill data

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

...

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

• All the boundary codes weather parent or child have to be unique across the data for a single ULB

Do’s and Don'ts

• Do not leave any hierarchy.

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

...