[GeoNode-devel] [GeoNode-users] GeoNode - PyCSW integration issues
tomkralidis at gmail.com
Thu Jul 27 04:39:26 PDT 2017
Hi Alessio: thanks for the info. Comments interleaved:
On Wed, 26 Jul 2017, Alessio Fabiani wrote:
> Date: Wed, 26 Jul 2017 11:10:36 +0200
> From: Alessio Fabiani <alessio.fabiani at geo-solutions.it>
> To: geonode-devel <geonode-devel at lists.osgeo.org>,
> geonode-users <geonode-users at lists.osgeo.org>
> Subject: [GeoNode-users] GeoNode - PyCSW integration issues
> Dear all,
> I want to highlight some important issues about the current integration
> between GeoNode and PyCSW.
> Other than a non-trivial security issue (basically the CSW exposes metadata
> for all Layers no matter if they are accessible or not by the user),
This is in my queue to fix (half way there).
> more, I would say, big issue is that currently is not possible to recognize
> the Layer "real name" from the metadata documents.
> Let me provide an example. Here below a snippet of a DublinCore XML
> produced by PyCSW
> <dct:references scheme="WWW:DOWNLOAD-1.0-http--download">
> <dct:references scheme="OGC:WMS">
> <dct:references scheme="OGC:WFS">
> (full XML here https://pastebin.com/Wu0vm79B)
> Seems to be good right? *Wrong!* There some important things missing here:
> 1. It is not possible to recognize the layer name at all; The element
> "title" is mapped to the resource title, meaning that whenever I change it
> on the metadata into a human readable fashion, I lose the layer name forever
You should use ISO instead? See below comment.
> 2. Layer qualified name is missing; if the name had a namespace, like on
> GeoServer, it is not possible to know which is at all
> 3. WMS and WFS links cannot be used at all, since the layer name cannot be
> retrieved anywhere
Anyone who wants to do tight coupling to OWS resources via CSW search
workflows needs to use the ISO output, which provides the bare URL
as well as the given Layer/FeatureType/Coverage.
Otherwise, the Dublin Core approach allows for discovery followed by
the client doing a full round trip (GetCapabilities, etc.) to be able
to find the layer again. This is not optimal, which is exactly why
the CSW ISO Application Profile was created to help tight couplling
If there are issues in the ISO output then let's tackle those?
> Following the notes written by Stephen Richard here
> the proposal here would be to add more references
Note that we promoted this into a canonical lookup at:
> in order to let CSW being able to send correct links to the clients.
> If there are no objections, I will create a PR accordingly related to the
> following ISSUE
> Please comment on this.
> Alessio Fabiani
> GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
> for more information.
> Ing. Alessio Fabiani
> Founder/Technical Lead
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054 Massarosa (LU)
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 331 6233686
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
More information about the geonode-devel