Limit Map: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
}} | }} | ||
Limit Map is a [[Setting]] that stores the Multi Polygon that will be used to limit the calculation of Grid | Limit Map is a [[Setting]] that stores the Multi Polygon that will be used to limit the calculation of [[Grid Overlay]]s. | ||
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. | |||
[[File:Limited_calculation_area.jpg|thumb|Calculation limited by a Areas, enveloped by a rectangular bounding box]] | [[File:Limited_calculation_area.jpg|thumb|Calculation limited by a Areas, enveloped by a rectangular bounding box]] | ||
Revision as of 09:21, 17 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
Limit Map is a Setting that stores the Multi Polygon that will be used to limit the calculation of 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.
- 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.