Home page: http://geoserver.org/ where they say "GeoServer is a Java-based software server that allows users to view and edit geospatial data. Using open standards set forth by the Open Geospatial Consortium (OGC), GeoServer allows for great flexibility in map creation and data sharing."
The crucial feature for me is that it allows edits via #WFS-T. That means I can hook up OpenLayers web clients to a database and allow them to create and edit data.
- 2019 Mar -- Migrated to Docker Compose.
- 2016 Sep -- updated Dart with 2.9.1 (latest stable release)
- 2012 Sep -- 2.2 installed on Kilchis and Dart.
- 2011 Oct -- I am working with 2.1.2 now on HuPI
- 2009 Feb 06 -- I decided to take a crack at installing GeoServer 1.7.2 today.
Example GeoServer site (not mine!)
This is from the Portland Trimet site... GeoServer, OpenLayers, TileCache, PostgreSQL, PostGIS, GDAL, Extjs, Freemarker, Solr, Antlr, Balance Ant, Http Client, Tomcat, Apache, and CentOS are the underlying technologies used on this application. We're indebted to the contributors of these (and many other: eclipse, firefox and firebug to name a few) open source projects for sharing their efforts and expertise.
Some GeoServer Capabilities
- WCS = Web Coverage Service = queryable feature data (OGC)
- WFS = Web Feature Service = vector data (OGC)
- WMS = Web Map Service = delivers rasters (not tiles) (OGC)
- TMS = Tile map service = delivers raster tiles (OSGEO)
- WMS-C = Web Map Service - Cached = WMS with tile caching (OSGEO draft)
- WMTS = Web Map Tile service (OGC)
I think WCS can return features that are related from several feature classes whereas WFS returns features from one class only??
Map vs feature services
What if you want features to overlay a map but want symbology defined by the server? You define styles and then pick the correct encoding.
With WFS there are several GML flavours, GeoJSON, shapefiles and CSV. None of these work for me because they only encode the geography and not the visual properties. I probably want to use a WMS encoded with KML.
Lew's approach is to convert the KML into a custom JSON format on the server for transfer. There must be a better way than that. But it has to be compatible with the Google Maps Android API too.
The official way to put markers and shapes onto a Google map is via their API. I don't want to go the route of putting shapes onto the screen ignoring the API because I hate having to do all the projection and transformation stuff on my own.
Being able to directly read GPX files would be a good thing.
If you are implementing a tile-based client you should probably use TMS or maybe WMTS. WMS-C was a OSGEO draft. WMTS is more complex so use TMS unless you really need WMTS features.
On the server side for performance and the best cartography you'd probably be better off pre-rendering and caching all the tiles. What's the best way to do that? Tilemill or gdal2tiles ? What's the best way to serve the prerendered tiles? TileCache? Or just use a web server (Apache)?
TMS reference implementation: see http://TileCache.org/
Geoserver in Docker
The docker-compose set up includes geoserver, geowebcache, postgis, and pgadmin4. See the full project on github, https://github.com/Wildsong/docker-geoserver
I had a reverse proxy built into the compose setup but realized I needed a proxy for the other services running on Bellman so now I have a generic proxy running in its own container. Because GeoServer is tucked behind a proxy, it is accessible "everywhere" (currently it's behind my Firewall settings but that's a different story).
I keep more PostGIS notes here: PostGIS.
See https://hub.docker.com/r/mdillon/postgis I will probably stop using this container, because I want the bleeding edge in my development server. (I live for pain) I can probably even go to PostGIS 3.0 now!!
From Postgis.org today: Although this release will work for PostgreSQL 9.4 and above, to take full advantage of what PostGIS 2.5 offers, you should be running PostgreSQL 11beta4+ and GEOS 3.7.0 which were released recently. Best served with PostgreSQL 11 beta4 and pgRouting 2.6.1.
In my current Docker, I can see using "docker inspect geoserver-db" that PostgreSQL is at 11.2 and from psql I can see GEOS is at 3.7.
postgres=# SELECT postgis_full_version(); POSTGIS="2.5.1 r17027" [EXTENSION] PGSQL="110" GEOS="3.5.1-CAPI-1.9.1 r4246" PROJ="Rel. 4.9.3, 15 August 2016" GDAL="GDAL 2.1.2, released 2016/10/24" LIBXML="2.9.4" LIBJSON="0.12.1" LIBPROTOBUF="1.2.1" RASTER (1 row)
See also its parent https://hub.docker.com/_/postgres/
You can run the database independent of the compose configuration to test it. These commands put the data and config files outside of the container, but still in a docker volume.
docker pull mdillon/postgis:11 docker volume create postgis_files docker run -d --name postgis -v postgis_files:/var/lib/postgresql/data \ -e PGDATA=/var/lib/postgresql/data -e POSTGRES_PASSWORD=secret mdillon/postgis:11
Run psql to talk to the database; I generally have psql installed on the host and run it directly but you might not want to do that.
docker exec -it postgis /usr/bin/psql -U postgres
Docker makes setting up PostGIS shockingly easy. You'll want pgadmin to maintain it.
ArcGIS and PostGIS
After completing the PostGIS setup, I can now add PostGIS layers directly into ArcMap for read-only access. I do this by creating a "Database Connection" in ArcCatalog; then I can see the layers in PostGIS and just drag them straight into ArcMap. I cannot EDIT them though, ArcMap does not support that directly. It might if you use the Data Interop extension but I don't have that.
If you have an ArcGIS Server license you can enable access to PostGIS in the PostgreSQL server. I can't afford the license fees.
I use this container: https://hub.docker.com/r/dpage/pgadmin4
Goal: Set up an example to allow storing dots from ol-react to a PostGIS instance and to an ArcGIS Enterprise instance. I don't care if they are WFS-T services or not as long as my web map works correctly. For PostGIS it looks easiest to use GeoServer and WFS-T. That's what set me on this whole docker-compose path; I can now set up the server infrastructure in 10 minutes.
- Create an empty "web_markers" point layer in temp memory in QGIS, then use the QGIS database tool to export it to PostGIS.
- Remove the PostGIS based layer from QGIS.
- Create a Workspace. Enable WFS on the workspace.
- Create a Store. Connect it to PostGIS using the gis_owner role and password, so that it has full read/write access on PostGIS.
- Make sure WFS is enabled and Service Level is set to Transactional or Complete, (Services->WFS)
- Publish sure web_markers in Layers.
- Created a role "PUBLIC_ACCESS" and give it READ and WRITE access to the web_markers layer.
- Create a "markers" user with password and assign the PUBLIC_ACCESS role to it.
- In a browser,
- test with this URL: https://maps.wildsong.biz/geoserver/wfs?service=wfs&version=1.2.0&request=GetCapabilities which gives results for every layer
- and https://maps.wildsong.biz/geoserver/wfs?service=wfs&request=DescribeFeatureType&version=1.1.0&typeName=clatsop-wfs:web_markers with results only for that layer
In the GetCapabilities request there should be an operation name = "Transaction" section when transactions are enabled.
- I did "Layer->Add Layer->Add WFS Layer"
- For "connection details" I used the URL https://maps.wildsong.biz/geoserver/wfs and left the authentication section alone.
- then I just selected the web_markers layer and clicked "Add" and "Closed".
The parts of OpenLayers 3 that we need to support feature editing through WFS-T are:
ol.interaction.Draw ol.interaction.Modify ol.format.WFS
References that I found last night:
An article on Medium https://medium.com/@goldrydigital/wfs-t-with-openlayers-3-16-6fb6a820ac58
Discussion re an example https://github.com/openlayers/openlayers/issues/8854
Serving MVT Vector Tiles
MVT = Mapbox Vector Tiles
You need to add a plugin to GeoServer for this to work. I had to create a new set up for GeoServer so that I could add plugins to the Docker image.
Once it's installed you can go look under Tile Layers at layers you have published and pull up the "Tile Caching" tab. Then you should see Tile Image Formats as a list that now includes "application/vnd.mapbox-vector-tile", turn that one one (and any others you wish to use of course).
If you do a preview of the layer you can select the PBF entries to test it and to find the correct URL to use in OpenLayers (or whereever...).
My (currently firewalled) test of Clatsop county is here: https://geoserver.wildsong.biz/geoserver/gwc/demo/clatsop_wm:taxlots?gridSet=EPSG:900913&format=application/vnd.mapbox-vector-tile
Internally it looks like it's using this: https://geoserver.wildsong.biz/geoserver/gwc/service/wmts?REQUEST=GetTile&SERVICE=WMTS&VERSION=1.0.0&LAYER=clatsop_wm:taxlots&STYLE=&TILEMATRIX=EPSG:900913:10&TILEMATRIXSET=EPSG:900913&FORMAT=application/vnd.mapbox-vector-tile&TILECOL=161&TILEROW=366
What's WMTS? https://en.wikipedia.org/wiki/Web_Map_Tile_Service
Using Docker Compose
Using Compose is AWESOME, it allows me to group services together and hook them up. I have successfully started and stopped the whole thing several times now. It tears down (basically throws everything away) your containers when you say "docker-compose down" but since I have persisted the data in volumes, everything comes right back online with "docker-compose up"! Did I say "awesome" already?
Installing Docker Compose
Compose is not part of Docker engine, it's installed separately.
Side note, on Bellman I installed Docker engine using the Docker repository for the latest stable version. Currently I have 18.09.02.
To install Docker Compose on Debian, see https://docs.docker.com/compose/install/#install-compose for example,
curl -L https://github.com/docker/compose/releases/download/1.24.0-rc1/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose chmod +x /usr/local/bin/docker-compose docker-compose --version docker-compose version 1.24.0-rc1, build 0f3d4dda
My compose file includes all services to run GeoServer, including GeoServer itself, GeoWebCache, PostGIS/PostgreSQL, PGAdmin4, and nginx.
Refer to its github repo at https://github.com/Geo-CEG/geoserver-compose for more information.
git clone https://github.com/Geo-CEG/geoserver-compose.git geoserver cd geoserver # Read the README.md file. # Copy files into the right places. dotenv.sample -> .env # Edit .env
Fire it up
docker-compose up -d
I have mapped the standard postgres port to the same port on the host, based on the assumption there is no instance of PostgreSQL already running on the host. I can connect to PostgreSQL as if it were running locally with the psql command; like this: psql -U postgres -h localhost
From the psql prompt, I can check out how the postgis set up went with
select postgis_full_version(); POSTGIS="2.5.1 r17027" [EXTENSION] PGSQL="110" GEOS="3.5.1-CAPI-1.9.1 r4246" PROJ="Rel. 4.9.3, 15 August 2016" GDAL="GDAL 2.1.2, released 2016/10/24" LIBXML="2.9.4" LIBJSON="0.12.1" LIBPROTOBUF="1.2.1" TOPOLOGY RASTER (1 row)
This looks good. I can test the nginx home page and geoserver and geowebcache and pgadmin4 at this point and they all work, too.
You can also use "docker inspect" for example
docker inspect geoserver-db | grep VERSION "GOSU_VERSION=1.11", "PG_VERSION=11.2-1.pgdg90+1", "POSTGIS_VERSION=2.5.1+dfsg-1.pgdg90+1"
Dealing with passwords
I keep the initial passwords (for example, for Postgres user) in the .env file; again, see the README.md
Accessing GeoServer WFS from ArcGIS Pro
There is probably an expensive extension (Interop?) for ArcMap to use WFS but I don't have it. AGS appears to have support; I am trying it out.
As is traditional for Esri I had to loosen security settings on GeoServer. Now anyone can see the services. Write access is still restricted.
Setting up GeoServer on Linux
I used to have some instructions in this page to help me set up GeoServer directly in Linux but now that I know how to use Docker, I deleted them. If you really feel the need to do it the hard way, use View History up there in the tabs and check for the version older than Feb 19 2019.
Getting data into GeoServer
Adding raster files
Walkthrough: Creating tiles with GeoServer at Penn State.
I want to do this so I can test WPS geoprocessing, not because I think it's the best way to distribute raster data, okay?
- I downloaded some data from DOGAMI months ago, a portion of LiDAR for Astoria. So I have a georeferenced TIFF file.
- Copy the .tif and .tfw files up onto GeoServer, to the Docker volume; on my server /home/docker/volumes/geoserver_data/_data/clatsop/
- Data (in left bar) -> Stores -> Add new store
- Raster Data Sources -> GeoTIFF
- I chose the clatsop workspace
- I used "Browse" to create the URL: file:clatsop/irving.tif
- This takes me to a New Layer page showing the layer name "irving" and I click on "Publish".
I accepted the rest of the defaults that GeoServer filled in for me.
I did a preview of the layer and it came up blank. Then I found the new layer in "Tile Layers" under "Tile Caching" and told it to build tiles for zoom levels 4-19 and waited for it to complete (5 minutes or so). NOW... I still get a blank preview map! "Scale 1:NaN" is wrong. WRONG place!
To preview, Tile Caching -> Tile Layers -> select the layer -> Select a preview mode (PNG for example) then a previewer pops up.
Using GeoServer with PostGIS
Some notes on using WFS-T http://blogs.law.harvard.edu/jreyes/2007/08/03/geotools-wfs-t-update-request/
- workspaces aka namespaces
- stores aka datastores
These are about organizing the data accessible to GeoServer.
You store data in stores and a store has to be in a workspace. A PostGIS store connects to a database, and the tables therein become accessible as layers (once you publish them)
So for example, you can create a workspace for Oregon and then put all your state-level data into stores that are in the Oregon workspace.
Queries in GeoServer
You can add CQL filters to a REST URL to filter on attributes in a WFS service, you can use spatial operators too.
See the docs