{"id":831,"date":"2021-01-01T12:41:16","date_gmt":"2021-01-01T17:41:16","guid":{"rendered":"https:\/\/www.kralidis.ca\/blog\/?p=831"},"modified":"2023-12-31T12:47:29","modified_gmt":"2023-12-31T17:47:29","slug":"bye-bye-2020","status":"publish","type":"post","link":"https:\/\/www.kralidis.ca\/blog\/2021\/01\/01\/bye-bye-2020\/","title":{"rendered":"Bye Bye 2020"},"content":{"rendered":"\n<p>So <a href=\"https:\/\/en.wikipedia.org\/wiki\/2020\">2020 didn&#8217;t quite work out<\/a> as expected or hoped.  Still, in a year where days seemed to fold into one another, the 24 hour home office and endless virtual meetings, some successes:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/pygeoapi.io\">pygeoapi<\/a>: the Python OGC API server continues to pick up steam.  The project was presented, demoed and discussed at numerous events.  2020 saw the addition of support for OGC API &#8211; Coverages, OGC API &#8211; Tiles, STAC, as well as improvements to OGC API &#8211; Processing job management and queryables<\/li><li>more <a href=\"https:\/\/geopython.github.io\">Geopython<\/a>: <a href=\"https:\/\/pycsw.org\">pycsw<\/a>, <a href=\"https:\/\/pywps.org\">PyWPS<\/a>, <a href=\"https:\/\/geopython.github.io\/OWSLib\">OWSLib<\/a>, <a href=\"https:\/\/geohealthcheck.org\">GeoHealthCheck<\/a> continue to be developed\/maintained, and we are starting to see OGC API support trickling in.  Big thanks to the communities that support those projects.  <a href=\"https:\/\/geopython.github.cio\/pygeometa\">pygeometa<\/a> has been refactored for supporting any metadata format output, which further positions the project for STAC and JSON-based metadata exchange<\/li><li>WMO: with the new WMO structure in place, I was honoured to be nominated to the Standing Committee on Information Management and Technology (<a href=\"https:\/\/community.wmo.int\/governance\/commission-membership\/commission-observation-infrastructures-and-information-systems-infcom\/commission-infrastructure-officers\/infcom-management-group\/standing-committee-information-management-and-technology-sc-imt\">SC-IMT<\/a>), as well as chairing the Expert Team on Metadata Standards of (<a href=\"https:\/\/community.wmo.int\/governance\/commission-membership\/commission-observation-infrastructures-and-information-systems-infcom\/commission-infrastructure-national-representatives\/infcom-management-group\/standing-committee-information-management-and-technology-sc-imt\/et-metadata\">ET-Metadata<\/a>) and participation on ET-Data<\/li><li><a href=\"https:\/\/www.canada.ca\/en\/environment-climate-change\/services\/weather-general-tools-resources\/weather-tools-specialized-data\/msc-geomet-api-geospatial-web-services.html\">GeoMet<\/a>: our weather\/climate\/water API platform continues to grow with more open data and OGC API support, powering the <a href=\"https:\/\/canada.ca\/climate-services\">Canadian Centre for Climate Services<\/a>, WeatherCAN, Canadian Open Data and beyond<\/li><li><a href=\"https:\/\/ogcapi.ogc.org\">OGC API<\/a>: Records and Coverages are groups that I was particularly involved in to move forward discovery and raster data API access.  I look forward to help lock down these standards<\/li><li><a href=\"https:\/\/www.osgeo.org\/about\/board\/\">OSGeo Board of Directors<\/a>: I was honoured to be re-elected for a second term to the Board and look forward helping OSGeo grow, particularly with regards to standards implementation in the Community<\/li><li>health<ul><li>another year (circa 2012) of not smoking<\/li><li>the pandemic has not been easy for weight management.  Time to get back on that!<\/li><\/ul><\/li><\/ul>\n\n\n\n<p>For 2021:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>OGC API: the march continues to modernize the API client\/server ecosystem, and I&#8217;ll be targeting the Geopython projects, as well as QGIS, MapServer, GeoNode and associated Golang tools<\/li><li>OSGeo: continue to foster interaction with standards development organizations (OGC, ISO TC211, etc.) and help navigate the community through these unprecedented times<\/li><li>pycsw: update the pycsw core model to encompass OGC API as well as integration with pygeoapi<\/li><li>pygeoapi: work on OGC API &#8211; Records and OGC API &#8211; Maps continues to progress and should make its way into master this year.  Other candidates include OGC API &#8211; Styles and EDR API.  In addition, I&#8217;m hoping this is the year we enter OSGeo incubation<\/li><li>this website: revitalize the photo galleries and possibly migrating the blog into a static site generator approach<\/li><\/ul>\n\n\n\n<p>In summary, another year of firm belief in the <a href=\"https:\/\/en.wikipedia.org\/wiki\/Unix_philosophy\">Unix philosophy<\/a>, composable workflow and lowering the barrier to geospatial data and tools for anyone.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<p>I hope we have the ability at some point to see one another this year, whether at a code sprint or meeting\/event.  I\u2019d like to wish everyone and their loved ones a healthy, safe, happy and, well, better 2021!  <\/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\">#map831 { width: 300px; height: 200px; }<\/style>\n\n<div id=\"map831\"><\/div>\n<script type=\"text\/javascript\">\n  var map831 = L.map('map831').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(map831);\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>So 2020 didn&#8217;t quite work out as expected or hoped. Still, in a year where days seemed to fold into one another, the 24 hour home office and endless virtual meetings, some successes: pygeoapi: the Python OGC API server continues to pick up steam. The project was presented, demoed and discussed at numerous events. 2020 [&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,7,4],"tags":[],"class_list":["post-831","post","type-post","status-publish","format-standard","hentry","category-geospatial","category-open-source","category-personal"],"_links":{"self":[{"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/posts\/831","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=831"}],"version-history":[{"count":16,"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/posts\/831\/revisions"}],"predecessor-version":[{"id":1069,"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/posts\/831\/revisions\/1069"}],"wp:attachment":[{"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/media?parent=831"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/categories?post=831"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kralidis.ca\/blog\/wp-json\/wp\/v2\/tags?post=831"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}