Table 2. Example Attribute code table for landuse/ landcover : luse.lut
(Source : Illustrative codes from NRIS Standards document)

Code	Description
	Level 1	Level 2	Level 3	Level 4
01-00-00-00	Built-up
01-01-00-00		Towns/cities (Urban)
01-01-01-00			Residential
01-01-02-00			Industrial
01-01-02-01				Salt pans
01-01-03-00			Commercial
01-01-03-01				Bus Stands
01-01-03-02				Rly Yards
01-02-00-00		Villages (Rural)
02-00-00-00	Agriculture
02-01-00-00		Crop land
02-01-01-00			Kharif
02-01-02-00			Rabi
02-02-00-00		Fallow
02-02-01-00			Current Fallow
02-02-02-00			Permanent Fallow
03-00-00-00	Forest
03-01-00-00		Evergreen/ Semi evergreen
03-01-01-00			Dense/ Closed
03-01-02-00			Open
03-02-00-00		Deciduous (Moist/Dry)
03-02-01-00			Dense/ Closed
03-02-02-00			Open
03-05-00-00		Shifting cultivation
03-05-01-00			Old Shifting Cultivation
03-05-02-00			Abandon Shifting Cultivation
03-05-03-00			Current Shifting Cultivation
03-06-00-00		Crop Land in Forest
04-00-00-00	Wastelands
04-01-00-00		Salt Affected Land
04-02-00-00		Gullied/ Ravenous Land
05-00-00-00	Water bodies
05-01-00-00		River
05-01-01-00			Water channel area
05-01-02-00			Sandy area
05-02-00-00		Canal
05-08-01-00			Back waters
05-08-02-00			Estuary/ Kayal
05-09-00-00		Cut-off Meander
07-00-00-00	Grass land / Grazing land
07-01-00-00		Dense
07-02-00-00		Degraded
STRUCTURE OF THE TABLE
Field –Name	Field Type	Key field(Y/N)
LU-Code	8,8,C	Y
Discr-L1	30,30,C	N
Discr-L2	30,30,C	N
Discr-L3	30,30,C	N
Discr-L4	30,30,C	N

Database Contents & Naming Conventions
A typical domain database would consist of both spatial and non-spatial data elements. A comprehensive list of data elements both spatial as well as non-spatial form is to be made. While making this list, care has to be taken to minimise the redundancy in the database by identifying the each input element to be a mutually exclusive item. Each of the listed elements has to be associated with specific system names for reference while accessing the database. Furthermore each element will have associated with it an attribute code table (name to be fixed) and a key field (fixed name) linking the spatial element with attribute table. An illustrative list of data elements has been provided in Table-1.

Feature Codification for individual Database Element
Each of the database elements has to follow pre-defined codification scheme. It is suggested to follow hierarchical codification as follows:

• Harmonise Various Mapping Legends prevailing in a particular theme ( e.g. Landuse- Coastal, wastelands, Forest …)
• Encompass Natural & Administrative hierarchy e.g. Landuse (Level-1,2,3,4), Admn (District, Taluk, Village) Watershed, Sub-watershed … Advantages of hierarchical codification approach
• Flexible extension of codes - Inclusion of occurrences at any level
• Reduced redundancy & improved integrity by entry of spatial features only at lowest level e.g Villages -> taluk, districts; Micro-watersheds -> mini, sub, ..
• Scope for tie-up with various collateral data sources.
  
  A typical codification for Landuse/ Landcover theme adopted under NRIS is given in Table 2 as an example.