With the following slides and interactive material you will be able to take part in the journey to discover Spatial Data Infrastructures (SDI) its components and benefits through the observation of multiple examples and exercises.
You can navigate through the course by pressing the navigation arrows at the bottom of each slide or using your arrow keys on your keyboard. You can move horizontally (← →) for viewing each theme and vertically (↑↓) to view extra recommended information
Let’s start with a demo…
After a click on the first search result
Now there are multiple possibilities:
On the website of the data owner I see a link to the own geo-portal.
There I see the same area (brown with yellow), but this map also shows other related layers from the same data producer.
Combine it with other maps (other themes) like historical maps
Abstract, contact information (again with a link to the website / geo-portal of the data producer)…
Questions:
Answers:
Different protocols work together
Browser
HTTP / HTTPS
TCP/I¨P
IPv4
PPP/…
Cable
Definition of web service (3WC):
“A software system designed to support (interoperable) machine-to-machine interaction over a network.”
Web services allow us to create client/server applications
Websites are for humans ↔ Web Services are for software
No GUI (Graphical User Interface) – only usable within applications
Web services advantages:
Provide interoperability between various software applications
Accessible via each network supporting open standards
Allow software and services from different organisations and locations to be combined easily to provide an integrated service
Are self-describing
Web Services main disadvantage:
Overhead: transmitting data (usually in XML) is not as efficient as using binary code. What you win in portability, you lose in efficiency.
Remote procedure calls (RPC)
A Client sends a request message to a known remote server to execute a specified procedure with supplied parameters
The remote server sends a response to the client
Service-oriented architecture (SOA):
The basic unit of communication is a XML message
"message-oriented" services
XML: eXtensible Markup Language
<?xml version="1.0" encoding="UTF-8" ?>
<painting>
<img src="madonna.jpg" alt="Madonna" />
<caption>This is Raphael's Foligno Madonna
<date>1511</date>
<date>1512</date>
</caption>
</painting>
Founded in 1994
Solve the issue of spatial data sharing and interoperability
Sets the standards that allow geographic information systems to interoperate
470+ members and growing
34 “core” standards
15 extensions/profiles
Note:
Source data from which the image is generated need not to be an image. It can be a Shapefile, PostGIS database, Oracle Spatial,…
Opengeo.org
WMS Server can do one of 3 things (WMS operations)
Provides the following information:
Image formats it can serve (jpeg, png, gif…)
List of the map layers
List of layers supporting the optional GetFeatureInfo interface
List of available spatial reference systems
List of exception formats for return of exceptions
(optional) SLD styles
(optional) Vendor specific capabilities (or properties)
Example
Response is a XML file
http://demo.opengeo.org/geoserver/wms?
The 'root' URL of the service.
SERVICE=WMS
Request for a WMS service
REQUEST=GetMap
Request for a map image
LAYERS=topp:states
Which layer? Multiple layers possible with comma separated list
SRS=EPSG:4326
The projection we are requesting using the EPSG code
BBOX==-124.731,24.956,-66.97,49.372
Bounding box coordinate
Format: “MinX, MinY, MaxX, MaxY”
WIDTH=600
Width of image we want
HEIGHT=255
Height of image we want
FORMAT=image/pgn
Image type (possibilities: png, jpeg, gif & tiff)
STYLES=
In case the WMS service offers multiple styling. Blanc → default style
To be found in the GetCapabilities
TRANSPARENT=FALSE
Will image be transparent in areas of no data
Image
Error
<ServiceExceptionReport version="1.1.1">
<ServiceException code="">
WIDTH and HEIGHT incorrectly specified
</ServiceException>
</ServiceExceptionReport>
Example:
http://demo.opengeo.org/geoserver/wms?SERVICE=WMS&REQUEST=getfeatureinfo&LAYERS=topp:states&BBOX=-124.731,24.956,-66.97,49.372&FORMAT=image/png&WIDTH=600&HEIGHT=255&X=100&Y=100&query_layers=topp:states http://www.ruimtemonitor.be/geoserver/wms?service=wms&request=getfeatureinfo&LAYERS=gemeenten_2003_rb&FORMAT=image/png&BBOX=21000,150000,117000,246000&WIDTH=256&HEIGHT=256&X=200&Y=200&query_layers=gemeenten_2003_rbResponse = XML or text file (dependent on your WMS server software)
<?xml version="1.0" encoding="UTF-8"?>
<FeatureInfoResponse>
<FIELDS FEMALES="226581" MALES="227007" POP1999="482025" STATE_NAME="Wyoming" _ID_="6" _SHAPE_="[Geometry]" _LAYERID_="0"/>
</FeatureInfoResponse>
→ response can be formatted by the (web) application
Provides map data (GML) to a (web) client
The client chooses style & presentational details
Geospatial features
Optional: Transactional Web Feature Service (WFS-T) enables the creation, deletion, and updating of features
Current version 2.0
= ISO 19142
Opengeo.org
A catalogue server publishes collections of descriptive information (metadata) about geospatial data
Defines interface to search for metadata (so you could ‘discover’ geospatial data)
Transaction: insert, update & delete of metadata
Harvest (optional) - create/update metadata by asking the server to 'pull' metadata from a specified target
Module “Metadata and catalogue services”
getCapabilities
Metadata about the service itself (indicating abilities, contact information…)
getRecords
Does a search
http://metadata.geopunt.be/zoekdienst/srv/dut/csw?service=CSW&version=2.0.2&request=GetRecords&CONSTRAINTLANGUAGE=CQL_TEXT&resultType=results
getRecordById
Returns the metadata (default representation) of a specific record using their identifier
http://metadata.geopunt.be/zoekdienst/srv/dut/csw?service=CSW&version=2.0.2&request=GetRecordById&id=DE022DEF-20BF-4016-82A1-57BCC917AF4E
All return a XML document
Standard way for data to be passed from one geographic application to another
Is the XML grammar defined by the Open Geospatial Consortium (OGC) to express geographical features.
Response of WFS requests is GML
Filename extension: .gml
<gml:MultiLineString srsName="http://www.opengis.net/gml/srs/epsg.xml#27354">
<gml:lineStringMember>
<gml:LineString>
<gml:coordinates decimal="." cs="," ts=" "> 494475.71056415,5433016.8189323
494982.70115662,5 435041.95096618 </gml:coordinates>
</gml:LineString>
</gml:lineStringMember>
</gml:MultiLineString>
Module “Basic concepts of XML and GML”
Desktop clients:
QGIS
ESRI ArcGIS for Desktop
uDIG
Kosmo
MapWindow
Web mapping clients comparison:
http://geotux.tuxfamily.org/index.php/en/geo-blogs/item/291-comparacion-clientes-web-
Servers:
|
|
Visit the following tools and software sites:
OpenGeo Suite