Recognize GeoPortal-style service/link type code types (WMS, WFS, WCS)

[emiliom]

Added additional acceptable link type strings for WMS, WFS, WCS, based on urn code types commonly used in GeoPortal (eg, 'urn:x-esri:specification:ServiceType:Gmd:URL.wms'). All changes limited to plugin/MetaSearch/dialogs/maindialog.py, to MetaSearchDialog find_services method.

Note that I haven't tested this in QGIS! I've never done a pip/git install that replaces an installed QGIS plugin, so I'm hesitant to do it right now. But the edits are pretty simple.

[tomkralidis]

cc @rsignell-usgs

thanks @emiliom for the contribution. This is hot topic these days (see activity in https://github.com/OSGeo/Cat-Interop).

I'm thinking MetaSearch should decouple and make these lists configurable by the user (if the default needs to be extended), given all the variations out there (@rsignell-usgs: this is a primary example of the issue at hand :) )

[emiliom]

Thanks, Tom. Wow, great to see all that activity around this topic! I was about to send an email to NGDC's Anna Milan to ask for recommendations on what link types to use, given that the default urn:x-esri ones we've been running into don't seem ideal, and we were also seeing the GeoNetwork strings being used in MetaSearch. BTW, "we" here means http://portal.westcoastoceans.org, a GeoPortal-backended metadata aggregator of both individual records (eg from a WAF) and records harvested from CSW endpoints. I'm in a position to help set a standard for this US West Coast aggregator, and possibly influence our partners out here as well. Tanya Haddad (@tchaddad -- I know you've been in touch with her vis a vis pycsw) is part of this conspiracy, too. Tanya, FYI, this thread from Rich is also roughly where I was coming from, too: http://lists.osgeo.org/pipermail/cat-interop/2014-February/000009.html

My pull requests to MetaSearch stemmed in large part from wanting to see that West Coast catalog be more helpfully accessible on MetaSearch.

I'll add myself to the Cat-Interop loop. Definitely relevant to my interoperability interests in IOOS and other circles I'm in.

BTW, most of my interoperability roads lead to @rsignell-usgs these days. Rich, is that good or bad? :)