1. Kartografik Bilgi Sistemleri - JDF470
Prof. Dr. Kazimierz Becek
Arş. Gör. Can Atalay

2. Cartography - Definition
The art, science and technology of making maps, together with their study as scientific documents and work of arts.
International Cartographic Association (ICA)

3. Definition of map
There are many definitions of a map. Here are some samples.
Maps are words encoded in the form of points, lines, polygons & annotations.
(Cartography & Map Design: Making Better Maps. URISA Workshop, Nashville, Tennessee, 1995)
 A graphic representation on a plane surface of the earth’s surface or part of it showing its geographical features.
(Computer Processing of Remotely Sensed Images, Paul M. Mather)
A map is a collection of spatially related data presented to user’s visual perception system for a purpose of extracting information.
K. Becek

4. GeoServer
GeoServer is an open source server for sharing geospatial data.
Designed for interoperability, it publishes data from any major spatial data source using open standards.

5. GeoServer Service Capabilities
WFS & (WFS-T) - Web Feature Service & Web Feature Transaction Service
WMS & WMS-C - Web Map Service and Tile Map Service
WCS - Web Coverage Service
WMTS - Web Map Tile Service

6. XML
Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.

7. GML - The Geography Markup Language
Is the XML grammar defined by the Open Geospatial Consortium (OGC) to express geographical features. GML serves as a modelling language for geographic systems as well as an open interchange format for geographic transactions on the Internet.

8. Web Map Service
The OpenGIS® WMS is a simple HTTP interface for requesting map images from one or more distributed geospatial databases. A WMS request defines the geographic layer(s) and area of interest to be processed. The response to the request is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a browser application.

9. Web Map Service (WMS)
is a standard protocol for serving over the Internet georeferenced map images which a map server generates using data from a GIS database
WMS specifies some request types such as:
GetCapabilities - returns parameters about map image format and the available layers, map bounding box, coordinate reference systems, and other.
GetMap - returns a map image. Parameters include: width and height of the map, coordinate reference system, image format and other.
There are also some optional request types that WMS may support.

10. Web Feature Service (WFS) and Web Feature Service –Transaction (WFS-T)
The WFS defines interfaces for data manipulation including querying and retrieval of features. The user generates the request and posts it to a WFS using HTTP. The WFS then executes the request.
A transactional Web Feature Service (WFS-T) allows creation, deletion, and updating of features.

11. Web Coverage Service
WCS is used to openly serve raster data using the OGC WCS specification. For example, you can use WCS to serve the pixel values contained in a multiband raster image. You can add WCS services as raster datasets in ArcMap and to add them as map layers and to use them as input to modelling and geoprocessing operations.

12. Web Coverage Service
WCS provides access to coverage data in forms that are useful for client-side rendering, as input into scientific models, and for other clients. It provides data inc. their detailed descriptions, which may be interpreted, extrapolated, etc., and not just portrayed.
WCS returns coverages representing space/time-varying phenomena that relate a spatio-temporal domain to a range of properties. As such, WCS focuses on coverages as a specialized class of features and, correspondingly, defines streamlined functionality.
WCS uses the coverage model of the OGC GML Application Schema for Coverages. Thus, WCS supports all coverage types supported by said Application Schema; it is not constrained to quadrilateral grid coverages like previous WCS versions.

13. SLD
 In cartography, a Styled Layer Descriptor is an XML schema for describing the appearance of map layers. It is capable of describing the rendering of vector and raster data. A typical use of SLDs is to instruct a Web Map Service (WMS) how to render a specific layer.

14. WPS - Web Processing Service
The WPS standard defines how a client can request the execution of a process, and how the output from the process is handled. It defines an interface that facilitates the publishing of geospatial processes and clients’ discovery of and binding to those processes.

15. CSW - Catalog Service for the Web
is a standard for exposing a catalogue of geospatial records in XML on the Internet. The catalogue is made up of records that describe geospatial data (e.g. KML), geospatial services (e.g. WMS), and related resources. Other words: this is a way to extract metadata out of a server. For example:

16. WMTS
A Web Map Tile Service is a standard protocol for serving pre-rendered georeferenced map tiles over the Internet.

17. Adding record to a Table
Records may be added to tables in three ways:
Manually through the table GUI;
Using a SQL INSERT query to add a single record, and
Using an INSERT query to add multiple records in bulk.
INSERT INTO Artists ( Artist_Name, Year_Begin, Year_End ) SELECT "The Beatles" AS Expr1, 1957 AS Expr2, 1970 AS Expr3;

18. Updating Existing Records
Can be done both manually through the GUI and programmatically with SQL.
Both should work:
- UPDATE Labels SET Labels.Label_Name = [Labels]![Label_Name] & " Records"; and
- UPDATE Labels SET Label_Name = Label_Name & " Records";

19. Deleting Records
Delete queries are used to delete entire rows meeting certain criteria.
It could be done manually through GUI or
Using the DELETE queery:
DELETE * FROM Labels
WHERE Label_Name="Track Records";

20. Database Design Concepts
When building a relational database, it is important that you spend enough time to design it first.
A poorly designed database can cause a number problems, inc. + Loss of data integrity; + Inability to support all type of queries; + Slow performance

21. Data integrity
Data integrity is the maintenance of, and the assurance of the accuracy and consistency of, data over its entire life-cycle, and is a critical aspect to the design, implementation and usage of any system which stores, processes, or retrieves data.

22. An example

23. A well-designed database
Seeks to minimize redundancy of data;
Represents a single subject;
Has a primary key;
Does not contain multi-part fields (e.g., “15, 67100")
Does not contain multi-valued fields (e.g., an Author field shouldn't hold values of the form "Jones, Martin, Williams");
Does not contain unnecessary duplicate fields (e.g., avoid using Author1, Author2, Author3)
Does not contain ‘calculated’ fields (e.g., don't create a wage field in a table that has PayRate and HrsWorked fields)

24. Database Normalization
First normal form (1NF) describes a database whose tables represent distinct entities, and have a primary key.
Second normal form (2NF) describes a database that is in 1NF and also has had duplicative data eliminated.
Third normal form (3NF) describes a database that is in 2NF and also avoids having columns that derive their values from columns other
than the primary key.

25. An example

26. An example con’t

27. Example – con’t

28. Example – con’t

29. Flavours & Orders

31. And a corresponding SQL statement
SELECT Orders.OrderID, Customers.NameLast, Customers.NameFirst, Flavors.Name, OrderItems.Qty, Customers.DeliveryAdd,
Orders.DeliveryDate FROM ((Orders INNER JOIN OrderItems ON Orders.OrderID = OrderItems.OrderID) INNER JOIN Customers ON Orders.CustID =
Customers.CustID) INNER JOIN Flavors ON OrderItems.FlavorID = Flavors.FlavorID WHERE (((Orders.DeliveryDate) < Now()+2)) ORDER BY
Orders.OrderID;

32. The purpose of the example was:
1. To illustrate that multi-table designs are often preferable to a "one-big-spreadsheet" approach.
2. To emphasize the importance of SQL in pulling together data spread across multiple tables to perform valuable database queries.

33. Homework: Designing a Relational Database
You work for a UFO investigation organization that has collected a lot of information related to sightings and you've been tasked with designing a database that will be used as the back end for a website. The information to be stored in the database includes the following:
sighting date/time
object shape (saucer, cigar, etc.)
sighting coordinates (latitude, longitude)
witness name, phone # and address
textual descriptions of the sighting
In addition to this basic information, the organization has many digital files that must be made available through the website:
photos
videos
drawings
audio (interviews with witnesses)