[QGIS-Developer] QGIS server and metadata

Paolo Cavallini cavallini at faunalia.it
Mon Nov 4 01:43:20 PST 2019


Thanks a lot Paul.
I believe closing the gap, and have a complete workflow, is important to
QGIS, so comments will be greatly appreciated.
All the best.

Il 04/11/19 10:06, Paul van Genuchten ha scritto:
> Hi, thank you for interesting QGIS server and metadata discussion, I
> have a couple of thoughts to add:
> - Related to FGDC support, since QGIS manages metadata in a local model,
> the capability is requested to import from and export to FGDC metadata,
> and potentially extend the local model to support important fields of
> FGDC. In our bridge product we foresee capabilities to import/export to
> iso19139 metadata, but would be interesting to also see FGDC support
> (see https://github.com/GeoCat/qgis-bridge-plugin/issues/6)
> - A getcapabilities typically exposes metadata in 2 ways, a limited set
> of properties embedded in service and layer metadata in getcapabilities
> (contact, title, abstract, keywords) and for each layer a link to an
> external document having detailed metadata. For the first set it makes
> sense to use metadata stored in the QGIS project directly. For the
> second set this will be a bit harder, since the metadata stored in the
> project is not necessarily exposed externally as a document. QGIS server
> would need a catalogue capability to facilitate this use case. An
> alternative could be to ‘publish’ records in an external catalogue
> instance (pycsw/geonetwork), and store locally a reference to where the
> metadata for a layer is published.  The bridge plugin already supports
> this use case as it publishes local records to an external catalog. A
> thing to consider is that metadata records exposed to the web typically
> require a common metadata model such as iso19115/FGDC, so the catalog
> component needs to have a capability to expose records in those models
> (or a transformation should be done while publishing the record).
> I would love to hear how people envision these workflows and how they
> see the bridge plugin would be able to contribute.
> 
> _______________________________________________
> 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/


More information about the QGIS-Developer mailing list