ogc services

The importance of being dynamic (for a WFS)

These are the results of a “personal” functionality comparison on some GIS desktop:

– web feature service:  Sardinia Region WFS (2000 objects limited)

– layer used: usoSuolo2008

Udig 1.2: AUTOMATIC load of the current map extent objects; AUTOMATIC new request during the navigation (zooming, pan, ecc.); preservation of the thematization; AUTOMATIC load of the web service intire list layer;

gvSIG 1.9: MANUAL load of the current map extent objects; MANUAL new request during the navigation (zooming, pan, ecc.);  NO preservation of the thematization; AUTOMATIC load of the web service intire list layer;

quantum GIS 1.3: NO load of current map extent objects; AUTOMATIC load of the web service intire list layer;

 

ESRI arcGIS 9.3.1: NO load of current map extent objects; NO loading intire list layer of the web service.

 

As you see with these requirements and these Web Feature Service charateristics the best GIS desktop that provide “dynamic WFS request funcionality” is Udig 1.2  followed by gvSIG 1.9, Qgis 1.3 and arcGIS 9.3.1.

Web Map Service

A Web Map Service (WMS) allows to show over the internet geographic contents stored in a spatial database or file system by using a HTTP protocol. Both a web-based application and a desktop GIS application can make a request (in the form of URL) to the map service which answers with georeferenced map images (usually PNG or JPEG). Some WMS manage the transparency and give detailed information of the showed geographic contents.

The prevalent specification for this standard is published by OGC (Open Geospatial Consortium) and referenced in INSPIRE Directive too. gvSIG and QGIS are excellent WMS client, while mapserver and geoserver are good OGC WMS server. The Sardinia Region exposes a WMS for raster images and one for vectors, with a good user guide (at the moment available in Italian only).