Limit Map: Difference between revisions

From Tygron Preview Support Wiki
Jump to navigation Jump to search
Maxim@tygron.com (talk | contribs)
Created page with "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=1 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."
 
Maxim@tygron.com (talk | contribs)
No edit summary
Line 2: Line 2:


* 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 SKIP_NO_DATA=1 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.

Revision as of 12:44, 2 September 2025

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=1 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.