Skip to content

Instantly share code, notes, and snippets.

@tomkralidis

tomkralidis/MetaSearch.textile Secret

Last active August 23, 2016 21:38
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save tomkralidis/7637988681e6f8fc683c3ff9f3d9c887 to your computer and use it in GitHub Desktop.
Save tomkralidis/7637988681e6f8fc683c3ff9f3d9c887 to your computer and use it in GitHub Desktop.
Download ZIP
QGIS MetaSearch wiki pages
Raw
MetaSearch.textile

Welcome to the MetaSearch wiki!

from @timlinux, irc://irc.freenode.net/qgis, 22 January 2014. http://irclogs.geoapt.com/qgis/%23qgis.2014-01-22.log
> tomkralidis: btw it would be great to see the CSW client made ready to go into QGIS core one of these days – its a missing piece from our ‘out of the box OGC compliance’

MetaSearch is a QGIS plugin to interact with CSW services.

Wiki Pages

  • [[MetaSearch Default Connections List|Default Connections List]]
  • [[MetaSearch Discovery Workflow|Discovery Workflow]]
  • [[MetaSearch Release Packaging|Release Packaging]]
  • [[MetaSearch Development Workflow|Development Workflow]]

Links

Raw
MetaSearch_Default_Connections_List.textile

MetaSearch Default Connections list

Overview
The MetaSearch default connections list) provides a sampling of CSW endpoints for users to get started with the MetaSearch plugin.

This file is also part of the continuous integration process (see pavement.test_default_csw_connections); on every commit / push to the repository, the CSW endpoints are health check tested. If the CSW is problematic (against a simple GetCapabilities test (which, if it cannot pass, then there are real problems :) ), the build fails.

Guidance for Adding CSWs to the Default List

  • default connections list provides a list of authoritative (preferably in national scope) CSW servers
  • servers are listed by CSW server name (taken from csw:Capabilities/ows:ServiceIdentification/ows:Title) in alphabetical order
  • servers are listed as base URLs. No CSW parameters. Any query string entities must be escaped correctly to ensure well-formed XML
  • servers can be proposed for inclusion to the default list by submitting a new issue
  • any server causing the build to break is removed
  • all other servers can be listed on this page either:
    • XML file that someone can copy/paste
    • anyone can host their own CSW collection XML elsewhere and link them off this page

CSW Connection Collections

Raw
MetaSearch_Development_Workflow.textile

MetaSearch Development Workflow

via git sparse-checkout

@ git init QGIS-MetaSearch
cd QGIS-MetaSearch/
git remote add -f origin https://github.com/QGIS/qgis.git
git config core.sparsecheckout true
git config core.sparsecheckout
echo “python/plugins/MetaSearch” >> .git/info/sparse-checkout
vi .git/info/sparse-checkout
git pull origin master@

Raw
MetaSearch_Discovery_Workflow.textile

MetaSearch Discovery Workflow

With the release of MetaSearch plugin, it is now easier to discover WMS/WFS/WCS resources and add them to QGIS.
However, some good practices must be defined in order to ensure that OGC services are correctly documented in metadata records.
For example, we recently discovered that in our GeoNetwork catalog all WMS services had the dc:URI elements scheme="OGC:WMS-1.1.1-http-get-map" and this was impending us to activate the “Add WMS” button in the plugin. The solution is to have scheme="OGC:WMS" and then everything works fine.

Consequently, this page is aiming to exchange ideas/experiences in order to dive deeper into this workflow and have this better supported in MetaSearch.

Ideas

1. Instead of adding WMS/WFS/WCS to the list of services in QGIS, it would be nice to have also the possibility to add data directly to the ToC and the View window (e.g. download selected data with the correct extent, etc…). Workflow:

  • discover records
  • record has a download data link type
  • users clicks “Add Data” (new button)
  • MetaSearch downloads the data (to where?) and adds to map (how does it figure out whether it’s raster or vector or something else? Test with GDAL/OGR first?)
Raw
MetaSearch_Release_Packaging.textile

MetaSearch Release Packaging

The following are step by step instructions on how to package a release.

  1. update the metadata.txt with the new version x.y.z:
  2. add major items in new line in metadata.txt, changelog value
  3. commit the above updates:

    
 git commit -m ‘[MetaSearch] update release version’ metadata.txt
    
 git push origin master
  4. Upload package to plugins.qgis.org:

    
 paver upload -u $OSGEO_USERID  # you will be prompted for your password
  5. Email announcement to:
  6. qgis-developer
  7. Twitter
  8. Google+

Message Template

Subject: MetaSearch x.y.z released

The MetaSearch team announces the release of MetaSearch x.y.z. 

[High level overview of release]

The plugin can be found on the QGIS Plugins Repository at http://plugins.qgis.org/plugins/MetaSearch

MetaSearch is a QGIS plugin to interact with metadata catalogue services (CSW).

Version x.y.z (YYYY-MM-DD):
---------------------------

[Bulleted list of enhancements / bug fixes]

Testers and developers are welcome.

The MetaSearch team.

https://hub.qgis.org/wiki/quantum-gis/MetaSearch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment