This document provides an overview of databases and WebGIS. It discusses different types of databases including MySQL, PostgreSQL, and spatially-enabled databases. It compares MySQL and PostgreSQL, covering when each would be used. It also covers database data conversions between formats like JSON, GeoJSON, CSV, SHP, and KML/KMZ. For WebGIS, it defines it as a distributed information system comprising a server and client, where the server is a GIS server and client a web browser. It discusses purposes, technologies, languages/frameworks like Python, JavaScript, GeoDjango, and case studies for building WebGIS systems.
In this document
Powered by AI
Overview of databases and WebGIS concepts, outlining types of databases, Spatial databases, and the importance of GIS.
Insights into databases and DBMS, types of databases including NoSQL, spatial databases like PostgreSQL with PostGIS, and data conversions.
Definition and purpose of WebGIS, highlighting visualization, spatial data management, and associated technologies used in WebGIS.
Focus on programming languages and frameworks used in GIS development, including PostgreSQL, JavaScript, and various web technologies.
Essential skills and experience areas for GIS development, including programming, database development, and GIS system architecture.
Application of GIS in a case study (BizTrac), concluding remarks on the importance of WebGIS databases in spatial analysis.
Outline • Databases Introduction Types ofdbase Spatial dbase Comparison: MySQL vs PostgreSQL Dbase data conversions • WebGIS Introduction Purpose Technologies GIS Languages & Frameworks GIS systems development Experience skills GIS system architecture Case study
3.
DATABASE • What isa dbase? A database is a collection of information organized to provide efficient retrieval. The collected information could be in any number of formats (electronic, printed, graphic, audio, statistical, combinations). • What is a DBMS? A database management system (DBMS) is a collection of programs that enables you to store, modify, and extract information from a database.
4.
• Different typesof dbases available: • NoSQL • Cassandra • MySQL • MongoDB – supports 2D • CouchDB - document based database system that can be spatially enabled by a plugin called Geocouch • CartoDB is a cloud based geospatial database on top of PostgreSQL with PostGIS • PostgreSQL -postgis
5.
• What isa spatially-enabled database? or geodatabase is a database that is optimized to store and query data that represents objects defined in a geometric space. PostgreSQL DBMS (database management system) uses the spatial extension PostGIS to implement the standardized datatype geometry and corresponding functions.
6.
COMPARISON MySQL • When ToUse Distributed operations High security Web-sites and web- applications Custom solutions • When Not To Use SQL compliance Concurrency Lack of features PostgreSQL • When To Use Data integrity. Complex, custom procedures Integration Complex designs: • When Not To Use Speed Simple set ups Replication
WEBGIS: INTRODUCTION • Whatis WebGIS? A type of distributed information system, comprising at least a server and a client, where the server is a GIS server and the client is a web browser, desktop application, or mobile application. • WebMap? Online map delivered by a GIS
9.
PURPOSE • The WebGIS is one of the Geoinformation Technology fields. • The basic tasks of Web GIS are: Visualization - spatial representation of the existing information Simplification of work with the spatial information in a web; Managements and publication of spatial data, search and other services based on a site of objects (LBS - location based services)
Case study: BizTrac •Access to GIS data and functionality • Can add value to web sites • Examples: – Service Location – Service Delivery – Data Access – Data Commerce
20.
Conclusion Creating ofcentralized WebGIS database will lead to success in every field of work related to spatial analysis. After completing of the module WebGIS you can build your own map in Internet with different attribute data. It means that you will be architecture but not client (user) of this product.