Re: [OSGeo-Discuss] What terms should go into an OSGeo Glossary?
Hi, On Thu, Sep 26, 2019 at 1:02 AM Cameron Shorter wrote: > > Hi folks, > > Felicity (CCed), one of the Tech Writers partaking in the Google Season > of Docs, is going to compile a Glossary for us. > Does anyone know of existing Glossaries that we can start from? I did some efforts years ago: https://wiki.osgeo.org/wiki/OSGeo_Multilanguage_Dictionary It was hosted on the "webextra" server but didn't survive the infrastructure migration in 2014. Dunno if anyone kept a copy... Best Markus -- Markus Neteler, PhD https://www.mundialis.de - free data with free software https://grass.osgeo.org https://courses.neteler.org/blog ___ Discuss mailing list Discuss@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/discuss
[OSGeo-Discuss] What terms should go into an OSGeo Glossary?
Hi folks, Felicity (CCed), one of the Tech Writers partaking in the Google Season of Docs, is going to compile a Glossary for us. Does anyone know of existing Glossaries that we can start from? I've found an OGC list of accronyms [0]. This coming week (by 29 September) she will be collating existing material. In the following weeks, she'll be asking us to review and see what extra terms should be added. Beyond that, she will also be working reviewing our Quickstarts, and selecting a writing style guide. (The Google Syle Guide is a likely contender). You can see results of her first pass [1]. If you'd like to contribute, conversations are happening on the OSGeoLive email list [2], or you can email Felicity directly. [0] https://www.opengeospatial.org/acronyms [1] https://docs.google.com/presentation/d/1jmSlp9GNwoPupeFJdjPsBnL7vqVG7AiWbWLEGOWEcy4/edit#slide=id.p1 [2] https://lists.osgeo.org/mailman/listinfo/osgeolive Cheers, -- Cameron Shorter Technology Demystifier Open Technologies and Geospatial Consultant M +61 (0) 419 142 254 ___ Discuss mailing list Discuss@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/discuss
[OSGeo-Discuss] PyWPS 4.2.2 released
Dear all, the PyWPS PSC [1] annones new bug-fix release of the PyWPS project: 4.2.2[2] This release is focused on bug fixing, namely: * Fixed scheduler extension (#480). * Fixed ValuesReference implementation (#471, #484). * Fixed AllowedValue range (#467, #464). * Add metalink support to facilitate outputs with multiple files (#466). * Rename async to async_ for Python 3.7 compatibility (#462). * Improve queue race conditions (#455). * Numerous bug-fixes, additional tests and documentation improvements. You can download new release from the GitHub [3] as well as from PyPI [4] Thank you to all the contributors. Looking forward to next release. Jachym (in the name of PyWPS PSC) [1] http://pywps.org [2] https://pywps.org/2019/09/25/pywps-4.2.2-released.html [3] https://github.com/geopython/pywps/tree/4.2.2 [4] https://pypi.org/project/pywps/4.2.2/ What is PyWPS: PyWPS (Python Web Processing Service) is implementation of Web Processing Service standard from Open Geospatial Consortium (OGC(R)). Processes can be written using GRASS GIS, but usage of other programs, like R package, GDAL or PROJ tools, is possible as well. PyWPS is the OSGeo project. -- Jachym Cepicky e-mail: jachym.cepicky gmail com URL: http://les-ejk.cz GPG: http://les-ejk.cz/pgp/JachymCepicky.pgp ___ Discuss mailing list Discuss@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/discuss
