I’m building a Workshop module that visualizes floor layouts using Map Templates with TIFF images and GeoShape polygon overlays. I’ve run into a couple of issues and was wondering if anyone has experienced something similar.
Issue 1: Map Template image alignment after reconfiguration
I recently noticed that my Map Template background had become clickable/selectable, which caused incorrect navigation behavior. After reconfiguring the Map Template to fix the selection issue, the TIFF image is now aligned to the left instead of being centered as it was before.
Has anyone encountered this? Is there a way to control the anchor point or alignment of a Map Template image?
Issue 2: GeoShape polygon layer not refreshing on data source change
My map widget displays GeoShape polygons on top of TIFF-based Map Templates. When switching between different layouts (which changes the underlying object set), the background Map Template image updates correctly, but the polygon overlay retains the previous data.
Some details:
This only occurs when the polygon count is relatively high (~40+ polygons per view, ~70+ total across all views)
These are two separate issues with different root causes and potential solutions.
Issue 1: TIFF Image Alignment After Reconfiguration
Current documentation does not expose an explicit anchor point or alignment setting for TIFF or raster background images within a Map Template widget. As a result, there is no documented option to directly control whether an image remains centered or becomes left-aligned after a widget reconfiguration.
A few areas are worth investigating:
If the TIFF is displayed as a georeferenced image layer
The image position is typically determined by the object’s geographic boundary definition (geoshape) rather than by any widget-level alignment configuration.
If the image appears shifted after reconfiguration:
Verify that the underlying boundary coordinates are still correct.
Confirm that the image bounds polygon has not been modified.
Check whether the map viewport has changed during the reconfiguration process.
If the TIFF is displayed as tiled imagery (GeoTIFF)
In this scenario, image placement is derived from the georeferencing information embedded in the GeoTIFF itself.
A widget reconfiguration would not normally alter the image position directly. However, if the viewport is reset as part of the reconfiguration, the imagery may appear misaligned even though the underlying coordinates remain unchanged.
A useful troubleshooting step is to enable or trigger viewport auto-zoom so the map recenters on the relevant objects after the configuration change.
General workaround
Force a complete widget reload rather than relying on incremental updates. In some cases, a full reload restores the expected rendering state and resolves apparent alignment issues.
When to escalate
If the image bounds are correct, the georeferencing metadata is valid, and a full reload does not resolve the issue, the behavior may indicate a rendering defect introduced by the reconfiguration process. In that case, collect before-and-after screenshots, configuration details, and reproduction steps before opening a support request.
Issue 2: GeoShape Polygon Layer Not Refreshing After a Data Source Change
This issue is typically related to how the map widget refreshes its data when the underlying object set changes.
Root cause
When switching between layouts or changing the data source, the widget generally attempts to update incrementally rather than performing a full reload.
For larger polygon datasets, especially those containing numerous GeoShape objects, incremental updates may not always refresh correctly. Smaller datasets often appear to work because the update completes before rendering limits are reached.
Large GeoShape geometries can also have a noticeable impact on loading and rendering performance.
Recommended solution: Use a Refresh Key
Many map widget configurations support a Refresh Key mechanism.
When the value of the refresh key changes, the widget performs a complete reload rather than an incremental update.
A common implementation pattern is:
Create a variable to act as the refresh key.
Bind the map widget’s Refresh Key setting to that variable.
Whenever the layout or object set changes, update the refresh key value as part of the same event.
Examples include:
Incrementing a numeric counter.
Setting the refresh key to the selected layout identifier.
Updating the key with a timestamp or unique value.
This forces the widget to reload all layers and retrieve data from the newly selected object set.
Additional optimization: Tile-Based Loading
For datasets containing dozens or hundreds of polygons, consider using Tile loading instead of loading all geometry at once.
Benefits include:
Loading only geometry visible within the current viewport.
Reducing memory and rendering overhead.
Improving responsiveness for larger datasets.
Better scalability as object counts increase.
To use tile-based loading:
Open the map layer configuration.
Navigate to the Geometry settings.
Change the Loading Method to Tile.
Ensure any required searchability or indexing settings are enabled for the geospatial property being used.
Recommended combination
For larger GeoShape datasets, the most effective approach is typically:
Use a Refresh Key to force a complete reload when layouts or object sets change.
Use Tile Loading to improve performance and reduce the likelihood of stale or partially refreshed overlays.
Together, these settings address both refresh consistency and rendering performance and are generally the first steps to try when polygon layers fail to update correctly after a data source switch.
Hi @shuvdeeo, thanks for the quick and insightful response — both issues are now resolved!
Issue 1: It turned out that the position at the time of saving the Map Template was the key. After adjusting the image position and re-saving the Map Template, it now displays centered correctly in Workshop as well.
Issue 2: Interestingly, a Refresh Key was already configured on the map widget. Removing it actually resolved the issue — the polygon layers now refresh correctly when switching between layouts. Your response helped me look at the configuration from a different angle and led me to this fix.
Some additional findings that might be useful: the polygon count didn’t seem to be the root cause. The issue only occurred on the second visit to a layout — the first transition always displayed correctly. On the second visit, the correct polygons would briefly flash before being replaced by the previous layout’s polygons. This suggests that the Refresh Key was interacting with some kind of caching mechanism, causing stale data to overwrite the newly loaded polygons.
Also, sorry for combining two issues in a single post — I’ll make sure to separate them next time for better clarity.
Really appreciate the detailed guidance and the quick turnaround. Thanks so much!
