Geo-visualisation for local resource planning- A Free / Libré / Open Source Approach.
Dissertation submitted to the School of Environmental Sciences, Mahatma Gandhi University in partial fulfilment of the requirement for the award of
Master of Science in Environment Science and Management
during Fourth Semester.
By
Jaisen. N. D. Reg No: 130608
Under the guidance of
Dr. T. V. Ramachandra Energy & Wetlands Research Group Centre for Ecological Sciences Indian Institute of Science Bangalore.
School of Environmental Sciences
Mahatma Gandhi University
Kottayam.
June 2008. This Work is dedicated to:
The People Declaration
I, Jaisen. N.D. hereby declare that the work presented in the dissertation entitled ‘Geo-visualisation for local resource planning - A Free / Libré / Open Source
Approach.’ is a Free / Open Source project completely, and no proprietary software tools or software platform is used in any part of this work. This project is submitted to the School of Environmental Sciences, Mahatma Gandhi University in partial fulfilment of the requirement for the award of the degree of Master of Science in
Environment Science and Management is a genuine record of the work I carried out at Centre for Ecological Sciences, Indian Institute of Science, Bangalore under the supervision of Dr.:T. V. Ramachandra, during 2008 (February to June) and no part of this work has formed the basis for the award of any degree, diploma or any other similar titles of any Universities.
Place: Bangalore Jaisen. N.D.
Date:
SCHOOL OF ENVIRONMENTAL SCIENCES MAHATMA GANDHI UNIVERSITY Tel : 0481-2732120, 2732620 PRIYADARSINI HILLS P.O., Fax : 0481-2732620 KOTTAYAM- 686 560, KERALA, INDIA. E-mail: [email protected]
CERTIFICATE
This is to certify that the dissertation entitled ‘Geo-visualisation for local resource planning - A Free / Libré / Open Source Approach’ is an original work done by the candidate, Mr. Jaisen. N. D. in CES, IISc, Bangalore under the supervision of Dr. T. V. Ramachandra, Energy & Wetlands Research Group, CES, IISc., and no part of the dissertation has formed the basis for the award of any degree, diploma or any other similar titles of any other University.
Place: Dr. A. P. Thomas Date: (Professor & Director) Abstract
73rd and 74th amendments of Indian constitution have strengthened the rural and urban local bodies all over the country, significantly. The role of local bodies in local resource planning is increasing, ever than before. In the context of rural local bodies, the Panchayat Raj system and grama sabhas become institutionalised by 73rd constitutional amendment, and converted them to true decision makers in plan and development activities which serve local needs.
This work is an attempt to develop a simple spatial decision support system, suitable for local area planning and developmental endeavour. SDSS is developed using Free/Libré/Open Source softwares, as free softwares grant ultimate freedom for it's users to alter and to make further modifications to adapt it for their added demands. This ensures the technical feasibility and economic viability for planning at decentralised levels with a capability to visualise decisions before implementation.
i Acknowledgement
I express my heartfelt thanks and gratitude to Dr. T. V. Ramachandra, Centre for Ecological Sciences, Indian Institute of Science, Bangalore who introduced this topic to me and, for his guidance, constant attention, critical suggestions and personal encouragement in doing this work.
I take opportunity to express my sincere gratitude to Dr. K.V. Gururaja, Sudhira.H.S., Uttam Kumar, Boominathan. M, Karthick. B, and Sindhu Prasanna and all other members of Energy and Wetlands Research Group, Librarian and staff at Centre for Ecological Sciences, Indian Institute of Science, Bangalore for their kind advice, suggestions, and help during the project.
I express my sincere thanks to all the faculty members of SES, Mahatma Gandhi University, especially to our Director Dr. A. P. Thomas, Dr. E. V. Ramasamy, Dr. Annie Mathai, Dr. Retnamma for their kind suggestions and encouragement. I would also like to thank to Rakesh. P. S, Joby Paul, Sylas, B. Ajaykumar, my dearest classmates, alumni and all other members of SES family for their encouragement and help.
My heartfelt thanks to Mr. Sameer Thahir (Co-ordinator) and Mr. Balakrishna Pillai (Member) of ILUG - Cochin, for clearing my doubts on setting up Debian GNU/Linux and configuring PostgreSQL.
I express my sincere gratitude to Vimal Joseph, Anivar Aravind, Praveen. A, and Santhosh Thottingal along with all other fellow members of Swathanthra Malayalam Computing, for their timely help on resolving software related problems during the project.
I have no words to express my sincere thanks to Mr. Sajith V. K. (Geo- informatics division, KELTRON, Thiruvananthapuram) who helped me to overcome the initial hitch on GRASS GIS and introducing me to various Free / Open source geo-visualisation tools, and without his encouragement and supportive mind, the entire project might have been impossible.
Without adopting a give and take policy with the user groups and mailing lists, a free software project would be hard to complete. I hereby mentioning all
ii the members of the the three user groups namely [email protected], [email protected] and [email protected] with deep sense of gratitude, where I received timely solutions on the software related problems. I would remember Mr. Johan Van de Wauw at Laboratory of Soil Science, Universiteit Gent, Belgium, Lorenzo Becchi, Alessio Di Lorenzo, Luca Casagrande and Peteris Bruns at [email protected] with gratitude, for their nice tips on ka-map.
I express my sincere gratitude to E. Dinesan, Sree Sankaracharya University of Sanskrit, Kalady, who helped me to clarify some doubts on the historical background of the study area.
My dearest mother, father, sister and other members of my family have been of immense help to me with encouragement. I remember them with deep sense of indebtedness.
- Jaisen. N. D.
iii Contents
Page Chapter Title No. 1. Introduction 1 1.1. Decentralised planning 1 1.2. Geo-visualisation 2 1.3. GIS and Geo-database 3 1.4. Categories of software technologies 4 1.4.1. Free/Libré/Open Source Software 5 1.4.2. Proprietary software 5 1.5. Selection of right software tools in the context of panchayats 6 2. Objectives 9 3. Study area 10 3.1. Physiography 10 3.2. History 10 3.3. Trivia 11 3.4. Present status 11 3.5. Agriculture, environment and life 14 3.6. Panchayat Raj experiments 16 3.7. Decision making in Cheruvannur Grama Panchayat 16 3.7.1. Grama sabha and it's importance 17 3.7.2. Development seminar 17 3.7.3. Plan-making grama sabha 17 3.7.4. Conventional method and limitations 18 4. Review of Literature 20 5. Basic database concepts 26 5.1. Database as a system 27 5.2. Designing databases 27 5.3. Relational data model 27 5.4. Entity Relationship Diagram 30 5.5. Normalisation 31 5.6. Database integrity 32 5.7. Computer based record keeping systems 33 5.8. Current Scenario 34 5.9. Need for local level geo-database and geo-visualisation 34 6. Cartography, Geo databases and Geoinformatics 35 6.1. Map projections 37 6.2. Geoinformatics 42
iv Page Chapter Title No. 6.3. Recent trends in GIS 43 6.4. Geo database 43 6.4.1. Characteristics of spatial databases 43 7. Methodology 45 7.1. Data collection 45 7.2. Setting up / upgradation of Hardware 45 7.3. Setting up the software environment 46 7.3.1. Installation of operating system 46 7.3.2. Post install configuration of operating system 46 7.3.2(a). Adding addresses of essential software locations to the 46 system's source list: 7.3.2(b). Network and internet configuration 47 7.3.2(c). Set-up for Unicode Malayalam support 47 7.3.2(d). OpenSSH 48 7.3.3. Installation and configuration of essential softwares for the 48 proposed work 7.3.3(a). Apache web server and php 49 7.3.3(b). Installation of PostgreSQL and PostGIS 49 7.3.3(c). Installation and configuration of GRASS 6.2.3 50 7.3.3(d). Installation of Quantum GIS 0.9.0 51 7.3.3(e). Installation of MapServer 51 7.4. Scanning and photographing maps 51 7.5. Georeferencing maps 52 7.6. Digitisation of vector layers 57 7.7. Creating database and attribute tables in PostgreSQL 59 7.7.1. Installation of a front-end to PostgreSQL database 60 7.8. Correction and completion of attribute tables and data entry 60 7.9. Creating base maps 61 7.9.1. Creating shaded relief map 61 7.9.2. Creating land use map 63 7.9.3. Converting the base map tif images to GeoTIF format 63 7.9.4. Exporting vector layers as shapefile format 64 7.10. Setting up visualisation 65 8. Results and Discussion 67 9. Conclusion 85 10. Future scope of work 86
v Page Sl. No. Reference and Annexure No. 1. Reference 87 2. ANNEXURE - I 91 3. ANNEXURE - II 92 4. ANNEXURE – III 93 5. ANNEXURE – IV 97 6. ANNEXURE – V 101
vi List of figures Page. Fig.No. Description No. 1.1. Categories of softwares. 5 3.1. Location of study area. 10 3.2. Office of the Cheruvannur Grama panchayat. 12 3.3. Govt. Public Health Centre, Avala. 12 3.4. Govt. Ayurveda Hospital, Cheruvannur. 13 3.5. Anganwadi centre, Nirappam kunnu. 13 3.6 Govt. U. P. School, Cheruvannur. 13 3.7. Valayarott kavu: A sacred grove in Cheruvannur. 14 3.8. Parappuzha Pandi: Paddy field. 14 3.9. Avala Pandi: Paddy field. 15 3.10. Kuttiyadi river: Scene near Avala. 15 3.11. Scene from river sand mining site, Chaniyam kadavu. 15 3.12. Weir near Kanhirakkuni. 16 5.1. A relational database model. 28 E-R Diagram depicting the decision making process related to 5.2. 31 the plan and development activities in Grama Panchayat. 5.3. Essential components of a DBMS. 34 Map of Cheruvannur grama panchayat showing common 6.1. 36 features. 6.2. The Earth surface showing surface irregularity. 38 6.3. Earth's ellipsoid, geoid, and two types of vertical deflection 41 6.4. Difference between global and local ellipsoids 42 6.5. Design of a web based Geo-database. 44 7.1. Georeferencing in GRASS - steps. 53 7.2. Diagrammatic representation of visualisation set-up. 66 Boundary lines of Cheruvannur village in Cheruvannur Grama 8.1. 67 Panchayat. Contours of Cheruvannur Grama Panchayat at 10 meters 8.2. 68 interval. 8.3. Land use pattern of Cheruvannur Grama Panchayat. 68 8.4. Ward boundaries of Cheruvannur Grama Panchayat (2000-2005). 69 8.5. Ward boundaries of Cheruvannur Grama Panchayat (2005-2010). 69 8.6. Stream channels (drainage). 70 8.7. Rivers and ponds. 70 8.8. Irrigation canals. 71
vii 8.9. Sacred groves. 71 Water resource development structures / Water flow control 8.10. 72 structures. 8.11. Sub watershed boundaries in Kuttiyadi river watershed area. 72 8.12. General public facilities – Government offices, Ration shops, etc. 73 8.13. Medical facilities. 73 8.14. Education facilities. 74 8.15. Child development - Anganwadi centres. 74 8.16. Communication facilities. 75 8.17. Energy – position of transformers and H.T. Line. 75 8.18. Roads. 76 8.19. Place names. 76 8.20. DEM. 77 8.21. Shaded relief. 77 8.22. Shaded relief map. 78 8.23. Rasterised vector layer land use. 78 8.24. Land use map - land use pattern of the grama panchayat area. 79 Spatial Decision Support System for Cheruvannur Grama 8.25. 80 Panchayat. 8.26. Layer selection – roads and place names. 81 8.27. Identify and query facility. 81 8.28. Search facility. 82 8.29. Display at scale – 1:20000. 82 8.30. Display at scale – 1:10000. 83 8.31. Locate feature (Scale 1:5000). 83 8.32. Panning in key map. 84 8.33. Land use overlayed on shaded relief. 84
viii 1. Introduction
1.1. Decentralised planning:
The word “decentralisation” indicates the presence of something at the centre, from there it may be dispersed. The planning and developmental activity carried out through decentralised way is referred as decentralised planning. Governments favour the concept of decentralisation because it implies the hope of opening the blockages of an inert central bureaucracy, giving more direct access for the people to the government and the government to the people, which essentially stimulate the entire nation to participate in national development plans (Mahwood, 1993). Decentralisation is a natural indispensable counterpart to pluralistic democracy, that is, it extends the work of democracy and fulfils democratic aspirations (Reddy, P.S. & Sabelo, T., 1997). Experiments in decentralised planning in many parts of the world show that this way of approach has the capacity to serve local needs. Decentralisation significantly changed public investment patterns in Bolivia. Throughout the country, investment changed unambiguously in education, water and sanitation, water management, agriculture and urban development after the 1994 reform. And these shifts are strongly and positively related to real local needs. In education, water and sanitation, water management, and agriculture, post-decentralisation investments are higher where illiteracy rates are higher, water and sewerage connection rates lower, and malnutrition a greater risk, respectively (Faguet, J.P., 2004).
In India, ideology of decentralisation by the term “gram swaraj” was introduced by Mahatma Gandhi, in pre-independence age. But experiments on decentralisation were taking place in isolated places of the country even before independence, especially in parts of the states of Karnataka and Kerala (Saito, C. & Kato, R. 2008).
Ambitious decentralisation efforts have been started nationwide, after passing a series of amendments in the constitution. The passing of the 73rd and 74th constitution amendments came in to effect in 1993, which institutionalised and empowered the rural representative bodies – the Panchayats (Johnson, C., 2003). Eventually, decentralised planning started to mediate through panchayats.
1 The 73rd amendment to the constitution of India delegated power to its states to pass acts to establish grama sabha and panchayat raj system with two or three tiers and to transfer powers to them (74th amendment is related with urban local bodies). This gave birth to acts related to panchayat raj nationwide, and established the local self government institutions in the states spanning from village, intermediate, and district levels. Established as the 3rd stratum of governance in India, with constitutional provisions, panchayats and grama sabhas have to take different sorts of decisions on developmental activities and implement them.
Decision making on developmental activities, entail planning that depends upon the availability of reliable and accurate data. Data required for natural resource planning is spatial data such as, information of physiography of the area, land use, what assets where situated, what ever things are affected with a particular project or decision etc., with an attribute information. Geographic information system (GIS) with a capability of handling spatial data helps in the analysis and visualisation of results effectively, and aids decision making process.
A Spatial visualisation of all the important assets, general physiography of the area, land use etc., based on a geo-database will be an added support for decision makers. As the imagination power and knowledge in different subjects varies from person to person, there may have chances of communication gaps between different stake holders.
There are many live examples around the world, of successful usage of GIS for solving decision making problems especially in the field of planning for example, those in various authorities in Greece, Germany, and Portugal (Masser etal, 1996). In India, there are online map services and GIS based information systems for few regions like Mumbai metropolitan area and Vasai Virar Subregion of Mumbai, Slum Information System (Korba Slum, Mumbai), Village Information System (Maharashtra) etc. However, use of geovisualisation for local level decision making in panchayats is at very primitive stage in India.
1.2. Geo-visualisation:
Geo-visualisation can be stated as a visual geo-spatial display. It enables the user to explore the geo-spatial data. By this exploration it helps to generate
2 assumptions or hypotheses, and through this way, it help the user to develop solutions for problems and construct knowledge, particularly on a defined geographical area.
Key parts in a geo-visualisation are maps (spatial data), associated attribute data and linked graphical visualisation. It is a set of hardware and software tools and techniques which support geo-spatial data analysis through the use of interactive visualisation.
Geographic visualisation or geo-visualisation is defined as “The interface between cartography and scientific visualisation, and between technology for mapping and ways in which mapping can facilitate geographic thinking” (MacEachren, A. M. and Monmonier, M. 1992).
Geo-visualisation has been developed essentially with the help of GIS. GIS, Geo-database and Geo-visualisation are increasingly used in various fields, a few of them are
1. Data storage and distribution alternatives 2. Environmental studies. 3. Military / Intelligence applications 4. Multimedia development 5. Reconstruction of historical events and settings 6. Information systems and planning
1.3. GIS and Geo-database:
A Geographical Information System (GIS) is a computerised system, and its primary purpose is to help to maintain data about geographic space (De By, RA, 2001). It is a set of tools for collecting, storing, retrieving at will, transforming, and displaying spatial data from the real world for a particular set of purposes (Burrough P.A. 1986). In other words, GIS is a computer system to capture, store, check, integrate, manipulate, analyse and display the data related to positions on the earth's surface.
GIS is in use for various fields, namely town and country planning, hazard analysis, geology, mining, forestry, hydrology etc for handling information in a
3 spatial context. A GIS is a logical arrangement between geographic features and attribute data. So it has two major parts, one for generating, analysing and representing geographic features and the other is a database, which stores the geographic features along with attribute data.
Being a computer based system, GIS essentially deals with softwares. GIS software fall into two major branches, proprietary GIS (like ArcGIS, ERDAS IMAGINE, MapInfo etc) and the wide array of Free / Open Source counterparts like GRASS, QuantumGIS, SAGA, GMT, etc.
GIS softwares have inbuilt database management system, and more often also have some provisions to connect with an external DBMS. The data related to the geographical features are stored in DBMS, as attribute tables and records, and these data are linked with the geographical features via a key field. Geo-database is a specific type of database, which store representations of geographic phenomena in the real world to be used in a GIS (De By, RA, 2001).
1.4. Categories of software technologies:
There are two major categories of technology development and distribution models, in the world of softwares. The model of proprietary softwares, share wares and closed-source ones, and Free / Libré / Open Source and public domain software. Further sub-categories are also there, inside these major categories. Figure: 1.1 provides differences among these categories.
4 Figure 1.1: Categories of softwares. (Image courtesy: Chao-Kuei, www.fsf.org)
1.4.1. Free/Libré/Open Source Software: 1. Free software: A free software is “that comes with permission for anyone to use, copy, and distribute, either verbatim or with modifications, either gratis or for a fee” (www.fsf.org) and essentially the source code of the software is available. 2. Open source software: As per the open source initiative, “Open source is a development method for software that harnesses the power of distributed peer review and transparency of process. The promise of open source is better quality, higher reliability, more flexibility, lower cost, and an end to predatory vendor lock-in” (www.opensource.org).
In common practice, Free, Open source and allied classes of softwares are grouped as one, and referred to as Free/Libré/Open Source Software and abbreviated as FLOSS or FOSS. The active user communities and developer communities around the globe are peculiar for this group of software.
1.4.2. Proprietary software: Proprietary softwares are “Computer programs which are the legal property
5 of one party, the use of which is made available to a second or more parties, usually under contract or licensing agreement” (State administrative manual, Dept. of General Services, State of California). Contrary to free softwares, proprietary softwares are with restrictions on use or private modification, copying, or publishing of modified versions.
1.5. Selection of right software tools in the context of panchayats:
Factors that decide the adoption of a particular software technology for planning at rural decentralised levels in public sector are:
1. Financial affordability: The technology should be financially affordable and suitable for the panchayats considering the plan outlay for local bodies. Most often, any of the FLOSS software for even specific uses are available free of charge. Some times the choices to select are more than one. For example, Debian GNU / Linux, a free operating system, comes with 18733 (www.debian.org) pieces of software for a variety of uses. Being these softwares are available free of charge, and come with a liberal license agreement (Chen Shun-ling, 2006), they are financially affordable.
2. Reliability: Reliable technology need to be adopted to minimise the running cost and allow the users to solve the problem themselves. In the case of reliability of operating systems, GNU/Linux, is more stable than proprietary counterparts according to studies (Wheeler, D. A.). GNU/Linux is free software, and many of its flavors are available without a hitch. These include the distributions like Debian GNU/Linux, which take the factor of system stability with a higher importance, available free of cost and used by a wide range of users of varying fields including educational institutions, commercial firms, non-profit organisations, and government organisations.
3. Support: For an effective local area planning, the technology should have enough technical support at all levels from the developer to the end user. Support from user communities and from the people who develop the FOSS software, spanning throughout the globe is an added advantage of free software. Users and developers are available on web forums, mailing lists, and on IRC channels to help out new users.
6 4. Security: The data security forms an important component in adopting particular technology and the technology should be free of any bugs and security holes. FLOSS is considered to be less vulnerable than proprietary softwares, because the source code is accessible (Redners tryckeri, 2003). Whoever want to look at the code, they can. People can check for any flaws in code, and found if any, can report a bug in bug tracking systems, and which are quickly repaired by the developer community. People can even develop their own solution for the security flaws they found and submit it to developers. There are more eyes, heads and hands are involved in this bazaar style development model, than the proprietary cathedral model. More eyes make fewer security flaws.
5. Community culture: The panchayats and grama sabhas, with different committees, beneficiary groups etc, present a community driven development model, which necessitates interoperable model. The support for FLOSS softwares are mainly through user groups and developers communities, rather than from commercial firms. The users and developers around the globe act as a global community, within which they share ideas to solve the problems and to make the software they use even better. This nature is very much similar to the participatory development model of grama panchayats, a model in which people share the ideas by communicating with each other, discussing, debating and selecting the right choice for them.
6. Comply with the current policy of the government: The technology need to comply with the present polices of 1st and 2nd stratums of governance as panchayats are an integral part of the governance system in India, along with union government, and state governments.
7. In India, the union government has setup a National Resource Centre for Free & Open Source Software in Chennai jointly with C-Dac and Anna University, with an objective to contribute to the growth of Free and Open Source Software in India (Information Technology Annual Report, 2007- 2008). The Information technology policy of state government of Kerala emphasises that “Free Software presents a unique opportunity in building a truly egalitarian knowledge society” and further says “Free and Open Source Software will be used in all government funded ICT e-Governance
7 projects to the maximum extent possible” and “intends to develop the State as the FOSS destination in the country (Information Technology Policy Document, 2007).
Availability of a wide range of softwares free of cost, including GIS tools is an added advantage of FLOSS model. It gives choices and options to select the most suitable, from the available.
The current endeavor focuses on the development of a geo-database and geo-visualisation based decision support system for panchayats using FLOSS for planning and development activities at panchayat level.
8 2. Objectives
Main objective of this endeavor is to develop appropriate geo-visulisation for an effective local level planning with the open source spatial information systems. Free / Libre / Open Source GIS software tools and Free operating system is used mainly to be economically viable and also to comply with the current I T Policies of the government. This endeavor involves:
1. Creating a geo-spatial database (for Cheruvannur Grama Panchayat) compiled from locally available data sources.
2. Developing geo-visualisation of basic themes in pre-defined scales, based on the geo-database, using open source spatial information systems, suitable for decision making and planning at disaggregated levels.
9 3. Study area
Figure 3.1: Location of study area 3.1. Physiography: Cheruvannur, one of the 78 grama panchayats of Kozhikode district, lies between North Latitude 11° 32' 37.11” and 11° 36' 4.67”, East Longitude 75° 40' 26.32” and 75° 43' 55.22” (Figure: 3.1). It has a total area of 21.61 square kilometers. The adjoining grama panchayats are Thiruvallur and Velom in the north, Perambra in the east, Nochad, Meppayur, and Thurayur in the south, Maniyur and Thiruvallur in the west. The Kuttiyadi river (Figure 3.10), erstwhile known as Kotta river is flowing from north to south, through the eastern side, detaches the grama panchayat from Vadakara taluk. The physiography is not planar. The ridges of smaller and medium hills and low lying valleys make the area an undulating terrain. Grama panchayat can be divided into three, according to the physiography – viz, hilly area, slopes and valleys. The highest area in grama panchayat is Purakkamala (പറകാമല) noted with a height of 115 metres above sea level. Cheruvannur Grama panchayat includes some of the lowest lying places of the region, and parts of these areas are often flooded during monsoon.
3.2. History: Formed in the year 1934 it is one of the oldest grama panchayats in the state. The area has a long history of human settlements. A hat stone (ൊൊാപികല്) -
10 megalithic burial monument - belongs to roughly a period of 300 B.C. to 500 A.D
(Ganesh, K.M., 1990.) is seen in Edakkayil (എടകയില) as a proof. A cave (Innes.
C.A, Evans. F.B.(Ed.), 1958) is also present in Moyiloth (ൊമായിോലാത്) near Muyippoth belongs to the same period, now lies under thick soil cover which was carelessly deposited on it during the construction of irrigation canal passing there by, remains almost forgotten.
Before British occupation, the place was included in Payyormala (പോോാരമല) a feudal principality controlled by three nair families namely Paleri (പാോലരി), Avinhatt (അവിഞാട്), and Koothali (കതാളി) and those acknowledged the suzerainty of Zamorin of Calicut (ോോാഴിോകാട് സാമൊിരി) (Innes. C.A, Evans. F.B.(Ed.), 1958). Payyormala is a slightly elevated area near Edakkayil, from where the name of the principality evolved, now remains a place of less importance. Remnants of a small shrine of payyormala muthassi (പോോാരമല മതശി) the guardian angel of the principality, still seen here. Under British administration the area included in Kurumbranad taluk, Malabar district of Madras presidency (Innes. C.A, Evans. F.B.(Ed.), 1958). At present it find its place in Perambra development block and in Koyilandi taluk, Kozhikode district of Kerala state. The people from the region has a rich tradition of participation in various important historical events, among them
Pazhassi revolts (പഴശി സമരം) against the rule of British East India Company took place between 1796 to 1805 and Koothali strike (കതാളി സമരം) took place in the period of 1940 -1950 are most notable. Many of freedom fighters who participated in mainstream freedom struggle, and two people who joined in I.N.A and fought against the British were from this area.
3.3. Trivia: Cheruvannur grama panchayat is often mistaken with Cheruvannur- Nallalom grama panchayat both in official and civil correspondences by its name, the later lies in Kozhikode taluk of Kozhikode district itself.
3.4. Present status: Grama panchayat is divided into 14 ward constituencies for developmental and administrative purposes. The representative members are elected from each ward for a quinquennium to the grama panchayat administrative committee. In the period of 1990-1995 the number of wards were 9, in 1995-2000 it was 10, in 2000- 2005 period it increased as 12 and now, for the period of 2005-2010 the number of ward constituencies are 14. The increase in number of wards is based on the
11 criteria set up by the State Election Commission, which finds the basics of increase in population, increase in the number of households etc.
The total population of Cheruvannur grama panchayat is 22150 and number of households are 4663 (Census 2001). It has a good connectivity of 27.477 kilometers of paved and 59.670 kilometers of unpaved roads. A total number of 65 ponds 12.629 kilometers of irrigation canal is present now.
Figure 3.2: Office of the Cheruvannur Grama panchayat.
In health sector, people of Cheruvannur Grama Panchayat have accessibility to the three systems of medicine by the presence of 1 Govt. PHC (Figure: 3.3), three FW centres, 1 Govt. Ayurveda Hospital (Figure: 3.4) and a Govt. Homeopathy dispensary. A total number of 20 Anganwadi centres (Figure: 3.5) serve the child welfare part very well.
Figure 3.3: Govt. Public Health Centre, Avala.
12 Figure 3.4: Govt. Ayurveda Hospital, Cheruvannur.
Figure 3.5: Anganwadi centre, Nirappam kunnu. In education sector, 10 lower primary schools, three upper primary schools, 1 high school, 1 higher secondary school, 1 un-aided school are present, and among them 1 U. P. School (Figure: 3.6), 1 L. P. School, high school and higher secondary school are in Govt sector.
Figure 3.6 : Govt. U. P. School, Cheruvannur.
13 3.5. Agriculture, environment and life: Avala pandi paddy field hosts numerous migratory birds each year. Sacred groves are places of worship and at the same time, traditional method of ecological conservation (Figure: 3.7). Place has a immense activity in agriculture particularly in rice cultivation. The area has a good potential for eco-tourism, with its scenic beauty not known much outside (Figures: 3.8, 3.9, 3.10 and 3.12), connectivity of roads, sensible people, essential communication and medical facilities.
The major source of income for the people living nearby river, is sand mining from the Kuttiyadi river (Figure: 3.11). Sand mining activity is controlled by grama panchayat, district collector, and district level kadavu committee jointly. This is the major income source to own fund for grama panchayat also.
Figure 3.7: Valayarott kavu: A sacred grove in Cheruvannur.
Figure 3.8: Parappuzha Pandi: Paddy field.
14 Figure 3.9 : Avala Pandi: Paddy field.
Figure 3.10: Kuttiyadi river: Scene near Avala.
Figure 3.11: Scene from river sand mining site, Chaniyam kadavu.
15 Figure 3.12: Weir near Kanhirakkuni.
3.6. Panchayat Raj experiments:
The 73rd and 74th amendments to the constitution of India gave birth to to the Kerala Panchayat Raj Act 1994 replacing Kerala Panchayat Act 1960 and associated acts and rules, and established a three tier Panchayat Raj system and local self government institutions in the state spanning to village, block, and district levels. Among these, grama panchayats have more importance as they have almost all the important components of a modern government. They have a legislature, an executive, authority to impose and collect taxes and to enforce bye laws, administration and financial powers, and all these make them true local governments. The new act and rules empowered the grama panchayats with financial powers even more. Being a part of 3rd stratum of governance in India, and empowered with various civil, quasi-judicial and administrative powers over a defined geographical area, the administrative body of a grama panchayat has to take different sorts of decisions and implement them.
3.7. Decision making in Cheruvannur Grama Panchayat:
Decisions on day to day activities relating to the grama panchayat are taken by the President, Secretary, heads of institutions under grama panchayat (Annexure: 1), other implementing officers, administrative committee, finance, development, welfare standing committees, various sub-committees at different levels.
16 3.7.1. Grama sabha and it's importance: For developmental activities, the process of decision making is done by grama sabha, a permanent statutory body described in the constitution of India. In Kerala scenario, grama sabha meetings are official ward level meetings, usually headed by ward member / president. Each elector resides in ward are the de-facto members of grama sabha, and these meetings take place 4 times in a year, and the interval between two grama sabhas will not exceed 6 months. Quorum for grama sabha is 10% of the total number of electors of that ward (Kerala Panchayat Raj Act, 1994). If it not satisfied, grama sabha is postponed to another convenient day. Ward member is the convener of the grama sabha and coordinators for each grama sabha would be one among the staff from any of the institutions under the grama panchayat, as decided by administrative committee on the advice of grama panchayat secretary. Dates for the grama sabhas in each ward are also decided.
3.7.2. Development seminar: In the first grama sabha, two or three representatives will be selected and send to forthcoming panchayat level development seminar. A short booklet is prepared, printed and distributed by the administrative committee, in development seminar as draft plan document in development seminar. Draft plan document contains the details of state plan funds alloted for the grama panchayat ear- marked for each developmental sectors as published in state's budget annexure, the details about own fund in grama panchayat's accounts, a draft outline of the proposed projects for that financial year. Also, a brief oral introduction is given by the Panchayat president and members. In the development seminar the representatives from grama sabha are fed with some ideas, and in next grama sabha, they perform in the role of resource persons to lead the group discussions.
3.7.3. Plan-making grama sabha:
The second grama sabha is a 'plan-making' grama sabha, in which more often draft plan document undergo open discussion, and heavy modifications. There may occur a debate on the performance of the grama panchayat in different developmental or administrative sectors on behalf of the grama sabha, some times may lead to open criticism. The convener and coordinator are supposed to respond to each of them. After this, people are divided into different groups of beneficiaries,
17 open discussions and debates takes place on the topics, and proposals for alterations, insertions, deletions and additions are suggested on the draft plan document and read in grama sabha meeting. These suggestions are approved jointly, or with modifications duly recorded in grama sabha minutes. After ending up the grama sabha meetings in all wards, all the decisions of grama sabhas are compiled, draft is changed according to it and final plan project document is prepared for the year, by the administrative committee and staff.
The copies of final plan document are sent to Technical Advisory Group (T.A.G), a block level experts group and to D.P.C. D.P.C or District Planning Committee is a statutory body, which acts as the representative of the state, to approve the plan documents of panchayats.
The final plan document is not an unchangeable one, as the grama sabha reserves the right to make modifications to it, in any of its fourth coming sittings. Some times plan document undergo fund adjustments as per the availability of funds.
Even if alterations in minor details of these whole process may vary from time to time depending on the region it takes place, or as per the guidelines of the state government, the outline of the whole process remain same.
3.7.4. Conventional method and limitations:
To formulate the plan projects several documents are used at various levels. For agricultural schemes, developing infrastructure etc, documents like watershed based development master plan, resource maps, road register are used for getting base data. Using the details from these documents, the teams formulate plan projects. As all these documents are available in office of the grama panchayat, formulation of details of plan projects are done in grama panchayat itself. The conventional method is fine, but has some drawbacks, indeed as discussed below:
1. A new entrant, (most probably coordinators of gramasabha) to these processes normally take some time to understand the general physiography of the area, land use, assets and location of assets, and also implications of a particular project or decision. 2. As the knowledge in different subjects varies from person to person, there
18 are chances of communication gaps between different stake holders leading to wrong decisions.
3. Project beneficiaries and decision makers usually think only about the benefits of their proposed work, without a holistic approach. This practice can't be effectively tackled down in conventional method.
4. Panchayat resource maps are often in 1: 4000, or 1: 5000 scales, and often 4 or 5 large sheets. These sheets are difficult to handle in discussion sessions. Searching and carrying all the documents relating to a plan project to the desk one by one and placing back each of them would be a tedious task.
5. The process of planning and implementing of a project is a time bound one, if it isn't finished, the funds allotted go lapse. So there is a tendency to however prepare plans proposed in grama sabhas without referring all documents concerned, to avoid the lapse of funds, the open questioning may essentially arise in the very next grama sabha and political failure.
These disadvantages can be addressed with the use of technology to an extent. Presenting essential details of the resources through spatial visualisation with the help of technology, would support the decision making process. The modern techniques of Geographical Information Systems (GIS) and geo- visualisation can be used for such a move. There are many successful efforts in the various parts of the world using GIS and Geo-visualisation for solving real-life problems and for decision making, especially in the field of planning. Presence of a comprehensive geo-database will serve as a knowledge base of grama panchayat which can be applied for its administrative, civil, and other various uses. Outcome of such a move would give rise to even better decisions, and essentially a better future.
In the light of all these, an effort has been made to develop a geo- visualisation for Cheruvannur Grama Panchayat, adopting FLOSS as a decision support system in the planning activities.
19 4. Review of Literature
Menno-Jan Kraak (2002) demonstrated the usefulness of geo-visualisation and how this technology can stimulate the visual thought process. This was done by applying geo-visualisation techniques to Minard's famous map the “Carte figurative des pertes successives en hommes de l' Armee Française dans la campagne de Russie 1812 - 1813” which depicts the invasion of Napoleonic forces into Russia. VRML is used for creating 3D model of event settings. The study shows that much more information can be revealed when using geo-visualisation techniques, rather than using conventional views. Work shows that, even if Minard data already have been discussed much earlier, a visualisation stimulate a kind of visual thinking, and generate more information, by that way.
Brewer, et al., (2000) examined the possibilities of a prototype of same-time / different-place collaborative geo-visualisation environment, taking the fact that most of the works with geospatial data, in any field like urban and environmental planning, etc. Geographic visualisation environments and related information technologies are generally developed by a map view which allows collaborators to manipulate a 3-D depiction of precipitation and temperature which varies with terrain. Users were allowed to control parameters of a time series animation and color scheme used to represent the data. The visualisation is set up with a combination of Java/Java3D tools namely VisAD Java class library, Hibbard, DEMViewer, ArcGrid ASCII export files and their own extensions for data queries, time referencing and networking. Accordingly, effective collaborative geo- visualisation is possible with: 1. A theoretical understanding of the social aspects of both local and remote collaboration through display objects in geospatial context, 2. advantages and disadvantages of interactive geographic and information visualisation methods and designing new methods to meet unique characteristics of group work, should be assessed and, 3. the role of different kinds of visual representations of collaborative settings to be examined.
MacEachren, et al., (2001) examined geo-visualisation methods and tools to support the work of groups, by considering the role of map-based displays in facilitating collaboration in the context of geospatial knowledge construction and
20 decision making activities. They have taken special emphasis to the situations where collaborators are interacting at distant places from one another. A prototype of an extension for an existing single-user geo-visualisation is developed, as part of Human-Environment Regional Observatory (HERO) project's Intelligent Networking Environment (HEROINE). Prototype is implemented in Java/Java3D using VisAD, and DEMViewer. Two datasets used are, climate data of Susquehanna river basin in US during 1983-1993, and monthly precipitation data for Greece from 1901-1995. The study shows that, multi-disciplinary approach to design collaborative geo- visualisation environments has the potential to help in a unique kind of distributed geo-visualisation system.
Madden, et al., (2006) studied the creation of digital vegetation databases for 21 National parks, Preserves, Home sites and Battlefields in the southeastern United States, a cooperative work of the Centre for Remote Sensing and Mapping Science (CRMS) at the University of Georgia with National Park Service. Throughout this process, geo-visualisation techniques are used, to extract data and assess the vegetation patterns, quality control evaluation and communication of information to managers and users of park. Geo-visualisation techniques are also used to qualitatively identify and assess areas prone to errors in the geometric orthorectification. Usage of this technique contributed to improve the thematic and geometric accuracy of the National Park Service vegetation data sets. National Park Service is using these geo-visualisations to prioritise the acquisition of additional lands to help preserve water quality and habitats of ecological importance. Visual display in 2D and 3D of vegetation boundaries registered to a DEM gave a clearer depiction of relationship between vegetation types and terrain characteristics such as slope, aspect and elevation range.
Slocum, et al. (2001) proposed a research agenda on cognitive and usability issues in geo-visualisation, for the International Cartographic Association's Commission on Visualisation and Virtual Environment working group. Cognitive and usability issues should be considered in the context of six major research themes, namely: 1) geospatial virtual environments (GeoVEs), 2) dynamic representations (including animated and interactive maps), 3) metaphors and schemata in user interface design, 4) individual and group differences, 5) collaborative geo-visualisation, and 6) evaluating the effectiveness of geo-visualisation methods. It was found that, traditional cognitive theory for static 2D maps may not be applicable to interactive 3D immersive GeoVEs and dynamic representations - thus new cognitive theory
21 may need to be developed. Usability engineering extends beyond the traditional cartographic practice of 'user testing' by evaluating software effectiveness throughout a life cycle (including design, development, and deployment).
MacEachren, and Kraak. (2001) discussed about the major research challenges in geo-visualisation, which are: 1. Challenges on visual representation: i.) To develop a theory for georepresentation and formalising representation methods. ii.) To develop new forms of representation that support the understanding of geospatial phenomena and space-time process. iii.) To adapt representation methods to meet the changing nature of data to be represented. iv.) Adapting representation methods to the increasing range in kinds of task that visual geospatial representations must support. v.) To take advantage of recent technological advances in both hardware and data formats. 2. Visualisation-computation integration: i.) To develop visual approaches to geospatial data mining, thus to using visual methods for uncovering unknown patterns and relationships in large geospatial data sets. ii.) To integrate visual and computational tools that enable human and machine to collaborate in the process of knowledge construction. iii.) To address the engineering problems of bringing together disparate technologies, each with their own established tools, systems, data structures and interfaces. 3. Interfaces: i.) To develop the understanding and mechanisms to capitalise on the potential of new media to prompt creative thinking. ii.) To extend our understanding of metaphor for geo-visualisation and develop principles for selection of appropriate metaphors. iii.) To investigate interfaces that support the concept of a Digital Earth and the concept of Digital Earth as an interface. iv.) To extend our understanding of interface design to take advantage of the potential of virtual environments. v.) To develop and assess formalisations for specifying interface operations
22 appropriate to geo-visualisation environments. vi.) To develop a comprehensive user-centered design approach to geo- visualisation usability. 4. Cognitive/usability Issues: i.) To develop cognitive theory to support, and assess usability of, methods for geo-visualisation that take advantage of developments in virtual environments. ii.) To develop cognitive theory to support, and assess usability of, methods for geo-visualisation that take advantage of advances in dynamic (animated and highly interactive) displays. iii.) To develop an integrated understanding of metaphors and knowledge schemata in the context of geo-visualisation interface design. iv.) To understand individual and group differences related to use and usability of geo-visualisation. v.) To extend our perspective on cognitive and usability issues associated with geo-visualisation to contexts that involve group work. vi.) To determine the contexts within which geo-visualisation is successful. vii.) To develop methods and tools that will enable the kinds of cognitive and usability research called for. 5. Crosscutting Research challenges: i.) To develop the understanding and integrated technologies that make it possible to take advantage of the potential offered by virtual environments, direct manipulation interfaces, and related multi-modal technologies. ii.) To develop extensible methods and tools that enable understanding of, and insight to be derived from, the increasingly large and complex volumes of geospatial data that are becoming available. iii.) To develop a new generation of geo-visualisation methods and tools that support group work. Most work with geospatial information requires coordinated effort by groups. However, current geo-visualisation methods and tools (as well as other geoinformation technologies) are designed for individual use. iv.) A challenge that under-pins those delineated above is to develop a human-centered approach to geo-visualisation.
Döllner, et al., (2006) reported the concepts, implementation, and experiences of
23 the Berlin virtual 3D city model based on the system for integrating, managing, integrating, presenting, and distributing complex urban geoinformation. The project was initiated by the Senate Department of Economics and the Senate Department of Urban Development. As first applications, the virtual 3D city model forms core part of the investor information system hosted at the Berlin Business Location Center, and it represents the basis for ongoing projects in city planning at the architecture working group of the Senate Department of Urban Development. The Berlin virtual 3d city model is developed with CityGML, a first open data model and XML-based format for storage and exchange of virtual 3D city models available. It is implemented as an application schema for the Geography Markup Language 3 (GML3), the extensible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. CityGML is intended to become an open standard and therefore can be used free of charge. The overall architecture of Berlin 3D model is like this: At back end, digital areal photos, DTMs, georeferenced thematic data, 3D geo data, digital architecture models, cadastral data etc are there in database. At application level, 3D authoring system, CityGML converter, CAD and 3D editor tools, 3D geodatabase system virtual 3D city model etc are connected with databases. At front end, Geodata web services, 3D presentation system, Geotainment system diddeminates the information to the end users. Photorealistic visualisation and information visualisation are achieved by this set-up.
Krisp (2006) studied about the relevance of geo-visualisation and knowledge discovery for decision making in ecological network planning. Study focused on geo-visualisation and its crucial role to derive problem-specific models and design task-specific maps to discover and incorporate knowledge into planning and decision making. Three case studies were i) to investigate the changing moose habitats, ii) wild life warning sign locations, and iii) ecological barriers. In the first case, the geo-visualisation in spatial statistical tools were used, which included interaction, animation and three dimensional density estimations. The data for study obtained from Finnish hunting association. Results are displayed as density maps in a four dimensional explorative visualisation to present and highlight changes in moose habitats. The second case considered the current placement of wildlife warning signs, investigated using the data provided by Finnish Road Administration. Current accident sites were pointed out, then calculated density of current accident distribution and calculated the contour of density and optimized
24 warned road section. The third case describes a process of modeling ecological barriers by a list of landuse and landcover elements and their impact on animal movement. The findings of this study, are, bringing in expert knowledge is one of the crucial points in developing the problem-specific maps which assist decision making process. The use of exploratory geo-visualisation tools help to study the ecological landscape and alternative approaches for landuse. geo-visualisation provides a wide set of tools and processes to interact and work with spatial data.
25 5. Basic database concepts
A Database is a logically arranged collection of information so that retrieval of information from a database in a presentable form, is easy with the application of optimised set of queries. Data is stored in databases in the form of tables. Tables are the collection of records and they are essentially, structures composed of rows and columns. Each row contains related data, which denotes a record or tuple and each column contain same type of data, which is generally called as field or attribute. Data is a form of representation of knowledge, in a broader sense, or a piece of un-synthesised information. Usually data refers to the raw information which could be some numbers, images, characters, words, etc. The difference between data and information is given in Table 5.1.
Data Information “Cheruvannur” The estimated total population of “Grama Panchayat“ Cheruvannur Grama Panchayat is 22150, “2001” as per the 2001 census.“ “22150” Table 5.1: differences between data and information.
The term metadata refers to the data about data and generally provides supplementary information such as “who collected the data”, “data source”, “how the data was collected”, etc. Data elements are basic units of information containing a set of values which points to a single fact. It can be located and extracted from data. In the above context, “Name of Local Authority” is a data element. Data type is an attribute to the data that describes what kind of data is that. Datatypes can be classified into three:
1. Simple data; 2. Complex data and 3. Specialised data
Examples for simple data types are strings, numbers, date and time etc. Complex data types are object data types, which may vary according to different relational databases. It may include reference pointers, collection arrays and user defined data types.
26 Specialised data types may include multimedia objects, spatial data, xml documents etc. A term Domain is used to denote a collection of unique things. They are a set of allowed values in a field of a table.
5.1. Database as a system: In these days, databases are more or less computerised, and the terms “Database” and “Database management systems” are used vice-versa, to denote each of them. Even they are related they differ from each other, slightly. A Database management system is something which manages a database. It is essentially a software, in the case of a computerised database. Database management systems which are in use today, are relational database systems. or, RDBMS in short. A database management system has to achieve some goals:
1. Allow users to create new databases and specify their logical structure of data, 2. Permit the users to query the data kept in, and to modify it. 3. Support the storage of large amounts of data. 4. Control access to many users at the same time, without affecting the transactions one another.
5.2. Designing databases: Databases are designed by meeting some general rules. There are some fixed design models like “Relational data model” for designing a database.
5.3. Relational data model: In this model, the database is considered as a collection of relations. A database may contain more than one relation. Tables are linked by type of relations (parent-child, etc.). A table consists of rows and columns, and each row represents a combination of data values. These rows denote the real world relationships, while the column denote how the attribute information. A simple representation of relational database model is given in Figure 5.1.
27 Figure 5.1: A relational database model
Attributes, columns or fields are of same meaning in a relational database. All of these terms are used to denote a field in a table. Records, rows or tuples are used to denote a record in a database table. A table may have multiple fields and set of fields can have many records created in that table. Data could be accessed according to field structure of the table, record by record. The relational data model was first developed by an IBM researcher named E. F. Codd which is popularly referred as E. F. Codd's rules. Codd’s rules are:
1. The information rule: Data should be presented to the user in a tabular form.
2. Guaranteed access rule: All data should be accessible without any doubtfulness.
3. Systematic treatment of NULL values: A field should be able to keep itself empty. NULL value is different from an empty string or zero. It is a valueless state.
4. Dynamic online catalogue based on the relational model: A database should provide access to its structure via the same tools which it use for
28 presenting data.
5. Comprehensive data sub language rule: A database should support any one of clearly defined languages for inserting, manipulating, deleting, updating data. Most of the present day databases support SQL query language for the above said purpose.
6. View updating rule: Data can be presented in different logical combinations called as views. This rule states that users can update the data through these views as efficiently as by updating to the original tables. But in practical side, no any present day DBMS fully complies this rule.
7. High Level Insert, Update, and Delete: This rule states that, data can be retrieved in sets of data which may have more than one row, and / or from more than one table. Insertion, deletion and updation can be done to multiple rows of data, which may, be present at one or more than one table.
8. Physical data independence: The user should be isolated from physical method of data storage. Changes can be made to the base physical system of database, without affecting the users accessibility.
9. Logical data independence: Even if the logical structure of a database is changed, the view of data to the user should remain as before. Most of the present day databases are having rigid connections with the logical structure of database and its views, and so, doesn't obey this rule.
10.Integrity independence: The Querying Language is supposed to impose some constrains on user, in order to maintain database integrity. In practice, this rule is not fully implemented. But as a common practice, primary keys cannot have a NULL value, and if there is a foreign key is set in a table, its values must exist as a foreign key in any other table.
11.Distribution independence: A user should be unaware of whether the parts of the database are located in one place, or in more than one place. This rule is rather difficult to implement.
29 12.No subversion rule: There should not be any other way to modify the physical structure of database, other than querying language. This rule also is not satisfied well today, as many databases have GUI interfaces which allow direct manipulations on database.
These rules are considered as guidelines today, because no any present day DBMS complies with all these entire 12 rules.
5.4. Entity Relationship Diagram: Entity relationship diagram is a graphical way of database modeling. They are called as E-R Diagrams in short. E-R Diagrams have three principal components. These are
1. Entity sets, 2. attributes and 3. Relationships.
An entity relationship diagram has four types of components, they are:-
1. Rectangles – used to denote entity sets. 2. Ellipses – used to denote attributes. 3. Diamonds – used to represent relationship sets and 4. Lines – used to represent links to components.
E-R Diagram depicting the decision making process related to the plan / development activities in Grama Panchayat. Is given in Figure 5.2.
30 Member 1 Member n
District Planning Committee Member 1 Member n
Technical Advisory Convenor Coordinator Group(Block)
Citizen 1
Grama Sabha Citizen n
President Decision
Secretary Staff n Secretary Member n
Panchayat O/o Administrative Decision Grama panchayat Committee
Implementing officer Staff n Decision Decision Decision Decision
Institution (n) under Grama Panchayat Development Finance Welfare Standing Standing Standing Committee Committee Committee
Figure 5.2: E-R Diagram depicting the decision making process related to the plan and development activities in a Grama Panchayat.
Data are organised in such a way to eliminate duplication of data and also for sensible data dependencies. This process is often known as data normalisation.
5.5. Normalisation: Database normalisation is a process of efficiently organising data in a database for eliminating duplication and redundancy of data and making sensible data dependencies. This process reduces the amount of space a database consumes, and ensures that data is logically stored. It is a kind of standardisation or to impose consistency with respect to the style and content. Removal of duplication tends to minimise redundancy. In practical approach, normalisation
31 manage to divide information into smaller, more manageable parts. The benefits of normalisation are:
i.) Physical space needed to store data is reduced. ii.) Data becomes better organised. iii.) Normalisation allows changes to small amounts of data (namely single records) to be made to one table at once.
Normalisation are stated in terms of normal forms. These are a series of guidelines for ensuring the databases are normalised. They are numbered as 1 to 4. namely 1NF, 2NF, 3NF, 4NF.
1st Normal Form (1NF): 1 NF sets very basic rules for an organised database. It eliminates duplicative columns from same table, and create separate tables for each group of related data and identify each row with a unique column (Primary key) or a set of columns. A term unique key is also there, which are set on fields which contain only unique values throughout entire table. They are set for the accuracy of searching.
2nd Normal Form (2NF): 2 NF Further addresses the concept of removing data duplication. It meet all the requirements of 1st normal form and remove subsets of data that apply to multiple rows of a table, and place them in separate tables. Then creates relationships between these new tables and their predecessors using foreign keys. Foreign key is a field in the new table which match the primary key column of predecessor table and used for cross-referencing.
3rd Normal Form (3NF): 3rd NF meet all the requirements of 2nd normal form and remove columns that are not dependent upon the primary key.
4th Normal Form (4NF): 4th NF meet all the requirements of 3rd normal form. If a relation is there in 4NF, it should have no multivalued dependencies.
5.6. Database integrity: Database constraints are certain type of controls on a database which require relations to satisfy some properties. Database integrity is a term referred to denote the data entered in the database is accurate and valid. Three levels of integrity are:
32 i. Entity integrity: Presence of primary key in a table, defines the entity integrity. If primary keys are defined for each entity, it will follow the entity integrity rule. ii. Domain integrity: Domain Integrity is achieved if column of table is kept within its allowable limits. This is achieved by keys and constraints. iii. referential integrity: Referential Integrity is achieved by the integrity of relationships between primary and foreign key values in related tables of a database. Databases achieve referential integrity by the effective integration of constraints. Primary and foreign keys are both constraints. A constraint is a metadata, defined on a table defining restrictions on values. For example, a primary key constraint makes the primary key field to be unique.
5.7. Computer based record keeping systems:
As its name denotes, DBMS is a system made up with different components, works all together, to achieve the above goals. Database has a distinct architecture. A simple schematic diagram of a DBMS is shown in figure 5.3.
Query processor: The function of this component mainly deals with the translation of requests from users, into low level operations. Transaction manager: It manages the transaction of data between the database and the users. Storage manager: In common situations, the storage manager is nothing but, the operating system itself. File manager: File manager, as its name denotes, keeps track of location of files on the storage media, and retrieves clusters of files when requested by buffer manager. Buffer manager: It handles main memory and obtains clusters of data from storage media from file manager and keeps those clusters in a part of main memory.
33 Schema Modifications Queries Modifications
Query Processor
Buffer Manager
Transaction Storage Manager Manager
File Manager
Data, Metadata
Figure 5.3: Essential components of a DBMS
5.8. Current Scenario: Databases are used in various fields today (for example: Census database). In governance and decision making, it is increasingly appear the prominence of databases for different types of uses. Spatial databases are designed for keeping track of the land revenue activities and are referred as geodatabases or geo-spatial databases.
5.9. Need for local level geo-database and geo-visualisation: A comprehensive spatial geo-database will serve as knowledge base of panchayats which can be applied for its administrative, civil, and other various uses. Properly implemented, an interactive database-searching can provide decision makers with instant access to high value information for use in time consuming, costly and complex planning and implementation activities. (Mohamed, M.Z. & Appalanaidu, U.B., 1998.)
34 6. Cartography, Geo databases and Geoinformatics
A map is a graphic representation of selected natural and man-made features of the whole or a part of the earth's surface on a flat sheet of paper on a definite scale, and in their correct relative geographic positions and elevations (Gupta, K.K., & Tyagi.V.C. 1992). The art and science of map making is known as cartography. Map making was probably originated in ancient Egypt. Number of practical problems are concerned with geometrical shapes (Newman, J.R., 1952). In India, Revenue maps were famous in medieval times and still in use during mid 18th century. Scientific mapping started India by Survey of India, in 1767. After 1947, Survey of India conducted extensive surveys to help to build a planned economy (Gupta, K.K., & Tyagi.V.C. 1992).
The common features in a map are Map body, North arrow, Scale bar, Legend box, Neat lines, Point data, Line data, Area data, Text data etc (Figure 6.1). 1. Map body: Map body is the body of the map with all details depicted. 2. North Arrow: The indicator of direction and the key of orientation of a map. It is represented by an arrow or a symbolic rose, which is pointing to the north direction. 3. Scale bar: Scale is the ratio of the distance between two points on the map to the actual distance between the corresponding points on the ground. It can be represented as three types namely, as a statement (Eg: one centimeter equals 0.5 kilometers or 50000 centimeters), as a numerical
1 fraction ( Eg: /100,000, 1:100,000) or as a graphical bar. Graphical representation of scale has an advantage, as it remain true after reduction / enlargement of a map. 4. Legend box: Legend is the key to the different symbols which are used in a map. It is a rectangular box placed on a convenient position on the map. It describes whichever symbols are used on the map, and what they represent. 5. Neatlines: Neatlines are the boundary line of the map, where the map begins and ends. Map body includes within neatlines. 6. Point data: Point data is the information depicted on the map in the form of a point. Eg: Locations, Spot heights etc. 7. Line data: Line data are the information depicted on the maps in the form of lines. Eg: Roads, Rivers, Canals, Boundaries etc.
35 8. Area data: Area data are the details of specific areas depicted in the form of polygons, ovals etc. Used to represent details of specific locations and terrestrial spaces. Eg: District, Watershed etc. 9. Text data: Text data is used for depicting the names of places and features.
Figure 6.1: Map of Cheruvannur grama panchayat showing common features.
Maps are classified based on scale and content / purpose. 1. Based on scale: i.) Cadastral / Revenue maps: These maps are either called as plans when prepared in larger scale, of a smaller area. These usually contain the details of land property. Commonly prepared in 1:4000, 1:5000 scales. ii.) Topographical maps: These maps contain natural and man-made features of land area. They are usually prepared in 1:250,000, 1:50,000, 1:25,000. Scales. The authority to prepare topographical maps in India is Survey of India. iii.) Geographical maps: They are still smaller maps than 1:250,000. They cover an area like country, state etc.
36 iv.) Atlas maps: Atlas maps are smaller scale maps than geographical maps.
2. Based on content and purpose maps are classified in two: 1. Physical and 2. Cultural. i.) Physical: Relief maps, climatic maps, weather maps, bathymetric maps, vegetation maps, geological maps and maps with various other themes etc. includes in this category. ii.) Cultural: They contain themes like population, ethnography, linguistics, economy, commerce, industry, history, communication etc.
Latitudes and longitudes along with geodesic height, are the components of a geographic coordinate system, a system which enable us to identify each location on the surface of earth.
➢ Latitude: Latitude values denote the angular distance between equator and points north or south of it on the surface of the earth. It is measured from the centre of earth. Lines joining points with the same latitude are referred to as parallels, which form concentric rings on north and south hemispheres. At equator it is denoted as 0° parallel, at north pole, 90° N and at south pole, 90° S. Latitudes in northern hemisphere are given +ve values and at southern hemisphere, given -ve values. ➢ Longitude: Either called as meridians, are lines running perpendicular to parallels, and pass through both poles. Longitudes are arcs, and not full circles. 0° meridian is passing through Greenwich, and referred as prime meridian. a longitude value indicates the angular distance between prime meridian and the point lie east or west of it, measured from the centre of earth. Earth is equally divided into 360 degrees, 180 degrees each in eastern and western hemispheres. ➢ Geodesic height: It is the vertical distance from the centre of earth to the surface of earth. It is commonly referred as vertical datum which generally follows mean sea level.
6.1. Map projections: Shape of earth is an irregular sphere (Figure 6.2). Depiction on earthly features onto a flat surface is mapping. So, the features on it cannot be represented on flat surface without distortions. So, projections are used, to minimise the errors.
37 (Source: NASA) Figure 6.2: The Earth surface showing surface irregularity.
A map projection is an orderly arrangement of two sets of lines or curves, which constitute the framework of a map, one set represent parallels and the other set represent the meridians (Gupta, K.K. and Tyagi. V.S. 1992). Locations on surface on earth can be represented or assigned definite position corresponding to the network of parallels and meridians. All projections can be expressed in mathematical terms. The errors that may occur in projections are deformation of angles, change of scales, errors of distances, and bearings, and shapes of areas. There are wide varieties of projections for different uses. Projections fall into three major classes namely:
i.) Cylindrical Projection: A cylindrical projection can be imagined in it's simplest form as a cylinder, that has been wrapped around the globe. If it is around the equator, projection is called as regular or normal. If it is tangent to a meridian, it is transverse. If it is tangent to another point of globe, it is called as oblique. Cylindrical projections usually used for depicting large rectangular areas. Example: mercator. ii.) Conical Projection: In a conical projection, the graticule (mesh of latitude and longitude lines) is projected on to a cone tangent, or secant to the globe along a mid latitude line. Latitudes are projected as arcs, and longitudes are projected as straight lines arising from top of flattened cone at uniform angular intervals. This type of projections are used for depicting medium sized triangular areas. Example: polyconic (Projection used in SOI toposheets.)
38 iii.) Planar or azimuthal Projections: A planar projection can be imagined as a plane being placed against the globe. If a light source inside the globe projects the graticule on to the plane, the shadow appear on plane would be a planar, or azimuthal map projection. Commonly used to represent smaller circular areas. Examples: gnomonic, stereographic, orthographic.
Property wise classifications of projections are: • Equal-area: Any region in the map has area linearly proportional to the corresponding region on the sphere. Useful for geographical comparisons. • Equidistant: Distance from any point to another point in the map is proportional to the distance between corresponding points on the earth surface along those corresponding lines. Scale is constant on these lines. • Conformal: Shapes are locally preserved. Useful for navigational purpose.
Projections are made using datums and spheroids and ellipsoids, assuming that the shape of earth in the area on the surface on earth, is a particular spheroid or ellipsoid, using datums. • Geoid: The equipotential surface of the earth's gravity field which best fits, in the least-squares sense, mean sea level (Geodetic Glossary, National Geodetic Survey). • Spheroids: A three dimensional quadric surface derived from rotating an ellipse about one of its principal axes. Three instances of a spheroid are: 1. prolate spheroid (Shape of a rugby ball), 2. oblate spheroid (similar to the shape of the earth) and 3. sphere (symmetric). • Ellipsoid: A quadric surface which is a higher dimensional analogue of an ellipse. Used as a surface of reference for the mathematical reduction of geodetic and cartographic data (D.M.A. Technical manual 8358.1).
A set of constants specifying the coordinate system used for geodetic control, i.e., for calculating the coordinates of points on the earth (Geodetic Glossary, National Geodetic Survey). There are two types of datums namely: • Vertical datum: A vertical datum is a set of constants specifying the coordinate system to which elevations are referred (Federal Geographic
39 Data Committee handbook). • Horizontal datum: A horizontal datum is the set of constants specifying the coordinate system to which horizontal coordinates are referred (Federal Geographic Data Committee handbook).
Datums and spheroids differ one another in parameters. A datum may not completely coincide with geoid or with the real earth surface (Figure: 6.3). A spheroid best defines India may not be good for other countries. Hence, each country has its own datums and spheroids which fits best when depicting their region. Mathematical parameters of all these spheroids vary each other. Their datum centres not necessarily would coincide with each other, or with the centre of earth (Figure 3.4). Two examples for datums are: 1. Everest datum: Everest datum is in use for India and adjacent countries for cartographic activities. Named after Sir George Everest, and derived in 1830, since then in use as the basis for all types of control surveys in India. This datum is the result of the Great Trignometric Survey of India. It is centred near Kalianpur in Madhya Pradesh, under the earth surface, but its' ellipsoidal centre does not coincide with the centre of the earth. Still, Everest is the best fitting spheroid and mathematical surface for India, but cannot be extended very far from it's origin. 2. WGS 84: The World Geodetic System is called as WGS 84. It is the reference system used by the Global Positioning System. It is an earth-fixed global reference frame and geocentric datum, globally consistent within ±1 m. The WGS 84 originally used the GRS 80 reference ellipsoid, but undergone some minor refinements several times after its initial publication. The last revision of WGS 84 was in 2004, and will be valid up to 2010.
40 Figure 6.3: Earth's ellipsoid, geoid, and two types of vertical deflection (Source: Wikipedia. Enhanced version of an image obtained from U. S. Department of Defense)
Figure 6.4: Difference between global and local ellipsoids.
41 6.2. Geoinformatics Traditional methods of map making and map reading is changing, and giving the way to more interactive and intelligent forms of geographic information stored in computer systems. The information of the surface, subsurface and atmosphere of the earth and, the information received through the analysis of data are referred as geo information all together. The art, science, or technology dealing with the acquisition, storage, processing, production, presentation and dissemination of geo information is referred as geoinformatics (Ehlers and Amer, 1991).
GIS is the acronym for Geographical Information Systems. GIS are sets of computer tools for the storage, retrieval, analysis and display of spatial data (Burrough, P.A., 2001). Now a days, GIS is a field of convergence from number of disciplines, namely, Geography, Cartography, Remote sensing, Photogrammetry, Surveying, Geodesy, Statitics & Operational Research, Mathematics, Computer science, etc. A GIS can answer many specific questions, like: ➔ What is at a specific location? ➔ Where is it? ➔ What spatial pattern exists there? ➔ What change has occurred since? ➔ What will happen if an event happens in some way? etc.
The major components of a GIS include, Hardware, Software, Geographic data and Personnel. The operations a GIS can mediate include, Data capture (input & verification), Data storage (storage & management), Data analysis and modelling (updating manipulating and analysis) and Display (data output and presentation). GIS use two major kinds of digital data models to handle spatial information - Vector and Raster. by which the points, lines, areas and surfaces are coded digitally.
Vector data: In vector data model, an x, y (cartesian) coordinate system references real-world locations and each location is recorded as a single x, y coordinate. In this model, spatial data is handled as points, lines, areas, boundaries and centroids. Points and centroids are recorded as a single coordinate, lines and boundaries are recorded as a series of ordered x, y coordinates and areas are recorded as a series of x, y coordinates. Defining line segments which enclose an area, termed as polygon, means 'a figure with many sides'. Raster data: The raster data model is used for handling surface information. it works as a regular grid of dots or square cells (pixels) filled with values.
42 6.3. Recent trends in GIS: 1. Many GIS databases are now distributed over local or wide area networks. 2. Multimedia and hypermedia will play a growing role in GIS, especially in help and training systems. 3. In governance, better decisions can done in case of land use, land revenue informations. 4. The integration of GIS and GPS will provide more accurate and precise information in temporal dimensions. 5. In-vehicle navigation systems will provide a clear picture of traffic of an area. 6. In Internet, geographic web searching will help more precise searching of local details.
6.4. Geodatabase: A geo database, either called as spatial database is defined as a database system that offers spatial data types in its data model and query language, and supports spatial data types in its implementation, providing at least spatial indexing and spatial join methods (Güting, R.H., 1994).
6.4.1. Characteristics of spatial databases: Usually, spatial data are linked with attribute data in the form of standard data that any database can handle. So, a spatial database can handle all standard data modelling and querying tasks along with, additional capabilities to handle and index spatial data. It can provide efficient algorithms for spatial join. In all standard GIS, there are underlying spatial DBMS’s, but most of them have limited capabilities to handle standard data.
A spatial database can manage the data related to geographic space (2D/2.5D) more precisely, objects in space, and space itself. Objects in space means, points, lines, area etc and space mean statement about each point in space, such as land use maps, partitions into panchayats, municipalities etc. The ability to handle geographic space, is helpful in GIS and town/country planning. Design of a web based geo-database is given figure 6.5. A spatial database, should have the capability to handle discrete geometric bases, spatial data Types or algebras, spatial relationships and it should Integrate geometry into the DBMS data model. It is expected to handle discrete geometric bases, because, space is continuous and the numbers handled by computers are discrete. A spatial database can handle spatial data types, as they require to handle general structure of values closed under, set operations on the underlying point sets. Spatial
43 relationships are maintained, as it can handle queries such as, to find all objects in a given relation. Queries may be, a. toplogical such as inside, intersect or adjascent, b. directional such as above, below, or north of, or c. metric such as distance <200 etc. A spatial database should have the capability to integrate geometry into the DBMS data model. This means that it could represent spatial objects by objects of the usual DBMS data model with at least one spatial data type attribute. A DBMS can be transformed in to spatial DBMS, by integrating following extensions to it: 1. Representations for data types of a spatial algebra. 2. Procedures for atomic operations. 3. Spatial index structures. 4. Access operations for spatial indices. 5. Spatial join algorithms. 6. Cost functions for all these operations. 7. Statistics for estimating selectivity of spatial selection and spatial join. 8. Extensions of the optimiser to map queries into the specialised query processing methods. 9. Spatial data types and operations within data definition and query language. 10. User interface extensions for graphical I/O.
Web RDBMS Browser Web Application Server Server Web Browser Map Server
Client side Server side
Figure 6.5: Design of a web based Geo-database.
44 7. Methodology
Development of effective geo-visualisation based decision support system (DSS) involved primarily data compilation from collateral sources, setting up appropriate hardware configuration, design of database and design of a spatial DSS.
7.1. Data collection: Data collected from various government sources includes:
1. Resource maps of panchayat, both in the form of hard copy and digital copy. 2. Panchayat Asset Register – (Details of roads, lanes, culverts, bridges and other constructions.) 3. Local Self Government Institutions Election - Ward de-limitation documents. 4. Census of India - District Census Hand book. 5. Watershed Atlas – State Land Use Board. 6. Watershed based development master plan – Block Panchayat. 7. Panchayat citizens' charter.
Data is collected primarily from office of the Cheruvannur Grama Panchayat itself. Features like roads, landuse, water resource polygons, water resource lines, place names, etc were extracted from resource maps. Survey of India toposheets 1:250000 (49M) was used to digitise taluk boundaries. With the help of this map, a taluk map with village boundaries was georegistered. Toposheet of 1:25000 (49M/10 SE) was used for extracting contour lines for creating DEM and shaded relief.
7.2. Setting up / upgradation of Hardware:
This was implemented in GNU/Linux with essential softwares like GIS, web server, geo-visualisation, etc. In order to suite these software certain changes in hardware was done by upgrading existing PC with DVD R/W, 256 MB RAM to 1 GB RAM and 15” monitor to 17” monitor and an additional hard disk. The full configuration of the system used is given in annexure-V.
45 7.3. Setting up the software environment:
7.3.1. Installation of operating system: The installation of the Debian GNU/Linux is a straight forward way. The CD image of Debian GNU/Linux Etch obtained from Swathantra Malayalam Computing - a patched release with Unicode Malayalam support and a graphical installer. The set of official Debian Etch binary DVDs (3 nos.) obtained from Indian Linux Users Group, Cochin chapter.
Made the DVD R/W drive into primary boot device in system BIOS settings, inserted Debian GNU/Linux CD into it and restarted the system. In the next consecutive screens appeared, selected installation language as English, location as India, System language as English, Keyboard layout as English. After the initial self checking of system, installer CD etc, the installer loaded the additional components. In the next screen, the host name selected 'localhost'.
In “Partition disks” screen, selected partitioning method as manual, and selected the hard disk. Then created the partitions (annexure-V), and selected the “finish partition” option, and written changes to disk, disk is formatted by installer. In the next steps, selected appropriate root password, created a user, and given user password. Base system is installed by installer. In the next screen, installer asked whether to use a network mirror for packages, selected no. Installer asked for CD or DVD media to install the packages, put them one by one. Next, chosen the packages to install, namely Desktop environment, Web server, SQL database, Standard system etc. Installer installed the required software environment on the system. Next asked for media change depending upon the packages selected to install, just followed the on screen instructions. Installer asked weather to install GRUB boot loader to master boot record, selected yes. After the installation of GRUB, the system rebooted to the installed Debian GNU/Linux, ejecting out the installation media from DVD drive.
7.3.2. Post install configuration of operating system: 7.3.2(a). Adding addresses of essential software locations to the system's source list: Address of a mirror site nearby is added to list of software sources, for the easy updation of the operating system, and installation of software packages. For this, the file /etc/apt/sources.list is edited (annexure-V).
46 7.3.2(b). Network and internet configuration: Internet connection is a must, to upgrade the system as and when updates are released, to download the required software tools and to be in communication with mailing lists and free software users community. Configured the network and internet settings by editing the configuration file /etc/network/interfaces as shown in annexure-V , and restarting the network daemon by issuing the following command in terminal:
# /etc/init.d/networking restart
Edited the file /etc/hosts to make it as appears in the annexure-V and issued the following command in terminal:
# echo localhost.ces.iisc.ernet.in > /etc/hostname
Added name server address to file /etc/network/resolv.conf
Restarted the system. After restart, issued the following commands in terminal as follows:
$ hostname localhost.ces.iisc.ernet.in
$ hostname -f localhost.ces.iisc.ernet.in
Both commands returned the host name. Network configuration is complete.
7.3.2(c). Set-up for Unicode Malayalam support: Malayalam is the mother tongue and administrative language of the people of the study area. In order to enter and handle data in Malayalam, Unicode Malayalam support is necessary. At present, Standard GNU/Linux systems are heavily patched to achieve Unicode Malayalam support after installation. Software patches are available in repositories of Swathantra Malayalam Computing. Swathantra Malayalam Computing or SMC is a group of volunteers working for developing Malayalam interfaces for free software as those can be used also by the people who know only Malayalam language. As this development is going on upstream, these patches would become integral part of the upcoming versions of
47 standard free operating systems. Followed the instructions given in the website of SMC and applied the commands as follows to get these patches applied in system. These commands will update the system with patches, and if latest updates of other softwares installed are available, upgrade them:
# wget http://download.savannah.gnu.org/releases/smc/praveen.key.asc
# apt-key add praveen.key.asc
# apt-get update
# apt-get upgrade
# apt-get install scim-ml-phonetic
Purpose of adding Praveen's (One among the project administrators of SMC.) GPG public key to the key-ring of apt, is to ensure the authenticity of package, and to confirm that nobody has changed the packages in repository after he did.
7.3.2(d). OpenSSH: For the security of passwords through internet, SSH and OpenSSH is installed by issuing the following command in terminal: localhost:/home/user# apt-get install ssh openssh-server
7.3.3. Installation and configuration of essential softwares for the proposed work:
The details of software tools used for the work are listed in annexure-V. Installation of software which are part of Debian Etch are done with the command:
# apt-get install
Among the software packages used, GRASS 6.2.3, Malayalam Patches, Quantum GIS 0.9.0, and ka-Map 1.0 are not part of Debian Etch system, and these need a separate installation and configuration.
48 7.3.3(a). Apache web server and php: A working web server and php, are necessarily installed on system. Apache is used as web server. php is a server-side, HTML-embedded scripting language, designed for producing dynamic web pages. Apache and php are installed by issuing the following commands:
# apt-get install apache2 apache2.2-common # apt-get install php5 php5-common libapache2-mod-php5 php5-pgsql # apt-get install php-db # /etc/init.d/apache2 restart
7.3.3(b). Installation of PostgreSQL and PostGIS: PostgreSQL is an open source, fully featured object-relational database management system which can be used for storing attribute data. PostGIS adds support for geographic objects to the PostgreSQL object-relational database. Installation is done via following commands:
# apt-get install postgresql-8.1 postgresql-client-8.1 # apt-get install postgis postgresql-8.1-postgis odbc-postgresql
Checked whether PostgreSQL is running or not, by issuing:
# /etc/init.d/postgresql-8.1 restart
Configured PostgreSQL as it can be used for the user user, via issuing following commands:
# su # su postgres # psql template1 # template1=# \q # exit
# su postgres # psql # CREATE ROLE “user” WITH LOGIN SUPERUSER; # ALTER ROLE “user” WITH PASSWORD '********'; # \q # exit
It is needed to ensure whether the client encoding is Unicode, as Unicode
49 (UTF8) support is needed to handle data in traditional Malayalam scripts. For checking this, issued:
$ psql # SHOW client_encoding; client_encoding ------UTF8 (1 row) # \q
7.3.3(c). Installation and configuration of GRASS 6.2.3: GRASS is a free software, and the leading GIS tool in the world of free softwares. GRASS is the abbreviation of the “Geographic Resources Analysis and Support System”. The source code of GRASS GIS package is downloaded from its website, extracted compiled and installed on system, by issuing following commands:
$ tar -zxvf grass-6.2.3.tar.gz $ cd grass-6.2.3 $ ./configure \ --with-tcltk-includes=/usr/include/tcl8.4/ \ --with-postgres-includes=/usr/include/postgresql/ \ --with-postgres-libs=/usr/lib/postgresql/8.1/lib/ \ --with-blas \ --with-lapack \ --with-motif \ --with-glw \ --with-nls \ --with-readline \ --with-odbc $ make $ su # make install
After installation, issued the following commands to create GRASS database:
$ mkdir data $ mkdir data/GRASSDATA
50 GRASS is started in terminal by issuing:
$ grass62
An icon is made for GRASS on Desktop, for easy access.
7.3.3(d). Installation of Quantum GIS 0.9.0: Downloaded the .deb packages for Etch from Quantum GIS website and installed via GDebi package installer by right click and select Open with “GDdebi package installer”.
An icon is made also for Quantum GIS on Desktop, for easy access.
7.3.3(e). Installation of MapServer: UMN MapServer is used for setting up geo-visualisation. MapServer is an open source development environment for building spatially-enabled internet applications. MapServer, and associated packages like php-MapScript (A dynamically loadable module that makes MapServer's MapScript functions and classes available in a PHP environment.), php-gd (GD module for php) etc are installed by issuing command:
# apt-get install mapserver-bin cgi-mapserver php5-mapscript php5-gd
7.4. Scanning and photographing maps:
i. S.O.I Toposheets: The Survey of India toposheets 49M (1:250,000 scale) and 49M/10/SE (1:25,000 scale) were scanned with a flat-bed scanner with a resolution of 200x200 pixels, part by part. ii. Taluk map: The taluk map with village boundaries is obtained from the District Census Handbook of Kozhikode, received from the Directorate of census operations, Thiruvananthapuram, was scanned with flat-bed scanner (Resolution: 200x200 pixels). iii. Resource maps: The resource map of grama panchayat was already converted to digital form in JPEG format, and received a copy from grama panchayat. As it lacked many of the details in the original, the original resource maps (10 sheets) were photographed and used for comparing while extracting features.
51 7.5. Georeferencing maps:
For georeferencing the maps and feature extraction, following method is adopted: Georeferenced the SOI toposheet 49M/10 (1:250,000) in which taluk boundaries are given, along with the SOI toposheet 49M/10/SE (1:25,000) with 1st order transformation.
The taluk map with village boundaries is georeferenced with 1st order transformation, by the help of coordinate points from georeferenced 49M/10 1:250,000 toposheet. Boundary coordinates and village boundary (it is the boundary of grama panchayat also) were extracted from taluk map.
Toposheets are projected maps on to Everest-1956 reference datum with polyconic projection. The grama panchayat resource map, already in digital format was made based on the village cadastral maps. Cadastral maps contain only direct field survey measurements and not projected on to any reference datum. In order to fit this resource map on a projected toposheet when overlaying, 3rd order transformation (either called as rubber sheeting) is adopted when georefencing. The problem of modifying boundary corners to fit existing ground features is solved by using a unique rubber sheeting procedure that takes into account linear features (Felus, Yaron A., 2007).
Resource map is georeferenced with the help of boundary coordinates extracted from taluk map, and with the coordinate points from georeferenced 49M/10/SE 1:25,000 toposheet, adopting 3rd order transformation with 33 GCPs uniformly spread in panchayat area selected from among 43 known control points. The features were extracted from georeferenced resource map, by extensively comparing with the digitised original resource map sheets. Contour lines were extracted from 49M/10/SE 1:25,000 toposheet.
52 Georeferencing is done with GRASS via following steps:
Figure 7.1: Georeferencing in GRASS - steps. (Source: GDF Hannover bR)
1. Created an x,y location tempxy and mapset user in GRASS database with default grid resolution settings, following on-screen directions of GRASS.
2. Changed into the GRASS x,y location, and converted scanned tif images of maps to GRASS format by issuing commands as follows:
GRASS 6.2.3 (tempxy):~ > r.in.gdal in=49m.tif out=49m GRASS 6.2.3 (tempxy):~ > r.in.gdal in=49m10se.tif out=49m10se GRASS 6.2.3 (tempxy):~ > r.in.gdal in=taluk.tif out=taluk GRASS 6.2.3 (tempxy):~ > r.in.gdal in=resource.jpeg out=resource
3. After exiting from x,y location, restarted GRASS and created a Lat-Long location with settings as follows:
Location: cheruvannur Mapset: user
Ellipsoid: everest 1956 Projection: Latitude-Longitude
north: 11:45 N south: 11:30 N east: 75:30 E west: 76:00 E
east-west resolution : 0:00:01 north-south resolution : 0:00:01
Then exited from the Lat-long location.
53 4. Georeferenced the toposheets in GRASS by the use of following sets of commands:
i.group - To collect raster map layers in an imagery group. i.target - To target the imagery group to GRASS lat-long location and mapset. i.points - To mark the ground control points on image to be rectified. and i.rectify - To rectifiy the image by computing coordinate transformation for each pixel in the image based on the control points.
Started GRASS again with x,y location tempxy and mapset user, and issued following commands: i.group:
GRASS 6.2.3 (tempxy):~ > i.group group=49m subgroup=49m \ input=49m.red,49m.blue,49m.green GRASS 6.2.3 (tempxy):~ > i.group group=49m10se subgroup=49m10se \ input=49m10se.red,49m10se.blue,49m10se.green GRASS 6.2.3 (tempxy):~ > i.group group=taluk subgroup=taluk \ input=taluk.red,taluk.blue,taluk.green GRASS 6.2.3 (tempxy):~ > i.group group=resource subgroup=resource \ input=resource.red,resource.blue,resource.green
i.target:
GRASS 6.2.3 (tempxy):~ > i.target group=49m \ location=cheruvannur mapset=user GRASS 6.2.3 (tempxy):~ > i.target group=49m10se \ location=cheruvannur mapset=user GRASS 6.2.3 (tempxy):~ > i.target group=taluk \ location=cheruvannur mapset=user GRASS 6.2.3 (tempxy):~ > i.target group=resource \ location=cheruvannur mapset=user
i.points:
To initialise a GRASS monitor, issued:
54 GRASS 6.2.3 (tempxy):~ > d.mon start=x0
Selected the 49M toposheet, and added ground control points by issuing:
GRASS 6.2.3 (tempxy):~ > i.points 49m
In the GRASS monitor, selected the raster file to be plotted, zoomed to centre pixel of lat-long cross hairs and placed control points. After this analysed for root mean square error, as it to be within zero. After adding 4 GCPs correctly, quit the screen. Repeated this process for the 49M/10/SE also, with following command:
GRASS 6.2.3 (tempxy):~ > i.points 49m10se
After adding GCPs to toposheet raster images, rectified the toposheets with following commands:
i.rectify:
GRASS 6.2.3 (tempxy):~ > i.rectify group=49m \ input=49m.blue,49m.green,49m.red \ extension=.rectified order=1
GRASS 6.2.3 (tempxy):~ > i.rectify group=49m10se \ input=49m10se.blue,49m10se.green,49m10se.red \ extension=.rectified order=1
Georectification of toposheets is complete. Exited from GRASS.
Selection of ground control points to georeference the taluk map:
Restarted GRASS with Latitude - Longitude location cheruvannur and mapset user. Adjusted the region and resolution with following command:
GRASS 6.2.3 (cheruvannur):~ > g.region rast=49m.blue.rectified
Selected and loaded the 49m.blue.rectified raster image from menu and comparing with the image taluk.tif, 10 GCPs are selected along the taluk boundary, noted down their coordinates, and exit from GRASS. Restarted GRASS with x, y location tempxy and mapset user and issued:
55 GRASS 6.2.3 (tempxy):~ > d.mon start=x0
Selected the taluk map, and added ground control points by issuing:
GRASS 6.2.3 (tempxy):~ > i.points taluk
Added points via same as the process described in case of toposheet 49M, and analysed for root mean square error, and ensured it to be within zero. After adding 10 known GCPs, quit the screen. Rectified the taluk map with following command:
GRASS 6.2.3 (tempxy):~ > i.rectify group=taluk \ input=taluk.blue,taluk.green,taluk.red \ extension=.rectified order=1
Georectification of taluk map is complete. Exited from GRASS.
Restarted GRASS with Latitude - Longitude location cheruvannur and mapset user. Adjusted the region and resolution with following command:
GRASS 6.2.3 (cheruvannur):~ > g.region rast=taluk.blue.rectified
Selected and loaded the taluk.blue.rectified raster image in map display from menu and, four GCPs which lie extreme north, east, south and west ends of village (grama panchayat) along the boundary line were selected. Noted down their coordinates. Followed by issuing command:
GRASS 6.2.3 (cheruvannur):~ > g.region rast=49m10se.blue.rectified
Selected and loaded the 49m10se.blue.rectified raster image in map display from menu, maximum number of GCPs could identify (43 nos) were selected and noted down their coordinates, comparing with the image resource.jpeg, and photographed original resource map sheets in an image viewer. Then exited from GRASS. Restarted GRASS with x, y location tempxy and mapset user, and issued:
GRASS 6.2.3 (tempxy):~ > d.mon start=x0 Selected the resource map map, and added ground control points by issuing:
56 GRASS 6.2.3 (tempxy):~ > i.points resource
Added all the selected 43 points via same as the process described in case of toposheet 49M. Analysed for root mean square error, and removed 10 points among them, those gave more error, as to ensure the error to be minimum and points are spread uniformly over the area. After this, quit the screen. Rectified the resource map map with 3rd order transformation via following command:
GRASS 6.2.3 (tempxy):~ > i.rectify group=resource \ input=resource.blue,resource.green,resource.red \ extension=.rectified order=3
Georectification of resource map is complete. Exited from GRASS.
7.6. Digitisation of vector layers:
For digitising vector layers, following method is adopted:
1. Extracting boundary lines of Cheruvannur village from georeferenced maps:
Restarted GRASS with Latitude - Longitude location cheruvannur and mapset user. Adjusted the region and resolution with following command:
GRASS 6.2.3 (cheruvannur):~ > g.region rast=taluk.blue.rectified
From GRASS GUI menu, selected item: Vector > Develop map >Digitize
and, from the appearing v.digit window, name for vector layer is given as villageboundaries. The raster image of taluk map is displayed as canvas backdrop. The commands for this:
GRASS 6.2.3 (cheruvannur):~ > d.mon start=x0 GRASS 6.2.3 (cheruvannur):~ > v.digit -n map=villageboundaries \ 'bgcmd=d.rast -o \ map=taluk.blue.rectified'
Selected tools from the appearing v.digit tools menu and drawn the features on the monitor. Then saved the features, followed by the command
57 v.build to build vector topology:
GRASS 6.2.3 (cheruvannur):~ > v.build villageboundaries
2. Correction of village boundary:
The correction of village boundary with the resource map was done with v.digit module, by displaying resource map as backdrop. The commands used:
GRASS 6.2.3 (cheruvannur):~ > g.region rast=resource.blue.rectified GRASS 6.2.3 (cheruvannur):~ > d.mon start=x0 GRASS 6.2.3 (cheruvannur):~ > v.digit map=villageboundaries \ 'bgcmd=d.rast -o \ map=resource.blue.rectified'
All the vector layers listed in annexure – II, are prepared via same method, using the corrected vector layer villageboundaries as second back drop. Only necessary fields in attribute table were created from the v.digit menu for entering essential identification details of features, such as name of feature etc. Remaining fields in table structure left to create later.
Post-digitising errors in vector layers were detected by issuing the command v.build as follows:
GRASS 6.2.3 (cheruvannur):~ > v.build map=luse error=luse_error \ option=build
And these errors were corrected by editing the vector layers with v.digit command itself.
For creating layer contours, the raster image of toposheet 49M/10/SE is used as backdrop image, and vector layer villageboundaries as second back drop. Drawn contour lines, entered attribute data in field height along with and saved the layer. The commands used are:
GRASS 6.2.3 (cheruvannur):~ > g.region rast=49m10se.blue.rectified GRASS 6.2.3 (cheruvannur):~ > d.mon start=x0
58 GRASS 6.2.3 (cheruvannur):~ > v.digit -n map=contours \ 'bgcmd=d.rast -o \ map=49m10se.blue.rectified; \ d.vect map=villageboundaries'
7.7. Creating database and attribute tables in PostgreSQL:
Attribute tables were created along with vector layers in GRASS itself, with limited number of fields. But the default database inside GRASS has limited SQL support and data-types. GRASS doesn't have the capability to handle Malayalam Unicode characters at present. Because of these reasons, and for more ease of managing the tables and data, attribute tables are transferred into a database named g28cgp set up in PostgreSQL. From GRASS prompt created and configured a database in PostgreSQL, by issuing:
GRASS 6.2.3 (cheruvannur):~ > createdb -h localhost g28cgp Password: CREATE DATABASE
Tested the database by issuing:
GRASS 6.2.3 (cheruvannur):~ > psql -h localhost g28cgp Password: Welcome to psql 8.1.11, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate with semicolon to execute query \q to quit g28cgp=# \q
Connected GRASS with the PostgreSQL database by issuing:
GRASS 6.2.3 (cheruvannur):~ > db.connect driver=pg \ database="host=localhost,dbname=g28cgp"
Checked the database connection by issuing:
GRASS 6.2.3 (cheruvannur):~ > db.login user=user
59 GRASS 6.2.3 (cheruvannur):~ > db.connect -p driver:pg database:host=localhost,dbname=g28cgp schema:(null) group:(null)
Copied the attribute tables from GRASS database to the g28cgp database set up in PostgreSQL, using db.copy command, by issuing:
GRASS 6.2.3 (cheruvannur):~ > db.login GRASS 6.2.3 (cheruvannur):~ > db.copy from_driver=dbf \ from_database=$HOME/data/GRASSDATA/cheruvannur/user/dbf \ from_table=contour \ to_driver=pg \ to_database="host=localhost,dbname=g28cgp" \ to_table=contour GRASS 6.2.3 (cheruvannur):~ >
All attribute tables other than contour also were transferred to PostgreSQL using this method.
7.7.1. Installation of a front-end to PostgreSQL database: For entering data to attribute tables easily, phpPgAdmin is used as front end for PostgreSQL. phpPgAdmin is a package written in php. phpPgAdmin will work on top of a web server and can be accessed via a web browser. phpPgAdmin is installed and configured by issuing:
# apt-get install phppgadmin # cd /var/www/ # ln -sf /usr/share/phppgadmin/
Accessed the database g28cgp in PostgreSQL through a browser by typing the address as:
http://localhost/phppgadmin/
7.8. Correction and completion of attribute tables and data entry:
Logged in to the attribute database through phpPgAdmin, made necessary changes to attribute tables and fields, and created rest of the fields left when digitising vector layers. The structure of attribute tables, adopted as per National
60 (Natural) Resources Information System (NRIS) Node Design and standards (NNRMS, ISRO). As the NRIS nodes are supposed to set-up in district level, and more detailed data is available from grama panchayat resource maps spatially, changes have made to the original NRIS table structures to accommodate these detailed data. An additional field descr_mal is also created to enter description in Malayalam language. The detailed attribute table structure for each layers are given in annexure – III, and code .
Entered rest of the attribute data. For entering data in Malayalam, SCIM platform is used. SCIM is the abbreviation of Smart Common Input Method. It a common input platform for typing Unicode text in languages other than English for Unix and Unix-like operating systems.
Batch entry of data such as land use code, is done through GRASS command interface itself, by using the command v.db.update as:
GRASS 6.2.3 (cheruvannur):~ > v.db.update luse col=lu_code \ value=02030400 where="descr_type='Coconut'"
7.9. Creating base maps:
7.9.1. Creating shaded relief map:
For creating shaded relief map cgprelief.tif, first created DEM (Digital Elevation Model) followed by creating shaded relief. Then overlayed DEM over Shaded relief, merged them by reducing opacity of DEM. Steps as follows:
1. Optimum resolution is identified and set for the DEM to create via a trial and error method with the following command:
GRASS 6.2.3 (cheruvannur):~ > g.region -a -p res=0.00005
2. Raster layer contour is made from vector layer contour by issuing command as follows:
GRASS 6.2.3 (cheruvannur):~ > v.to.rast input=contour \ output=contour \ column=height
61 3. A raster mask is need to be created for limiting raster operations inside mask, and for this purpose, layer administrative boundary (admin_2005_2010) is copied to a temporary vector file landmass by issuing:
GRASS 6.2.3 (cheruvannur):~ > g.copy vect=admin_2005_2010,landmass
4. Removed all the inside boundary lines and centroids inside it with the help of v.digit command, as a single boundary exist for the land mass. Put one centroid and given attribute value in the field const_code as 1 for it.
5. Then rasterised this vector layer by issuing the command:
GRASS 6.2.3 (cheruvannur):~ > v.to.rast input=landmass \ output=landmass column=const_code
6. Created raster mask by issuing:
GRASS 6.2.3 (cheruvannur):~ > r.mask input=landmass maskcats=*
7. Created a surface (DEM) by issuing command as follows:
GRASS 6.2.3 (cheruvannur):~ > r.surf.contour input=contour \ output=surface.dem
8. Shaded relief is created by issuing command:
GRASS 6.2.3 (cheruvannur):~ > r.shaded.relief map=surface.dem \ shadedmap=shadedrelief \ altitude=30 azimuth=270 \ zmult=1 scale=1 \ units=meters –overwrite
9. The shaded relief map is generated in GRASS map display screen by overlaying the raster layer surface.dem on layer shadedrelief by reducing opacity, and exported as tif image relief.tif.
62 7.9.2. Creating land use map:
For creating land use map, cgplanduse.tif, followed the steps:
1. An additional field lu_code_pseudo is added in the attribute table of the vector layer luse and a pseudo colour code is entered for each land use type as given in annexure-IV, for rasterising the layer, and identifying each land-use type distinctly, after rasterisation.
2. Batch entry of codes for each land use type were done by issuing command as:
GRASS 6.2.3 (cheruvannur):~ > v.db.update luse col=lu_code_pseudo \ value=16 where="descr_type='Coconut'"
3. Rasterised the vector layer luse applying command:
GRASS 6.2.3 (cheruvannur):~ > v.to.rast input=luse \ output=luse column=lu_code_pseudo
4. The land use map in pseudo colours is generated in GRASS map display screen and exported as tif image landuse.tif. 5. The colours of the land use types are changed by editing the image with GIMP as it may match with the land use colours of grama panchayat resource map.
7.9.3. Converting the base map tif images to GeoTIF format:
The base map tif images landuse.tif and relief.tif are converted to GeoTIF format by the help of GDAL (Geospatial Data Abstraction Library). gdalinfo and gdal_translate are the modules used for this purpose. gdalinfo is used to get the information about the image, and gdal_translate is used for converting tif image to GeoTIFF format.
The latitude-longitude extends for the images are obtained from GRASS, by issuing command:
GRASS 6.2.3 (cheruvannur):~ > v.info -g map=villageboundaries layer=1
63 Then command is issued to convert the images to GeoTIF as:
$ gdal_translate -of GTiff -co "TILED=YES" -a_ullr 75.673957 \ 11.601310 75.732038 11.543698 relief.tif cgprelief.tif
$ gdal_translate -of GTiff -co "TILED=YES" -a_ullr 75.673957 \ 11.601310 75.732038 11.543698 landuse.tif cgplanduse.tif
The command gdalinfo is used for checking the image:
$ gdalinfo cgplanduse.tif Driver: GTiff/GeoTIFF Files: cgplanduse.tif Size is 1980, 1965 Coordinate System is `' Origin = (75.673957000000001,11.601310000000000) Pixel Size = (0.000029333838384,-0.000029319083969) Metadata: TIFFTAG_DOCUMENTNAME=/var/www/ka-map-1.0- 20070205/htdocs/cgpdata/cgpland_use.tif TIFFTAG_XRESOLUTION=72 TIFFTAG_YRESOLUTION=72 TIFFTAG_RESOLUTIONUNIT=2 (pixels/inch) Image Structure Metadata: INTERLEAVE=PIXEL Corner Coordinates: Upper Left ( 75.6739570, 11.6013100) Lower Left ( 75.6739570, 11.5436980) Upper Right ( 75.7320380, 11.6013100) Lower Right ( 75.7320380, 11.5436980) Center ( 75.7029975, 11.5725040) Band 1 Block=256x256 Type=Byte, ColorInterp=Red Band 2 Block=256x256 Type=Byte, ColorInterp=Green Band 3 Block=256x256 Type=Byte, ColorInterp=Blue $
7.9.4. Exporting vector layers as shapefile format:
Each vector layers are converted to ESRI shapefile format by issuing commands as:
GRASS 6.2.3 (cheruvannur):~ > v.out.ogr -e input=gen_fac \ type=point dsn=gen_fac olayer=gen_fac \ layer=1 format=ESRI_Shapefile
64 7.10. Setting up visualisation:
An Open Source API (Application programme interface) – ka-Map is used for setting up visualisation. It is a javascript API used to develop interactive web- mapping interfaces using the features available in modern web browsers. It works on top of Apache, Mapserver, PHP, and PHP Mapscript.
1. Downloaded the file ka-map-0.2-20060207.tar.gz from the ka-Map website, and extracted on to the directory /var/www/.
2. Changes were made in ka-Map configuration and index scripts as it may work properly with operating system, as given in annexure-V. Changes made in ka-Map's config.php script file are the settings to point to two shared object files namely gd.so and php_mapscript.so as the name and position of these files differ in various operating systems. The other change is setting of the pre-defined scales of visualisation.
3. A data directory is created in /var/www/ka-map-1.0-20070205/htdocs/ directory by issuing following command:
$ mkdir /var/www/ka-map-1.0-20070205/htdocs/cgpdata
4. Copied all the vector layers which were exported to ESRI Shapefile format, to the directory cgpdata, along with the two raster base maps.
5. Created a key map keymap.png with a lesser resolution with GRASS, put an image of compass rose on it with the help of GIMP, also copied to this directory.
6. Created map file cgp.map, symbol file symbols,sym, fonts file fonts.list as given in annexure – V.
7. cgp.map is copied to the /var/www/ka-map-1.0-20070205/htdocs/ directory, symbols,sym, and fonts.list are copied to the directory /var/www/ka-map-1.0-20070205/htdocs/cgpdata. 8. The fonts listed in file fonts.list also copied to the directory /var/www/ka-map-1.0-20070205/htdocs/cgpdata.
65 9. Created a raster legend legend.png using GIMP, copied into the /var/www/ka-map-1.0-20070205/htdocs/ directory.
10. Set web server aliases in file /etc/apache2/sites-available/default, as given in annexure – V. Then restarted the web server by issuing following command:
# /etc/init.d/apache2 restart
Setting up of geo-visualisation is complete.
Figure 7.2: Diagrammatic representation of visualisation set-up.
66 8. Results and Discussion
Geo spatial-database is created along with the attribute information as discussed in the previous chapter. Raster and vector layers are listed in annexure - II, while annexure - III provides the table structure and annexure - IV provides the codes. Base vector layers digitized are village boundary (Figure 8.1), contour (Figure 8.2) and land use (Figure 8.3). Other vector layers are ward boundaries during 2000-2005 (Figure 8.4), ward boundaries during 2005-2010 (Figure 8.5), stream channels (Figure 8.6), rivers and ponds (Figure 8.7), irrigation canals (Figure 8.8), sacred groves (Figure 8.9), water resource development structures / water flow control structures (Figure 8.10), Sub-watershed boundaries (Figure 8.11), general facilities (Figure 8.12), medical facilities (Figure 8.13), education facilities (Figure 8.14), child development - anganwadi centres (Figure 8.15), communication facilities (Figure 8.16), energy (Figure 8.17), roads (Figure 8.18) and place names (Figure 8.19).
Figure 8.1: Boundary lines of Cheruvannur village in Cheruvannur Grama Panchayat (source: Map of Koyilandi taluk in District Census Hand book and Grama panchayat resource map)
67 Figure 8.2: Contours of Cheruvannur Grama Panchayat at 10 meters interval. (source: SOI Toposheet 49M/10/SE – 1:25,000)
Figure 8.3: Land use pattern of Cheruvannur Grama Panchayat. (source: resource map of Grama Panchayat. 1:4000)
68 Figure 8.4: Ward boundaries of Cheruvannur Grama Panchayat (2000-2005). (source: Resource map of Grama Panchayat. 1:4000)
Figure 8.5: Ward boundaries of Cheruvannur Grama Panchayat (2005-2010). (source: Local Self Government Institutions Election 2005 – Ward de-limitation documents)
69 Figure 8.6: Stream channels (drainage). (source: Resource map of Grama Panchayat. 1:4000)
Figure 8.7: Rivers and ponds. (source: Resource map of Grama Panchayat. 1:4000)
70 Figure 8.8: Irrigation canals. (source: Resource map of Grama Panchayat. 1:4000) Three irrigation canal distributories are passing through the grama panchayat area, and ending up inside. These canals are represented in this layer.
Figure 8.9: Sacred groves. (source: Resource map of Grama Panchayat. 1:4000)
71 Figure 8.10: Water resource development structures / Water flow control structures. (source: SOI Toposheet 49M/10/SE – 1:25,000)
Figure 8.11: Sub watershed boundaries in Kuttiyadi river watershed area. (sources: Watershed Atlas, Kerala Land Use Board and wWatershed based development master plan – Perambra Block Panchayat.)
The grama panchayat area lies withing the watershed of Kuttiyadi river, and area divided into four sub watersheds of the river. The developmental activities of grama panchayat are based mainly on watershed. Sub watershed boundaries are represented in this layer.
72 Figure 8.12: General public facilities – Government offices, Ration shops, etc. (source: Resource map of Grama Panchayat. 1:4000)
This layer covers the general public facilities. This include grama panchayat office, krishi bhavan etc, civil supply arrangements like ration shops and Maveli stores, other facilities like banks, cemetery, river sand mining sites, 'Akshaya' computer kiosks, institutions of animal husbandry namely veterinary hospital and artificial insemination centre for cattle development.
Figure 8.13: Medical facilities – include Primary Health Centre, Family Welfare Centres, Ayurveda hospital, Homeopathy dispensary, private clinic, and medical shops. (source: Resource map of Grama Panchayat. 1:4000)
73 Figure 8.14: Education facilities - Schools, public libraries, and literacy centers. (source: Resource map of Grama Panchayat. 1:4000)
Figure 8.15: Child development - Anganwadi centres. (source: Resource map of Grama Panchayat. 1:4000)
74 Figure 8.16: Communication facilities – Post offices, Telephone exchanges and Public telephone booths (source: Resource map of Grama Panchayat. 1:4000)
Figure 8.17: Energy – Position of Transformers and H.T. Line. (source: Resource map of Grama Panchayat. 1:4000)
75 Figure 8.18: Roads. (source: Resource map of Grama Panchayat. 1:4000)
Figure 8.19: Place names (Number of points reduced to avoid cluttering). (source: Resource map of Grama Panchayat. 1:4000)
76 Digital elevation model (DEM) and shaded relief created using contours (Figure 6.2) is given in Figure 6.20 and Figure 6.21 respectively. By merging these two layers a relief map is generated, which is given in Figure 6.22. Land use of the panchayat is given in Figure 6.24, that is created based on the resource map.
Figure 8.20: DEM.
Figure 8.21: Shaded relief.
77 Figure 8.22: Shaded relief map.
Figure 8.23: Rasterised vector layer land use.
78 Figure 8.24: Land use map - land use pattern of the grama panchayat area.
79 Spatial Decision Support System designed for Cheruvannur Grama Panchayat in Koyilandi taluk, Kozhikode district of Kerala state, India is given in Figure 6.25. It is accessible through a web browser, by typing address as http://wgbis.ces.iisc.ernet.in/resources/. The DSS consists of options for layer selection, identify and query, search and locate facilities, opting different scales etc. are shown through figures 8.26 to 8.33. Figure 8.26 gives the display of roads with labels. Landuse with shaded relief useful in watershed programmes is given in Figure 8.33.
Figure 8.25: Spatial Decision Support System for Cheruvannur Grama Panchayat.
80 Figure 8.26: Layer selection – roads and place names.
Figure 8.27: Identify and query facility.
81 Figure 8.28: Search facility.
Figure 8.29: Display at scale – 1:20000.
82 Figure 8.30: Display at scale – 1:10000.
Figure 8.31: Locate feature (Scale 1:5000).
83
Figure 8.32: Panning in key map.
Figure 8.33: – Land use overlayed on shaded relief.
84 9. Conclusion
Spatial decision support systems are designed suitable for local area planning using free / open source software tools. This helps the line departments to visualize the decisions which helps in effective planning in grama panchayat. Usage of free open source software has proved to be economical and also availability of source codes has helped in modification of softwares to suite local needs.
This is useful to the decision makers – notably, the people who take part in grama sabhas, the resource persons who participate in panchayat level development seminar, the implementing officers and staff, the elected body of the grama panchayat, block level technical advisory group (TAG) and district planning committee (DPC). This SDSS can be installed in a computer system in grama panchayat office, computers available under “Asraya” project at “Kudumbasree” CDS office, and make use of it. Cheruvannur grama panchayat have two public computer kiosks, under the 'Akshaya' project of state IT Mission. These kiosks can also be made as accessing points of this tool for the people, by installing it there.
Besides, I.T. Education in schools of Kerala state remain almost completely shifted to free software under “IT@school” project. Government schools in grama panchayat also have computer facilities. So students of these schools also can take part in the future development, expansion and optimisation of this tool by installing this tool there.
85 10. Future scope of work
In this work, layers are exported to shapefile format along with attribute tables. These tables are placed in document root and accessed. Geo-database is standing separately. By using an implementation of web processing service called PyWPS (Python Web Processing Service) with kaMap, the GRASS commands can be used to query the geo-database directly and more effectively from web interface. Implementation of a wide array of GRASS commands would be the advantage of it. Queries for more specific issues can also be implemented then.
Web based 3D GIS is still experimental in the FOSS world, but the active development of projects like Open3DGIS are promising.
Similar works can be done for other panchayats also. District and block level databases and visualisations can be developed in similar way. It is possible to develop a distributed spatial database spanning from district headquarters to block panchayats and grama panchayats, making district headquarters as the central node. NRIS database specifications can be used for it with modifications, provided NRIS is to be expanded as it can also accommodate detailed village level spatial data. Such a move would disseminate the local spatial information and leverage the decentralised planning activities as a whole.
86 Reference:
1. Burrough, P.A., 2001. GIS and geostatistics: Essential partners for spatial analysis. Environmental and Ecological Statistics, 8(4), 361-377.
2. Brail, R. K. & Klosterman, R.E., 2001. Planning Support Systems: Integrating Geographic Information Systems, Models, and Visualization Tools, Esri Press.
3. Brewer, I., A. M. MacEachren, H. Abdo, J. Gundrum, and G. Otto. 2000. Collaborative Geographic Visualization: Enabling shared understanding of environmental processes. IEEE Information Visualization Symposium: 137- 141.
4. Chen Shun-ling, 2006. Free/Open Source Software Licensing, Elsevier, New Delhi. 5. Cheruvannur Grama panchayat Janakeeyasutrana Vikasana Rekha, 1994. Cheruvannur Grama Panchayat, Cheruvannur. 6. Dassau, Otto etal.(Ed.), 2005. An introduction to the practical use of the Free Geographical Informaiton System GRASS 6.0, GDF Hannover bR, Hanover. 7. De By, R.A, 2001. Principles of Geographic Information Systems. ITC Educational Textbook Series. 8. Döllner, J., T. H. Kolbe, F. Liecke, T. Sgouros, and K. Teichmann. 2006. The Virtual 3D City Model of Berlin-Managing, Integrating, and Communicating Complex Urban Information. Proceedings of the 25th Urban Data Management Symposium UDMS 2006: 15-17. 9. Ehlers, M and Amer, S., 1991. Geoinformatics: An integrated approach to acquisition, processing and production of geo-data, Proceedings EGIS'91, Brussels, 306-312. 10.Faguet, J.P., 2004. Does decentralization increase government responsiveness to local needs? Evidence from Bolivia. Journal of Public Economics, 88(3-4), 867-893. 11.Felus, Yaron A., 2007. On the positional enhancement of digital cadastral maps, Survey review, 39, 268-281(14). 12.Ganesh, K.M., 1990. Keralathinte Innalekal, Dept. of Cultural Publications, Govt. of Kerala, Thiruvananthapuram. 13.Geodetic Glossary, National Geodetic Survey, National Ocean Service, National Oceanic and Atmospheric Administration, Rockville, MD,
87 September 1986, pp. 54.
14.Gupta, K.K., & Tyagi, V.C, 1992. Working with maps, Survey of India, Dehra dun. 15.Güting, R.H., 1994. An introduction to spatial database systems. The VLDB Journal The International Journal on Very Large Data Bases, 3(4), 357-399.
16.Hellerstein, J. M., Stonebraker, M & Hamilton J., 2007. Architecture of a Database System, now Publishers Inc. 17.Hernandez, T. 2007. Enhancing retail location decision support: The development and application of geovisualization. Journal of Retailing and Consumer Services 14, no. 4: 249-258. 18.Information Technology Annual Report, 2007-2008. Government of India, New Delhi. 19.Information Technology Policy Document, 2007. Government of Kerala, Thiruvananthapuram. 20.Innes.C.A, Evans.F.B.(Ed.), 1958(Reprint). Gazatteer of the Malabar District, Vol-1, Superintendent of Govt.Press, Madras. 21.Jeffrey D. Ullman & Jennifer Widom, 2001. A first course in database systems, Pearson Education Asia, Delhi. 22.Johnson Dominic & Johnson George (Ed.), 2003. Kerala Panchayat Law Manual. Law Book Centre. Ernakulam. 23.Johnson, C., 2003. Decentralisation in India: Poverty, Politics and Panchayati Raj, Overseas Development Institute, London. 24.Kei Saito, Shinji Chiba, Michihiko Shinozaki, 2005. Development of open source GIS Educational Tools for urban planning - Migration to the GRASS- GIS package in the GIS educational environment, International Journal of GeoInformatics. 25.Kei Saito, Shinji Chiba, Michihiko Shinozaki, 2005. Development of GIS Educational tools for Urban Planning Using Free and Open Source Software, 8th International Conference of the Asian Planning Schools Association. 26.Kraak, M. J. 2003. Geovisualization illustrated, ISPRS Journal of Photogrammetry and Remote Sensing 57. no. 5-6: 390-399. 27.Krisp, J. M. 2006. Geovisualization and knowledge discovery for decision- making in ecological network planning. Doctor’s thesis, Helsinki University of Technology. 28.Kurup, K.K.N., 1999. Pazhassi Samarangal, Kerala Bhasha Institute,
88 Thiruvananthapuram. 29.Lloyd, D., and J. Dykes, 2007. Understanding geovisualization users and their requirements - a user - centred approach. Proceedings of the Geographical Information Science Research UK (GISRUK) Conference: 209- 214. 30.MacEachren, A. M., I. Brewer, and E. Steiner. 2001. Geovisualization to mediate collaborative work: tools to support different-place knowledge construction and decision-making. Proceedings of the 20th International cartographic conference, Beijing, China, August: 6-10. 31.MacEachren, A. M., and M. J. Kraak. 2001. Research challenges in geovisualization. Cartography and Geographic Information Science 28, no. 1: 3-12. 32.MacEachren, A. M. and Monmonier, M. 1992. Introduction to special content: geographic visualization: Cartography and Geographic Information Systems. 33.Madden, M., T. Jordan, and J. Dolezal. 2006. Geovisualization of Vegetation Patterns in National Parks of the Southeastern United States., Geographic Hypermedia – Concepts and systems (Lecture Notes in Geoinformation and Cartography). Springer, Berlin: Part -IV 329-345. 34.Mahwood, P., 1983. Local Government in the Third World, John Wiley & Sons, Chichester. 35.Masser, I., Campbell, H. & Craglia, M., 1996. GIS Diffusion: The Adoption and Use of Geographical Information Systems in, CRC Press.
36.Mohamed, M.Z. & Appalanaidu, U.B., 1998. Information systems for decentralization of development planning: Managing the change process. International Journal of Information Management, 18(1), 49-60.
37.Neteler, M., and H. Mitasova, 2002. Open Source Gis: A Grass Gis Approach. Kluwer Academic Pub. 38.Newman, J.R., 1952. The Rhind Papyrus. Scientific American, 187(2), 24-27.
39.Omer, I., R. Goldblatt, and U. Or. 2005. Virtual city design based on urban image theory. The Cartographic Journal 42, no. 1: 1-12.
40.Powell, G. 2006. Beginning database design, Wiley publishing Inc, Indianapolis. 41.Ravi Kumar.V, Sinha.P.K, Satya Kumar.A.V, Free and Open Source Geographic Information System for Urban Planning, GIS Development.
89 42.Reddy, P.S. & Sabelo, T., 1997. Democratic decentralization and central/provincial/local relations in South Africa. International Journal of Public Sector Management, 10(7), 572-588. 43.Redners tryckeri, 2003, Free and Open Source Software - A feasibility study, The Swedish Agency for Public Management Publication Service. 44.Rinner, C. 2007. A geographic visualization approach to multi-criteria evaluation of urban quality of life. International Journal of Geographical Information Science 21, no. 8: 907-919. 45.Saito, C. & Kato, R. 2008. Contrasting Experiences of Decentralization in Two States in India. Foundations for Local Governance, Physica-verlag HD. 46.Sengtianthr, V. 2004. Solid Waste Management in Urban Areas of Vientiane Capital City using GIS. 30th WEDC International Conference. Vientiane, LAO PDR. 47.Sheela Thomas, 2006. District Census Handbook - Kozhikode 2001, Directorate of Census Operations – Thiruvananthapuram. 48.Slocum, T. A., C. Blok, B. Jiang, et al. 2001. Cognitive and Usability Issues in Geovisualization. Cartography and Geographic Information Science 28, no. 1: 61-75. 49.Wheeler, D. A. Why Open Source Software/Free Software (OSS/FS, FLOSS, or FOSS)? Look at the Numbers! David A. Wheeler's Personal Home Page. 50.Doytsher, Y., Gelbman, E, 1995. Rubber-Sheeting Algorithm for Cadastral Maps, Journal of Surveying Engineering, 121(4).
51.http://earth-info.nga.mil/GandG/publications/tm8358.1/toc.html
52.http://fci.wikia.com/wiki/സ്തന_മലയാളം_കമ്ടിങ്/െെബിയനള_േേഖരം 53.http://indictrans.in/demos/chameleon/samples/htdocs/korba.phtml 54.http://indictrans.in/demos/maha_map.dev/ 55.http://mumbai.freemap.in/ 56.http://sam.dgs.ca.gov/ 57.http://vvsr.freemap.in/ 58.http://www.debian.org/ 59.http://www.fsf.org/licensing/essays/categories.html 60.http://www.ngs.noaa.gov/CORS-Proxy/Glossary/xml/NGS_Glossary.xml 61.http://www.opensource.org/ 62.http://www.smc.org.in/
90 ANNEXURE - I Table – 1 Important institutions under Cheruvannur Grama Panchayat
Head of Office / Concerned Department of S.I. Institution Implementing State Officer / Key position Office of the 1. Cheruvannur Grama Department of Panchayats Secretary Panchayat Krishi Bhavan*, Agriculture Officer 2. Department of Agriculture Cheruvannur (Gazetted) Primary Health Department of Medical Officer 3. centre*, Avala Health Services (Gazetted) Ayurveda Hospital*, Medical Officer 4. Department of Ayurveda Cheruvannur (Gazetted) Homeo Dispensary*, Medical Officer 5. Department of Homeopathy Cheruvannur (Gazetted) 6. Anganwadi Centres* Directorate of Social Welfare Anganwadi Supervisor Govt. Upper Primary Department of Head Master 7. School***, General Education (Gazetted) Cheruvannur Govt. M. L. P. Department of 8. Head Master School*, Avala General Education Village Extension* - Village Extension Cheruvannur and Commissionerate of 9. Officer / Lady Village Avala Circles Rural Development Extension Officer.
Veterinary Hospital*, Department of Veterinary Surgeon 10. Muyippoth Animal Husbandry (Gazetted) I.C.D.P. Sub Centre*, Department of 11. Live Stock Inspector Avala Animal Husbandry Ground water Department Assistant Engineer 12. Public Works Wing ** and Department of Public (Gazetted) Works
Orders issued by State Government of Kerala to transfer the control of institutions to Grama Panchayat:
* G.O(P) No. 189/95/LAD dt.18/9/1995 ** G.O(M.S.) No. 31/2003/LSGD dt.29/1/2003 *** G.O(M.S.) No. 41/2005/Plg dt. 7/6/2005
91 ANNEXURE - II Layers Table – 1 Raster Layers S.I. Name Description 1. cgprelief.tif Merged image of Digital Elevation Model and Shaded relief 2. cgplanduse.tif Land Use / land Cover
Table - 2 Vector Layers S.I. Name Description 1. admin_2000_2005 Ward boundaries 2000-2005 – Boundary 2. admin_2005_2010 Ward boundaries 2005-2010 – Boundary 3. drainl Drainage/Streams – Lines 4. drainp Water body mask – Polygons (Ponds and River) 5. canal Irrigation canals – Line 6. s_grove Sacred groves – Boundary 7. wrdpp Water resource development structures – Point (Weir, Regulator, Siphon and Aqueduct) 8. wshed Watershed boundaries – Line 9. gen_fac General Facilities – Point (Details in annexure - IV) 10. med_fac Medical Facilities – Point (Details in annexure - IV) 11. ed_fac Educational Facilities – Point (Schools & Libraries) 12. child_fac Child Development Facilities – Point (Anganwadi Centres) 13. comm_fac Communication Facilities – Point (Post offices, Telephone exchanges, Telephone booths) 14. energy Electricity – Point (Transformers and H.T. Line towers) 15. roads Road network - Line 16. place_name Place names - Point
92 ANNEXURE – III Attribute Tables – Structure
1. admin_2000_2005: Name Type Width Description cat integer 4 Link to vector geometry const_code numeric 2,0 Ward number descr character 30 Description descr_mal character 50 Description in Malayalam 2. admin_2005_2010: Name Type Width Description cat integer 4 Link to vector geometry const_code numeric 2,0 Ward number descr character 30 Description descr_mal character 50 Description in Malayalam 3. drainl: Name Type Width Description cat integer 4 Link to vector geometry drainl_code character 2 Feature code1 descr character 30 Description descr_mal character 50 Description in Malayalam 4. drainp: Name Type Width Description cat integer 4 Link to vector geometry drnp_code character 2 Feature code2 descr character 30 Description descr_mal character 50 Description in Malayalam 5. canal: Name Type Width Description cat integer 4 Link to vector geometry can_code character 2 Feature code3 can_type character 30 Code description descr character 30 Description descr_mal character 50 Description in Malayalam
93 6. s_grove: Name Type Width Description cat integer 4 Link to vector geometry descr character 50 Description descr_mal character 50 Description in Malayalam 7. wrdpp: Name Type Width Description cat integer 4 Link to vector geometry wrdpp_code character 2 Location specific prescription code4 wr_prescription character 30 Prescription (Type) descr character 50 Description descr_mal character 50 Description in Malayalam 8. wshed: Name Type Width Description cat integer 4 Link to vector geometry ws_lcode character 16 Location specific prescription code5 ws_code character 8 AISLUS code5 region character 40 Region description basin character 40 Basin description catchment character 40 Catchment description subcatch character 40 Sub catchment description watershed character 40 Watershed description subwshed character 40 Sub watershed description microwshed character 40 Micro watershed description descr_mal character 50 Description in Malayalam 9. gen_fac: Name Type Width Description cat integer 4 Link to vector geometry gen_type character 50 Facility type code6 descr character 50 Description descr_mal character 50 Description in Malayalam
94 10. med_fac: Name Type Width Description cat integer 4 Link to vector geometry med_type character 50 Facility type code7 descr character 50 Description descr_mal character 50 Description in Malayalam 11. ed_fac: Name Type Width Description cat integer 4 Link to vector geometry ed_type character 50 Facility type descr character 50 Description descr_mal character 50 Description in Malayalam 12. child_fac: Name Type Width Description cat integer 4 Link to vector geometry descr character 50 Description descr_mal character 50 Description in Malayalam code_no character 4 Centre Number 13. comm_fac: Name Type Width Description cat integer 4 Link to vector geometry descr character 50 Description descr_mal character 50 Description in Malayalam 14. energy: Name Type Width Description cat integer 4 Link to vector geometry p_type character 50 Type descr character 50 Description descr_mal character 50 Description in Malayalam
95 15. roads: Name Type Width Description cat integer 4 Link to vector geometry rd_code character 4 Road code8 descr character 50 Description type character 30 Construction method subtype character 30 Category descr_mal character 50 Description in Malayalam 16. place_name: Name Type Width Description cat integer 4 Link to vector geometry descr character 50 Description descr_mal character 50 Description in Malayalam
17. luse (To create raster layer cgplanduse.tif): Name Type Width Description cat integer 4 Link to vector geometry lu_code character 8 Land Use Code9 lu_code_pseudo numeric 2 Pseudo code for distinct colours9 descr_type character 30 Landuse type descr_mal character 50 Description in Malayalam
17. contour (To make DEM and shaded relief related to cgprelief.tif): Name Type Width Description cat integer 4 Link to vector geometry height integer 4 Contour Height
Note 1-9: Codes are explained in Annexure – IV.
96 ANNEXURE – IV Based on Natural(National) Resources Information System Node Design and standards 1. Codes for attribute table drainl: drainl_code description 01 Perennial 02 Dry 03 Tidal 04 Undefined/Unreliable 05 Perennial/Unreliable
2. Codes for attribute table drainp: drnp_code description 01 River 02 Canal 03 Lakes/ Ponds 04 Reservoir 05 Tanks
3. Codes for attribute table canal: can_code description 01 Main Canal 02 Branch Canal 03 Canal Under Construction 04 Distributory Canal
4. Codes for attribute table wrdpp: wrdpp_code description 01 Check dams 02 Nullah bunds 03 Percolation Tank 04 Underground Bandharas 05 K.T. Weirs 06 Reservoir 07 Siphon 08 Aqueduct
97 5. Code for attribute table wshed (All India Soil & Land Use Survey Code): Code scheme followed is AA-BB-CC-DD-EE-FF-GG-HH Where:
AA BB CC DD EE FF GG HH d t d d e n e e t h e d h h s n s e s r m e n r r h e n h o i e t e s i m c t t s r a t g h a a a e a c e t B t W R a W W C a i o r b b W n C i c u u i S S M M d t d d e h n e e e h c e n d h n t h s i o s o s i a m s r w c c h
ws_lcode g - w a e o c b e t s r b b t r u c a u w i a s s c w m i a e e 4 ,c h K e h h
05-01-02-03-07-00-00-00 5A2C7 t b 4 8 , a a , a S a v 3 2 M n i M a a d 4 r o o i , t a a b
t 2 i y h r a i n t r a 4 , S t a y A i o 1 u n r K 4 t n e n o P i P r o m o C e p a C
6. Codes for attribute table gen_fac: gen_type description Cem Cemetery Comp.S Computer Service CS Civil Supply GO Government Office SCB Service Cooperative Bank SM River sand mining site VH Veterinary hospital VSC Veterinary sub centre
98 7. Codes for attribute table med_fac: med_type description D Dispensary FPC Family Planning Centre HO Hospital MDO Medical Shop PHC Primary Health Centre PHS Health Sub Centre RP Private Clinic
8. Codes for attribute table roads: rd_code description subtype 01-00 Metalled – Black Topped (BT) or Bitumen 01-01 National Highway 01-02 State Highway 01-03 District Road 01-04 Village Road 02-00 Unmetalled – Roads 02-01 National Highway 02-02 State Highway 02-03 District Road 02-04 Village Road
99 9. Codes for attribute table luse Pseudo colour code given in square brackets: description- description description description lu_code L1 - L2 - L3 - L4 1:1 M 1:250,000 1:50,000 1:25,000 01-00-00-00 Built-up 01-02-00-00 Village (Rural) 01-02-06-00 Commercial [90] 02-00-00-00 Agriculture 02-01-00-00 Crop land (Paddy) [0] 02-01-08-00 Paddy converted to coconut [80] 02-01-09-00 Paddy converted to mixed crops [95] 02-02-00-00 Fallow 02-02-01-00 Present Fallow [112] 02-03-00-00 Plantations 02-03-03-00 Rubber [35] 02-03-04-00 Coconut [16] 02-03-08-00 Mixed Trees [100] 02-03-09-00 Cashew [8] 04-00-00-00 Wastelands 04-04-00-00 Land without Scrub [110] 04-07-00-00 Sheet Rock [65] 04-07-01-00 Rock Quarry [65] 04-08-00-00 Laterite 04-08-01-00 Laterite Quarry [88] 05-00-00-00 Water bodies 05-01-00-00 River 05-01-01-00 Water Channel Area [48] 06-00-00-00 Wetlands 06-01-00-00 Inland Wetlands 06-01-01-00 Water logged [48]
100 ANNEXURE – V List of softwares and packages used
S.I. Software Used as / for 1. Debian GNU/Linux 'Etch' Ver. 4.0 Operating System. 2. GNOME 2.14.3 Desktop Environment. 3. GRASS 6.2.3* GIS operations – Both vector and raster analysis, Preparing maps. 4. PostgreSQL 8.1 To store attribute data. 5. PostGIS 1.1.2 As support for geographic objects to the PostgreSQL object-relational database. 6. phpPgAdmin 4.0 As front end for PostgreSQL. 7. Malayalam Patches* To get Unicode Malayalam support. (From apt repository of Swathantra Malayalam Computing) 8. SCIM platform 1.4.4 Entering data in Malayalam (Unicode) 9. GIMP 2.2 For editing photographs, Finishing touches for maps. 10. GNU Paint 2.0.3 For minor editing on photographed maps. 11. GDAL 1.3.2 gdalinfo - to get information about image and gdal_translate - to convert TIFF format to GeoTIFF. 12. Quantum GIS 0.9.0* To check the attribute information of vector layers, converted from GRASS format to Shapefile format. 13. F-Spot 0.2.1 For handling Photographs of study area, and photographed maps. 14. Eye of GNOME 2.16.3 Viewing photographs, pictures and maps. 15. ImageMagick 6.2.4 identify – to get the details of images such as resolution, channel statistics etc. 16. Inkscape 0.44 To do finishing touches to maps. 17. php 5.2.0 As server-side scripting language to back phpPgAdmin, MapServer and ka-Map. 18. Apache 2.2.3 Web server to support phpPgAdmin, MapServer and ka-Map. 19. UMN MapServer 4.10.0 To set-up geo-visualization. 20. ka-Map 1.0* As API to set-up geo-visualization. 21. iceweasel 2.0.0 Web browser to view and test geo-visualization. (A re-branding of Mozilla Firefox web browser) 22. Epiphany 2.14.3 Another Web browser to view and test geo- visualization. 23. OpenOffice.Org 2.0 For preparing dissertation. 24. Zotero 1.0.6* For managing and citing research sources while preparing dissertation. (An extension of Mozilla Firefox web browser.) * Package not a part of Debian Etch and needed separate install.
101 Listing of changes in system configuration scripts
Lines appended to file: /etc/apt/sources.list
#Mirror of Debian GNU/Linux repositories - Indian Institute of Technology, Chennai:- deb ftp://ftp.iitm.ac.in/debian/ etch contrib main deb ftp://ftp.iitm.ac.in/debian/ etch main contrib non-free
#Unicode Malayalam repositories – Swathanthra Malayalam Computing, Savannah:- deb http://download.savannah.gnu.org/releases/smc/debian etch main
#Backport packages:- #deb http://www.backports.org/debian etch-backports main contrib non-free
Appended/ Edited lines in file: /etc/network/interfaces
address 10.132.18.12 netmask 255.255.255.0 network 10.132.18.0 broadcast 10.132.18.255 gateway 10.132.18.1 nameserver 10.16.25.15 10.16.25.13
Appended line in file : /etc/network/resolv.conf nameserver 10.16.25.15 10.16.25.13
Added / Edited lines in file: /etc/hosts
127.0.0.1 localhost.localdomain localhost 10.132.18.12 localhost.ces.iisc.ernet.in localhost
Aliases set in file: /etc/apache2/sites-available/default
Alias /resources/ "/var/www/ka-map-1.0-20070205/htdocs/"
102 Edited ka-Map configuration scripts
Changes to file: /var/www/ka-map-1.0-20070205/include/config.php (File name changed from config.dist.php to config.php) Lines 49 and 50:-
$szPHPMapScriptModule = 'php_mapscript.'.PHP_SHLIB_SUFFIX; $szPHPGDModule = 'gd.'.PHP_SHLIB_SUFFIX;
Lines 106 to 115:-
$aszGMap = array ( 'title' => "Resource Map", 'path' => "/var/www/ka-map-1.0-20070205/htdocs/cgp.map", 'scales' => array( 40000, 20000, 10000, 5000 ), 'format' => "PNG" /* Sample authorized_users entry. See auth.php for more details: * ,'authorized_users' => array('popplace' => array('user1', 'user2'), * 'park' => array('user1') */ );
Line 155:-
$szBaseCacheDir = "/var/www/ka-map-1.0-20070205/htdocs/kacache/";
Changes to file: /var/www/ka-map-1.0-20070205/htdocs/index.html
Line 45:-
Lines 80 and 81:-
Line 83:-
Added following line after line 212:-
103 Listing of visualization scripts
File: /var/www/ka-map-1.0-20070205/htdocs/cgp.map
MAP # Begin map file.. ഭപട വിവരണം ഇവിെട തടങന... NAME CheruvannurGP # Name of Map file. STATUS ON SIZE 660 655 SYMBOLSET cgpdata/symbols.sym # Symbology description is in this file and path. FONTSET "cgpdata/fonts.list" # List of fonts used are in this file and path. EXTENT 75.673957 11.543698 75.732038 11.601310 # Latitude Longitude extents. UNITS DD # Map units are in degree decimals. IMAGECOLOR 255 255 255 # Background colour - White (R G B values). IMAGETYPE png
WEB IMAGEPATH "/var/www/ka-map-1.0-20070205/htdocs/" IMAGEURL "/ka-map/tmp/" METADATA "max_extents" "75.67, 11.54, 75.736, 11.605" # Bounds to pan. END # കാണാവന പരമാവധി പരിധി END
REFERENCE # Key map. EXTENT 75.673957 11.543698 75.732038 11.601310 SIZE 235 234 IMAGE cgpdata/keymap.png COLOR -1 -1 -1 OUTLINECOLOR 255 0 0 END
LEGEND TRANSPARENT TRUE END
SCALEBAR TRANSPARENT TRUE END
LAYER # Raster layer 1 - Base map- Elevation. GROUP "Elevation / Height" NAME elevation TYPE RASTER STATUS ON DATA "cgpdata/cgprelief.tif" METADATA "imageformat" "jpeg" # For picture enhancement in browser. END END
LAYER # Raster layer 2 - Land use. GROUP "Land use / Land cover" NAME landuse TYPE RASTER
104 METADATA "opacity" "45" # Opacity reduced to view the base layer through. END STATUS OFF DATA "cgpdata/cgplanduse.tif" METADATA "imageformat" "jpeg" END END
LAYER # Vector layer 1 - Administrative boundaries 2005 - 2010. GROUP "Admin boundary 2005 - 2010" NAME admin_boundaries TYPE LINE STATUS ON DATA "cgpdata/admin_2005_2010.shp" CLASS NAME "Admin boundary 2005 - 2010" STYLE # Style of feature appearance, symbol etc. SYMBOL "border" SIZE 1 COLOR 200 000 100 END END END
LAYER # Vector layer 2 - Administrative boundaries 2000 - 2005. GROUP "Admin boundary 2000 - 2005" NAME admin_boundaries_old TYPE LINE STATUS OFF DATA "cgpdata/admin_2000_2005.shp" CLASS NAME "Admin boundary 2000 - 2005" STYLE SYMBOL "border" SIZE 1 COLOR 255 40 195 END END END
LAYER # Vector layer 3 - Streams / ോോാടകള. GROUP "Streams" NAME "Streams / ോോാടകള" TYPE LINE STATUS ON DATA "cgpdata/drainl.shp" METADATA # Settings for query / search in attribute tables. "queryable" "true" "searchfield" "descr" "fields" "descr:Name,descr_mal:ോപര്" END CLASS NAME "Streams" STYLE
105 SYMBOL 'point' SIZE 2 COLOR 75 250 255 END END TEMPLATE "Streams" # Query sytem need a string here. END
LAYER # Vector layer 4 - River and ponds / പഴ, കളം. GROUP "River and ponds" NAME "River and ponds / പഴ, കളം" TYPE POLYGON STATUS ON DATA "cgpdata/drainp.shp" METADATA "queryable" "true" "searchfield" "descr" "fields" "descr:Name,descr_mal:ോപര്" END CLASS NAME "River and ponds" STYLE SYMBOL 'square' SIZE 2 COLOR 75 250 255 END END TEMPLATE "River and ponds" END
LAYER # Vector layer 5 - Canals / കനാലകള. GROUP "Canals" NAME "Canals / കനാലകള" TYPE LINE STATUS OFF DATA "cgpdata/canal.shp" METADATA "queryable" "true" "searchfield" "descr" "fields" "descr:Name,descr_mal:കനാലിെെ ോപര്,can_type:Type" END CLASS NAME "Canals" STYLE SYMBOL 'point' SIZE 2 COLOR 55 145 255 END END TEMPLATE "Canals" END
LAYER # Vector layer 6 - Sacred groves / കാവകള. GROUP "Sacred Groves"
106 NAME "Sacred Groves / കാവകള" TYPE POINT STATUS OFF DATA "cgpdata/s_grove.shp" METADATA "queryable" "true" "searchfield" "descr" "fields" "descr:Name,descr_mal:കാവിെെ േേര്" END CLASS NAME "Sacred Groves" STYLE SYMBOL "tent" SIZE 10 COLOR 0 140 0 END END TEMPLATE "Sacred groves" END
LAYER # Vector layer 7 - Water-flow Structures / ജലനിരഗമനം. GROUP "Water-flow Structures" NAME "Water-flow Structures / ജലനിരഗമനം" TYPE POINT STATUS OFF DATA "cgpdata/wrdpp.shp" METADATA "queryable" "true" "searchfield" "wr_prescri" "fields" "wr_prescri:Facility,descr:Place,descr_mal:വിവരണം" END LABELITEM "wr_prescri" # Item label field in attribute table. CLASS NAME "Water-flow Structures" STYLE SYMBOL "water_struct" SIZE 10 COLOR 0 195 255 END LABEL # Item label settings - font, position etc. TYPE TRUETYPE FONT "rachana" SIZE 10 POSITION AUTO BUFFER 5 COLOR 0 0 0 OUTLINECOLOR 245 245 231 ANTIALIAS FALSE PARTIALS FALSE END END TEMPLATE "Water-flow Structures" END
LAYER # Vector layer 8 - Watershed boundaries / നീരതടങളെട അോിരകള.
107 GROUP "Watershed Boundaries" NAME wshed TYPE LINE STATUS OFF DATA "cgpdata/wshed.shp" CLASS NAME "Watershed Boundaries" STYLE SYMBOL "border" SIZE 1 COLOR 30 195 235 END END END
LAYER # Vector layer 9 - General Facilities / െപാതസാപനങള. GROUP "General Facilities" NAME "General Facilities / െപാതസാപനങള" TYPE POINT STATUS OFF DATA "cgpdata/gen_fac.shp" METADATA "queryable" "true" "searchfield" "descr" "fields" "descr:Institution,descr_mal:സാപനം,gen_type:Type" END LABELITEM "descr" CLASS NAME "General Facilities" STYLE SYMBOL "star" SIZE 10 COLOR 000 165 255 END LABEL TYPE TRUETYPE FONT "rachana" SIZE 10 POSITION AUTO BUFFER 2 COLOR 0 0 0 OUTLINECOLOR 245 245 231 ANTIALIAS FALSE PARTIALS FALSE END TEMPLATE "General Facilities" END END
LAYER # Vector layer 10 - Medical Facilities / ആതരോേവനം. GROUP "Medical Facilities" NAME "Medical Facilities / ആതരോേവനം" TYPE POINT STATUS OFF DATA "cgpdata/med_fac.shp"
108 METADATA "queryable" "true" "searchfield" "descr" "fields" "descr:Facility,descr_mal:സാപനം,med_type:Type" END LABELITEM "descr" CLASS NAME "Medical Facilities" STYLE SYMBOL "cross" SIZE 10 COLOR 240 65 55 END LABEL TYPE TRUETYPE FONT "rachana" SIZE 10 POSITION AUTO BUFFER 5 COLOR 0 0 0 OUTLINECOLOR 245 245 231 ANTIALIAS FALSE PARTIALS FALSE END END TEMPLATE "Medical Facilities" END
LAYER # Vector layer 11 - Educational Facilities / വിദ്ാഭ്ാേം. GROUP "Educational Facilities" NAME "Educational Facilities / വിദ്ാഭ്ാേം" TYPE POINT STATUS OFF DATA "cgpdata/ed_fac.shp" METADATA "queryable" "true" "searchfield" "descr" "fields" "descr:Facility,descr_mal:സാപനം,ed_type:Type" END LABELITEM "descr" CLASS NAME "Educational Facilities" STYLE SYMBOL "diamond" SIZE 10 COLOR 245 210 45 END LABEL TYPE TRUETYPE FONT "rachana" SIZE 10 POSITION AUTO BUFFER 5 COLOR 0 0 0 OUTLINECOLOR 245 245 231 ANTIALIAS FALSE
109 PARTIALS FALSE END END TEMPLATE "Educational Facilities" END
LAYER # Vector layer 12 - Anganwadi Centres / അംഗനവാടികള. GROUP "Anganwadi Centres" NAME "Anganwadi Centres / അംഗനവാടികള" TYPE POINT STATUS OFF DATA "cgpdata/child_fac.shp" METADATA "queryable" "true" "searchfield" "code_no" "fields" "code_no:Centre No,descr:Centre Name,descr_mal:അംഗനവാടി ോകനം" END LABELITEM "descr" CLASS NAME "Anganwadi Centres" STYLE SYMBOL "hexagon" SIZE 10 COLOR 230 155 245 END LABEL TYPE TRUETYPE FONT "rachana" SIZE 10 POSITION AUTO BUFFER 5 COLOR 0 0 0 OUTLINECOLOR 245 245 231 ANTIALIAS FALSE PARTIALS FALSE END END TEMPLATE "Anganwadi Centres" END
LAYER # Vector layer 13 - Communication Facilities / വിവര വിനിമയം. GROUP "Communication Facilities" NAME "Communication Facilities / വിവര വിനിമയം" TYPE POINT STATUS OFF DATA "cgpdata/comm_fac.shp" METADATA "queryable" "true" "searchfield" "descr" "fields" "descr:Facility,descr_mal:ോപര്" END LABELITEM "descr" CLASS NAME "Communication Facilities" STYLE
110 SYMBOL "circle" SIZE 10 COLOR 140 110 175 END LABEL TYPE TRUETYPE FONT "rachana" SIZE 10 POSITION AUTO BUFFER 5 COLOR 0 0 0 OUTLINECOLOR 245 245 231 ANTIALIAS FALSE PARTIALS FALSE END END TEMPLATE "Communication Facilities" END
LAYER # Vector layer 14 - Energy Sector / ഊരജ രംഗം. GROUP "Energy" NAME "Energy Sector / ഊരജ രംഗം" TYPE POINT STATUS OFF DATA "cgpdata/energy.shp" METADATA "queryable" "true" "searchfield" "p_type" "fields" "p_type:Asset,descr:Load,descr_mal:ആസി" END LABELITEM "p_type" CLASS NAME "Energy" STYLE SYMBOL "square" SIZE 10 COLOR 255 255 0 END LABEL TYPE TRUETYPE FONT "rachana" SIZE 10 POSITION AUTO BUFFER 5 COLOR 0 0 0 OUTLINECOLOR 245 245 231 ANTIALIAS FALSE PARTIALS FALSE END END TEMPLATE "Energy" END
LAYER # Vector layer 15 - Roads / നിരതകള. GROUP "Roads"
111 NAME "Roads / നിരതകള" TYPE LINE STATUS OFF DATA "cgpdata/roads.shp" METADATA "queryable" "true" "searchfield" "descr" "fields" "descr:Name,descr_mal:ോപര്,type:Construction,subtype:Type" END CLASS NAME "Roads" STYLE SYMBOL 'point' SIZE 2 COLOR 0 0 0 END END TEMPLATE "Roads" END
LAYER # Vector layer 16 - Place Names / സലോേരകള. GROUP "Place Names" NAME "Place Names / സലോേരകള" TYPE POINT STATUS OFF DATA "cgpdata/place_name.shp" METADATA "queryable" "true" "searchfield" "descr" "fields" "descr:Place Name,descr_mal:സലോേര്" END LABELITEM "descr" CLASS NAME "Place Names" STYLE COLOR 255 255 255 END LABEL TYPE TRUETYPE FONT "rachana" SIZE 10 POSITION AUTO BUFFER 5 COLOR 0 0 0 OUTLINECOLOR 245 245 231 ANTIALIAS FALSE PARTIALS FALSE END END TEMPLATE "Place Names" END
END #MAP END.. വിഭവ ഭപടതിെെ വിവരണം ോീരന...
112 File: /var/www/ka-map-1.0-20070205/htdocs/cgpdata/symbols.sym
#Symbology used in map. വിഭവ ഭപടതില ഉപോയാഗിചിരികന അടയാളങള.
#1 SYMBOL NAME "border" TYPE VECTOR POINTS 0 0 1 0 1 0.8 0 0.8 0 0 END STYLE 10 6 1 6 END FILLED TRUE END
#2 SYMBOL NAME "star" TYPE VECTOR POINTS 0 0.375 0.35 0.375 0.5 0 0.65 0.375 1 0.375 0.75 0.625 0.875 1 0.5 0.75 0.125 1 0.25 0.625 0 0.375 END FILLED TRUE STYLE 1 20 1 20 END END
#3 SYMBOL NAME "cross" TYPE VECTOR POINTS 0 0.4 0.4 0.4 0.4 0 0.6 0 0.6 0.4 1 0.4 1 0.6
113 0.6 0.6 0.6 1 0.4 1 0.4 0.6 0 0.6 0 0.4 END FILLED TRUE END
#4 SYMBOL NAME 'point' TYPE ELLIPSE POINTS 1 1 END FILLED TRUE END
#5 SYMBOL NAME "diamond" TYPE VECTOR POINTS 0 0.5 0.5 0 1 0.5 0.5 1 0 0.5 END FILLED TRUE END
#6 SYMBOL NAME "water_struct" TYPE VECTOR POINTS 0 1 0 0.5 0.5 0 1 0.5 1 1 0 1 END FILLED TRUE END
#7 SYMBOL NAME "tent" TYPE VECTOR POINTS 0 4 2 0 4 4
114 3 4 2 2 1 4 0 4 END FILLED TRUE END
#8 SYMBOL NAME "hexagon" TYPE VECTOR POINTS 0 0.25 0.5 0 1 0.25 1 0.75 0.5 1 0 0.75 0 0.25 END FILLED TRUE END
#9 SYMBOL NAME "circle" TYPE ELLIPSE POINTS 1 1 END STYLE 1 10 1 10 END FILLED TRUE END
#10 SYMBOL NAME "square" TYPE VECTOR POINTS 0 0 0 1 1 1 1 0 0 0 END FILLED TRUE STYLE 1 20 1 20 END END
115 File: /var/www/ka-map-1.0-20070205/htdocs/cgpdata/fonts.list
#List of fonts used.. അകരരപങള rachana Rachana_g03.ttf meera Meera_g03.ttf symbols symbols.ttf
116 Major files related to project – on Debian GNU/Linux (Etch) directory tree / +bin +boot +dev +etc+ -> hosts, resolv.conf | | | +apt -> sources.list | +apache2+ | | | | | +sites-available -> default | +init.d -> apache2 | +network -> interfaces +home+ | | | +user+ | | | | | +data+ | | | | | +GRASSDATA+ | +postgres | | +lost+found +tempxy +lib +cheruvannur +lost+found +cgputm +media+ | | | +cdrom +mnt +proc +root +sbin +sys +tmp | +usr+ | | | +share+ | | +var+ +phppgadmin (A symbolic link need to be made in /var/www/ to this directory.) | +lib+ | | | +php5+ | | | | | + 20060613+lfs+ -> gd.so, php_mapscript.so | | | +postgresql+ | | +www+ +8.1+ | | | +main | +ka-map-1.0-20070205+ | | +phppgadmin +htdocs+ -> cgp.map, index.html | | | +cgpdata+ -> fonts.list, symbols.sym | | | +kacache | +include+ -> config.php
117 Hardware Specification of system used for the project
CPU : Intel(R) Pentium(R) 4 CPU 2.40GHz (32 bits)
System Memory : 1GB DDR Synchronous 333 MHz
Motherboard : Intel(R) D845GVSR
Display : Integrated Graphics - Intel(R) 82845G/GL[Brookdale-G]/GE Chipset.
USB Controller : Integrated - Intel(R) 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller – 3 nos.
Ethernet interface : Intel(R) 82801DB PRO/100 VE (LOM) Ethernet Controller
Hard disk : Seagate(R) ST380215A ATA Disk 80GB
Hard disk partition volumes under GNU/Linux: Access Path Size File system / 14 GB ext3 file system
DVD-RAM writer : SONY(R) DVD RW DRU-840A
CD-ROM Drive : SAMSUNG(R) CD-ROM SH-152A
Monitor : PHILIPS(R) 107B 17”
Peripherals : Logitech(R) Keyboard and optical mouse.
(Details of CPU as obtained by the command lshw as root user.)
118