[GeoNode-devel] [GeoNode-users] Pycsw vs Geonetwork

Ariel Nunez ingenieroariel at gmail.com
Thu Feb 18 14:00:30 PST 2016

The main issue was that geonetwork has it's own db and with pycsw we were
able to set it up in read only mode from the geonetwork db.

GeoNetwork is not designed to be a library but an application, pycsw on the
other hand acts as a library within GeoNode and therefore is much smaller,
easier to maintain and to reason about.

GeoNetwork on it's own is a very good piece of software and with it's
latest releases is more of an alternative to GeoNode itself.

On Thu, Feb 18, 2016 at 4:43 PM, Allan Oware <allanoware at gmail.com> wrote:

> Hi,
> Am not sure whether this has been mentioned on the list before, starting
> Geonode 2.0, why was Pycsw preferred as the default catalogue server
> instead of Geonetwork opensource ? I understand one can switch to an
> alternate csw backend after installing geonode, but were there issues with
> geonetwork that prompted the switch to pycsw ?
> Regards.
> --
> Allan Oware
> _______________________________________________
> geonode-users mailing list
> geonode-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geonode-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20160218/27cd38b0/attachment.html>

More information about the geonode-devel mailing list