0

We are facing the problem that we have multiple projects with multiple high-resolution orthophotos from drones (1 photo > 2GB). We are using Geoserver with the integrated GeoWebCache. As a storage container we are using the ImageMosaic with a temporal enabled config (time-series) storing the references to each ortho (granule) in a PostGre table. We enabled a TIME filter (dimension) for the GeoWebCache, so we can query different timestamps. Projects are created every now and then, so the amount of orthophotos increases over time.

The data is only consumed via the GWC (WMTS, TMS) on different clients.

The problem we are facing is that even though our VM has 32GB of RAM with 8 cores (Windows Azure VM), processing multiple photos in high resolution takes a lot of time.

So my idea was to create some kind of GeoWebCache Docker container which can get spawned multiple times depending on the amount of orthophotos to be processed.

Our whole infrastructure is on Azure so I would like to use Azure Container Instances for the Docker Container and a Storage Account (File Storage) as the shared Data Container which is mounted on our VM to GeoServer as a NetworkDrive and to the GWC in the Docker Container.

My questions now:

  • Does the whole concept make sense?
  • Has anyone already done something like that?
  • I have found some posts about starting multiple GeoServer Instances - would that be a better solution? (For me only multiple GWC make sense as I only need to create the caches)

1 Answer 1

2

It does not, the image processing is done by GeoServer, not by GeoWebCache, which merely takes the images and stores them on disk (well, it might take a larger image produced by WMS and slice it into tiles). There are multiple topologies to consider:

  • multiple GeoServer instances with integrated GWC
  • one stand-alone GeoWebCache with multiple Geoserver on the back
  • one or more public facing GeoServer and ad-hoc instances on the side created just to run a seed job, and destroyed once done.
3
  • So I would have one "main" GeoServer to which my clients speak to and every now and then I would spawn a GeoServer Docker Container (or mulitple) to process the orthophotos and kill the container after the caches are created? Jul 28, 2021 at 7:26
  • 1
    That is yet another option, but yes, it's one we use to pre-seed caches without hampering the public facing cluster ability to respond quickly. Jul 28, 2021 at 7:46
  • Thanks Andrea - multi Geoserver Docker instances it is. Will give this a try. Jul 28, 2021 at 8:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.