Limit Map: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
* When updating Grid Overlays only the box is updated and the rest contains NO_DATA values. | * When updating Grid Overlays only the box is updated and the rest contains NO_DATA values. | ||
* Adding <code>SKIP_NO_DATA=1</code> as an attribute to the 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. | * Adding <code>SKIP_NO_DATA=1</code> as an attribute to the 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. | ||
{{article end | |||
|howtos= | |||
* [[How to calculate only a part of the Project map]] | |||
* [[How to combine multiple calculations into a single result]] | |||
}} | |||
Revision as of 12:21, 3 October 2025
This article is a stub. The following information should be added:
- where is this setting in the UI.
- what kind of Item is it
- what happens when set based on a different Item (are changes reflected or not)
- 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
When this setting is active the grid and TQL Queries are limited to a portion of the map. Limit map is always a rectangle bounding box shape.
- When updating Grid Overlays only the box is updated and the rest contains NO_DATA values.
- Adding
SKIP_NO_DATA=1as an attribute to the 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.