“GeoNode is built with QGIS Server or GeoServer, both of which provide OGC Catalogue Service for the Web (CSW). External clients are able to interact with GeoNode via these OGC services”
GeoNode uses CSW as a cataloguing mechanism to query and present geospatial metadata. Other tools can then interact with GeoNode instances using the CSW standard. In QGIS one such tool is Metasearch. MetaSearch is a QGIS plugin to interact with metadata catalogue services, supporting the OGC Catalogue Service for the Web (CSW) standard. This plugin provides an easy and intuitive approach and user-friendly interface to searching metadata catalogues within QGIS.
In this module, we will look at how GeoNode with GeoServer backend interacts with external application to view the data and manipulate it.
Goal: To explore GeoNode data in QGIS using various tools available in QGIS
NB: WFS and WCS are sometimes slow because they depend on the size of the image being accessed from GeoNode.
Local GeoNode
Check your results
After importing the layer in QGIS using WFS you should be able to see the attributes of the layer and be able to toggle edit so
Name | Expectation |
---|---|
OGC connector |
MetaSearch |
Site URL |
http://geonode.com/csw |
Layer |
Name of layer available in GeoNode |
OGC services |
WFS/ WMS/ WCS |
QGIS tools |
Field Calculator, Digitising |
GeoNode is based on CSW (Catalogue Service for the Web) specification, which defines common interfaces to discover, browse, and query metadata about data, services, and other potential resources.
GeoNode uses pycsw as the default CSW server. Other CSW server implementations are:
These backends can be configured as an alternative to the CSW backend in GeoNode.
When using a tool like MetaSearch tools with login it simulates the permissions for all layers that are visible to you in GeoNode. When accessing the CSW service without login credentials you see public layers (layer with no access restrictions) in GeoNode.
What kind of OGC service do you use if you need to edit the raster:
What is produced when you click service info in MetaSearch and what details does it contain:
Why is it desirable to put your username,password when setting up connection endpoint in MetaSearch: