{"id":253,"date":"2009-02-05T16:53:48","date_gmt":"2009-02-05T21:53:48","guid":{"rendered":"http:\/\/www.kralidis.ca\/blog\/?p=253"},"modified":"2022-11-07T17:45:12","modified_gmt":"2022-11-07T22:45:12","slug":"ows-metadata-matters","status":"publish","type":"post","link":"https:\/\/www.kralidis.ca\/blog\/2009\/02\/05\/ows-metadata-matters\/","title":{"rendered":"OWS Metadata Matters"},"content":{"rendered":"<p>This has seemingly been the theme for me in the last few weeks.&nbsp; From publishing to discovery, lack of metadata in OWS endpoints results in increased metadata management away from source, as well as crappy search results.<\/p>\n<p>So here&#8217;s some friendly advice:<\/p>\n<p>Service Metadata<\/p>\n<ul>\n<li>fill out title, abstract (representative of the OWS as a whole) with descriptive metadata<\/li>\n<li>fill out keywords to categorize the service.&nbsp; If possible, use a known <a title=\"thesaurus\" href=\"http:\/\/gcmd.nasa.gov\/Resources\/valids\/\">thesaurus<\/a>, or one specific to your organization.&nbsp; Don&#8217;t use keywords like &#8220;OGC&#8221;; we already know it&#8217;s an OGC service from the get-go by interacting with it<\/li>\n<li>fill out contact information.&nbsp; <a title=\"OWS Common\" href=\"http:\/\/www.opengeospatial.org\/standards\/common\">OWS Common<\/a> defines ServiceProvider metadata constructs, so if your organization has a service provider dishing out your OWS, they belong in this metadata.&nbsp; This is a contact person for the service itself, not the data<\/li>\n<li>fill out Fees and AccessConstraints.&nbsp; If there aren&#8217;t any, use the term &#8220;None&#8221;<\/li>\n<li>the OnlineResource for Service Metadata might be some website, not the URL of the service itself (we already get this from the OperationsMetadata)<\/li>\n<\/ul>\n<p>Content Metadata<\/p>\n<ul>\n<li>fill in title, abstract and keywords in the same manner as above, specific to the given Layer\/FeatureType\/Coverage\/ObservationOffering.&nbsp; A title like &#8220;ROAD_1M&#8221; doesn&#8217;t cut it<\/li>\n<li>your data comes with an <a title=\"FGDC\" href=\"http:\/\/www.fgdc.gov\/metadata\/geospatial-metadata-standards\">FGDC<\/a> or <a title=\"ISO 19115\" href=\"http:\/\/www.iso.org\/iso\/iso_catalogue\/catalogue_tc\/catalogue_detail.htm?csnumber=26020\">ISO 19115<\/a> XML document already, right?&nbsp; \ud83d\ude42 Use MetadataURL to point to the XML document.&nbsp; Smart catalogues will harvest this too and associate it with the resource<\/li>\n<li>WMS DataURL: if the data can be downloaded online (tgz\/zip\/etc.), point to it here.&nbsp; Or, put a pointer to an access service like WFS\/WCS\/SOS<\/li>\n<li>WMS Layer Attribution: this provides reference to the content provider (URL, title and LogoURL).&nbsp; Filling in LogoURL is neat as catalogues can display this when users search for content.&nbsp; If possible, use an image of smaller dimensions so as to display as a thumbnail<\/li>\n<li>Last but not least, bounding boxes.&nbsp; Whether your OWS software automagically calculates these per layer on the fly, or you can override these and set before runtime, please set spatial extents accordingly.&nbsp; This improves searching spatially by leaps and bounds.&nbsp; Don&#8217;t settle for the often used default of -180, -90, 180, 90 unless it is really a global dataset<\/li>\n<\/ul>\n<p>From here, OGC Catalogues will be able to harvest your metadata and provide useful search results.&nbsp; For wider spread discovery, throw an OpenSearch definition in front of your CSW.&nbsp; Wrap your OWS endpoints in KML\/GeoRSS documents (Geo Sitemaps too), and you&#8217;ll power mainstream use of your stuff.<\/p>\n<p>Funeral news from <a href=\"https:\/\/newrestfunerals.co.uk\/\">newrestfunerals.co.uk<\/a> said:<br \/>\n&#8216;Mourners buried under a bridge for the lost&#8217;<\/p>\n<p>A group of members of London&#8217;s funeral procession paid their respects to a man and his mother at the Royal Greenwich Cathedral where they lost a loved one to cancer<\/p>\n<p>The two sisters and their daughter, who was buried the same night, were buried at the Royal Greenwich Cathedral, where he passed away last weekend.<\/p>\n<p>Grieve: The two sisters and their daughter, who was buried the same night, were buried at the Royal Greenwich Cathedral, where he passed away last weekend<\/p>\n<p>At the bottom of the stairs of the church, you can see a cemeterie. It looked like an Indian wedding feast to the first group and there were candles and flowers on the ceiling.<\/p>\n<p>The funeral family were in their homes in London but only a brief family procession was in progress.<\/p>\n<p>The group had gathered in a cemeterie outside the cathedral and the coffin was handed over to the funeral director.<\/p>\n<p>The funeral director also handed in to the British Transport Police and they placed the coffin in a safe house at Queen&#8217;s Park, New York.<\/p>\n<p>The couple went to the funeral home and their body was found on the day of the operation.<\/p>\n<p>Casket search: &#8216;Mourners raised at arms pace&#8217;<\/p>\n<p>No word on a cause of death or why they died but the couple&#8217;s family said in a statement.<\/p>\n<p>Bye bye useless searches!<\/p>\n<link rel=\"stylesheet\" href=\"http:\/\/cdn.leafletjs.com\/leaflet-0.5\/leaflet.css\" \/>\n<!--[if lte IE 8]>\n  <link rel=\"stylesheet\" href=\"http:\/\/cdn.leafletjs.com\/leaflet-0.5\/leaflet.ie.css\" \/>\n<![endif]-->\n<script src=\"http:\/\/cdn.leafletjs.com\/leaflet-0.5\/leaflet.js\"><\/script>\n<style type=\"text\/css\">#map253 { width: 300px; height: 200px; }<\/style>\n\n<div id=\"map253\"><\/div>\n<script type=\"text\/javascript\">\n  var map253 = L.map('map253').setView([43.620495, -79.513198], 10);\n  L.tileLayer('http:\/\/{s}.tile.osm.org\/{z}\/{x}\/{y}.png', {\n      attribution: '&copy; <a href=\"http:\/\/osm.org\/copyright\">OpenStreetMap<\/a> contributors'\n  }).addTo(map253);\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>This has seemingly been the theme for me in the last few weeks.&nbsp; From publishing to discovery, lack of metadata in OWS endpoints results in increased metadata management away from source, as well as crappy search results. So here&#8217;s some friendly advice: Service Metadata fill out title, abstract (representative of the OWS as a whole) [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,3,11],"tags":[],"class_list":["post-253","post","type-post","status-publish","format-standard","hentry","category-geospatial","category-technology","category-web"],"_links":{"self":[{"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/posts\/253","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/comments?post=253"}],"version-history":[{"count":11,"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/posts\/253\/revisions"}],"predecessor-version":[{"id":903,"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/posts\/253\/revisions\/903"}],"wp:attachment":[{"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/media?parent=253"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/categories?post=253"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/tags?post=253"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}