Rafael Schouten

Ok. well lets put in some time to get `GeoInterface.convert` working everywhere, then think about package level conversions. I don't think we can delete the `Base.convert` methods here though, probably...

Meshes doesnt want to for some kind of geometric purity reasons. There is some package that type pyrates it in.

It means `GI.convert` cant work

It would be good to use these tests, but the current (newer) implementation is lazy over rings which is much faster for many applications than separating out the polygons. I'm...

This is not longer a problem as `GeoInterface.getring` can access rings without sorting

@dgleich if you ever wanted to PR this change it would be useful.

Note that I've implemented this for ArchGDAL and LibGEOS, it's just waiting on the wrapper types PR for testing. https://github.com/JuliaGeo/LibGEOS.jl/pull/156 https://github.com/yeesian/ArchGDAL.jl/pull/366 It's surprisingly easy to implement.

The LibGEOS example works now

@evetion do you know witch packages use `Vector` rather than `AbstractVector` ? lets just swap that.

So we really have to materialize at least the geometries from JSON3.jl to real Arrays. Although keeping the `FeautureCollection` itself lazy may be best. See https://github.com/quinnj/JSON3.jl/issues/250 That would solve this...