Skip to content
François Prunayre edited this page Nov 21, 2013 · 15 revisions

On the last couple of years, open government and the use of open data has increased exponentially. There are new platforms highly focused on open data like CKAN. In that movement people focus on lean standards (DCAT). To solve the geometry usecase they looked for similar lean standards and embraced geojson.

The ease of use of these protocols (and availability of free data) has gathered a large group of users willing to use and develop around this environment. This process has popularized multiple applications based on open data.

GeoNetwork could profit from these developments and could implement some of their spin-offs (leafletjs/D3js). But also we should not abandon our xml users (OGC/Inspire). The challenge is to be lean where possible, and complient in other parts.

For example EU recently released a DCAT profile for open government data. It would be good to have it available as a schema plugin, but might be integrated in other parts of geonetwork also (harvester, csw-format)

In the open data movement some new catalogues are set up (for example in git). Some new harvesters could be made to retrieve metadata from those kind of repositories.

Another development is the increased interest for linked data (also within inspire).

Also there are currently limited ways to link to the actual data. One could imagine a component that uses a combination of iso19139 and feature-catalog metadata or WFS XSD to create RDF from WFS data.

DCAT support in GeoNetwork

GeoNetwork provides some features related to the linked data domain:

See http://trac.osgeo.org/geonetwork/wiki/proposals/DCATandRDFServices

Geonetwork currently does not provide SPARQL query support but could be harvested by tools like Virtuoso.

DCAT support improvements

GeoNetwork nodes publishing opendata

GeoNetwork nodes describing opendata resources:

Clone this wiki locally