QGIS/resources/metadata-ISO/LinkPropertyLookupTable.csv
Etienne Trimaille ba81068f49 [FEATURE] [needs-docs] Metadata editor
Adds a new metadata tab to layer properties, representing the new metadata model from QEP #91
2017-09-23 14:08:32 +10:00

25 KiB

1identifierurilabelurltargetownerresource_typeregistrantcommentsdeprecated
2OGC:CSWhttp://www.opengis.net/def/serviceType/ogc/cswOGC Catalog Service for the Webhttp://www.opengeospatial.org/standards/catsrv:serviceType;gmd:protocol;usgin:overlayAPIservice@tomkralidisgmd:protocol value that indicates CI_OnlineResource URL is for an OGC Catalog service for the web v2.0.2 endpoint (should use different protocol identifier if the endpoint is not v2.0.2; these are not yet defined here). The gmd:function value in the CI_Online resource should be 'information' if the provided URL is a getCapabilities request.
3OGC:SOShttp://www.opengis.net/def/serviceType/ogc/sosOGC Sensor Observation Servicehttp://www.opengeospatial.org/standards/sossrv:serviceType;gmd:protocol;usgin:overlayAPIservice@tomkralidisgmd:protocol value that indicates CI_OnlineResource URL is for an OGC Sensor Observation service v?? endpoint (should use different protocol identifier if the endpoint is not that version; these are not yet defined here). The gmd:function value in the CI_Online resource should be 'information' if the provided URL is a getCapabilities request. Note that if the service offers multiple datasets in different offerings, the parameters necessary to access the correct offering should be specified in the gmd:CI_OnlineResource/gmd:description element; recommended practice is to use a JSON object with keys that are parameter names and values that are the necessary parameters.urn:x-esri:specification:ServiceType:SOS; urn:x-esri:specification:ServiceType:sos:url
4OGC:SPShttp://www.opengeospatial.org/standards/spsOGC Sensor Planning Servicehttp://www.opengeospatial.org/standards/spssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an Sensor Planning Service
5OGC:SAShttp://www.ogcnetwork.net/SASOGC Sensor Alert Servicehttp://www.ogcnetwork.net/SASsrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an Sensor Alert Service
6OGC:WNShttp://www.ogcnetwork.net/WNSOGC Web Notification Servicehttp://portal.opengeospatial.org/files/?artifact_id=1367srv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an Web Notification Service
7OGC:WCShttp://www.opengis.net/def/serviceType/ogc/wcsOGC Web Coverage Servicehttp://www.opengeospatial.org/standards/wcssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@tomkralidisgmd:protocol value that indicates CI_OnlineResource URL is for an OGC Web coverage service v?? endpoint (should use different protocol identifier if the endpoint is not that version; these are not yet defined here). The gmd:function value in the CI_Online resource should be 'information' if the provided URL is a getCapabilities request. Note that if the service offers multiple datasets in different coverages, the parameters necessary to access the correct coverage should be specified in the gmd:CI_OnlineResource/gmd:description element; recommended practice is to use a JSON object with keys that are parameter names and values that are the necessary parameters.urn:x-esri:specification:ServiceType:WCS; urn:x-esri:specification:ServiceType:wcs:url
8OGC:WFShttp://www.opengis.net/def/serviceType/ogc/wfsOGC Web Feature Servicehttp://www.opengeospatial.org/standards/wfssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@tomkralidisgmd:protocol value that indicates CI_OnlineResource URL is for an OGC Web Feature Service v?? endpoint (should use different protocol identifier if the endpoint is not that version; these are not yet defined here). The gmd:function value in the CI_Online resource should be 'information' if the provided URL is a getCapabilities request. Note that if the service offers multiple datasets in different feature types the typeName parameter necessary to access the correct data should be specified in the gmd:CI_OnlineResource/gmd:description element; recommended practice is to use a JSON object with keys that are parameter names and values that are the necessary parameters.urn:x-esri:specification:ServiceType:WFS; urn:x-esri:specification:ServiceType:wfs:url
9OGC:WMShttp://www.opengis.net/def/serviceType/ogc/wmsOGC Web Map Servicehttp://www.opengeospatial.org/standards/wmssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@tomkralidisgmd:protocol value that indicates CI_OnlineResource URL is for an OGC Web Map Service v?? endpoint (should use different protocol identifier if the endpoint is not that version; these are not yet defined here). The gmd:function value in the CI_Online resource should be 'information' if the provided URL is a getCapabilities request. Note that if the service offers multiple datasets in different map layers, the layers parameters necessary to access the correct data should be specified in the gmd:CI_OnlineResource/gmd:description element; recommended practice is to use a JSON object with keys that are parameter names and values that are the necessary parameters.urn:x-esri:specification:ServiceType:WMS; urn:x-esri:specification:ServiceType:wms:url
10OGC:WMS-Chttp://www.opengis.net/def/serviceType/ogc/wmsOGC Web Map Service - Cachedhttps://wiki.osgeo.org/wiki/WMS_Tile_Cachingsrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pacioosThis is an unofficial profile of WMS using OSGeo recommendations to pull cached map tiles from the server when available. Often this is specified with a 'tiled=true' URL parameter in the GetMap request.While WMS-C has been superseded by the OSGeo Tile Map Service specification (TMS) and the OGC Web Map Tile Service standard (WMTS), it is still widely supported.
11OGC:WMTShttp://www.opengeospatial.org/standards/wmtsOGC Web Map Tile Servicehttp://www.opengeospatial.org/standards/wmtssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an OGC Web Map Tile Service
12OGC:WPShttp://www.opengis.net/def/serviceType/ogc/wpsOGC Web Processing Servicehttp://www.opengeospatial.org/standards/wpssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@tomkralidisgmd:protocol value that indicates CI_OnlineResource URL is for an OGC Web Processing Service v?? endpoint (should use different protocol identifier if the endpoint is not that version; these are not yet defined here). The gmd:function value in the CI_Online resource should be 'information' if the provided URL is a getCapabilities request. Other parameters necessary to access the correct processing service should be specified in the gmd:CI_OnlineResource/gmd:description element; recommended practice is to use a JSON object with keys that are parameter names and values that are the necessary parameters.
13OGC:ODShttp://www.opengeospatial.org/standards/ols#odsOGC OpenLS Directory Servicehttp://www.opengeospatial.org/standards/olssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an OGC OpenLS Directory Service
14OGC:OGShttp://www.opengeospatial.org/standards/ols#ogsOGC OpenLS Gateway Servicehttp://www.opengeospatial.org/standards/olssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an OGC OpenLS Gateway Service
15OGC:OUShttp://www.opengeospatial.org/standards/ols#ousOGC OpenLS Utility Servicehttp://www.opengeospatial.org/standards/olssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an OGC OpenLS Utility Service
16OGC:OPShttp://www.opengeospatial.org/standards/ols#opsOGC OpenLS Presentation Servicehttp://www.opengeospatial.org/standards/olssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an OGC OpenLS Presentation Service
17OGC:ORShttp://www.opengeospatial.org/standards/ols#orsOGC OpenLS Route Servicehttp://www.opengeospatial.org/standards/olssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an OGC OpenLS Route Service
18OGC:CThttp://www.opengeospatial.org/standards/ctOGC Coordinate Transformation Servicehttp://www.opengeospatial.org/standards/ctsrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an OGC Coordinate Transformation Service
19OGC:WFS-Ghttp://www.opengeospatial.org/standards/wfs-gGazetteer Service Profile of the Web Feature Service Implementation Specificationhttp://portal.opengeospatial.org/files/?artifact_id=7175srv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an OGC Gazetteer Service Profile of the Web Feature Service Implementation Specification
20OGC:OWChttp://www.opengeospatial.org/standards/owcOGC OWS Contexthttp://www.opengeospatial.org/standards/owcgmd:MD_Format/gmd:name;gmd:applicationProfiledata@pvgenuchtenSpecifies a fully configured service set which can be exchanged
21OGC:GPKGhttp://www.opengeospatial.org/standards/geopackageOGC Geopackagehttp://www.opengeospatial.org/standards/geopackagegmd:MD_Format/gmd:name;gmd:applicationProfiledata@pvgenuchtenSQLite Extension for exchange or direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales
22OGC:IoThttp://www.ogcnetwork.net/IoTOGC SensorThings APIhttp://ogc-iot.github.io/ogc-iot-apisrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for a SensorThings API
23ESRI:ArcIMSurn:x-esri:serviceType:ArcIMSESRI ArcIMS Servicesrv:serviceType;gmd:protocol;usgin:overlayAPIEsri Inc.service@tomkralidisgmd:protocol value that indicates CI_OnlineResource URL is for an ArcIMS endpoint. ArcIMS requests are tunneled via HTTP Get URL's
24ESRI:ArcGISurn:x-esri:serviceType:ArcGISESRI ArcGIS Servicesrv:serviceType;gmd:protocol;usgin:overlayAPIEsri Inc.service@tomkralidisgmd:protocol value that indicates CI_OnlineResource URL is for an ESRI Map service endpoint. ESRI REST requests are tunneled via HTTP Get URL's
25ESRI:MPKhttp://esriurl.com/mpk.xmlArcGIS Map Packagehttp://esriurl.com/mpk.xmlgmd:MD_Format/gmd:name;gmd:applicationProfileEsri Inc.data@mhogewegExample URI for ArcGIS Map Package. Mpk is a file format. A map package contains a map document (.mxd) and the data referenced by the layers it contains, packaged into one convenient, portable file.
26OPeNDAP:OPeNDAPOPeNDAP root URLhttp://docs.opendap.org/index.php/UserGuideOPeNDAPMessagessrv:serviceType;gmd:protocol;usgin:overlayAPIservice@tomkralidisLink is the root URL for an OpenDAP endpoint. An OPeNDAP server replies to queries for data and other services in the form of specially formed URLs that start with a root URL, and use a suffix on the root URL and a constraint expression to indicate which service is requested and what the parameters are. Example suffixes are dods, das, dds, nc. OpenDAP defines a syntax for constraint expressions as well.urn:x-esri:specification:ServiceType:OPeNDAP; urn:x-esri:specification:ServiceType:odp:url
27OPeNDAP:HyraxOPeNDAP Hyrax serverhttp://docs.opendap.org/index.php/Hyraxsrv:serviceType;gmd:protocol;usgin:overlayAPIservice@amilan17Link is the root URL for an This is the OPeNDAP 4 Data Server, also known as Hyrax. Hyrax is a data server that implements the DAP2 and DAP4 protocols, works with a number of different data formats and supports a wide variety of customization options from tailoring the look of the server's web pages to complex server-side processing operations.
28UNIDATA:NCSSNetCDF Subset Servicehttps://www.unidata.ucar.edu/software/thredds/current/tds/interfaceSpec/NetcdfSubsetService.htmlgmd:protocol; usgin:overlayAPIservice@tomkralidisLink is the root URL for a THREDDS datasets. The NetCDF Subset Service enables subsetting CDM scientific datasets using earth coordinates, such as lat/lon bounding boxes and date ranges; requests are made via HTTP GET with key-value pairs (KVP) for parameters encoded in HTTP URIs. The resources identified are THREDDS datasets. The resource URIs have a root host name and path, typically something like http://servername:8080/thredds/ncss/, followed by a path that identifies a particular dataset {path/dataset}. A subset of the dataset is considered a view of a resource, specified by query parameters following the character '?' after the dataset path: http://servername:8080/thredds/ncss/{path/dataset}?{subset}. An 'accept' parameter may be used to specify the desired resource representation.
29UNIDATA:CDMCommon Data Model Remote Web Servicehttps://www.unidata.ucar.edu/software/thredds/current/netcdf-java/stream/CdmRemote.htmlsrv:serviceType;gmd:protocol;usgin:overlayAPIUnidataservice@tomkralidisExample
30UNIDATA:CdmRemoteCommon Data Model index subsettinghttps://www.unidata.ucar.edu/software/thredds/current/netcdf-java/stream/CdmRemote.htmlgmd:protocol; usgin:overlayAPIUnidataservice@smrazgsCDM Remote provides remote access to UNIDATA Common Data Model (CDM) datasets, using ncstream as the on-the-wire protocol. Client requests are of the form endpoint?query, and the specification defines a vocabulary of valid query parameters. There are two levels of service: 1) CdmRemote provides index subsetting on remote CDM datasets; 2) CdmrFeature provides coordinate subsetting on remote CDM Feature Datasets
31UNIDATA:CdmrFeatureCommon Data Model coordinate subsettinghttps://www.unidata.ucar.edu/software/thredds/current/netcdf-java/stream/CdmRemote.htmlgmd:protocol; usgin:overlayAPIUnidata@smrazgsLink is endpoint URL that provides coordinate subsetting on UNIDATA Common Data Model (CDM) datasets, using ncstream as the on-the-wire protocol. Client requests are of the form endpoint?query, and the specification defines a vocabulary of valid query parameters.
32UNIDATA:THREDDShttp://www.unidata.ucar.edu/namespaces/thredds/InvCatalog/v1.0THREDDS Cataloghttp://www.unidata.ucar.edu/software/thredds/current/tds/catalog/InvCatalogSpec.htmlsrv:serviceType;gmd:protocol;usgin:overlayAPIUnidataservice@kwilcoxLink is a THREDDS Catalog URL that provides the XML for traversing programmatically. Can be used for datasets and collections of datasets.
33OGC:GMLhttp://www.opengis.net/gmlOGC Geography Markup Languagegmd:MD_Format/gmd:name;gmd:applicationProfiledata@tomkralidisExample
34WWW:LINKhttp://www.w3.org/TR/xlink/Web Address (URL)dct:references/@schemeinformation@tomkralidis @smrazgsIndicates that XLINK properties are encoded as key-value pairs in content of a dct:references element to provide a machine actionable link.
35WWW:WSDLhttp://www.w3.org/TR/wsdlWeb Service Description Language XML document describing service operationhttp://www.w3.org/TR/wsdlgmd:applicationProfileW3C@smrazgs
36WWW:SPARQL:1.1http://www.w3.org/TR/sparql11-protocolSPARQL protocol for HTTPhttp://www.w3.org/TR/rdf-sparql-querysrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtenSPARQL Protocol specifies a means for conveying SPARQL queries and updates to a SPARQL processing service and returning the results via HTTP to the entity that requested them
37OpenSearch1.1http://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_URL_template_syntaxOpenSearch templatehttp://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_URL_template_syntaxusgin:template;gmd:applicationProfileOpenSearch.org@smrazgsuse to indicate link is a template conforming to the OpenSearch specification
38OpenSearch1.1:Descriptionhttp://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_description_documentOpenSearch description documenthttp://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_description_documentgmd:applicationProfileOpenSearch.org@smrazgsindicates a link to get an openSearch description document
39informationlink provides information about resourcegmd:functionISO TC211@smrazgsfunction of link it to http:GET information about resource
40templatehttp://tools.ietf.org/html/rfc6570link provides template to access resourcehttp://tools.ietf.org/html/rfc6570gmd:functionUSGIN@smrazgsLink text is a URI template; applicationProfile attribute value associated with the link should indicate the specification for the template scheme (e.g. OpenSearch1.1).
41downloadlink will get resourcegmd:functionISO TC211@smrazgsfunction of link it to http:GET a representation of the resource; the link type attribute value(s) should indicate the MIME types of available representations
42servicelink is service endpointgmd:functionISO TC211@smrazgsLink value is the URL of a service endpoint; the link protocol and applicationProfile (and possibly other link properties like overlayAPI, depending on the link attributes profile in use) attribute values should identify the service protocol specification
43orderlink provides form to obtain resourcegmd:functionISO TC211@smrazgslink value is URL of web application requiring user interaction to order/request access to the resource
44searchlink provides form for searching resourcegmd:functionISO TC211@smrazgslink value is URL of web application requiring user interaction to search/browse/subset the resource.
45esip:CollectionCasthttp://commons.esipfed.org/ns/discovery/1.2/collectionCast# ESIP collection castgmd:applicationProfileESIP@smrazgs
46tilejson:2.0.0tile mill map service descriptionhttps://github.com/mapbox/tilejson-specgmd:applicationProfileMapBox@smrazgslink is description of a TileMill map service endpoint. Link type would be application/json; function would be information.
47iris:fdsnws-eventhttp://service.iris.edu/fdsnws/event/1/IRIS Seismic event servicehttp://service.iris.edu/fdsnws/event/1gmd:applicationProfile;usgin:overlayAPIIRIS@smrazgsLink returns event (earthquake) information from the catalogs submitted to the IRIS DMC
48QuakeML1.2http://quakeml.org /xmlns /quakeml/1.2Earthquake markup languagehttps://quake.ethz.ch/quakemlgmd:MD_Format/gmd:name;gmd:applicationProfilequakeml@sed.ethz.ch@smrazgsXML markup language for earthquake hypocenter data
49filea filehttp://docs.ckan.org/en/ckan-1.8/domain-model-resource.htmlgmd:functionOKFN@smrazgsCKAN metadata vocabulary for populating the type attribute on a CKAN resource; indicates that an http GET of this url should yield a bitstream
50ISO 19115:2003/19139ISO 19115 metadata in ISO19139 encodinggmd:metadataStandardNameGeoNetwork@smrazgsThis is the CharacterString value used by Geonetwork OpenSource to identify ISO metadata record instances; apparently have to assume that its using the 2006 corrigendum with no specific profile conventions.
51ISO-USGINUSGIN-profile ISO 19115 metadatahttp://repository.usgin.org/uri_gin/usgin/dlio/337gmd:metadataStandardNameUSGIN@smrazgsThis is the CharacterString Value mandated by the USGIN profile of ISO19115/19139 for instance documents to self-identify.
52httphttps://www.ietf.org/rfc/rfc2616Hypertext transfer Protocol, v1.1https://www.ietf.org/rfc/rfc2616.txtgmd:protocolIETF@smrazgsUse to indicate gmd:CI_OnlineResource URLs that are simple http links to a target resource representation for download; redundant as the URL prefix 'http:' conveys the same information.
53httpshttps://tools.ietf.org/html/rfc2818HTTP over TLShttps://www.ietf.org/rfc/rfc2818.txtgmd:protocolIETF@amilan17Use to indicate gmd:CI_OnlineResource URLs that are simple https links to a target resource representation for download; redundant as the URL prefix 'https:' conveys the same information.
54ftphttps://tools.ietf.org/html/rfc959FILE TRANSFER PROTOCOL (FTP)https://www.ietf.org/rfc/rfc959.txtgmd:protocolIETF@amilan17Use to indicate gmd:CI_OnlineResource URLs that are simple ftp links to a target resource representation for download; redundant as the URL prefix 'ftp:' conveys the same information.
55IETF:GeoJSONhttp://geojson.orgGeoJSONhttps://datatracker.ietf.org/doc/draft-butler-geojsongmd:MD_Format/gmd:name;gmd:applicationProfiledata@pvgenuchtenGeoJSON is a geospatial data interchange format based on JavaScript Object Notation (JSON)
56GIThttp://git-scm.com/GIThttp://git-scm.com/book/commandssrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for a GIT repository
57OKFN:datapackagehttp://data.okfn.org/doc/data-packageOKFN Data Packagehttp://dataprotocols.org/data-packagesgmd:MD_Format/gmd:name;gmd:applicationProfiledata@pvgenuchtenA Data Package is a simple way of packaging up data
58boundless:geogighttp://geogig.orgBoundless GeoGighttp://geogig.org/docs/interaction/web-api.htmlsrv:serviceType;gmd:protocol;usgin:overlayAPIBoundlessservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for a GeoGig REST API
59OASIS:OData:4.0http://docs.oasis-open.org/odata/odata/v4.0OData v4.0http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.htmlsrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for an OData JSON endpoint
60maxogden:dathttp://dat-data.comdat REST APIhttps://github.com/maxogden/dat/blob/master/docs/rest-api.mdsrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for a dat REST API
61geoserver:resthttp://docs.geoserver.org/latest/en/user/restGeoServer REST configuration APIhttp://docs.geoserver.org/latest/en/user/restsrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for a Geoserver rest API to configure featuretypes in Geoserver (and mapserver) remotely
62google:protocol-buffershttps://developers.google.com/protocol-buffersGoogle Protocol Buffershttps://developers.google.com/protocol-buffersgmd:MD_Format/gmd:name;gmd:applicationProfileGoogledata@pvgenuchtenGoogles mechanism for serializing structured data
63google:fusion-tableshttp://google.com/fusiontablesGoogle Fusion Tableshttps://developers.google.com/fusiontablesgmd:MD_Format/gmd:name;gmd:applicationProfileGoogledata@pvgenuchtenGoogle mechanism for interating with online data tables
64NOAA:LAShttp://ferret.pmel.noaa.gov/LASLive Access Serverhttp://ferret.pmel.noaa.gov/LAS/documentation/developer-documentation/the-xml-messages-used-by-lassrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is a LAS endpoint
65OSMhttp://wiki.openstreetmap.org/wiki/APIOpen Street Map APIhttp://wiki.openstreetmap.org/wiki/APIsrv:serviceType;gmd:protocol;usgin:overlayAPIservice@pvgenuchtengmd:protocol value that indicates CI_OnlineResource URL is for a OSM APIfor fetching and saving raw geodata from/to an OpenStreetMap database
66ERDDAP:griddaphttp://coastwatch.pfeg.noaa.gov/erddap/griddap/documentation.htmlERDDAP Data Service for Gridded Datasetshttp://coastwatch.pfeg.noaa.gov/erddap/griddap/documentation.htmlsrv:serviceType;gmd:protocol;usgin:overlayAPI@BobSimonsservice@BobSimonsgriddap lets you request a data subset, graph, or map from a gridded dataset (for example, sea surface temperature data from a satellite), via a specially formed URL. griddap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its projection constraints (external link). Link is the root URL for an ERDDAP griddap service endpoint. The service responds to OPeNDAP requests and related ERDDAP-specific requests to a gridded dataset. A request starts with this root URL, adds a file type extension, and sometimes a constraint expression to specify a subset of data. Example file type extensions which don't require a constraint are .das, .dds, .html, and .graph. Example file type extensions which do require a constraint are .dods, .nc, .mat, .json, and .htmlTable. Full documentation for ERDDAP API at http://coastwatch.pfeg.noaa.gov/erddap/rest.html
67ERDDAP:tabledaphttp://coastwatch.pfeg.noaa.gov/erddap/tabledap/documentation.htmlERDDAP Data Service for Tabular Datasetshttp://coastwatch.pfeg.noaa.gov/erddap/tabledap/documentation.htmlsrv:serviceType;gmd:protocol;usgin:overlayAPI@BobSimonsservice@BobSimonsTabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its selection constraints (external link). Link is the root URL for an ERDDAP tabledap service endpoint. The service responds to OPeNDAP requests and related ERDDAP-specific requests to a tabular (sequence) dataset. A request starts with this root URL, adds a file type extension, and sometimes a constraint expression to specify a subset of data. Example file type extensions which don't require a constraint are .das, .dds, .html, and .graph. Example file type extensions which do require a constraint are .dods, .nc, .mat, .json, and .htmlTable. Full documentation for ERDDAP API at http://coastwatch.pfeg.noaa.gov/erddap/rest.html
68OASIS:AMQPhttps://amqp.orgAdvanced Message Queuing Protocolhttps://amqp.orggmd:protocolservice@tomkralidisgmd:protocol value that indicates CI_OnlineResource URL is for an AMQP broker