Refactor into MapTilesBase.jl

[asinghvi17]

Since the name is so natural it would be nice to have MapTiles.jl be a toplevel package that includes Downloads.jl/HTTP.jl, TileProviders.jl and some future VectorTiles.jl to be a toplevel package, and then include some of the downloading / caching functionality from Tyler.jl there.

Then we can have the base functionality that is currently in MapTiles hosted in MapTilesBase.jl. I don't mind making it a monorepo and potentially even stuffing TileProviders.jl in there as well.

What do you think?

@visr @evetion @rafaqz

[rafaqz]

Is there a concrete problem with putting Downloads.jl, HTTP.jl and TileProviders.jl dependencies directly in MapTiles.jl without adding MapTilesBase.jl?

I don't think it has any dependents that don't use those packages anyway, but maybe there is some reason I'm not aware of.

[asinghvi17]

MapTilesBase would then be an interface that PyramidScheme etc can use

Maybe it should be MapTilesInterface then

[rafaqz]

Makes sense,in that case I'm happy with either Base or Interface

[visr]

Yeah sounds like a good plan. Having them together in a monorepo is probably a bit easier to handle.