DockerImagesMeta - Revision history

Doublebyte: /* Projects with many images */

2016-11-23T10:27:33Z

Projects with many images

Nuest: fix heading

2016-09-21T09:10:59Z

fix heading

Nuest: add hale

2016-08-30T10:15:51Z

add hale

Nuest at 06:34, 26 August 2016

2016-08-26T06:34:00Z

Nuest at 06:28, 26 August 2016

2016-08-26T06:28:41Z

Nuest: add initial list of tasks and notes

2016-08-26T06:25:00Z

add initial list of tasks and notes

New page

This page contains meta-information about the list of Docker images at DockerImages. It can be used to collect tasks and information about images not present in the main list.

== TODO ==

'''Help welcome!'''

* SciDB: https://github.com/albhasan/docker_scidb
* https://hub.docker.com/u/gisjedi/
* landsat stuff, see <https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=0&q=landsat&starCount=0>
* Python geo: https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=0&q=python+geo&starCount=0
* https://www.locationtech.org/list-of-projects
* geomesa - https://locationtech.org/mhonarc/lists/geomesa-users/msg00686.html and https://hub.docker.com/r/jamesmcclain/geomesa/ could be starting points
* ''whole of quai.io''
* GRASS with UI, see https://github.com/wenzeslaus/grass-gis-docker

== Images and organisations with geo/GIS relation ==

These images are not yet on the list - should they be?

* R: [Rocker](https://hub.docker.com/r/rocker)
* Geospatial Jupyter: <https://hub.docker.com/r/weihanglo/geo-jupyter/>
* [GeoDocker Cluster](https://github.com/geodocker/geodocker) is a collection of Docker images encapsulating a distributed geo-processing platform based on GeoTrellis, GeoMesa, and GeoWave. Images are [on quay.io](https://quay.io/organization/geodocker).

== docker-compose configurations ==

Should these be a separate list?

* https://github.com/gisjedi/docker-compose-modis
* https://github.com/gisjedi/docker-compose-geodata

== Sources ==

* Docker Hub searches for "gis" and "geo", Aug 2016
* https://2016.foss4g-na.org/session/spatial-data-processing-docker (see slides)

## Sorted out

The following images have been sorted out during the searches. It will be worth rechecking them from time to time, as issues such as missing documentation can quickly be mitigated by maintainers.

* https://hub.docker.com/r/kaiserpelagic/gdal-tile/ (no docs)
* https://hub.docker.com/r/jamesshoebox/nominatim-web/ (no Dockerfile)
* https://hub.docker.com/r/nicopace/nominatim-docker/ (did not start properly)
* https://hub.docker.com/r/tdgp/gdal/ (no Dockerfile)
* https://hub.docker.com/r/ordnancesurvey/nominatim-runner/ (no instructions, GitHub repo is gone)
* https://github.com/geo-data/openstreetmap-website-docker (old!)
* https://hub.docker.com/r/radiantbluetechnologies/rialto-cesium/ (could be interesting fork, but no usage instructions)
* https://hub.docker.com/r/pamtrak06/grass7-ubuntu14.04/ (unclear why apache is needed, instructions end with docker exec - not well designed)
* https://github.com/dit4c/dockerfile-dit4c-container-qgis (by [DIT4C](http://dit4c.github.io/), 3rd party, based on `dit4c/dit4c-container-x11:debian`, no README/usage instructions)
* https://hub.docker.com/r/kaiserpelagic/mapnik2.3/ (no Dockerfile, no instructions)
* https://hub.docker.com/r/tnris/docker-node-mapnik/ (no Dockerfile, no instructions)
* https://hub.docker.com/r/instagis/mapnik/ (no Dockerfile, partial instructions)
* https://hub.docker.com/r/massimo1962/ckan-spatial/ (no Dockerfile, coarse instructions)
* https://hub.docker.com/r/agrian/ubuntugis/~/dockerfile/ (coarse instructions, actually not using ubuntugis)
* https://hub.docker.com/r/turnkeylinux/sahana-eden-14.1/ (and other repos under the same username) - see https://www.turnkeylinux.org/blog/14.0-optimized-builds-pt2-proxmox-opennode-docker#docker (no Dockerfile)
* https://hub.docker.com/r/segoerke (Sebastian Goerke) has geonetwork, geoserver, but no Dockerfiles
* https://hub.docker.com/r/jusabatier/georchestra_geonetwork/ (warfiles are mounted at build time - not transferable, not documented)
* https://hub.docker.com/r/ioos/catalog-docker-pycsw/ by [IOOS](https://ioos.us/) (no docs; tailored to IOOS deployment, also CKAN as base image...)
* https://github.com/GeographicaGS/Docker-PyCSW (not on Docker Hub)
* https://hub.docker.com/u/mapsherpa/ (no Dockerfiles, not documentation)
* https://hub.docker.com/r/kevensen/docker-geosuite/ (no working builds)

@@ Line 27: / Line 27: @@
 * osm2pgwsl: https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=0&q=osm2pgsql&starCount=0
 * CartodB, see https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=0&q=cartodb&starCount=0
 == Images and organisations with geo/GIS relation ==

@@ Line 16: / Line 16: @@
 * hale: https://hub.docker.com/u/wetransform/ and https://github.com/halestudio/hale-cli/issues/15#issuecomment-242744229
-=== Projects with many images
+== Projects with many images ==
 The following searches on Docker Hub (and other registries, if possible!) result in a relatively large number of hits. Contributions in checking the "long tail" of these lists are highly welcome, so far only the most starred and downloaded images have been considered.
@@ Line 27: / Line 27: @@
 * osm2pgwsl: https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=0&q=osm2pgsql&starCount=0
 * CartodB, see https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=0&q=cartodb&starCount=0
 == Images and organisations with geo/GIS relation ==

@@ Line 14: / Line 14: @@
 * ''whole of quai.io''
 * GRASS with UI, see https://github.com/wenzeslaus/grass-gis-docker
 === Projects with many images

@@ Line 45: / Line 45: @@
 == Sources ==
-* Docker Hub searches for "gis" and "geo", Aug 2016
+The following searches have been applied so far (please add date and sign)
 * https://2016.foss4g-na.org/session/spatial-data-processing-docker (see slides)
-## Sorted out
+=== Criteria ===
 The following images have been sorted out during the searches. It will be worth rechecking them from time to time, as issues such as missing documentation can quickly be mitigated by maintainers.