Skip to main content
Question

Raster mosaicking performance tips on FME Server

  • April 5, 2018
  • 3 replies
  • 25 views
nic_ran
Contributor
Forum|alt.badge.img+16

I'm looking for any performance tips for mosaicking a large number of rasters.

I already know about parallel processing and don't need any further advice on that aspect (thanks!).

I'm wondering if anything can be gained from using a large number of FME Server Engines or FME Cloud instances and if there's a simple workflow for achieving this. My initial thought is to build my own version of parallel processing and split the mosaicking into several workspaces for submission by the FMEServerJobSubmitter. Anyone got any other ideas?

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

nic_ran
Contributor
Forum|alt.badge.img+16
  • nic_ranContributor
  • Author
  • Contributor
  • April 5, 2018
PS. I'd be particularly interested in hearing from @donatsafe if there's some way of using Docker Swarms or Kubernetes to help with this. :)

 

jdh
Contributor
Forum|alt.badge.img+40
  • jdhContributor
  • Contributor
  • April 5, 2018

I have in the past when dealing with mosaicking very large amounts of files, created a child workspace the would mosaic a subset of the data (say 512 files) in either a strip or tile (depending on how the input data was structured), and a parent workspace that would call the child workspace for each subset, and then read in the resultant files and mosaic them.

nic_ran
Contributor
Forum|alt.badge.img+16
  • nic_ranContributor
  • Author
  • Contributor
  • April 6, 2018

I have in the past when dealing with mosaicking very large amounts of files, created a child workspace the would mosaic a subset of the data (say 512 files) in either a strip or tile (depending on how the input data was structured), and a parent workspace that would call the child workspace for each subset, and then read in the resultant files and mosaic them.

Thanks @jdh. Given the 512 open file limit, this might be the way to go. The child workspaces would each be sent to different Engines, which would help with performance.

 

Community Stats

32,180
Posts
122,172
Replies
39,855
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.