Limit Map: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
|seealso= | |seealso= | ||
* [[Skip_no_data_(Grid_Overlay)|SKIP_NO_DATA]] | * [[Skip_no_data_(Grid_Overlay)|SKIP_NO_DATA]] | ||
* [[Calculation panel]] | |||
|howtos= | |howtos= | ||
* [[How to calculate only a part of the Project map]] | * [[How to calculate only a part of the Project map]] | ||
* [[How to combine multiple calculations into a single result]] | * [[How to combine multiple calculations into a single result]] | ||
}} | }} | ||
Revision as of 09:26, 17 October 2025
This article is a stub. The following information should be added:
- Affects all grid overlays
- what about X queries of TQL for items outside limit map
- Document SKIP_NO_DATA on separate appropriate page.
- how to page for splitting up calculation
Limit Map is a Setting that stores the Multi Polygon that will be used to limit the calculation of active Grid Overlays.
When this setting is configured with a non-empty Multi Polygon, the grid and TQL Queries are limited to a portion of the map. Limit map is always a rectangle bounding box of the Multi Polygon of the setting.
To adjust this setting using the Tygron Client, see How to calculate only a part of the Project map.
Notes
- Only active Grid Overlays are affected by this setting
- When updating Grid Overlays only the box is updated and the rest contains NO_DATA values.
- Adding SKIP_NO_DATA=1 as an attribute to any Grid Overlay, keeps the orginal values in place. Note: This method allows for calculation larger then the GPU grid would allow by splitting the map up in Limit map boxes.
How-to's
- How to calculate only a part of the Project map
- How to combine multiple calculations into a single result