[QGIS-Developer] QGIS server and metadata

Tom Kralidis tomkralidis at gmail.com
Thu Oct 31 09:35:17 PDT 2019


For Python it's entirely feasible to put pycsw atop the metadata, and
was discussed as
as approach as part of the QGIS metadata strategy / planning.

On Thu, Oct 31, 2019 at 11:47 AM Paolo Cavallini <cavallini at faunalia.it> wrote:
>
> Thanks Ale for the explanation. Indeed, a suboptimal situation.
> Perhaps worth an ad hoc crowdfunding.
> Cheers.
>
> Il 31/10/19 16:40, Alessandro Pasotti ha scritto:
> >
> > On Thu, Oct 31, 2019 at 4:28 PM Paolo Cavallini <cavallini at faunalia.it
> > <mailto:cavallini at faunalia.it>> wrote:
> >
> >     Hi all,
> >     apparently our server does not expose the metadata stored in the project
> >     and layer properties:
> >     * is this true?
> >
> >
> > There is a metadata section in the server configuration (Service
> > Capabilities) of the project properties, modeled on WMS/WFS metadata,
> > they are exposed. The sad thing is that when the new metadata framework
> > was developed it was not connected with the existing server metadata, so
> > we currently have two separate APIs for metadata, the old very limited
> > one for the server and the new one. On the other hand, the old existing
> > API is exactly what was required by WMS/WFS.
> >
> >
> >     * is there any reason for this, besides the usual lack of resources to
> >     implement it?
> >
> >
> > Not that I'm aware of.
> >
> >
> >     * anyone has estimates or plans to implement it?
> >
> >
> > Not that I'm aware of.
> >
> > I though about it for WFS3 but I couldn't find the time/resources to do
> > anything (mainly because of missing API in the server), for now I've
> > just implemented what was available in the server's WFS code.
> >
> >
> >
> >     Moreover, I wonder how users are managing their metadata from QGIS, now
> >     that several plugins that helped compiling them are not available for
> >     current versions. Any feedback will be appreciated.
> >     Cheers.
> >     --
> >     Paolo Cavallini - www.faunalia.eu <http://www.faunalia.eu>
> >     QGIS.ORG <http://QGIS.ORG> Chair:
> >     http://planet.qgis.org/planet/user/28/tag/qgis%20board/
> >     _______________________________________________
> >     QGIS-Developer mailing list
> >     QGIS-Developer at lists.osgeo.org <mailto:QGIS-Developer at lists.osgeo.org>
> >     List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >     Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
> >
> >
> > --
> > Alessandro Pasotti
> > w3:   www.itopen.it <http://www.itopen.it>
> >
> > _______________________________________________
> > QGIS-Developer mailing list
> > QGIS-Developer at lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS.ORG Chair:
> http://planet.qgis.org/planet/user/28/tag/qgis%20board/
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


More information about the QGIS-Developer mailing list