wradlib - releaseshttp://wradlib.org/2018-04-01T07:00:00+02:00Release 1.0.02018-04-01T07:00:00+02:002018-04-01T07:00:00+02:00wradlibtag:wradlib.org,2018-04-01:/2018/04/wradlib_release_1_0_0/<p>We have now released version 1.0.0 of&nbsp;wradlib. </p> <p>As some of you might be aware, version 1.x is generally considered as a major milestone, indicating that the software has all major features, and is considered reliable enough for general&nbsp;release.</p> <p>The first commit to wradlib is now …</p><p>We have now released version 1.0.0 of&nbsp;wradlib. </p> <p>As some of you might be aware, version 1.x is generally considered as a major milestone, indicating that the software has all major features, and is considered reliable enough for general&nbsp;release.</p> <p>The first commit to wradlib is now almost seven years ago. During these years, a lot of changes have been introduced in terms of algorithms, but also in terms of documentation and maintenance workflows. Yet, the <span class="caps">API</span> has become more and more stable, so we decided that wradlib is now mature enough for switching to a 1.x development&nbsp;line.</p> <p>At the same time, we wanted to use that opportunity to address a couple of issues that we considered important from a developer&#8217;s perspective. Addressing those issues will most likely break existing code and workflows. Yet, <em>this</em> is the time to do it, and doing it is vital to guarantee sustainable, efficient and reliable code development in the future. We cordially invite you to come along with us, and make use of version 1.0.0, even if it means that you might have to refactor your code. If you want to benefit from future improvements, this is the way to go! Limited resources will not allow us to further support the 0.x development line - from today on, it&#8217;ll be&nbsp;legacy.</p> <p>So, these are the most important&nbsp;changes:</p> <h1>Removing redundant and outdated&nbsp;code</h1> <p>A lot of functions had been accumulating over time which remained immature, redundant, or scarcely used. Those functions and (partly) modules have been entirely removed. If you <strong>really</strong> miss one of them, <a href="https://github.com/wradlib/wradlib/issues">raise an issue</a>. </p> <h1>Conform with <span class="caps">PEP</span>&nbsp;conventions</h1> <p>Lots of function, class and variable names have been renamed in order to conform with <a href="https://www.python.org/dev/peps/pep-0008/#naming-conventions"><span class="caps">PEP</span> conventions</a>. It might hurt, first, but we are confident that refactoring will be&nbsp;quick.</p> <h1>Revise&nbsp;georeferencing</h1> <p>Georeferencing has become more precise and transparent, making more use of gdal&#8217;s potential. You will most likely not feel the difference - but we like&nbsp;it!</p> <h1>Revise repository structure and <span class="caps">CI</span>&nbsp;workflows</h1> <p>In order to make developing and releasing more efficient, we fundamentally revised the repository structure: - the actual wradlib code remains under <a href="http://github.com/wradlib/wradlib">http://github.com/wradlib/wradlib</a> - the notebooks have been moved to <a href="https://github.com/wradlib/wradlib-notebooks">https://github.com/wradlib/wradlib-notebooks</a></p> <h1>Documentation&nbsp;pages</h1> <p>The doc pages will mostly look the same, but they are now available under <a href="http://docs.wradlib.org">http://docs.wradlib.org</a>.</p> <h1>For all&nbsp;developers</h1> <p>The pre-1.0 repository state is kept under <a href="https://github.com/wradlib/wradlib-old">https://github.com/wradlib/wradlib-old</a> (not recommended). If you want to keep up with the latest developments, just stick with https://github.com/wradlib/wradlib. There&#8217;s a small catch, though: if you want to base your development on the new wradlib/master, you need to merge it with brute force. On the local version of your current fork, you need&nbsp;to</p> <div class="highlight"><pre><span></span>$ git remote add upstream https://github.com/wradlib/wradlib.git $ git checkout master $ git fetch upstream $ git reset --hard upstream/master $ git push origin master --force </pre></div>Release 0.11.02017-11-15T16:00:00+01:002017-11-15T16:00:00+01:00wradlibtag:wradlib.org,2017-11-15:/2017/11/wradlib_release_0_11_0/<p>We are happy to announce the release of wradlib&nbsp;0.11.0.</p> <p>It introduces our first shot at reading <span class="caps">IRIS</span> (Sigmet) data - a feature that has been requested by quite a number users. Learn more about io.read_iris, and see it at work <a href="http://docs.wradlib.org/en/latest/notebooks/fileio/wradlib_radar_formats.html#Vaisala-Sigmet-IRIS">here</a>. We are looking forward to your …</p><p>We are happy to announce the release of wradlib&nbsp;0.11.0.</p> <p>It introduces our first shot at reading <span class="caps">IRIS</span> (Sigmet) data - a feature that has been requested by quite a number users. Learn more about io.read_iris, and see it at work <a href="http://docs.wradlib.org/en/latest/notebooks/fileio/wradlib_radar_formats.html#Vaisala-Sigmet-IRIS">here</a>. We are looking forward to your&nbsp;feedback!</p> <p>In addition, we redesigned the <code>io</code> and <code>georef</code> modules. As a user, you will hopefully not notice. As a developer, you will hopefully welcome a higher level of&nbsp;(sub-)modularization.</p> <p>For more details on the new release, please visit our <a href="http://docs.wradlib.org/en/latest/release_notes.html">release notes</a>.</p>Release 0.10.12017-06-23T16:00:00+02:002017-06-23T16:00:00+02:00wradlibtag:wradlib.org,2017-06-23:/2017/06/wradlib_release_0_10_1/<p>We are happy to announce the release of wradlib&nbsp;0.10.1.</p> <p>This release is mainly a bug-fix release to make wradlib work with the latest numpy release&nbsp;1.13. </p> <p>For more details on the new release, please visit our <a href="http://wradlib.org/wradlib-docs/0.10.1/release_notes.html">release notes</a>.</p><p>We are happy to announce the release of wradlib&nbsp;0.10.1.</p> <p>This release is mainly a bug-fix release to make wradlib work with the latest numpy release&nbsp;1.13. </p> <p>For more details on the new release, please visit our <a href="http://wradlib.org/wradlib-docs/0.10.1/release_notes.html">release notes</a>.</p>Release 0.10.02017-04-10T16:00:00+02:002017-04-10T16:00:00+02:00wradlibtag:wradlib.org,2017-04-10:/2017/04/wradlib_release_0_10_0/<p>We are happy to announce the release of wradlib&nbsp;0.10.0.</p> <h3>Highlights</h3> <p>Highlight of this release is the implementation of matching of <span class="caps">GPM</span>/<span class="caps">TRMM</span>-platforms with ground radar observations in 3D. A step-by-step guide is available as <a href="http://wradlib.org/wradlib-docs/0.10.0/notebooks/match3d/wradlib_match_workflow.html">jupyter notebook</a>. Also the wradlib raster handling has been improved considerably with …</p><p>We are happy to announce the release of wradlib&nbsp;0.10.0.</p> <h3>Highlights</h3> <p>Highlight of this release is the implementation of matching of <span class="caps">GPM</span>/<span class="caps">TRMM</span>-platforms with ground radar observations in 3D. A step-by-step guide is available as <a href="http://wradlib.org/wradlib-docs/0.10.0/notebooks/match3d/wradlib_match_workflow.html">jupyter notebook</a>. Also the wradlib raster handling has been improved considerably with <a href="https://github.com/wradlib/wradlib/pull/137"><span class="caps">PR</span>#137</a>.</p> <h3>Further changes in wradlib&nbsp;0.10.0</h3> <p>There are also a couple of community enhancements and other improvements and&nbsp;fixes.</p> <p>Community Contribution by <a href="https://github.com/cchwala">Christian Chwala</a>:</p> <ul> <li><code>wradlib.io.read_RADOLAN_composite</code> accept file handles <a href="https://github.com/wradlib/wradlib/pull/114"><span class="caps">PR</span>#114</a>,</li> <li><code>wradlib.io.read_Rainbow</code> accept file handles <a href="https://github.com/wradlib/wradlib/pull/140"><span class="caps">PR</span>#140</a>.</li> </ul> <p>Community Contribution by <a href="https://github.com/franklinvv">franklinvv</a>:</p> <ul> <li><code>wradlib.georef.get_radolan_grid</code> was enhanced to read extended-<span class="caps">RADOLAN</span>-grid <a href="https://github.com/wradlib/wradlib/pull/119"><span class="caps">PR</span>#119</a>.</li> </ul> <p>Improvements:</p> <ul> <li>Merged the curvelinear grid plotting functions into the normal plotting functions. Added <strong>contour</strong> and <strong>filled contour</strong> plotting&nbsp;capabilities.</li> <li>Generic netcdf reader can read <strong>groups</strong>&nbsp;now.</li> <li>Added <code>wradlib.qual.cum_beam_block_frac</code> to compute cumulative beam&nbsp;blockage.</li> <li>Added <strong>Earth Curvature Display</strong> to <a href="http://wradlib.org/wradlib-docs/0.10.0/notebooks/beamblockage/wradlib_beamblock.html">beam blockage&nbsp;notebook</a></li> <li>Enhance <code>wradlib.georef.read_gdal_values</code> to read multiband&nbsp;data.</li> </ul> <p>Fixes:</p> <ul> <li>The build process on Travis-<span class="caps">CI</span> was significantly improved by running test-suites in dedicated&nbsp;threads/subprocesses.</li> <li>We also fixed some documentation&nbsp;inconsistencies.</li> <li>Several bugs were fixed in <code>wradlib.qual.pulse_volume</code>, <code>wradlib.georef.transform_geometry</code>, <code>wradlib.util.find_bbox_indices</code> and <code>wradlib.ipol.cart2irregular_spline</code>.</li> <li>Several other minor&nbsp;fixes.</li> </ul> <p>For more details on the new release, please visit our <a href="http://wradlib.org/wradlib-docs/0.10.0/release_notes.html">release notes</a>.</p>Release 0.9.02016-08-31T13:00:00+02:002016-08-31T13:00:00+02:00wradlibtag:wradlib.org,2016-08-31:/2016/08/wradlib_release_0_9_0/<p>With this post, we announce the release of wradlib 0.9.0. It finalizes our transition from example Python scripts to jupyter notebooks (as already announced in a <a href="http://wradlib.org/2016/04/introducing-wradlib-jupyter-notebooks/">previous post</a>). As a result, the documentation pages have become more consistent, and the handling of examples and tutorials more convenient and …</p><p>With this post, we announce the release of wradlib 0.9.0. It finalizes our transition from example Python scripts to jupyter notebooks (as already announced in a <a href="http://wradlib.org/2016/04/introducing-wradlib-jupyter-notebooks/">previous post</a>). As a result, the documentation pages have become more consistent, and the handling of examples and tutorials more convenient and interactive. We hope you&#8217;ll&nbsp;agree!</p> <h3>Interactive examples with jupyter&nbsp;notebooks</h3> <p>As a consequence, the previous doc sections &#8220;Tutorials&#8221; and &#8220;Recipes&#8221; have been replaced by one single section <a href="http://docs.wradlib.org/en/latest/notebooks.html">Tutorials and Examples</a>. The pages in that section were automatically built from jupyter (IPython) notebooks. These notebooks are distributed with the <a href="https://pypi.python.org/pypi/wradlib">new release</a>, and you can use them to interactively browse through our tutorials and examples. You can always download the latest notebooks from the <a href="https://github.com/wradlib/wradlib/tree/master/notebooks">wradlib repository</a>.</p> <p>For those who do not know, yet, how to handle jupyter notebooks, we prepared a <a href="http://docs.wradlib.org/en/latest/jupyter.html">quick tutorial</a>. We also added a brief (and certainly incomplete) <a href="http://docs.wradlib.org/en/latest/notebooks/learnpython.html">intro to Python</a> for those who would like to have some entry point to that language. This intro will certainly be further developed in the&nbsp;future.</p> <p>In case you don&#8217;t want to use notebooks: straight Python scripts are distributed alongside the notebooks with <a href="https://pypi.python.org/pypi/wradlib">each new release &gt;= 0.9.0</a>.</p> <h3>Get the example data from the new wradlib data&nbsp;repository</h3> <p>We moved all the example data from the main <a href="https://github.com/wradlib/wradlib/">wradlib repository</a> to a new <a href="https://github.com/wradlib/wradlib-data">data repository</a>. In order to run the notebooks on your computer, you need to download the example data archive yourself, and extract it to any directory on your computer. Then you need to create an environment variable pointing to that directory. After that, the example notebooks will automagically pull the required example data from that directory. See <a href="http://docs.wradlib.org/en/latest/jupyter.html#how-can-i-get-the-example-data">here</a> for more detailed guidance on the&nbsp;process.</p> <h3>Further changes in wradlib&nbsp;0.9.0</h3> <p>Along with wradlib 0.9.0, we also released a couple of minor, though hopefully useful new features and fixes,&nbsp;e.g.:</p> <ul> <li><code>wradlib.io.read_RADOLAN_composite</code> can now read the new radolan <a href="https://github.com/wradlib/wradlib/pull/73"><span class="caps">FZ</span> product</a>,</li> <li><code>wradlib.io.readDX</code> can now read gzipped <span class="caps">DX</span>&nbsp;data,</li> <li><code>wradlib.io.read_Rainbow</code> was enhanced to read product pixmap data from rainbow5&nbsp;files,</li> <li>fixed <a href="https://github.com/wradlib/wradlib/issues/86">incompatibility issue with scipy 0.18.0</a>,</li> <li>and fixed some other&nbsp;issues.</li> </ul> <p>For more details on the new release, please visit our <a href="http://wradlib.org/wradlib-docs/0.9.0/">release notes</a>.</p> <h3>Updating to wradlib&nbsp;0.9.0</h3> <p>Do you want to safely check out the new version and still keep the old one? Then you can install wraldib 0.9.0 into a new conda environment, e.g. like&nbsp;this: </p> <div class="highlight"><pre><span></span>$ conda config --add channels conda-forge $ conda create --name wradlib090 <span class="nv">python</span><span class="o">=</span><span class="m">2</span>.7 $ activate wradlib090 $ conda install wradlib </pre></div> <p>You can drop the first line if you already added the conda-forge&nbsp;channel.</p> <p>For more details, or if you do not use Anaconda or conda, see our <a href="http://docs.wradlib.org/en/latest/gettingstarted.html">installation instructions</a>.</p> <p>In case you lost track of your Anaconda environments, you can&nbsp;use</p> <div class="highlight"><pre><span></span>$ conda --info envs </pre></div> <p>in order to get an overview. You can list all the packages (and their versions) in an environment (let&#8217;s say wradlib090)&nbsp;via</p> <div class="highlight"><pre><span></span>$ conda list --name wradlib090 </pre></div> <h3>For&nbsp;developers</h3> <p>Untagged <span class="caps">MICRO</span>-releases (0.9.1 and so on) are now released on <a href="https://testpypi.python.org/pypi/wradlib/">testpypi</a>. In the future, we hope to adopt this for <a href="https://anaconda.org/conda-forge/wradlib">conda-forge</a>, too. This might be interesting for users, too, for early checking of bug fixes (in case they do not want to use the bleeding edge&nbsp;code). </p>