# A native Julia package for satellite images?

**URL:** <https://discourse.julialang.org/t/a-native-julia-package-for-satellite-images/44689>\
**Category:** Geo\
**Created:** [August 10, 2020, 2:23pm UTC](https://discourse.julialang.org/t/a-native-julia-package-for-satellite-images/44689 "2020-08-10T14:23:29Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![visr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/visr/32/17204_2.png) [@visr](https://discourse.julialang.org/u/visr)\
**Post date:** [August 17, 2020, 4:33pm UTC](https://discourse.julialang.org/t/a-native-julia-package-for-satellite-images/44689/10 "2020-08-17T16:33:17Z")

</div>

Yeah I agree. Rather than remote sensing / satellite I think the basis should be fully domain agnostic. And if we want we can sprinkle domain specific convenience functions on top in separate packages. This approach is also used for [GeoData.jl](https://github.com/rafaqz/GeoData.jl).

But indeed I also like AxisKeys.jl + NamedDims.jl. GeoArrays.jl uses an affine map rather than keys, but in AxisKeys ranges could be used instead. I have [xarray](http://xarray.pydata.org/en/stable/) in the back of my head, that is also why I posted here: [[ANN] FileTrees.jl -- easy everyday parallelism on trees of files - #6 by visr](https://discourse.julialang.org/t/ann-filetrees-jl-easy-everyday-parallelism-on-trees-of-files/44891/6). Because if we have nice composable packages for:

- named dimensions (e.g. NamedDims.jl)
- fancy array indexing (e.g. AxisKeys.jl)
- chunked arrays (e.g. DiskArrays.jl)
- and can process the chunks in parallel using Dagger.jl / FileTrees.jl / DataSets.jl (see FileTrees link above)

If we have that, we’d be essentially there. But we can take small steps, and not all components are always needed (such as lazy / parallel operations).

---

_[View the full topic](https://discourse.julialang.org/t/a-native-julia-package-for-satellite-images/44689)._