pusing balik... a recap...

Okei... so far we have covered a bit on GIS software and database components.

Basically, I feel a GIS Software should cover any computing aspect of maps, plans, geography, images, analysis, editing, compilation, visualisation and geoprocessing. With the advent of GIS software in the last 20 years we can now work faster, precise and more efficient... as compared to work done manually for centuries. Its a slow revolution, not easy to accomplish... many countries are slowly embarking on digital evolution.. its a process that will take months... if not years to reach a proficient level. Its not like any other software... in GIS u need industry experience too. Some are still arguing the benefits of GIS... all kinds of technology issues to solve. No doubt GIS software has come a long way and many are beginning to see the benefits... its not easy though.

A database component of GIS is also called geodatabase and its the main storage area for spatial data. Its actually referenced to a location on the earth's surface. The schema design (data model) of a geodatabase should actually cover every aspect of the geographic feature.. be it points or lines. I would say that its the evolution of data storage that changes the GIS software features... how GIS data is stored has a direct effect on GIS software functions and performance. Computing power changes and hardware improves, of course... but storage factors now govern more important aspects of GIS implementations. Data models, Table Relationships, Data Type, Field Constraints are becoming more important these days... hopefully moving at the same pace as other non-GIS UML database implementations.