https://wiki.osgeo.org/w/api.php?action=feedcontributions&feedformat=atom&user=Wiki-Brian+H+WilsonOSGeo - User contributions [en]2026-04-13T01:43:14ZUser contributionsMediaWiki 1.35.9https://wiki.osgeo.org/w/index.php?title=California_Chapter_Membership_Page&diff=118694California Chapter Membership Page2018-12-09T21:50:47Z<p>Wiki-Brian H Wilson: /* Members List */ removed myself</p>
<hr />
<div>== Members List ==<br />
Name(IRC/Chat Handle) - Short Description <br />
<br />
*[[User:TaraAthan|Tara Athan]]<br />
*[[User:Lbali|Lokesh Bali]] | Richmond Police<br />
*[[User:Osospdb|Paul Bartsch (osospdb)]] | UC Santa Barbara | Cal Poly - SLO Alumni<br />
*[[User:Dmbianco|David Bianco (talldave)]] - US Army Corps of Engineers, San Francisco<br />
*[[User:DylanBeaudette|Dylan Beaudette]] | CA Soil Resource Lab - UC Davis<br />
*[[User:SunburnedSurveyor|Landon Blake(Sunburned Surveyor)]]<br />
*[[User:Rburhum|Ragi Yaser Burhum(rburhum)]] | Self<br />
*[[User:TheSteve0|Steve Citron (TheSteve0)]] - Pousty - ICF/Jones&amp;Stokes, San Jose<br />
*[[User:StaceyEllis|Stacey Ellis]] - UC Davis<br />
* Brian Galey | Geospatial Innovation Facility, UC Berkeley<br />
*[[User:Glennon|Alan Glennon]] - spatial@ucsb<br />
*[[User:Darkblue b|Brian Hamlin (darkblue_b)]] - Berkeley<br />
*[[User:Mdhancher|Matt Hancher]] - Google Earth Engine - interested in Bay Area local activities<br />
*[[Jeff Hobbs]] | San Jose Water Company - San Jose, CA<br />
*[[User:Hollander|Allan Hollander ]]<br />
*[[User:ortelius|Jeffrey Johnson]] - Consultant<br />
*[[User:PacificGeodata|Matt Lamborn]] | Pacific Geodata - Napa, CA<br />
*[[User:J03lar50n|Joe Larson (j03lar50n)]] | CAL FIRE / San Luis Obispo County Fire | Cal Poly - SLO Alumni<br />
*[[User:Jlivni|Josh Livni (jlivni)]] Google Developer Relations (San Francisco)<br />
*[[User:Wildintellect|Alex Mandel (Wildintellect)]] - UC Davis<br />
*[[User:Cgs bob|Bob Moskovitz (bmoskovi)]]<br />
*[[User:jmunowitch|Jeffrey Munowitch]] - Ceres Imaging<br />
* [[User:brylie|Brylie Oxley]] | (brylie on freenode) - Nevada City, CA<br />
* Bborie Park | Center for Vectorborne Diseases, UC Davis<br />
*[[User:MPfister|Marc Pfister (drwelby)]] | ENPLAN (Redding)<br />
* [[User:brainey|Bill Rainey]] - Santa Clara, CA<br />
*[[User:Jsonnentag|Jeffrey Sonnentag]] - L&L Environmental, Inc., Redlands/Riverside, CA<br />
*[[User:MicheleTobias|Michele Tobias]] - UC Davis<br />
*[[User:geomercurial|Mike Treichler]] - Core-Mark International<br />
* Frank Warmerdam | Google<br />
*[[User:Cwhitney|Chris Whitney (Cwhitney)]] - UC San Diego / NASA ISS EarthKAM<br />
*[[User:Bwoodall|Bill Woodall(bwoodall)]] San Diego<br />
<br />
== Navigation ==<br />
<br />
[http://wiki.osgeo.org/wiki/California California Chapter Wiki Home Page]<br />
<br />
<br />
<br />
[[Category: Local Chapters]]<br />
<br />
[[Category: California]]</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=California_Chapter_Membership_Page&diff=109245California Chapter Membership Page2017-09-10T01:10:03Z<p>Wiki-Brian H Wilson: /* Members List */ Added myself + sorted into alphabetical order by last name.</p>
<hr />
<div>== Members List ==<br />
Name(IRC/Chat Handle) - Short Description <br />
<br />
*[[User:TaraAthan|Tara Athan]]<br />
*[[User:Lbali|Lokesh Bali]] | Richmond Police<br />
*[[User:Osospdb|Paul Bartsch (osospdb)]] | UC Santa Barbara | Cal Poly - SLO Alumni<br />
*[[User:Dmbianco|David Bianco (talldave)]] - US Army Corps of Engineers, San Francisco<br />
*[[User:DylanBeaudette|Dylan Beaudette]] | CA Soil Resource Lab - UC Davis<br />
*[[User:SunburnedSurveyor|Landon Blake(Sunburned Surveyor)]]<br />
*[[User:Rburhum|Ragi Yaser Burhum(rburhum)]] | Self<br />
*[[User:TheSteve0|Steve Citron (TheSteve0)]] - Pousty - ICF/Jones&amp;Stokes, San Jose<br />
*[[User:StaceyEllis|Stacey Ellis]] - UC Davis<br />
* Brian Galey | Geospatial Innovation Facility, UC Berkeley<br />
*[[User:Glennon|Alan Glennon]] - spatial@ucsb<br />
*[[User:Darkblue b|Brian Hamlin (darkblue_b)]] - Berkeley<br />
*[[User:Mdhancher|Matt Hancher]] - Google Earth Engine - interested in Bay Area local activities<br />
*[[Jeff Hobbs]] | San Jose Water Company - San Jose, CA<br />
*[[User:Hollander|Allan Hollander ]]<br />
*[[User:ortelius|Jeffrey Johnson]] - Consultant<br />
*[[User:PacificGeodata|Matt Lamborn]] | Pacific Geodata - Napa, CA<br />
*[[User:J03lar50n|Joe Larson (j03lar50n)]] | CAL FIRE / San Luis Obispo County Fire | Cal Poly - SLO Alumni<br />
*[[User:Jlivni|Josh Livni (jlivni)]] Google Developer Relations (San Francisco)<br />
*[[User:Wildintellect|Alex Mandel (Wildintellect)]] - UC Davis<br />
*[[User:Cgs bob|Bob Moskovitz (bmoskovi)]]<br />
*[[User:jmunowitch|Jeffrey Munowitch]] - Farallon Geographics<br />
* [[User:brylie|Brylie Oxley]] | (brylie on freenode) - Nevada City, CA<br />
* Bborie Park | Center for Vectorborne Diseases, UC Davis<br />
*[[User:MPfister|Marc Pfister (drwelby)]] | ENPLAN (Redding)<br />
* [[User:brainey|Bill Rainey]] - Santa Clara, CA<br />
*[[User:Jsonnentag|Jeffrey Sonnentag]] - L&L Environmental, Inc., Redlands/Riverside, CA<br />
*[[User:MicheleTobias|Michele Tobias]] - UC Davis<br />
*[[User:geomercurial|Mike Treichler]] - Core-Mark International<br />
* Frank Warmerdam | Google<br />
*[[User:Cwhitney|Chris Whitney (Cwhitney)]] - UC San Diego / NASA ISS EarthKAM<br />
*[[User:Brian H Wilson|Brian H Wilson]] - Cotati CA<br />
*[[User:Bwoodall|Bill Woodall(bwoodall)]] San Diego<br />
<br />
== Navigation ==<br />
<br />
[http://wiki.osgeo.org/wiki/California California Chapter Wiki Home Page]<br />
<br />
<br />
<br />
[[Category: Local Chapters]]<br />
<br />
[[Category: California]]</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=Talk:DockerImages&diff=109192Talk:DockerImages2017-09-08T17:56:03Z<p>Wiki-Brian H Wilson: </p>
<hr />
<div>I converted the first column using "rowspan" tags so that project (for example PostGIS) can span more than one row.<br />
I made the projects be links, but it's not done yet. Some are links to non-existent wiki pages, others are direct links outside the wiki.<br />
Since this wiki is not a comprehensive index of all things GIS it's probably okay to mix it up and have some be internal links when the pages exist and some be links directly to the projects (eg gdal.org)<br />
<br />
Oh - Also I started putting the projects in alphabetical order!</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=Talk:DockerImages&diff=109191Talk:DockerImages2017-09-08T17:55:08Z<p>Wiki-Brian H Wilson: Created page with "I converted the first column using "rowspan" tags so that project (for example PostGIS) can span more than one row. I made the projects be links, but it's not done yet. Some a..."</p>
<hr />
<div>I converted the first column using "rowspan" tags so that project (for example PostGIS) can span more than one row.<br />
I made the projects be links, but it's not done yet. Some are links to non-existent wiki pages, others are direct links outside the wiki.<br />
Since this wiki is not a comprehensive index of all things GIS it's probably okay to mix it up and have some be internal links when the pages exist and some be links directly to the projects (eg gdal.org)</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=DockerImages&diff=109110DockerImages2017-09-08T05:37:17Z<p>Wiki-Brian H Wilson: </p>
<hr />
<div><br />
The goal of this list is to provide an overview of OSGeo-related Docker images to leverage the advantages of containerization across the geoinformatics communities.<br />
<br />
You want to learn how this list was created? See [[DockerImagesMeta]].<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Project !! Image on Hub !! Maintainer !! Link !! Specific goals / target users? !! License !! Base image !! Comments<br />
<br />
|-<br />
| [[Cartaro]] || <code>geops/cartaro</code> || [http://cartaro.org/ Cartaro] || https://www.drupal.org/node/2579221 || - || - || <code>ubuntu:14.04</code> || good docs, works<br />
<br />
|-<br />
| [[Deegree]] ||<code>tfr42/deegree</code> || Deegree TMC || https://github.com/tfr42/deegree-docker || - || - || <code>tomcat:8-jre7</code> and<code> java:8</code> (which is <code>debian:jessie</code>) || also docker-compose with PostGIS, [https://docs.google.com/document/d/1DEcTxNKMtJD3LjONKz4O9umowTh3KnMfDB4cuDYBGfI/edit#heading=h.c7bibbfs1pv FOSS4G workshop documentation]<br />
<br />
|-<br />
| [[geoblacklight]] || <code>geoblacklight/geoblacklight</code> || [http://geoblacklight.org GeoBlacklight] || https://github.com/geoblacklight/geoblacklight-docker || - || - || <code>rails:4.2.3</code> || detailed instructions, including image with test data; see also [https://hub.docker.com/r/geoblacklight/geoserver/ docker-compose configuration] and open at http://localhost/catalog<br />
<br />
|-<br />
| [[geogig]] || <code>kartoza/geogig</code> || kartoza/Tim Sutton, 3rd party || https://github.com/kartoza/docker-geogig || - || - || <code>ubuntu:14.04</code> || clear instructions; untested<br />
|-<br />
| [[geogig]] server and cli || <code>jasoncallaway/geogig-server</code> and<code> jasoncallaway/geogig-cli</code> || Jason Callaway, 3rd party || https://github.com/jason-callaway || - || - || <code>centos:latest</code> || under development, untested<br />
<br />
|-<br />
| [http://geomoose.org GeoMOOSE] || Build yourself || [http://www.geomoose.org/ GeoMOOSE] || https://github.com/geomoose/docker-geomoose || demo and [http://www.geomoose.org/releases/2.9.0.html#release development environment} || MIT || <code>ubuntu:trusty</code> || must build yourself, but very good documentation<br />
<br />
|-<br />
| [[GeoServer]] || <code>winsent/geoserver</code> || [https://github.com/winsento) winsento]/"ololoteam", independent || https://bitbucket.org/ololoteam/geoserver-docker || unclear - production? || - || | uses Oracle Java; well documented<br />
<br />
|-<br />
| [[Jupyter Notebook]] || <code>dcal12/python-geospatial</code> || Doug Callaway/DCAL12 || https://github.com/DCAL12/docker-python-geospatial || - || <code>jupyter/base-notebook:latest</code> || works, very small dockerfile but lacks docs/examples<br />
<br />
|-<br />
| rowspan="2" | mapcache || <code>pamtrak06/mapcache-ubuntu14.04</code> || - || https://github.com/pamtrak06/mapcache-ubuntu14.04 || - || - || <code>pamtrak06/ubuntu14.04-apache2-python</code> || ... untested<br />
|-<br />
| <code>camptocamp/mapcache</code> || [https://github.com/camptocamp camptocamp] || https://github.com/camptocamp/docker-mapcache || - || - || <code>debian:stable</code> || ... untested<br />
<br />
|-<br />
| [[MapFish]] Print || <code>unknownlighter/mapfish-print</code> || Maintainer || https://bitbucket.org/lighter/mapfish-print || - || - || <code>tomcat:8-jre7</code> || No documentation, but just open http://localhost:8080/<br />
|-<br />
| [[MapGuide]] || <code>jumpinjackie/mapguide-base</code> || Jackie Ng || https://github.com/jumpinjackie/mapguide-centos-docker || as a base image? || - || <code>centos:centos6</code> || Dockerfile is missing command, run with <code>docker run --rm -it -p 8008:8008 jumpinjackie/mapguide-base /usr/bin/supervisord</code>, but only shows [https://github.com/jumpinjackie/mapguide-centos-docker/issues/4 error]<br />
<br />
|-<br />
| [[MapServer]] || <code>geodata/mapserver</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/mapserver-docker || mapserver with a "broad range of options enabled including a comprehensive GDAL library" || - || <code>geodata/gdal:latest</code> || good instructions<br />
<br />
|-<br />
| [[neo4j-spatial]] || <code>jeffreyjharris/docker-neo4j-spatial</code> || Kenny Bastani, 3rd party || https://github.com/jeffreyjharris/docker-neo4j-spatial || - || - || <code>java:openjdk-8-jdk</code> || open at <http://localhost:7474/browser/>; extension/fork of <code>kbastani/docker-neo4j</code><br />
<br />
|-<br />
| rowspan="4" | [[PostGIS]] || <code>mdillon/postgis</code> || Mike Dillon/Appropriate Computing || https://github.com/md5/docker-postgis || - || file<code> LICENSE</code> || <code>postgres:9.5</code> || simple and good<br />
|-<br />
| <code>neowaylabs/postgis</code> || NeowayLabs, 3rd party || https://github.com/NeowayLabs/docker-postgis || - || License || <code>neowaylabs/baseimage</code> || installs from http://apt.postgresql...<br />
|-<br />
| <code>camptocamp/postgis</code> || capmtocamp, 3rd party || https://github.com/camptocamp/docker-postgis || base image for own configuration || - || <code>postgres:9.5</code> || installs from sources, documentation recommends usage as a base image<br />
|-<br />
| <code>kartoza/postgis</code> || kartoza/Tim Sutton, 3rd party || https://github.com/kartoza/docker-postgis || Ready to run PostGIS geospatial databaseg || - || <code>debian:stable</code> || installs from http://apt.postgresql<br />
<br />
|-<br />
| rowspan="3" | [[QGIS Desktop]] || <code>kartoza/qgis-desktop</code> || kartoza/Tim Sutton, 3rd party || https://github.com/kartoza/docker-qgis-desktop || complete replacement for usage on Desktop, see http://kartoza.com/qgis-desktop-in-docker/ || - || <code>kartoza/qgis-base</code> || good instructions, including docker-compose with a postgis server; [https://hub.docker.com/u/qgis/ QGIS community is on Docker Hub] but not with a QGIS image<br />
<br />
|-<br />
| <code>timcera/qgis-desktop-ubuntu</code> || timcera, 3rd party || https://github.com/timcera/qgis-desktop-ubuntu || "Instead of compiling, this image is [..] latest QGIS" || - || <code>ubuntu:xenial</code> and UbuntuGIS repos || instructions for run script including mounting as setting user, untested but looks promising<br />
|-<br />
| <code>elpaso/qgis-testing-environment</code> || elpase, 3rd party || - || Simple container for testing QGIS Desktop and for executing unit tests inside a real QGIS instance || - || ? || incl. instructions for running on Travis, uses xhost forwarding (dont forget to<code> xhost -</code> when youre done)<br />
<br />
|-<br />
| rowspan="2" | [[QGIS Server]] || <code>kartoza/qgis-server</code> || kartoza/Tim Sutton || https://github.com/kartoza/docker-qgis-server || complete replacement for usage on Desktop, see http://kartoza.com/qgis-desktop-in-docker/ || - || <code>kartoza/qgis-desktop</code> || good instructions<br />
|-<br />
| <code>kartoza/qgis-server</code> || kartoza, 3rd party || https://github.com/kartoza/docker-qgis-server || A simple docker container that runs QGIS Server || - || <code>kartoza/qgis-desktop</code> || - <br />
<br />
|-<br />
| QGIS MapServer + web client || <code>opengisch/qgis-server-webclient</code> || opengis.ch, 3rd party || https://github.com/opengisch/docker-qgis-server-webclient || - || - || <code>debian:stable</code> || [https://hub.docker.com/u/qgis/ QGIS community is on Docker Hub] but not with a QGIS image<br />
<br />
|-<br />
| [[tileserver-mapnik]] || <code>klokantech/tileserver-mapnik</code> || [https://hub.docker.com/u/klokantech/ klokantech] || https://github.com/klokantech/tileserver-mapnik || Mapnik based map tileserver generating raster tiles from MapBox Studio project & custom vector tiles || file<code> License</code> || <code>node:0.10</code> || installation instructions just refer to the Dockerfile - nice! see [http://osm2vectortiles.org/docs/serve-raster-tiles-docker instructions by osm2vectortiles]<br />
<br />
|-<br />
| rowspan="2" | [[gdal]] || <code>geodata/gdal</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/gdal-docker || build specific versions of gdal from source, see [https://hub.docker.com/r/geodata/gdal/tags/ tags] || - || <code>ubuntu:trusty</code> || some forks, e.g. [https://hub.docker.com/r/geometalab/gdal-debian/ geometalab], compare on GitHub before use<br />
|-<br />
| <code>spara/gdal_ef</code> || 3rd party || https://github.com/spara/gdal-docker || demo FOSS4G-NA 2016 || - || <code>ubuntu:trusty</code> || -<br />
<br />
|-<br />
| [[pdal]] || <code>pdal/pdal</code> || PDAL maintainers || http://www.pdal.io/workshop/docker.html || PDAL stands on the shoulders of giants. It uses GDAL, GEOS, and many other dependencies. Because of this, it is very challenging to build it yourself. We could easily burn an entire workshop learning the esoteric build miseries of PDAL and all of its dependencies. Fortunately, Docker will allow us to use a fully-featured known configuration to run our examples and exercises without having to suffer so much. || License || <code>pdal/dependencies</code>, [https://github.com/PDAL/PDAL/blob/master/scripts/docker/dependencies/Dockerfile which is based on]<code> ubuntu:15.04</code> || great docs; build libs from source;<br />
<br />
|-<br />
| [[saga]] || <code>ntonshevtsov/saga-gis</code> || || - || - || - || <code>-</code> || no Dockerfile, but works! Use <code>xhost +</code> before and<code> xhost -</code> after<br />
<br />
|-<br />
| [[Grass]] || <code>geodata/grass</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/grass-docker || specific subservsion version of grass compiled against specific gdal version || - || <code>ubuntu:trusty</code> || good instructions for usage and build, GRASS is build outside of container, see Makefile in repo<br />
<br />
|-<br />
| rowspan="2" | [[opticks]] || <code>toddstavish/opticks</code> || Todd Stavish || https://github.com/toddstavish/Dockerfiles || - || - || <code>ubuntu:15.04</code> || run with <code>docker run -i -t -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=unix$DISPLAY -v $(pwd)/tmp:/home/data toddstavish/opticks</code><br />
|-<br />
| <code>tclarke/opticks</code> || Trevor R.H. Clarke/Opticks || https://github.com/tclarke/opticks-docker || - || - || <code>centos:centos7</code> || good documentation, error on run;<br />
<br />
|-<br />
| rowspan="2" | [[CartoDB]] || <code>sverhoeven/cartodb</code> || Stefan Verhoeven, 3rd party || https://github.com/sverhoeven/docker-cartodb || fully working cartodb development solution without the installation hassle. || - || <code>ubuntu:14.04</code> || large image; includes multiple "apps" (postgres, node, redis-server); use together with nginx proxy in container: https://hub.docker.com/r/spawnthink/cartodb-nginx/<br />
|-<br />
| <code>akvo/akvo-provisioning</code> || Akvo, 3rd party || https://github.com/akvo/akvo-provisioning/tree/develop/docker/cartodb || what's needed to dockerize the five main components CartoDB || - || - || multiple images, and docker-compose orchestration<br />
<br />
|-<br />
| rowspan="2" | [[Nominatim]] || <code>helvalius/nominatim-docker-development</code> || helvalius, 3rd party || https://github.com/helvalius/nominatim-docker || builds current master or development || - || <code>ubuntu:14.04</code> || includes PG database and apache2<br />
|-<br />
| <code>mediagis/nominatim</code> || [https://github.com/winsento winsento]/mediagis, 3rd party || https://github.com/mediagis/nominatim-docker || "100% working container" || - || <code>ubuntu:trusty</code> || fork by [https://github.com/cartography/nominatim-docker cartography], test data is in Monaco<br />
<br />
|-<br />
| [[osmtools]] || <code>mediagis/osmtools</code> || [https://github.com/winsento winsento]/mediagis, 3rd party || https://github.com/mediagis/osmtools || package CLI tools osmconvert, osmfilter, osmupdate || - || <code>ubuntu:latest</code> || fork by [https://hub.docker.com/r/cartography/osmtools/ cartography]<br />
|-<br />
| [[osrm]] (Frontend, Backend) || <code>cartography/osrm-backend-docker</code> and<code> docker pull cartography/osrm-frontend-docker</code> || Project-OSRM || http://project-osrm.org/ || - || LICENSE.txt || <code>ubuntu:trusty</code> || untested, documentation seems good<br />
<br />
|-<br />
| rowspan="2" | [[osmosis]] || <code>farberg/openstreetmap-osmosis-docker</code> || Dennis Pfisterer || https://github.com/pfisterer/openstreetmap-osmosis-docker || - || - || <code>debian:jessie</code> || not much, but works<br />
|-<br />
| <code>ferimer/osmosis</code> || [https://ferimer.es/ Ferimer] || https://github.com/ferimer/docker-osmosis || - || - || <code>debian:latest</code> || not much, but works; "latest" tag missing, not well maintained<br />
<br />
|-<br />
| [[osmosis]] + Jenkins || <code>henkel/jenkins-slave-osmosis</code> || Philipp Henkel || https://github.com/henkel/jenkins-slave-osmosis || presumably for automation? || - || <code>debian:latest</code> || untested (quite specific use case)<br />
<br />
|-<br />
| [[osm2pgsql]] || <code>openfirmware/osm2pgsql</code> || James Badger/openfirmware || https://github.com/openfirmware/docker-osm2pgsql || A Docker image with osm2pgsql, the tool for importing OpenStreetMap data into a Postgresql database. || - || <code>debian:wheezy</code> || [https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=1&q=osm2pgsql&starCount=0 many images exist], untested, could profit from docs including postgres<br />
<br />
|-<br />
| OSM-ready postgres || <code>openfirmware/postgres-osm</code> || James Badger/openfirmware || https://github.com/openfirmware/docker-postgres-osm |The base postgres image from Docker with extensions for importing OpenStreetMap data. || - || <code>postgres:9.3.6</code> || README says it is unfinished<br />
<br />
|-<br />
| [[r-spatial]] || <code>achubaty/r-spatial-base</code> and<code> achubaty/r-spatial-devel</code> || Alex Chubaty || https://github.com/achubaty/rocker-files || extend Rocker base image with spatial packages || License || <code>rocker/r-base:latest</code> respectively<code> rocker/r-devel:latest</code> || -<br />
<br />
|-<br />
| ubuntugis-docker || <code>javimarlop/ubuntugis-docker</code> || Martinez-Lopez Javier, 3rd party || https://github.com/javimarlop/ubuntugis-docker || VM using Docker for Geospatial Analysis || - || <code>ubuntu:14.04</code> || untested; really installs a lot of stuff, not best use of Docker<br />
|-<br />
| [[mapnik]] || <code>mapsquare/mapnik3</code> || [https://hub.docker.com/u/mapsquare/ mapsquare] || https://github.com/jawg/docker-mapnik3 || - || - || <code>debian:jessie</code> || versions as tags; untested, partial instructions only<br />
|-<br />
| [[GeoNode]] || <code>openmarble/arch-geonode</code> || Maintainer || https://github.com/OpenMarble/geomelting || - || - || <code>openmarble/arch-imaging:latest</code> || lacking documentation, run with<code> docker run -it --rm -p 8000:8000 -p 8080:8080 openmarble/arch-geonode</code> and open GeoNode at http://localhost:8000/ (login with admin/admin) or GeoServer at http://localhost:8080/geoserver/web/<br />
|-<br />
| [[geosuite]] || <code>devdattat/docker-opengeosuite</code> || Devdatta Tengshe || https://github.com/devdattaT/docker-OpenGeoSuite || - || MIT || <code>ubuntu:14.04</code> || incomplete instructions; Dockerfile has no start command... cannot work<br />
<br />
|-<br />
| cesium terrain server and cesium.js || <code>geodata/cesium-terrain-server</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/cesium-terrain-server || - || - || <code>phusion/baseimage:0.9.15</code> (Ubuntu 14.04 Trusty Tahr) || good documentation, untested because tiles must be created first<br />
<br />
|-<br />
| rowspan="2" | [[GeoNetwork]] || <code>oscarfonts/geonetwork</code> || Oscar Fonts (geomati.co) || https://github.com/oscarfonts/docker-geonetwork || - || - || <code>tomcat:8-jre8</code> || reasonable documetation, newer fork of [https://hub.docker.com/r/eliotjordan/geonetwork-docker/ elitojordan], open at http://localhost:8888/geonetwork<br />
|-<br />
| <code>geonetwork</code> || Official /Joana Simoes, [https://www.geocat.net/ GeoCat] || https://github.com/geonetwork/docker-geonetwork || <br />
* First-time users: try GeoNetwork; <br />
* Advanced users: Run specific version of GeoNetwork, with an external PostgreSQL DB backend<br />
|| Specified on the<code> README</code> file || <code>tomcat:8</code> || Follows the [https://github.com/docker-library/official-images best practices for official Docker images]. Official documentation [https://github.com/docker-library/docs/tree/master/geonetwork here]. <br />
<br />
|-<br />
| [[landsat-util]] || <code>developmentseed/landsat-util</code> || [https://developmentseed.org/ developmentseed] || https://pythonhosted.org/landsat-util/installation.html?highlight=docker#docker || - || - || <code>ubuntu:14.04</code> || has several related images, see https://hub.docker.com/u/developmentseed/<br />
<br />
|-<br />
| [[opendronemap]] || <code>opendronemap/opendronemap</code> || [https://github.com/OpenDroneMap OpenDroneMap] || https://github.com/OpenDroneMap/OpenDroneMap || OpenDroneMap is a tool to postprocess drone, balloon, kite, and street view data to geographic data. || - || <code>ubuntu:14.04</code> || not tested, but good documentation available<br />
<br />
<br />
|-<br />
| rowspan="4" | [[pycsw]] || <code>geocontainer/pycsw</code> || [http://geocontainers.org/ Geocontainers] || https://github.com/geocontainers/dockerfiles || - || - || <code>alpine:3.4</code> || very short documenation only, simply open CSW Capabilities at http://<ip>/<br />
|-<br />
| <code>birdhouse/pycsw</code> || [http://bird-house.github.io/ Birdhouse] || https://github.com/bird-house/birdhouse-playground || - || - || <code>birdhouse/bird-base:latest</code> || no docs; only pycsw 1.10.3, but Capabilities available at http://<ip>:8082/csw?service=CSW&request=GetCapabilities<br />
|-<br />
| <code>datagov/catalog-pycsw</code> || [https://github.com/GSA U.S. General Services Administration] || datagov/catalog-pycsw || [https://github.com/GSA/catalog-app production use for catalog.data.gov] || - || <code>ubuntu:14.04</code> || tailored to their installation, docs lacking; run with<code> </code> and should be available at http://<ip>/csw - does not work!<br />
<br />
|-<br />
| <code>axiom/docker-pycsw</code> || [http://axiomdatascience.com/ Axiom Data Science] || https://github.com/axiom-data-science/docker-pycsw || testing as well as production || - || <code>phusion/baseimage:0.9.18</code> (Ubuntu++) || good documentation, [https://github.com/axiom-data-science/docker-pycsw/issues/1 currently not working]<br />
<br />
|-<br />
| pyWPS4-demo || <code>geocontainer/pywps/4/pywps-demo</code> || [http://geocontainers.org/ Geocontainers] || https://github.com/geocontainers/dockerfiles || - || MIT || <code>alpine/latest</code>|| Good docs https://pywps.readthedocs.io/en/latest/ <br />
<br />
|-<br />
| [[Zoo-Project]] || <code>yoms/zoo-project</code> || yomd || https://github.com/yoms/zoo-project || - || file<code> LICENSE</code> || <code>centos:6.7</code> || no documentation, seems to start but don't know where to look next<br />
<br />
|-<br />
| [[Team Engine]] || <code>tfr42/teamengine</code> || tfr42 || https://hub.docker.com/r/tfr42/teamengine/ || - || - || <code>-</code> || Dockerfile missing, but good instructions<br />
<br />
|-<br />
| rowspan="3" | [[52°North WPS]] || <code>ciwater/n52wps</code> || Tethys Platform, 3rd party || https://github.com/CI-WATER/tethys_docker<br />
|| 52 North Web Processing Service with GRASS and Sextante backends enabled. || - || <code> ubuntu:14.04</code> || good instructions, several processing backends included<br />
|-<br />
| <code>zuncle/52n-wps</code> || Xavier Thomas, 3rd party || https://bitbucket.org/zuncle/docker || - || - || <code>zuncle/tomcat8-oracle-java8</code> || installs from source using Maven<br />
|-<br />
| <code>geocontainers/52n-wps</code> || [http://geocontainers.org/ Geocontainers] || https://github.com/geocontainers/dockerfiles/tree/master/52n-wps || ? || - || <code>tomcat:9</code> || -<br />
<br />
|-<br />
| 52°North SOS || - || - || - || - || - || - || only makes sense when using compose file, which includes PostGIS, work in progess at https://github.com/geocontainers/dockerfiles/issues/4<br />
|-<br />
| epsg.io || <code>klokantech/epsg.io</code> || [https://hub.docker.com/u/klokantech/ klokantech] || https://github.com/klokantech/epsg.io || - || file<code> LICENSE</code> || <code>klokantech/gdal:1.11</code> || Run with<code> -p 8080:8080</code> to open at <http://localhost:8080/> Run a clone in you local network<br />
<br />
|-<br />
| osm2vectortiles || multiple || [http://osm2vectortiles.org/ osm2vectortiles] || https://hub.docker.com/r/osm2vectortiles/ || - || - || multiple || see also tileserver-mapnik by klokantech<br />
<br />
|}</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=DockerImages&diff=109109DockerImages2017-09-08T05:33:46Z<p>Wiki-Brian H Wilson: </p>
<hr />
<div><br />
The goal of this list is to provide an overview of OSGeo-related Docker images to leverage the advantages of containerization across the geoinformatics communities.<br />
<br />
You want to learn how this list was created? See [[DockerImagesMeta]].<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Project !! Image on Hub !! Maintainer !! Link !! Specific goals / target users? !! License !! Base image !! Comments<br />
<br />
|-<br />
| [[Cartaro]] || <code>geops/cartaro</code> || [http://cartaro.org/ Cartaro] || https://www.drupal.org/node/2579221 || - || - || <code>ubuntu:14.04</code> || good docs, works<br />
<br />
|-<br />
| [[Deegree]] ||<code>tfr42/deegree</code> || Deegree TMC || https://github.com/tfr42/deegree-docker || - || - || <code>tomcat:8-jre7</code> and<code> java:8</code> (which is <code>debian:jessie</code>) || also docker-compose with PostGIS, [https://docs.google.com/document/d/1DEcTxNKMtJD3LjONKz4O9umowTh3KnMfDB4cuDYBGfI/edit#heading=h.c7bibbfs1pv FOSS4G workshop documentation]<br />
<br />
|-<br />
| [[geoblacklight]] || <code>geoblacklight/geoblacklight</code> || [http://geoblacklight.org GeoBlacklight] || https://github.com/geoblacklight/geoblacklight-docker || - || - || <code>rails:4.2.3</code> || detailed instructions, including image with test data; see also [https://hub.docker.com/r/geoblacklight/geoserver/ docker-compose configuration] and open at http://localhost/catalog<br />
<br />
|-<br />
| [[geogig]] || <code>kartoza/geogig</code> || kartoza/Tim Sutton, 3rd party || https://github.com/kartoza/docker-geogig || - || - || <code>ubuntu:14.04</code> || clear instructions; untested<br />
|-<br />
| [[geogig]] server and cli || <code>jasoncallaway/geogig-server</code> and<code> jasoncallaway/geogig-cli</code> || Jason Callaway, 3rd party || https://github.com/jason-callaway || - || - || <code>centos:latest</code> || under development, untested<br />
<br />
|-<br />
| [[GeoMOOSE]] || - || [http://www.geomoose.org/ GeoMOOSE] || https://github.com/geomoose/docker-geomoose || demo and [http://www.geomoose.org/releases/2.9.0.html#release development environment} || MIT || <code>ubuntu:trusty</code> || must build yourself, but very good documentation<br />
<br />
|-<br />
| [[GeoServer]] || <code>winsent/geoserver</code> || [https://github.com/winsento) winsento]/"ololoteam", independent || https://bitbucket.org/ololoteam/geoserver-docker || unclear - production? || - || | uses Oracle Java; well documented<br />
<br />
|-<br />
| [http://grasss.osgeo.org/ Grass] || <code>geodata/grass</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/grass-docker || specific subservsion version of grass compiled against specific gdal version || - || <code>ubuntu:trusty</code> || good instructions for usage and build, GRASS is build outside of container, see Makefile in repo<br />
<br />
|-<br />
| [[Jupyter Notebook]] || <code>dcal12/python-geospatial</code> || Doug Callaway/DCAL12 || https://github.com/DCAL12/docker-python-geospatial || - || <code>jupyter/base-notebook:latest</code> || works, very small dockerfile but lacks docs/examples<br />
<br />
|-<br />
| rowspan="2" | mapcache || <code>pamtrak06/mapcache-ubuntu14.04</code> || - || https://github.com/pamtrak06/mapcache-ubuntu14.04 || - || - || <code>pamtrak06/ubuntu14.04-apache2-python</code> || ... untested<br />
|-<br />
| <code>camptocamp/mapcache</code> || [https://github.com/camptocamp camptocamp] || https://github.com/camptocamp/docker-mapcache || - || - || <code>debian:stable</code> || ... untested<br />
<br />
|-<br />
| [[MapFish]] Print || <code>unknownlighter/mapfish-print</code> || Maintainer || https://bitbucket.org/lighter/mapfish-print || - || - || <code>tomcat:8-jre7</code> || No documentation, but just open http://localhost:8080/<br />
|-<br />
| [[MapGuide]] || <code>jumpinjackie/mapguide-base</code> || Jackie Ng || https://github.com/jumpinjackie/mapguide-centos-docker || as a base image? || - || <code>centos:centos6</code> || Dockerfile is missing command, run with <code>docker run --rm -it -p 8008:8008 jumpinjackie/mapguide-base /usr/bin/supervisord</code>, but only shows [https://github.com/jumpinjackie/mapguide-centos-docker/issues/4 error]<br />
<br />
|-<br />
| [[MapServer]] || <code>geodata/mapserver</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/mapserver-docker || mapserver with a "broad range of options enabled including a comprehensive GDAL library" || - || <code>geodata/gdal:latest</code> || good instructions<br />
<br />
|-<br />
| [[neo4j-spatial]] || <code>jeffreyjharris/docker-neo4j-spatial</code> || Kenny Bastani, 3rd party || https://github.com/jeffreyjharris/docker-neo4j-spatial || - || - || <code>java:openjdk-8-jdk</code> || open at <http://localhost:7474/browser/>; extension/fork of <code>kbastani/docker-neo4j</code><br />
<br />
|-<br />
| rowspan="4" | [[PostGIS]] || <code>mdillon/postgis</code> || Mike Dillon/Appropriate Computing || https://github.com/md5/docker-postgis || - || file<code> LICENSE</code> || <code>postgres:9.5</code> || simple and good<br />
|-<br />
| <code>neowaylabs/postgis</code> || NeowayLabs, 3rd party || https://github.com/NeowayLabs/docker-postgis || - || License || <code>neowaylabs/baseimage</code> || installs from http://apt.postgresql...<br />
|-<br />
| <code>camptocamp/postgis</code> || capmtocamp, 3rd party || https://github.com/camptocamp/docker-postgis || base image for own configuration || - || <code>postgres:9.5</code> || installs from sources, documentation recommends usage as a base image<br />
|-<br />
| <code>kartoza/postgis</code> || kartoza/Tim Sutton, 3rd party || https://github.com/kartoza/docker-postgis || Ready to run PostGIS geospatial databaseg || - || <code>debian:stable</code> || installs from http://apt.postgresql<br />
<br />
|-<br />
| rowspan="3" | [[QGIS Desktop]] || <code>kartoza/qgis-desktop</code> || kartoza/Tim Sutton, 3rd party || https://github.com/kartoza/docker-qgis-desktop || complete replacement for usage on Desktop, see http://kartoza.com/qgis-desktop-in-docker/ || - || <code>kartoza/qgis-base</code> || good instructions, including docker-compose with a postgis server; [https://hub.docker.com/u/qgis/ QGIS community is on Docker Hub] but not with a QGIS image<br />
<br />
|-<br />
| <code>timcera/qgis-desktop-ubuntu</code> || timcera, 3rd party || https://github.com/timcera/qgis-desktop-ubuntu || "Instead of compiling, this image is [..] latest QGIS" || - || <code>ubuntu:xenial</code> and UbuntuGIS repos || instructions for run script including mounting as setting user, untested but looks promising<br />
|-<br />
| <code>elpaso/qgis-testing-environment</code> || elpase, 3rd party || - || Simple container for testing QGIS Desktop and for executing unit tests inside a real QGIS instance || - || ? || incl. instructions for running on Travis, uses xhost forwarding (dont forget to<code> xhost -</code> when youre done)<br />
<br />
|-<br />
| rowspan="2" | [[QGIS Server]] || <code>kartoza/qgis-server</code> || kartoza/Tim Sutton || https://github.com/kartoza/docker-qgis-server || complete replacement for usage on Desktop, see http://kartoza.com/qgis-desktop-in-docker/ || - || <code>kartoza/qgis-desktop</code> || good instructions<br />
|-<br />
| <code>kartoza/qgis-server</code> || kartoza, 3rd party || https://github.com/kartoza/docker-qgis-server || A simple docker container that runs QGIS Server || - || <code>kartoza/qgis-desktop</code> || - <br />
<br />
|-<br />
| QGIS MapServer + web client || <code>opengisch/qgis-server-webclient</code> || opengis.ch, 3rd party || https://github.com/opengisch/docker-qgis-server-webclient || - || - || <code>debian:stable</code> || [https://hub.docker.com/u/qgis/ QGIS community is on Docker Hub] but not with a QGIS image<br />
<br />
|-<br />
| [[tileserver-mapnik]] || <code>klokantech/tileserver-mapnik</code> || [https://hub.docker.com/u/klokantech/ klokantech] || https://github.com/klokantech/tileserver-mapnik || Mapnik based map tileserver generating raster tiles from MapBox Studio project & custom vector tiles || file<code> License</code> || <code>node:0.10</code> || installation instructions just refer to the Dockerfile - nice! see [http://osm2vectortiles.org/docs/serve-raster-tiles-docker instructions by osm2vectortiles]<br />
<br />
|-<br />
| rowspan="2" | [[gdal]] || <code>geodata/gdal</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/gdal-docker || build specific versions of gdal from source, see [https://hub.docker.com/r/geodata/gdal/tags/ tags] || - || <code>ubuntu:trusty</code> || some forks, e.g. [https://hub.docker.com/r/geometalab/gdal-debian/ geometalab], compare on GitHub before use<br />
|-<br />
| <code>spara/gdal_ef</code> || 3rd party || https://github.com/spara/gdal-docker || demo FOSS4G-NA 2016 || - || <code>ubuntu:trusty</code> || -<br />
<br />
|-<br />
| [[pdal]] || <code>pdal/pdal</code> || PDAL maintainers || http://www.pdal.io/workshop/docker.html || PDAL stands on the shoulders of giants. It uses GDAL, GEOS, and many other dependencies. Because of this, it is very challenging to build it yourself. We could easily burn an entire workshop learning the esoteric build miseries of PDAL and all of its dependencies. Fortunately, Docker will allow us to use a fully-featured known configuration to run our examples and exercises without having to suffer so much. || License || <code>pdal/dependencies</code>, [https://github.com/PDAL/PDAL/blob/master/scripts/docker/dependencies/Dockerfile which is based on]<code> ubuntu:15.04</code> || great docs; build libs from source;<br />
<br />
|-<br />
| [[saga]] || <code>ntonshevtsov/saga-gis</code> || || - || - || - || <code>-</code> || no Dockerfile, but works! Use <code>xhost +</code> before and<code> xhost -</code> after<br />
<br />
|-<br />
| rowspan="2" | [[opticks]] || <code>toddstavish/opticks</code> || Todd Stavish || https://github.com/toddstavish/Dockerfiles || - || - || <code>ubuntu:15.04</code> || run with <code>docker run -i -t -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=unix$DISPLAY -v $(pwd)/tmp:/home/data toddstavish/opticks</code><br />
|-<br />
| <code>tclarke/opticks</code> || Trevor R.H. Clarke/Opticks || https://github.com/tclarke/opticks-docker || - || - || <code>centos:centos7</code> || good documentation, error on run;<br />
<br />
|-<br />
| rowspan="2" | [[CartoDB]] || <code>sverhoeven/cartodb</code> || Stefan Verhoeven, 3rd party || https://github.com/sverhoeven/docker-cartodb || fully working cartodb development solution without the installation hassle. || - || <code>ubuntu:14.04</code> || large image; includes multiple "apps" (postgres, node, redis-server); use together with nginx proxy in container: https://hub.docker.com/r/spawnthink/cartodb-nginx/<br />
|-<br />
| <code>akvo/akvo-provisioning</code> || Akvo, 3rd party || https://github.com/akvo/akvo-provisioning/tree/develop/docker/cartodb || what's needed to dockerize the five main components CartoDB || - || - || multiple images, and docker-compose orchestration<br />
<br />
|-<br />
| rowspan="2" | [[Nominatim]] || <code>helvalius/nominatim-docker-development</code> || helvalius, 3rd party || https://github.com/helvalius/nominatim-docker || builds current master or development || - || <code>ubuntu:14.04</code> || includes PG database and apache2<br />
|-<br />
| <code>mediagis/nominatim</code> || [https://github.com/winsento winsento]/mediagis, 3rd party || https://github.com/mediagis/nominatim-docker || "100% working container" || - || <code>ubuntu:trusty</code> || fork by [https://github.com/cartography/nominatim-docker cartography], test data is in Monaco<br />
<br />
|-<br />
| [[osmtools]] || <code>mediagis/osmtools</code> || [https://github.com/winsento winsento]/mediagis, 3rd party || https://github.com/mediagis/osmtools || package CLI tools osmconvert, osmfilter, osmupdate || - || <code>ubuntu:latest</code> || fork by [https://hub.docker.com/r/cartography/osmtools/ cartography]<br />
|-<br />
| [[osrm]] (Frontend, Backend) || <code>cartography/osrm-backend-docker</code> and<code> docker pull cartography/osrm-frontend-docker</code> || Project-OSRM || http://project-osrm.org/ || - || LICENSE.txt || <code>ubuntu:trusty</code> || untested, documentation seems good<br />
<br />
|-<br />
| rowspan="2" | [[osmosis]] || <code>farberg/openstreetmap-osmosis-docker</code> || Dennis Pfisterer || https://github.com/pfisterer/openstreetmap-osmosis-docker || - || - || <code>debian:jessie</code> || not much, but works<br />
|-<br />
| <code>ferimer/osmosis</code> || [https://ferimer.es/ Ferimer] || https://github.com/ferimer/docker-osmosis || - || - || <code>debian:latest</code> || not much, but works; "latest" tag missing, not well maintained<br />
<br />
|-<br />
| [[osmosis]] + Jenkins || <code>henkel/jenkins-slave-osmosis</code> || Philipp Henkel || https://github.com/henkel/jenkins-slave-osmosis || presumably for automation? || - || <code>debian:latest</code> || untested (quite specific use case)<br />
<br />
|-<br />
| [[osm2pgsql]] || <code>openfirmware/osm2pgsql</code> || James Badger/openfirmware || https://github.com/openfirmware/docker-osm2pgsql || A Docker image with osm2pgsql, the tool for importing OpenStreetMap data into a Postgresql database. || - || <code>debian:wheezy</code> || [https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=1&q=osm2pgsql&starCount=0 many images exist], untested, could profit from docs including postgres<br />
<br />
|-<br />
| OSM-ready postgres || <code>openfirmware/postgres-osm</code> || James Badger/openfirmware || https://github.com/openfirmware/docker-postgres-osm |The base postgres image from Docker with extensions for importing OpenStreetMap data. || - || <code>postgres:9.3.6</code> || README says it is unfinished<br />
<br />
|-<br />
| [[r-spatial]] || <code>achubaty/r-spatial-base</code> and<code> achubaty/r-spatial-devel</code> || Alex Chubaty || https://github.com/achubaty/rocker-files || extend Rocker base image with spatial packages || License || <code>rocker/r-base:latest</code> respectively<code> rocker/r-devel:latest</code> || -<br />
<br />
|-<br />
| ubuntugis-docker || <code>javimarlop/ubuntugis-docker</code> || Martinez-Lopez Javier, 3rd party || https://github.com/javimarlop/ubuntugis-docker || VM using Docker for Geospatial Analysis || - || <code>ubuntu:14.04</code> || untested; really installs a lot of stuff, not best use of Docker<br />
|-<br />
| [[mapnik]] || <code>mapsquare/mapnik3</code> || [https://hub.docker.com/u/mapsquare/ mapsquare] || https://github.com/jawg/docker-mapnik3 || - || - || <code>debian:jessie</code> || versions as tags; untested, partial instructions only<br />
|-<br />
| [[GeoNode]] || <code>openmarble/arch-geonode</code> || Maintainer || https://github.com/OpenMarble/geomelting || - || - || <code>openmarble/arch-imaging:latest</code> || lacking documentation, run with<code> docker run -it --rm -p 8000:8000 -p 8080:8080 openmarble/arch-geonode</code> and open GeoNode at http://localhost:8000/ (login with admin/admin) or GeoServer at http://localhost:8080/geoserver/web/<br />
|-<br />
| [[geosuite]] || <code>devdattat/docker-opengeosuite</code> || Devdatta Tengshe || https://github.com/devdattaT/docker-OpenGeoSuite || - || MIT || <code>ubuntu:14.04</code> || incomplete instructions; Dockerfile has no start command... cannot work<br />
<br />
|-<br />
| cesium terrain server and cesium.js || <code>geodata/cesium-terrain-server</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/cesium-terrain-server || - || - || <code>phusion/baseimage:0.9.15</code> (Ubuntu 14.04 Trusty Tahr) || good documentation, untested because tiles must be created first<br />
<br />
|-<br />
| rowspan="2" | [[GeoNetwork]] || <code>oscarfonts/geonetwork</code> || Oscar Fonts (geomati.co) || https://github.com/oscarfonts/docker-geonetwork || - || - || <code>tomcat:8-jre8</code> || reasonable documetation, newer fork of [https://hub.docker.com/r/eliotjordan/geonetwork-docker/ elitojordan], open at http://localhost:8888/geonetwork<br />
|-<br />
| <code>geonetwork</code> || Official /Joana Simoes, [https://www.geocat.net/ GeoCat] || https://github.com/geonetwork/docker-geonetwork || <br />
* First-time users: try GeoNetwork; <br />
* Advanced users: Run specific version of GeoNetwork, with an external PostgreSQL DB backend<br />
|| Specified on the<code> README</code> file || <code>tomcat:8</code> || Follows the [https://github.com/docker-library/official-images best practices for official Docker images]. Official documentation [https://github.com/docker-library/docs/tree/master/geonetwork here]. <br />
<br />
|-<br />
| [[landsat-util]] || <code>developmentseed/landsat-util</code> || [https://developmentseed.org/ developmentseed] || https://pythonhosted.org/landsat-util/installation.html?highlight=docker#docker || - || - || <code>ubuntu:14.04</code> || has several related images, see https://hub.docker.com/u/developmentseed/<br />
<br />
|-<br />
| [[opendronemap]] || <code>opendronemap/opendronemap</code> || [https://github.com/OpenDroneMap OpenDroneMap] || https://github.com/OpenDroneMap/OpenDroneMap || OpenDroneMap is a tool to postprocess drone, balloon, kite, and street view data to geographic data. || - || <code>ubuntu:14.04</code> || not tested, but good documentation available<br />
<br />
<br />
|-<br />
| rowspan="4" | [[pycsw]] || <code>geocontainer/pycsw</code> || [http://geocontainers.org/ Geocontainers] || https://github.com/geocontainers/dockerfiles || - || - || <code>alpine:3.4</code> || very short documenation only, simply open CSW Capabilities at http://<ip>/<br />
|-<br />
| <code>birdhouse/pycsw</code> || [http://bird-house.github.io/ Birdhouse] || https://github.com/bird-house/birdhouse-playground || - || - || <code>birdhouse/bird-base:latest</code> || no docs; only pycsw 1.10.3, but Capabilities available at http://<ip>:8082/csw?service=CSW&request=GetCapabilities<br />
|-<br />
| <code>datagov/catalog-pycsw</code> || [https://github.com/GSA U.S. General Services Administration] || datagov/catalog-pycsw || [https://github.com/GSA/catalog-app production use for catalog.data.gov] || - || <code>ubuntu:14.04</code> || tailored to their installation, docs lacking; run with<code> </code> and should be available at http://<ip>/csw - does not work!<br />
<br />
|-<br />
| <code>axiom/docker-pycsw</code> || [http://axiomdatascience.com/ Axiom Data Science] || https://github.com/axiom-data-science/docker-pycsw || testing as well as production || - || <code>phusion/baseimage:0.9.18</code> (Ubuntu++) || good documentation, [https://github.com/axiom-data-science/docker-pycsw/issues/1 currently not working]<br />
<br />
|-<br />
| pyWPS4-demo || <code>geocontainer/pywps/4/pywps-demo</code> || [http://geocontainers.org/ Geocontainers] || https://github.com/geocontainers/dockerfiles || - || MIT || <code>alpine/latest</code>|| Good docs https://pywps.readthedocs.io/en/latest/ <br />
<br />
|-<br />
| [[Zoo-Project]] || <code>yoms/zoo-project</code> || yomd || https://github.com/yoms/zoo-project || - || file<code> LICENSE</code> || <code>centos:6.7</code> || no documentation, seems to start but don't know where to look next<br />
<br />
|-<br />
| [[Team Engine]] || <code>tfr42/teamengine</code> || tfr42 || https://hub.docker.com/r/tfr42/teamengine/ || - || - || <code>-</code> || Dockerfile missing, but good instructions<br />
<br />
|-<br />
| rowspan="3" | [[52°North WPS]] || <code>ciwater/n52wps</code> || Tethys Platform, 3rd party || https://github.com/CI-WATER/tethys_docker<br />
|| 52 North Web Processing Service with GRASS and Sextante backends enabled. || - || <code> ubuntu:14.04</code> || good instructions, several processing backends included<br />
|-<br />
| <code>zuncle/52n-wps</code> || Xavier Thomas, 3rd party || https://bitbucket.org/zuncle/docker || - || - || <code>zuncle/tomcat8-oracle-java8</code> || installs from source using Maven<br />
|-<br />
| <code>geocontainers/52n-wps</code> || [http://geocontainers.org/ Geocontainers] || https://github.com/geocontainers/dockerfiles/tree/master/52n-wps || ? || - || <code>tomcat:9</code> || -<br />
<br />
|-<br />
| 52°North SOS || - || - || - || - || - || - || only makes sense when using compose file, which includes PostGIS, work in progess at https://github.com/geocontainers/dockerfiles/issues/4<br />
|-<br />
| epsg.io || <code>klokantech/epsg.io</code> || [https://hub.docker.com/u/klokantech/ klokantech] || https://github.com/klokantech/epsg.io || - || file<code> LICENSE</code> || <code>klokantech/gdal:1.11</code> || Run with<code> -p 8080:8080</code> to open at <http://localhost:8080/> Run a clone in you local network<br />
<br />
|-<br />
| osm2vectortiles || multiple || [http://osm2vectortiles.org/ osm2vectortiles] || https://hub.docker.com/r/osm2vectortiles/ || - || - || multiple || see also tileserver-mapnik by klokantech<br />
<br />
|}</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=User:Brian_H_Wilson&diff=109108User:Brian H Wilson2017-09-08T05:28:12Z<p>Wiki-Brian H Wilson: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Brian Wilson<br />
|State=California<br />
|City=Cotati<br />
|Coordinate=38.332276N,122.693209W<br />
|LocalChapter=California Chapter<br />
|Email=brian@wildsong.biz<br />
|Phone=707-827-0001<br />
|Website=http://wildsong.biz<br />
}}<br />
{{OSGeo Experience<br />
|User=No<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=No<br />
|PSC=No<br />
|ExBoard=No<br />
|Charter=No<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=No<br />
}}<br />
I keep most of my stuff on http://wildsong.biz/ including my [http://wildsong.biz/index.php/User:Brian_Wilson User] page.<br />
<br />
[[Category: OSGeo Member]]</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=User:Brian_H_Wilson&diff=109107User:Brian H Wilson2017-09-08T05:26:18Z<p>Wiki-Brian H Wilson: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Brian Wilson<br />
|State=California<br />
|City=Cotati<br />
|Coordinate=38N,122W<br />
|LocalChapter=California Chapter<br />
|Email=brian@wildsong.biz<br />
|Phone=707-827-0001<br />
|Website=http://wildsong.biz<br />
}}<br />
{{OSGeo Experience<br />
|User=No<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=No<br />
|PSC=No<br />
|ExBoard=No<br />
|Charter=No<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=No<br />
}}<br />
I keep most of my stuff on http://wildsong.biz/ including my [http://wildsong.biz/index.php/User:Brian_Wilson User] page.<br />
<br />
[[Category: OSGeo Member]]</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=User:Brian_H_Wilson&diff=109106User:Brian H Wilson2017-09-08T05:22:06Z<p>Wiki-Brian H Wilson: </p>
<hr />
<div>I keep most of my stuff on http://wildsong.biz/ including my [http://wildsong.biz/index.php/User:Brian_Wilson User] page.<br />
<br />
[[Category: OSGeo Member]]</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=User:Brian_H_Wilson&diff=109105User:Brian H Wilson2017-09-08T05:21:50Z<p>Wiki-Brian H Wilson: </p>
<hr />
<div>I keep most of my stuff on http://wildsong.biz/ including my [http://wildsong.biz/index.php/User:Brian_Wilson User] page.<br />
<br />
[[Category: OSGEO Member]]</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=DockerImages&diff=109104DockerImages2017-09-08T05:16:37Z<p>Wiki-Brian H Wilson: </p>
<hr />
<div><br />
The goal of this list is to provide an overview of OSGeo-related Docker images to leverage the advantages of containerization across the geoinformatics communities.<br />
<br />
You want to learn how this list was created? See [[DockerImagesMeta]].<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Project !! Image on Hub !! Maintainer !! Link !! Specific goals / target users? !! License !! Base image !! Comments<br />
<br />
|-<br />
| [[Cartaro]] || <code>geops/cartaro</code> || [http://cartaro.org/ Cartaro] || https://www.drupal.org/node/2579221 || - || - || <code>ubuntu:14.04</code> || good docs, works<br />
<br />
|-<br />
| [[Deegree]] ||<code>tfr42/deegree</code> || Deegree TMC || https://github.com/tfr42/deegree-docker || - || - || <code>tomcat:8-jre7</code> and<code> java:8</code> (which is <code>debian:jessie</code>) || also docker-compose with PostGIS, [https://docs.google.com/document/d/1DEcTxNKMtJD3LjONKz4O9umowTh3KnMfDB4cuDYBGfI/edit#heading=h.c7bibbfs1pv FOSS4G workshop documentation]<br />
<br />
|-<br />
| [[geoblacklight]] || <code>geoblacklight/geoblacklight</code> || [http://geoblacklight.org GeoBlacklight] || https://github.com/geoblacklight/geoblacklight-docker || - || - || <code>rails:4.2.3</code> || detailed instructions, including image with test data; see also [https://hub.docker.com/r/geoblacklight/geoserver/ docker-compose configuration] and open at http://localhost/catalog<br />
<br />
|-<br />
| [[geogig]] || <code>kartoza/geogig</code> || kartoza/Tim Sutton, 3rd party || https://github.com/kartoza/docker-geogig || - || - || <code>ubuntu:14.04</code> || clear instructions; untested<br />
|-<br />
| [[geogig]] server and cli || <code>jasoncallaway/geogig-server</code> and<code> jasoncallaway/geogig-cli</code> || Jason Callaway, 3rd party || https://github.com/jason-callaway || - || - || <code>centos:latest</code> || under development, untested<br />
<br />
|-<br />
| [[GeoMOOSE]] || - || [http://www.geomoose.org/ GeoMOOSE] || https://github.com/geomoose/docker-geomoose || demo and [http://www.geomoose.org/releases/2.9.0.html#release development environment} || MIT || <code>ubuntu:trusty</code> || must build yourself, but very good documentation<br />
<br />
|-<br />
| [[GeoServer]] || <code>winsent/geoserver</code> || [https://github.com/winsento) winsento]/"ololoteam", independent || https://bitbucket.org/ololoteam/geoserver-docker || unclear - production? || - || | uses Oracle Java; well documented<br />
<br />
|-<br />
| [[Jupyter Notebook]] || <code>dcal12/python-geospatial</code> || Doug Callaway/DCAL12 || https://github.com/DCAL12/docker-python-geospatial || - || <code>jupyter/base-notebook:latest</code> || works, very small dockerfile but lacks docs/examples<br />
<br />
|-<br />
| rowspan="2" | mapcache || <code>pamtrak06/mapcache-ubuntu14.04</code> || - || https://github.com/pamtrak06/mapcache-ubuntu14.04 || - || - || <code>pamtrak06/ubuntu14.04-apache2-python</code> || ... untested<br />
|-<br />
| <code>camptocamp/mapcache</code> || [https://github.com/camptocamp camptocamp] || https://github.com/camptocamp/docker-mapcache || - || - || <code>debian:stable</code> || ... untested<br />
<br />
|-<br />
| [[MapFish]] Print || <code>unknownlighter/mapfish-print</code> || Maintainer || https://bitbucket.org/lighter/mapfish-print || - || - || <code>tomcat:8-jre7</code> || No documentation, but just open http://localhost:8080/<br />
|-<br />
| [[MapGuide]] || <code>jumpinjackie/mapguide-base</code> || Jackie Ng || https://github.com/jumpinjackie/mapguide-centos-docker || as a base image? || - || <code>centos:centos6</code> || Dockerfile is missing command, run with <code>docker run --rm -it -p 8008:8008 jumpinjackie/mapguide-base /usr/bin/supervisord</code>, but only shows [https://github.com/jumpinjackie/mapguide-centos-docker/issues/4 error]<br />
<br />
|-<br />
| [[MapServer]] || <code>geodata/mapserver</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/mapserver-docker || mapserver with a "broad range of options enabled including a comprehensive GDAL library" || - || <code>geodata/gdal:latest</code> || good instructions<br />
<br />
|-<br />
| [[neo4j-spatial]] || <code>jeffreyjharris/docker-neo4j-spatial</code> || Kenny Bastani, 3rd party || https://github.com/jeffreyjharris/docker-neo4j-spatial || - || - || <code>java:openjdk-8-jdk</code> || open at <http://localhost:7474/browser/>; extension/fork of <code>kbastani/docker-neo4j</code><br />
<br />
|-<br />
| rowspan="4" | [[PostGIS]] || <code>mdillon/postgis</code> || Mike Dillon/Appropriate Computing || https://github.com/md5/docker-postgis || - || file<code> LICENSE</code> || <code>postgres:9.5</code> || simple and good<br />
|-<br />
| <code>neowaylabs/postgis</code> || NeowayLabs, 3rd party || https://github.com/NeowayLabs/docker-postgis || - || License || <code>neowaylabs/baseimage</code> || installs from http://apt.postgresql...<br />
|-<br />
| <code>camptocamp/postgis</code> || capmtocamp, 3rd party || https://github.com/camptocamp/docker-postgis || base image for own configuration || - || <code>postgres:9.5</code> || installs from sources, documentation recommends usage as a base image<br />
|-<br />
| <code>kartoza/postgis</code> || kartoza/Tim Sutton, 3rd party || https://github.com/kartoza/docker-postgis || Ready to run PostGIS geospatial databaseg || - || <code>debian:stable</code> || installs from http://apt.postgresql<br />
<br />
|-<br />
| rowspan="3" | [[QGIS Desktop]] || <code>kartoza/qgis-desktop</code> || kartoza/Tim Sutton, 3rd party || https://github.com/kartoza/docker-qgis-desktop || complete replacement for usage on Desktop, see http://kartoza.com/qgis-desktop-in-docker/ || - || <code>kartoza/qgis-base</code> || good instructions, including docker-compose with a postgis server; [https://hub.docker.com/u/qgis/ QGIS community is on Docker Hub] but not with a QGIS image<br />
<br />
|-<br />
| <code>timcera/qgis-desktop-ubuntu</code> || timcera, 3rd party || https://github.com/timcera/qgis-desktop-ubuntu || "Instead of compiling, this image is [..] latest QGIS" || - || <code>ubuntu:xenial</code> and UbuntuGIS repos || instructions for run script including mounting as setting user, untested but looks promising<br />
|-<br />
| <code>elpaso/qgis-testing-environment</code> || elpase, 3rd party || - || Simple container for testing QGIS Desktop and for executing unit tests inside a real QGIS instance || - || ? || incl. instructions for running on Travis, uses xhost forwarding (dont forget to<code> xhost -</code> when youre done)<br />
<br />
|-<br />
| rowspan="2" | [[QGIS Server]] || <code>kartoza/qgis-server</code> || kartoza/Tim Sutton || https://github.com/kartoza/docker-qgis-server || complete replacement for usage on Desktop, see http://kartoza.com/qgis-desktop-in-docker/ || - || <code>kartoza/qgis-desktop</code> || good instructions<br />
|-<br />
| <code>kartoza/qgis-server</code> || kartoza, 3rd party || https://github.com/kartoza/docker-qgis-server || A simple docker container that runs QGIS Server || - || <code>kartoza/qgis-desktop</code> || - <br />
<br />
|-<br />
| QGIS MapServer + web client || <code>opengisch/qgis-server-webclient</code> || opengis.ch, 3rd party || https://github.com/opengisch/docker-qgis-server-webclient || - || - || <code>debian:stable</code> || [https://hub.docker.com/u/qgis/ QGIS community is on Docker Hub] but not with a QGIS image<br />
<br />
|-<br />
| [[tileserver-mapnik]] || <code>klokantech/tileserver-mapnik</code> || [https://hub.docker.com/u/klokantech/ klokantech] || https://github.com/klokantech/tileserver-mapnik || Mapnik based map tileserver generating raster tiles from MapBox Studio project & custom vector tiles || file<code> License</code> || <code>node:0.10</code> || installation instructions just refer to the Dockerfile - nice! see [http://osm2vectortiles.org/docs/serve-raster-tiles-docker instructions by osm2vectortiles]<br />
<br />
|-<br />
| rowspan="2" | [[gdal]] || <code>geodata/gdal</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/gdal-docker || build specific versions of gdal from source, see [https://hub.docker.com/r/geodata/gdal/tags/ tags] || - || <code>ubuntu:trusty</code> || some forks, e.g. [https://hub.docker.com/r/geometalab/gdal-debian/ geometalab], compare on GitHub before use<br />
|-<br />
| <code>spara/gdal_ef</code> || 3rd party || https://github.com/spara/gdal-docker || demo FOSS4G-NA 2016 || - || <code>ubuntu:trusty</code> || -<br />
<br />
|-<br />
| [[pdal]] || <code>pdal/pdal</code> || PDAL maintainers || http://www.pdal.io/workshop/docker.html || PDAL stands on the shoulders of giants. It uses GDAL, GEOS, and many other dependencies. Because of this, it is very challenging to build it yourself. We could easily burn an entire workshop learning the esoteric build miseries of PDAL and all of its dependencies. Fortunately, Docker will allow us to use a fully-featured known configuration to run our examples and exercises without having to suffer so much. || License || <code>pdal/dependencies</code>, [https://github.com/PDAL/PDAL/blob/master/scripts/docker/dependencies/Dockerfile which is based on]<code> ubuntu:15.04</code> || great docs; build libs from source;<br />
<br />
|-<br />
| [[saga]] || <code>ntonshevtsov/saga-gis</code> || || - || - || - || <code>-</code> || no Dockerfile, but works! Use <code>xhost +</code> before and<code> xhost -</code> after<br />
<br />
|-<br />
| [[Grass]] || <code>geodata/grass</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/grass-docker || specific subservsion version of grass compiled against specific gdal version || - || <code>ubuntu:trusty</code> || good instructions for usage and build, GRASS is build outside of container, see Makefile in repo<br />
<br />
|-<br />
| rowspan="2" | [[opticks]] || <code>toddstavish/opticks</code> || Todd Stavish || https://github.com/toddstavish/Dockerfiles || - || - || <code>ubuntu:15.04</code> || run with <code>docker run -i -t -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=unix$DISPLAY -v $(pwd)/tmp:/home/data toddstavish/opticks</code><br />
|-<br />
| <code>tclarke/opticks</code> || Trevor R.H. Clarke/Opticks || https://github.com/tclarke/opticks-docker || - || - || <code>centos:centos7</code> || good documentation, error on run;<br />
<br />
|-<br />
| rowspan="2" | [[CartoDB]] || <code>sverhoeven/cartodb</code> || Stefan Verhoeven, 3rd party || https://github.com/sverhoeven/docker-cartodb || fully working cartodb development solution without the installation hassle. || - || <code>ubuntu:14.04</code> || large image; includes multiple "apps" (postgres, node, redis-server); use together with nginx proxy in container: https://hub.docker.com/r/spawnthink/cartodb-nginx/<br />
|-<br />
| <code>akvo/akvo-provisioning</code> || Akvo, 3rd party || https://github.com/akvo/akvo-provisioning/tree/develop/docker/cartodb || what's needed to dockerize the five main components CartoDB || - || - || multiple images, and docker-compose orchestration<br />
<br />
|-<br />
| rowspan="2" | [[Nominatim]] || <code>helvalius/nominatim-docker-development</code> || helvalius, 3rd party || https://github.com/helvalius/nominatim-docker || builds current master or development || - || <code>ubuntu:14.04</code> || includes PG database and apache2<br />
|-<br />
| <code>mediagis/nominatim</code> || [https://github.com/winsento winsento]/mediagis, 3rd party || https://github.com/mediagis/nominatim-docker || "100% working container" || - || <code>ubuntu:trusty</code> || fork by [https://github.com/cartography/nominatim-docker cartography], test data is in Monaco<br />
<br />
|-<br />
| [[osmtools]] || <code>mediagis/osmtools</code> || [https://github.com/winsento winsento]/mediagis, 3rd party || https://github.com/mediagis/osmtools || package CLI tools osmconvert, osmfilter, osmupdate || - || <code>ubuntu:latest</code> || fork by [https://hub.docker.com/r/cartography/osmtools/ cartography]<br />
|-<br />
| [[osrm]] (Frontend, Backend) || <code>cartography/osrm-backend-docker</code> and<code> docker pull cartography/osrm-frontend-docker</code> || Project-OSRM || http://project-osrm.org/ || - || LICENSE.txt || <code>ubuntu:trusty</code> || untested, documentation seems good<br />
<br />
|-<br />
| rowspan="2" | [[osmosis]] || <code>farberg/openstreetmap-osmosis-docker</code> || Dennis Pfisterer || https://github.com/pfisterer/openstreetmap-osmosis-docker || - || - || <code>debian:jessie</code> || not much, but works<br />
|-<br />
| <code>ferimer/osmosis</code> || [https://ferimer.es/ Ferimer] || https://github.com/ferimer/docker-osmosis || - || - || <code>debian:latest</code> || not much, but works; "latest" tag missing, not well maintained<br />
<br />
|-<br />
| [[osmosis]] + Jenkins || <code>henkel/jenkins-slave-osmosis</code> || Philipp Henkel || https://github.com/henkel/jenkins-slave-osmosis || presumably for automation? || - || <code>debian:latest</code> || untested (quite specific use case)<br />
<br />
|-<br />
| [[osm2pgsql]] || <code>openfirmware/osm2pgsql</code> || James Badger/openfirmware || https://github.com/openfirmware/docker-osm2pgsql || A Docker image with osm2pgsql, the tool for importing OpenStreetMap data into a Postgresql database. || - || <code>debian:wheezy</code> || [https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=1&q=osm2pgsql&starCount=0 many images exist], untested, could profit from docs including postgres<br />
<br />
|-<br />
| OSM-ready postgres || <code>openfirmware/postgres-osm</code> || James Badger/openfirmware || https://github.com/openfirmware/docker-postgres-osm |The base postgres image from Docker with extensions for importing OpenStreetMap data. || - || <code>postgres:9.3.6</code> || README says it is unfinished<br />
<br />
|-<br />
| [[r-spatial]] || <code>achubaty/r-spatial-base</code> and<code> achubaty/r-spatial-devel</code> || Alex Chubaty || https://github.com/achubaty/rocker-files || extend Rocker base image with spatial packages || License || <code>rocker/r-base:latest</code> respectively<code> rocker/r-devel:latest</code> || -<br />
<br />
|-<br />
| ubuntugis-docker || <code>javimarlop/ubuntugis-docker</code> || Martinez-Lopez Javier, 3rd party || https://github.com/javimarlop/ubuntugis-docker || VM using Docker for Geospatial Analysis || - || <code>ubuntu:14.04</code> || untested; really installs a lot of stuff, not best use of Docker<br />
|-<br />
| [[mapnik]] || <code>mapsquare/mapnik3</code> || [https://hub.docker.com/u/mapsquare/ mapsquare] || https://github.com/jawg/docker-mapnik3 || - || - || <code>debian:jessie</code> || versions as tags; untested, partial instructions only<br />
|-<br />
| [[GeoNode]] || <code>openmarble/arch-geonode</code> || Maintainer || https://github.com/OpenMarble/geomelting || - || - || <code>openmarble/arch-imaging:latest</code> || lacking documentation, run with<code> docker run -it --rm -p 8000:8000 -p 8080:8080 openmarble/arch-geonode</code> and open GeoNode at http://localhost:8000/ (login with admin/admin) or GeoServer at http://localhost:8080/geoserver/web/<br />
|-<br />
| [[geosuite]] || <code>devdattat/docker-opengeosuite</code> || Devdatta Tengshe || https://github.com/devdattaT/docker-OpenGeoSuite || - || MIT || <code>ubuntu:14.04</code> || incomplete instructions; Dockerfile has no start command... cannot work<br />
<br />
|-<br />
| cesium terrain server and cesium.js || <code>geodata/cesium-terrain-server</code> || [https://github.com/geo-data GeoData Institute], 3rd party || https://github.com/geo-data/cesium-terrain-server || - || - || <code>phusion/baseimage:0.9.15</code> (Ubuntu 14.04 Trusty Tahr) || good documentation, untested because tiles must be created first<br />
<br />
|-<br />
| rowspan="2" | [[GeoNetwork]] || <code>oscarfonts/geonetwork</code> || Oscar Fonts (geomati.co) || https://github.com/oscarfonts/docker-geonetwork || - || - || <code>tomcat:8-jre8</code> || reasonable documetation, newer fork of [https://hub.docker.com/r/eliotjordan/geonetwork-docker/ elitojordan], open at http://localhost:8888/geonetwork<br />
|-<br />
| <code>geonetwork</code> || Official /Joana Simoes, [https://www.geocat.net/ GeoCat] || https://github.com/geonetwork/docker-geonetwork || <br />
* First-time users: try GeoNetwork; <br />
* Advanced users: Run specific version of GeoNetwork, with an external PostgreSQL DB backend<br />
|| Specified on the<code> README</code> file || <code>tomcat:8</code> || Follows the [https://github.com/docker-library/official-images best practices for official Docker images]. Official documentation [https://github.com/docker-library/docs/tree/master/geonetwork here]. <br />
<br />
|-<br />
| [[landsat-util]] || <code>developmentseed/landsat-util</code> || [https://developmentseed.org/ developmentseed] || https://pythonhosted.org/landsat-util/installation.html?highlight=docker#docker || - || - || <code>ubuntu:14.04</code> || has several related images, see https://hub.docker.com/u/developmentseed/<br />
<br />
|-<br />
| [[opendronemap]] || <code>opendronemap/opendronemap</code> || [https://github.com/OpenDroneMap OpenDroneMap] || https://github.com/OpenDroneMap/OpenDroneMap || OpenDroneMap is a tool to postprocess drone, balloon, kite, and street view data to geographic data. || - || <code>ubuntu:14.04</code> || not tested, but good documentation available<br />
<br />
<br />
|-<br />
| rowspan="4" | [[pycsw]] || <code>geocontainer/pycsw</code> || [http://geocontainers.org/ Geocontainers] || https://github.com/geocontainers/dockerfiles || - || - || <code>alpine:3.4</code> || very short documenation only, simply open CSW Capabilities at http://<ip>/<br />
|-<br />
| <code>birdhouse/pycsw</code> || [http://bird-house.github.io/ Birdhouse] || https://github.com/bird-house/birdhouse-playground || - || - || <code>birdhouse/bird-base:latest</code> || no docs; only pycsw 1.10.3, but Capabilities available at http://<ip>:8082/csw?service=CSW&request=GetCapabilities<br />
|-<br />
| <code>datagov/catalog-pycsw</code> || [https://github.com/GSA U.S. General Services Administration] || datagov/catalog-pycsw || [https://github.com/GSA/catalog-app production use for catalog.data.gov] || - || <code>ubuntu:14.04</code> || tailored to their installation, docs lacking; run with<code> </code> and should be available at http://<ip>/csw - does not work!<br />
<br />
|-<br />
| <code>axiom/docker-pycsw</code> || [http://axiomdatascience.com/ Axiom Data Science] || https://github.com/axiom-data-science/docker-pycsw || testing as well as production || - || <code>phusion/baseimage:0.9.18</code> (Ubuntu++) || good documentation, [https://github.com/axiom-data-science/docker-pycsw/issues/1 currently not working]<br />
<br />
|-<br />
| pyWPS4-demo || <code>geocontainer/pywps/4/pywps-demo</code> || [http://geocontainers.org/ Geocontainers] || https://github.com/geocontainers/dockerfiles || - || MIT || <code>alpine/latest</code>|| Good docs https://pywps.readthedocs.io/en/latest/ <br />
<br />
|-<br />
| [[Zoo-Project]] || <code>yoms/zoo-project</code> || yomd || https://github.com/yoms/zoo-project || - || file<code> LICENSE</code> || <code>centos:6.7</code> || no documentation, seems to start but don't know where to look next<br />
<br />
|-<br />
| [[Team Engine]] || <code>tfr42/teamengine</code> || tfr42 || https://hub.docker.com/r/tfr42/teamengine/ || - || - || <code>-</code> || Dockerfile missing, but good instructions<br />
<br />
|-<br />
| rowspan="3" | [[52°North WPS]] || <code>ciwater/n52wps</code> || Tethys Platform, 3rd party || https://github.com/CI-WATER/tethys_docker<br />
|| 52 North Web Processing Service with GRASS and Sextante backends enabled. || - || <code> ubuntu:14.04</code> || good instructions, several processing backends included<br />
|-<br />
| <code>zuncle/52n-wps</code> || Xavier Thomas, 3rd party || https://bitbucket.org/zuncle/docker || - || - || <code>zuncle/tomcat8-oracle-java8</code> || installs from source using Maven<br />
|-<br />
| <code>geocontainers/52n-wps</code> || [http://geocontainers.org/ Geocontainers] || https://github.com/geocontainers/dockerfiles/tree/master/52n-wps || ? || - || <code>tomcat:9</code> || -<br />
<br />
|-<br />
| 52°North SOS || - || - || - || - || - || - || only makes sense when using compose file, which includes PostGIS, work in progess at https://github.com/geocontainers/dockerfiles/issues/4<br />
|-<br />
| epsg.io || <code>klokantech/epsg.io</code> || [https://hub.docker.com/u/klokantech/ klokantech] || https://github.com/klokantech/epsg.io || - || file<code> LICENSE</code> || <code>klokantech/gdal:1.11</code> || Run with<code> -p 8080:8080</code> to open at <http://localhost:8080/> Run a clone in you local network<br />
<br />
|-<br />
| osm2vectortiles || multiple || [http://osm2vectortiles.org/ osm2vectortiles] || https://hub.docker.com/r/osm2vectortiles/ || - || - || multiple || see also tileserver-mapnik by klokantech<br />
<br />
|}</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&diff=68003WMS Tile Caching2012-12-24T20:14:00Z<p>Wiki-Brian H Wilson: </p>
<hr />
<div>This is an old page (2006/2007), check the History tab.<br />
<br />
WMS-C has been superceded by the OSGEO [[Tile Map Service Specification]] (TMS) and the OGC [http://www.opengeospatial.org/standards/wmts Web Map Tile Service Standard] (WMTS).<br />
<br />
WMS-C is supported still but if you are writing new applications you should look at TMS and WMTS.<br />
<br />
== Goal ==<br />
<br />
The goal of a '''WMS Tile Caching''' proposal, perhaps ''WMS-C'' for short, is to find a way to optimize the delivery of map imagery across the Internet. The proposal needs to offer ideally some means by which map clients can fetch tiles from existing servers, in such a way that the images can be cached on the server, or at an intermediate location, or even be completely pre-generated, if desired. Further, the proposal needs to offer a way of advertising that a cached tile set is available for a given layer from a particular WMS or WMS proxy. The proposal should leverage the existing investment in OGC-compliant WMS servers on the 'Net.<br />
<br />
The two main questions to be addressed are:<br />
# How does a server advertise its cacheable image tiles?<br />
# How does a client request possibly cached image tiles?<br />
<br />
== Proposal ==<br />
<br />
=== WMS-C as WMS Profile ===<br />
<br />
One approach to take might be to define ''WMS-C'' (as in ''Web Mapping Service - Cached'') as a constrained profile of [http://www.opengeospatial.org/docs/01-068r2.pdf OGC WMS] that permits servers to optimize their image generation, and allows tiles to be cached at intermediate points. A WMS-C service would likely only deliver images for bounding boxes aligned to a given rectangular origin and grid, and only at particular scale levels.<br />
<br />
The basic idea is that, unlike with WMS, two different requests for a given WMS-C tile should form the exact same HTTP GET request. This invites several constraints on WMS ''GetMap'' requests:<br />
<br />
# Minimal query string arguments (i.e. no optional arguments permitted, versus &sect;7.2)<br />
# Fixed query string argument ordering and case (versus &sect;6.4.1; q.v. also &sect;7.2.2, Table 8)<br />
# Fixed range of possible bounding boxes, computed from the WMS-C profile parameters<br />
# Fixed precision on bounding box values (clarifying &sect;6.5.6)<br />
# Fixed tile size in pixels<br />
# Fixed layer name and/or layer name ordering<br />
# Fixed styling<br />
# Fixed output format<br />
<br />
Some means of identifying these constraints programmatically on a per-server basis, a la ''GetCapabilities'' might be desirable. From the table below, it appears that minimum/maximum scale (and scale quantization factor, which should probably never be other than 2) are the only suggested tiling regime parameters that would be difficult to directly express in a WMS GetCapabilities document. Is there some existing way to add custom parameters to a GetCapabilities declaration?<br />
<br />
Note that the ''LAYERS'', ''STYLES'', ''SRS'', ''HEIGHT'', ''WIDTH'', and ''FORMAT'' arguments to a ''GetMap'' request would become fixed for a particular WMS-C tiled layer, but the WMS specification would still require the inclusion of these arguments in every WMS-C request (&sect; 7.2).<br />
<br />
A WMS-C proxy or server should be free to return an exception or a redirect, if it receives a WMS request that is not WMS-C compliant, or involves a bounding box that does not correspond to a single tile in the cache.<br />
<br />
=== Calculating Valid Tile Extents for a Given Request ===<br />
<br />
WMS tile caching implies fixed scale or zoom levels. Typically, each valid scale level would be half that of the next larger scale. It would be worth writing reference code to help developers figure out which tiles they need to load to cover a given bounding box at a given scale.<br />
<br />
=== Possible Tile Scheme Parameters ===<br />
<br />
{| cellpadding="5" cellspacing="1" border="1"<br />
| '''Parameter''' || '''Default value''' || '''Specifiable in WMS GetCapabilities?'''<br />
|-<br />
| "This service suppports tiling." || ''none'' || ''&lt;KeywordList&gt;'' contains the string 'tiled', perhaps? (&sect;7.1.4.5.3)<br />
|-<br />
| Projection || EPSG:4326 || ''&lt;SRS&gt;'' <br />
|-<br />
| Maximal extent || (-180,-90,180,90) || ''&lt;BoundingBox&gt;'' (&sect;7.1.4.5.7)<br />
|-<br />
| Number of horizontal and vertical tiles at the maximal extent || ''none'' || Could be implied by ''&lt;ScaleHint&gt;'' (&sect;7.1.4.5.8, but note that the format is weakly specified)... Alternately, could use ''&lt;DataURL&gt;'' (&sect;7.1.4.5.14)<br />
|-<br />
| Tile size in pixels || some power of 2 || &lt;Layer&gt; attribute ''fixedWidth'', ''fixedHeight'' (&sect;7.1.4.6)<br />
|-<br />
| Minimum scale || ''none'' || ''&lt;ScaleHint&gt;'' or ''&lt;DataURL&gt;'' (see note, above)<br />
|-<br />
| Scale quantization factor || 2 || ''&lt;DataURL&gt;''<br />
|}<br />
<br />
----<br />
<br />
== Other Considerations ==<br />
<br />
* Would non-rectangular tessellations yield more efficient results? If so, which tessellations to consider? Also, are the processing and bandwidth advantages of a non-rectangular tessellation outweighed by the potential implementation complexity?<br />
* Norm Vine rightly points out that a tile request basically boils (or should boil down to) Layer + Zoom Level + Row + Column. Can we define an even simpler method for requesting tiles from servers in the know? How are those capabilities advertised, if not shoehorned into WMS? Note that WorldWind basically already has a mechanism for this. Their tiling requests basically look like:<br />
<br />
http://domain.tld/service?L=0&X=1&Y=2<br />
* Like all caching schemes, WMS-C caches would need to be cognizant of expiration. Easy with using the proper HTTP headers. There is a wide range of freshness/staleness, with OpenStreetMap being highly volatile, and Landsat being pretty stable (until the ice caps melt ;).<br />
* Several people (particularly Paul Spencer and Chris Schmidt) have argued that a separate ''GetTile'' request should be used. This topic probably warrants discussion.<br />
<br />
== Distributed Caching ==<br />
<br />
* A WMS-C standard would permit tile caching through [http://www.coralcdn.org/ Coral]. However, the World Wind community's experience has been that using Coral to serve tiles results in frustratingly high latency.<br />
* Alternately, one could do (distributed) [[Distributed Tile Caching|peer-to-peer tile caching]] optimized specifically for geographic space, which might still suffer the latency issues associated with P2P networks.<br />
<br />
== Existing Tiling Schemes ==<br />
<br />
* Mikel Maron's description of [http://lists.eogeo.org/pipermail/tiling/2006-March/000017.html OnEarth's LandSat tiling scheme]<br />
* World Wind's LandSat tiling scheme: [http://www.ceteranet.com/nww-tile-struct.pdf PDF], [http://www.worldwindcentral.com/wiki/Making_Layers wiki]<br />
* World Wind ''QuadTileSet'' [http://rafb.net/paste/results/S3I8Zr92.html sample description], [http://forum.worldwind.arc.nasa.gov/lofiversion/index.php?t2965.html forum discussion], [http://rafb.net/paste/results/z2dQKa54.html sample PHP code] to fetch WW tiles for a given WMS GetMap request<br />
* osgPlanet's C++ code for [http://www.remotesensing.org/cgi-bin/cvsweb.cgi/osgPlanet/src/osgPlanet/osgPlanetGridUtility.cpp?rev=HEAD;content-type=text%2Fx-cvsweb-markup tiling the Earth]<br />
* WorldWind Example code for tiling the Earth (needs Proj.4 and GDAL libraries)[http://download.worldwindcentral.com/dstile-0.2.tar.gz DSTile and Tilepack]<br />
* OnEarth's code for intercepting WW requests and converting into WMS requests and caching them [http://www.twobeds.com/upload/userfiles/adamhill/lucians%20code%20-%20cache_1_1.gz?PHPSESSID=f485cf3fd66cd30ad7a4f814a127d2cb from Lucian Plesa]<br />
* Casey Chestnut explains Microsoft Virtual Earth's tiling scheme + code to experiment with the URL's [http://www.brains-n-brawn.com/veWorldWind/]<br />
* GeoOdyssey's [http://www.geodyssey.com/tileshare/index.html TileShare scheme]<br />
* Chuck Stein's [http://www.geongrid.org/workshops/geonvis2005/Presentations/ChuckStein/GeoFusion.ppt GeoFusion presentation] from GEON (warning: PowerPoint)<br />
* [http://globe.sintef.no/documentation/projection.html The Finite Nearly-Conformal Normal Cylindrical Projection] (Aasgaard's map projection)<br />
<br />
Note: WW and OnEarth's schemes are pretty much identical, the WW client just allows you to specify arbitrary tile sizes, coverages and number of levels to accomodate a given client.<br />
<br />
== Related Projects ==<br />
<br />
* [http://www.ossim.org/osgPlanet.html osgPlanet]<br />
* [http://worldwind.arc.nasa.gov/ NASA WorldWind] ([http://www.worldwindcentral.com/wiki/Main_page wiki])<br />
* [http://worldkit.org/ worldKit]<br />
* [http://communitymapbuilder.org/ Community MapBuilder]<br />
* [http://ka-map.maptools.org/ ka-Map!]<br />
* [http://openlayers.org/ OpenLayers]<br />
* [http://www.geomoose.org/moose/ GeoMoose]<br />
* other AJAX map clients, presumably<br />
<br />
== Interested Parties ==<br />
<br />
There is a mailing list on tiling, [http://lists.osgeo.org/mailman/listinfo/tiling OSGEO Tiling]<br />
but it looks pretty moribund (no activity since 2011)<br />
<br />
* [[User:SchuylerErle|Schuyler Erle]]<br />
* [[User"Adoyle"|Allan Doyle]]<br />
* [[user"Nhv"|Norman Vine]]<br />
* [[user"Joshli"|Josh Lieberman]]<br />
* [[user"Adamhill"|Adam Hill]]<br />
* [[user"bitner"|David Bitner]]<br />
* [[user:Mikel|Mikel Maron]]<br />
* [[user:mpg|Michael P. Gerlek]]<br />
* [[user:stvn|Steven M. Ottens]]<br />
* [[user:Pagameba|Paul Spencer]]<br />
* [[user:hallkbrdz|Bryan Hall]]<br />
* [[user:tschaub|Tim Schaub]]<br />
* [[user:dmorissette|Daniel Morissette]]<br />
* [[user:dpatton|Dave Patton]]<br />
* [[user:cholmes|Chris Holmes]]<br />
* [[user:pwramsey3|Paul Ramsey]]<br />
* [[user:luisw|Luis W. Sevilla]]<br />
* [[user:ominiverdi|Lorenzo Becchi]]<br />
* [[user:wilfred|Wilfred Springer]]<br />
* [[user:fpurcell|Frank Purcell]]<br />
* [[user:Pauldendulk|Paul den Dulk]]<br />
* [[user:Schpidi|Stephan Meißl]]<br />
* [[user:Mornsunrain|Xi Chen]]<br />
* [[user:blammo|Bob Basques]]<br />
* [[user:Woodbri|Stephen Woodbridge]]<br />
* ''add yourself''<br />
<br />
[[Category:Standards]]<br />
[[Category:Tiling]]</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&diff=68002WMS Tile Caching2012-12-24T20:02:29Z<p>Wiki-Brian H Wilson: /* Interested Parties */</p>
<hr />
<div>== Goal ==<br />
<br />
The goal of a '''WMS Tile Caching''' proposal, perhaps ''WMS-C'' for short, is to find a way to optimize the delivery of map imagery across the Internet. The proposal needs to offer ideally some means by which map clients can fetch tiles from existing servers, in such a way that the images can be cached on the server, or at an intermediate location, or even be completely pre-generated, if desired. Further, the proposal needs to offer a way of advertising that a cached tile set is available for a given layer from a particular WMS or WMS proxy. The proposal should leverage the existing investment in OGC-compliant WMS servers on the 'Net.<br />
<br />
The two main questions to be addressed are:<br />
# How does a server advertise its cacheable image tiles?<br />
# How does a client request possibly cached image tiles?<br />
<br />
== Proposal ==<br />
<br />
=== WMS-C as WMS Profile ===<br />
<br />
One approach to take might be to define ''WMS-C'' (as in ''Web Mapping Service - Cached'') as a constrained profile of [http://www.opengeospatial.org/docs/01-068r2.pdf OGC WMS] that permits servers to optimize their image generation, and allows tiles to be cached at intermediate points. A WMS-C service would likely only deliver images for bounding boxes aligned to a given rectangular origin and grid, and only at particular scale levels.<br />
<br />
The basic idea is that, unlike with WMS, two different requests for a given WMS-C tile should form the exact same HTTP GET request. This invites several constraints on WMS ''GetMap'' requests:<br />
<br />
# Minimal query string arguments (i.e. no optional arguments permitted, versus &sect;7.2)<br />
# Fixed query string argument ordering and case (versus &sect;6.4.1; q.v. also &sect;7.2.2, Table 8)<br />
# Fixed range of possible bounding boxes, computed from the WMS-C profile parameters<br />
# Fixed precision on bounding box values (clarifying &sect;6.5.6)<br />
# Fixed tile size in pixels<br />
# Fixed layer name and/or layer name ordering<br />
# Fixed styling<br />
# Fixed output format<br />
<br />
Some means of identifying these constraints programmatically on a per-server basis, a la ''GetCapabilities'' might be desirable. From the table below, it appears that minimum/maximum scale (and scale quantization factor, which should probably never be other than 2) are the only suggested tiling regime parameters that would be difficult to directly express in a WMS GetCapabilities document. Is there some existing way to add custom parameters to a GetCapabilities declaration?<br />
<br />
Note that the ''LAYERS'', ''STYLES'', ''SRS'', ''HEIGHT'', ''WIDTH'', and ''FORMAT'' arguments to a ''GetMap'' request would become fixed for a particular WMS-C tiled layer, but the WMS specification would still require the inclusion of these arguments in every WMS-C request (&sect; 7.2).<br />
<br />
A WMS-C proxy or server should be free to return an exception or a redirect, if it receives a WMS request that is not WMS-C compliant, or involves a bounding box that does not correspond to a single tile in the cache.<br />
<br />
=== Calculating Valid Tile Extents for a Given Request ===<br />
<br />
WMS tile caching implies fixed scale or zoom levels. Typically, each valid scale level would be half that of the next larger scale. It would be worth writing reference code to help developers figure out which tiles they need to load to cover a given bounding box at a given scale.<br />
<br />
=== Possible Tile Scheme Parameters ===<br />
<br />
{| cellpadding="5" cellspacing="1" border="1"<br />
| '''Parameter''' || '''Default value''' || '''Specifiable in WMS GetCapabilities?'''<br />
|-<br />
| "This service suppports tiling." || ''none'' || ''&lt;KeywordList&gt;'' contains the string 'tiled', perhaps? (&sect;7.1.4.5.3)<br />
|-<br />
| Projection || EPSG:4326 || ''&lt;SRS&gt;'' <br />
|-<br />
| Maximal extent || (-180,-90,180,90) || ''&lt;BoundingBox&gt;'' (&sect;7.1.4.5.7)<br />
|-<br />
| Number of horizontal and vertical tiles at the maximal extent || ''none'' || Could be implied by ''&lt;ScaleHint&gt;'' (&sect;7.1.4.5.8, but note that the format is weakly specified)... Alternately, could use ''&lt;DataURL&gt;'' (&sect;7.1.4.5.14)<br />
|-<br />
| Tile size in pixels || some power of 2 || &lt;Layer&gt; attribute ''fixedWidth'', ''fixedHeight'' (&sect;7.1.4.6)<br />
|-<br />
| Minimum scale || ''none'' || ''&lt;ScaleHint&gt;'' or ''&lt;DataURL&gt;'' (see note, above)<br />
|-<br />
| Scale quantization factor || 2 || ''&lt;DataURL&gt;''<br />
|}<br />
<br />
----<br />
<br />
== Other Considerations ==<br />
<br />
* Would non-rectangular tessellations yield more efficient results? If so, which tessellations to consider? Also, are the processing and bandwidth advantages of a non-rectangular tessellation outweighed by the potential implementation complexity?<br />
* Norm Vine rightly points out that a tile request basically boils (or should boil down to) Layer + Zoom Level + Row + Column. Can we define an even simpler method for requesting tiles from servers in the know? How are those capabilities advertised, if not shoehorned into WMS? Note that WorldWind basically already has a mechanism for this. Their tiling requests basically look like:<br />
<br />
http://domain.tld/service?L=0&X=1&Y=2<br />
* Like all caching schemes, WMS-C caches would need to be cognizant of expiration. Easy with using the proper HTTP headers. There is a wide range of freshness/staleness, with OpenStreetMap being highly volatile, and Landsat being pretty stable (until the ice caps melt ;).<br />
* Several people (particularly Paul Spencer and Chris Schmidt) have argued that a separate ''GetTile'' request should be used. This topic probably warrants discussion.<br />
<br />
== Distributed Caching ==<br />
<br />
* A WMS-C standard would permit tile caching through [http://www.coralcdn.org/ Coral]. However, the World Wind community's experience has been that using Coral to serve tiles results in frustratingly high latency.<br />
* Alternately, one could do (distributed) [[Distributed Tile Caching|peer-to-peer tile caching]] optimized specifically for geographic space, which might still suffer the latency issues associated with P2P networks.<br />
<br />
== Existing Tiling Schemes ==<br />
<br />
* Mikel Maron's description of [http://lists.eogeo.org/pipermail/tiling/2006-March/000017.html OnEarth's LandSat tiling scheme]<br />
* World Wind's LandSat tiling scheme: [http://www.ceteranet.com/nww-tile-struct.pdf PDF], [http://www.worldwindcentral.com/wiki/Making_Layers wiki]<br />
* World Wind ''QuadTileSet'' [http://rafb.net/paste/results/S3I8Zr92.html sample description], [http://forum.worldwind.arc.nasa.gov/lofiversion/index.php?t2965.html forum discussion], [http://rafb.net/paste/results/z2dQKa54.html sample PHP code] to fetch WW tiles for a given WMS GetMap request<br />
* osgPlanet's C++ code for [http://www.remotesensing.org/cgi-bin/cvsweb.cgi/osgPlanet/src/osgPlanet/osgPlanetGridUtility.cpp?rev=HEAD;content-type=text%2Fx-cvsweb-markup tiling the Earth]<br />
* WorldWind Example code for tiling the Earth (needs Proj.4 and GDAL libraries)[http://download.worldwindcentral.com/dstile-0.2.tar.gz DSTile and Tilepack]<br />
* OnEarth's code for intercepting WW requests and converting into WMS requests and caching them [http://www.twobeds.com/upload/userfiles/adamhill/lucians%20code%20-%20cache_1_1.gz?PHPSESSID=f485cf3fd66cd30ad7a4f814a127d2cb from Lucian Plesa]<br />
* Casey Chestnut explains Microsoft Virtual Earth's tiling scheme + code to experiment with the URL's [http://www.brains-n-brawn.com/veWorldWind/]<br />
* GeoOdyssey's [http://www.geodyssey.com/tileshare/index.html TileShare scheme]<br />
* Chuck Stein's [http://www.geongrid.org/workshops/geonvis2005/Presentations/ChuckStein/GeoFusion.ppt GeoFusion presentation] from GEON (warning: PowerPoint)<br />
* [http://globe.sintef.no/documentation/projection.html The Finite Nearly-Conformal Normal Cylindrical Projection] (Aasgaard's map projection)<br />
<br />
Note: WW and OnEarth's schemes are pretty much identical, the WW client just allows you to specify arbitrary tile sizes, coverages and number of levels to accomodate a given client.<br />
<br />
== Related Projects ==<br />
<br />
* [http://www.ossim.org/osgPlanet.html osgPlanet]<br />
* [http://worldwind.arc.nasa.gov/ NASA WorldWind] ([http://www.worldwindcentral.com/wiki/Main_page wiki])<br />
* [http://worldkit.org/ worldKit]<br />
* [http://communitymapbuilder.org/ Community MapBuilder]<br />
* [http://ka-map.maptools.org/ ka-Map!]<br />
* [http://openlayers.org/ OpenLayers]<br />
* [http://www.geomoose.org/moose/ GeoMoose]<br />
* other AJAX map clients, presumably<br />
<br />
== Interested Parties ==<br />
<br />
There is a mailing list on tiling, [http://lists.osgeo.org/mailman/listinfo/tiling OSGEO Tiling]<br />
but it looks pretty moribund (no activity since 2011)<br />
<br />
* [[User:SchuylerErle|Schuyler Erle]]<br />
* [[User"Adoyle"|Allan Doyle]]<br />
* [[user"Nhv"|Norman Vine]]<br />
* [[user"Joshli"|Josh Lieberman]]<br />
* [[user"Adamhill"|Adam Hill]]<br />
* [[user"bitner"|David Bitner]]<br />
* [[user:Mikel|Mikel Maron]]<br />
* [[user:mpg|Michael P. Gerlek]]<br />
* [[user:stvn|Steven M. Ottens]]<br />
* [[user:Pagameba|Paul Spencer]]<br />
* [[user:hallkbrdz|Bryan Hall]]<br />
* [[user:tschaub|Tim Schaub]]<br />
* [[user:dmorissette|Daniel Morissette]]<br />
* [[user:dpatton|Dave Patton]]<br />
* [[user:cholmes|Chris Holmes]]<br />
* [[user:pwramsey3|Paul Ramsey]]<br />
* [[user:luisw|Luis W. Sevilla]]<br />
* [[user:ominiverdi|Lorenzo Becchi]]<br />
* [[user:wilfred|Wilfred Springer]]<br />
* [[user:fpurcell|Frank Purcell]]<br />
* [[user:Pauldendulk|Paul den Dulk]]<br />
* [[user:Schpidi|Stephan Meißl]]<br />
* [[user:Mornsunrain|Xi Chen]]<br />
* [[user:blammo|Bob Basques]]<br />
* [[user:Woodbri|Stephen Woodbridge]]<br />
* ''add yourself''<br />
<br />
[[Category:Standards]]<br />
[[Category:Tiling]]</div>Wiki-Brian H Wilsonhttps://wiki.osgeo.org/w/index.php?title=User:Brian_H_Wilson&diff=68001User:Brian H Wilson2012-12-24T19:56:09Z<p>Wiki-Brian H Wilson: Created page with "I keep most of my stuff on http://wildsong.biz/ including my [http://wildsong.biz/index.php/User:Brian_Wilson User] page."</p>
<hr />
<div>I keep most of my stuff on http://wildsong.biz/ including my [http://wildsong.biz/index.php/User:Brian_Wilson User] page.</div>Wiki-Brian H Wilson