Júlio Hoffimann

I think the issue of having pipelines here is separate from the issue of integrating with MLJ.jl. I personally find it more attractive to implement pipelines here as a standalone...

Also from the a community standpoint, it is much nicer to focus efforts on transforms in a separate hub that is detached from the huge MLJ.jl ecosystem that is already...

Just pointing out in case someone missed it... We addressed a couple of design issues in this package on a fresh new package called TableTransforms.jl, which supports composible, revertible pipelines:...

I second this suggestion, but I think the API in this package needs some refactoring first. Namely, I think all transforms should be detached from the data (table or array)...

> Can you elaborate a little? Is this related to #59 in that you have to have already determined the scaling parameters before the transform can be applied? I didn't...

For anyone interested, here is our attempt to provide transforms for general Tables.jl. We support revertible pipelines with very clean syntax. All the issues I raised above are solved in...

I can confirm that FFMPEG.jl build is failing on Travis/Windows. It is the reason my tests are failing in the platform: https://travis-ci.org/juliohm/GeoStatsBase.jl/jobs/584956834

This is a limitation of Travis build on Windows unfortunately: https://travis-ci.community/t/any-chance-of-providing-an-environment-with-desktop-experience/1024 thank you @giordano for sharing.

I don't think GeometryTypes.jl is maintained anymore. Take a look at Meshes.jl if you are doing geometric processing or GeometryBasics.jl if you are simply trying to visualize basic geometries.

This issue is still valid in Julia v0.5.